virtio — archive

clarification regarding Ballot: "move specification development to git"

From: Robin Cover <[email protected]>
To: [email protected]
Date: Fri, 01 Sep 2017 16:20:00 -0000

On Thu, Aug 31, 2017 at 5:06 AM, Cornelia Huck < [email protected] > wrote: [Re-send, in the hope that there was only a temporary problem at oasis...] Re: clarifying the TC's preference for use of comment list for public feedback [1a] > Can we note somewhere that we prefer to get feedback through the mailing list? I'll be happy to help with modification of the OASIS boilerplate text used in each GitHub repository's CONTRIBUTING file to support you. If you wish, we can modify that document to clarify your preference for comment mailing list. Comments provided as public feedback (quite rare, actually, in the OASIS TC GitHub repositories) are usually composed as GitHib repo Issues, When someone begins to create a new Issue (clicks on "New..."), GitHub will display a prominent link to the repository CONTRIBUTING file, with this message "Please review the guidelines for contributing to this repository" So, users have ample opportunity to understand your preferences when it comes to providing feedback. > just wait and see what comes and maybe gently push people towards the mailing list. I think that will work well. - Robin [1a] Date: Thu, 31 Aug 2017 12:06:42 +0200 From: Cornelia Huck < [email protected] > To: "Michael S. Tsirkin" < [email protected] > Cc: [email protected] Message-ID: < 20170831090028.5d9c988b. [email protected] > > Can we note somewhere that we prefer to get feedback through the mailing list? > With the popularity of github, we will have to deal with contributions through that path sooner or later, though. My take is to just wait and see what comes and maybe gently push people towards the mailing list.. On Thu, 31 Aug 2017 02:09:26 +0300 "Michael S. Tsirkin" < [email protected] > wrote: > Hello, > > With regards to the ongoing ballot for moving development to git, > the following was pointed out to me: > > github is not just git hosting. It also adds ability to add feedback > in the form of comments, issues, pull requests, etc. > > The online OASIS documentation explains that while substantive repo contributions > come only from TC members, public feedback may be posted on github. > > The static immutable policy files in each repository further clarify the terms > for contributing, and applicarbility of the OASIS Feedback License to any such > public comment [2], [3] > > [1] Public Feedback > https://www.oasis-open.org/res ources/tcadmin/ > github-repositories-for-oasis- tc-members-chartered-work# > contributionsAndFeedback > > [2] CONTRIBUTING > https://github.com/oasis-tcs/o data-openapi/blob/master/CONTR IBUTING.md > > [3] LICENSE > https://github.com/oasis-tcs/o data-openapi/blob/master/LICEN SE.md > > Please note that this policy is static which is slightly different from > contributing patches on the mailing list where the contributor is made > to click through on a form about agreeing to the IPR policy. > > I am not sure what is the best way to handle such feedback. For > example, I consider github pull requests generally not well formatted. > I suggest that we focus on maintaing the spec itself in git, and look at > this problem if and when we get feedback through these means. Can we note somewhere that we prefer to get feedback through the mailing list? With the popularity of github, we will have to deal with contributions through that path sooner or later, though. My take is to just wait and see what comes and maybe gently push people towards the mailing list... > > However, in case other TC members feel differently, please answer on > the mailing list, or (if you are a voting member) vote on the ballot. > ------------------------------ ------------------------------ --------- 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/app s/org/workgroup/portal/my_work groups.php -- Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: [email protected] Staff bio: http://www.oasis-open.org/ people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/ newsletterArchive.html Tel: +1 972-296-1783