OASIS Virtual I/O Device (VIRTIO) TC

Hello! We are now all set to vote on issues from github. The github process is much more lightweight than jira. Further, anyone with a github account can create issues. The only requirement for starting the voting is that the issue body (1st comment) includes a link to the list archives which should include the proposal for fixing the issue. Issue milestone should also be set correctly, but that's a minor issue I can handle for people who don't have the permission. The process is thus: 1. send email to mailing list 2. open github issue 3. include link to email in OASIS archives with the proposal 4. if you post newer proposals, edit comment to update the proposal link 5. once ready (give people time to comment), make me or one of the other editors know to start voting -- MST

On Thu, 1 Mar 2018 18:24:43 +0200 "Michael S. Tsirkin" <mst@redhat.com> wrote: > Hello! > We are now all set to vote on issues from github. The github process is > much more lightweight than jira. Further, anyone with a github > account can create issues. > > The only requirement for starting the voting is that the issue body (1st > comment) includes a link to the list archives which should include the > proposal for fixing the issue. > > Issue milestone should also be set correctly, but that's a minor > issue I can handle for people who don't have the permission. > > The process is thus: > > 1. send email to mailing list > 2. open github issue > 3. include link to email in OASIS archives with the proposal > 4. if you post newer proposals, edit comment to update the proposal link > 5. once ready (give people time to comment), make me or one of the other editors know to start voting One of the other editors... who does have the rights nowadays? I know I have, but who else? Do we list that somewhere?

On Thu, Mar 01, 2018 at 05:48:57PM +0100, Cornelia Huck wrote: > On Thu, 1 Mar 2018 18:24:43 +0200 > "Michael S. Tsirkin" <mst@redhat.com> wrote: > > > Hello! > > We are now all set to vote on issues from github. The github process is > > much more lightweight than jira. Further, anyone with a github > > account can create issues. > > > > The only requirement for starting the voting is that the issue body (1st > > comment) includes a link to the list archives which should include the > > proposal for fixing the issue. > > > > Issue milestone should also be set correctly, but that's a minor > > issue I can handle for people who don't have the permission. > > > > The process is thus: > > > > 1. send email to mailing list > > 2. open github issue > > 3. include link to email in OASIS archives with the proposal > > 4. if you post newer proposals, edit comment to update the proposal link > > 5. once ready (give people time to comment), make me or one of the other editors know to start voting > > One of the other editors... who does have the rights nowadays? I know I > have, but who else? Oh I forgot, Pawel left. Just us two right now. > Do we list that somewhere? In the spec I guess... -- MST

On GitHub lightweight issues tracking process: Keeping your process as light as possible might imply NOT using labels, but several OASIS TCs are making profitable use of labels to help in the workflow.  With label descriptors and colors, you can classify issues and get visual imput. Let me know if you want other examples (from OASIS or beyond), but here are a couple, which you could adapt or excerpt if you want labels other than the default 7x [1] SARIF TC https://github.com/oasis-tcs/sarif-spec/ issues https://github.com/oasis-tcs/sarif-spec/ labels CTI TC https://github.com/oasis-tcs/cti-stix2/ issues https://github.com/oasis-tcs/cti-stix2/ labels Cheers, - Robin [1]  VIRTIO GitHub Repositories (Issues) https://github.com/oasis-tcs/virtio-spec https://github.com/oasis-tcs/virtio-spec/issues https://github.com/oasis-tcs/virtio-spec/labels https://github.com/oasis-tcs/virtio-docs https://github.com/oasis-tcs/virtio-docs/issues https://github.com/oasis-tcs/virtio-docs/labels https://github.com/oasis-tcs/virtio-admin https://github.com/oasis-tcs/virtio-admin/issues https://github.com/oasis-tcs/virtio-admin/labels On Thu, Mar 1, 2018 at 10:24 AM, Michael S. Tsirkin < mst@redhat.com > wrote: Hello! We are now all set to vote on issues from github.  The github process is much more lightweight than jira. Further, anyone with a github account can create issues. The only requirement for starting the voting is that the issue body (1st comment) includes a link to the list archives which should include the proposal for fixing the issue. Issue milestone should also be set correctly, but that's a minor issue I can handle for people who don't have the permission. The process is thus: 1. send email to mailing list 2. open github issue 3. include link to email in OASIS archives with the proposal 4. if you post newer proposals, edit comment to update the proposal link 5. once ready (give people time to comment), make me or one of the other editors know to start voting -- MST ------------------------------ ------------------------------ --------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/ apps/org/workgroup/portal/my_ workgroups.php -- Robin Cover OASIS, Director of Information Services Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover

On Thu, Mar 01, 2018 at 11:19:15AM -0600, Robin Cover wrote: > On GitHub lightweight issues tracking process: > > Keeping your process as light as possible might imply NOT using labels, but > several OASIS TCs are making profitable use of labels to help in the workflow.  > With label descriptors and colors, you can classify issues and get visual > imput. > > Let me know if you want other examples (from OASIS or beyond), but here are a > couple, which you could adapt or excerpt if you want labels other than the > default 7x [1] > > SARIF TC > https://github.com/oasis-tcs/sarif-spec/issues > https://github.com/oasis-tcs/sarif-spec/labels > > CTI TC > https://github.com/oasis-tcs/cti-stix2/issues > https://github.com/oasis-tcs/cti-stix2/labels > > Cheers, > > - Robin > > [1]  VIRTIO GitHub Repositories (Issues) > > https://github.com/oasis-tcs/virtio-spec > https://github.com/oasis-tcs/virtio-spec/issues > https://github.com/oasis-tcs/virtio-spec/labels > > https://github.com/oasis-tcs/virtio-docs > https://github.com/oasis-tcs/virtio-docs/issues > https://github.com/oasis-tcs/virtio-docs/labels > > https://github.com/oasis-tcs/virtio-admin > https://github.com/oasis-tcs/virtio-admin/issues > https://github.com/oasis-tcs/virtio-admin/labels Maybe we should use labels rather than the milestones to tag fixed-in version. the advantage is that the same issue can have many labels but only 1 milestone. > > > > On Thu, Mar 1, 2018 at 10:24 AM, Michael S. Tsirkin <mst@redhat.com> wrote: > > Hello! > We are now all set to vote on issues from github.  The github process is > much more lightweight than jira. Further, anyone with a github > account can create issues. > > The only requirement for starting the voting is that the issue body (1st > comment) includes a link to the list archives which should include the > proposal for fixing the issue. > > Issue milestone should also be set correctly, but that's a minor > issue I can handle for people who don't have the permission. > > The process is thus: > > 1. send email to mailing list > 2. open github issue > 3. include link to email in OASIS archives with the proposal > 4. if you post newer proposals, edit comment to update the proposal link > 5. once ready (give people time to comment), make me or one of the other > editors know to start voting > > -- > MST > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail.  Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > > > > -- > Robin Cover > OASIS, Director of Information Services > Email: robin@oasis-open.org > Staff bio: http://www.oasis-open.org/people/staff/robin-cover >