Re: github repo created for VIRTIO

["Michael S. Tsirkin" <mst@redhat.com>]

On Fri, Sep 08, 2017 at 11:42:25AM +0200, Cornelia Huck wrote:
> On Fri, 8 Sep 2017 08:29:01 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > Hi all!
> > OK I pushed the initial version here:
> > 
> > https://github.com/oasis-tcs/virtio-spec
> > 
> > This should match what is there in svn.
> > 
> > There's a single branch: master.
> > 
> > I also pushed out signed (by myself) tags for cs01 to 04 and csprd05 tags
> > that we had in svn.
> 
> Do we want to continue to work on master and apply tags, or do we want
> to do some kind of branch-based workflow? As we only have three
> committers anyway, the former should be good enough.

I think so too.

> > 
> > Please take a look.
> 
> Did not see anything off so far.
> 
> > 
> > Things to do:
> > 
> > Protect LICENSE and CONTRIBUTING files as immutable (OASIS
> > boilerplate). 
> 
> Frankly, no idea how to do this.
> 
> > Update README as below, but leave the startup
> > text as-is:
> > 
> > a) https://github.com/oasis-tcs/virtio-spec#description
> > update as needed (desc)
> > 
> > b) https://github.com/oasis-tcs/virtio-spec#
> > further-description-of-this-repository
> > Add any text we want there
> 
> The desc as above should be fine for now, I think.
> 
> > 
> > Update SVN to point to github.
> 
> Updated README.txt. Please take a look.
> 
> > 
> > Update TC homepage.
> 
> I have not been able to figure out how edit this. Maybe only the chair
> can do that?

I guess so.

> > 
> > Commit changes for ballots voted in.
> 
> Pushed code for 161 and also updated my affiliation.

Pls update the jira instance with commit ID in resolution and resolve it.

> I do not have the original mails for 155, 159, and 160, though (due to
> switching employers). The oasis mailing list archive does not seem to
> offer the option to download the original mail, and I could not find
> any other public archive. Can someone else please push these?

I'll bounce them to you.

> > 
> > Start populating docs and admin repositories.
> 
> What should they contain? I'd guess 'docs' our past releases; not sure
> what is supposed to go into 'admin'.
> 
> > 
> > Cornelia, Pawel as I'll be on vacation I'd appreciate
> > it if you can make some more progress on the above.
> >