Eliot, I think we need to discuss pros and cons. We have some TC
members who find SVN difficult; I don't want to eliminate their
contributions by moving our work to GitHub.
One possibility might be to use both SVN and GitHub, for example:
- SVN for committee notes
- GitHub for spec
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
On 10/10/2016 4:19 PM, Eliot Kimber
wrote:
Excellent news. I move that we transition our Subversion
repository to GitHub as soon as reasonably possible.
Cheers,
E.
For our discussion.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
-------- Forwarded Message --------
In response to a growing number of member requests, OASIS Staff is now providing
support for use of GitHub public repositories by TCs that need dedicated version
control. Use of Git/GitHub will be supported in addition to, or in place of, a
TC's Subversion (SVN) repository.
These GitHub repositories for TC work will be configured using the GitHub
default (simple) setup options that enable GitHub issues and the GitHub Wiki.
The new offering is distinct from OASIS Open Repositories [5], which also use
Git/GitHub, but are governed by open source licensing and separate contribution
rules. The GitHub repositories for TC Members' chartered work are governed by
the familiar OASIS policies which govern use of other TC collaboration tools,
including a TC Wiki, a TC Subversion repository, a TC JIRA Issues Tracker, and a
TC Kavi document repository (OASIS IPR Policy, TC Process etc.)
References are provided below for the online request form and related
documentation.
Staff hereby extends a note of appreciation to the TAB, OASIS Board, and several
TC Chairs who provided encouragement and feedback on rollout of this additional
collaboration tool.
Please send comments or questions to Robin Cover and Chet Ensign, via email at:
robin@oasis-open.org (and) chet.ensign@oasis-open.org
** References
[1] GitHub Repositories for OASIS TC Members' Chartered Work
https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work
[2] Online Request Form
https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created
[3] Model repository to illustrate use of default startup files
https://github.com/oasis-tcs/water-new-metrics
[4] Design Notes (provisional/temporary)
https://oasis-tcs.github.io/design-notes.html
[5] OASIS Open Repositories (different than: GitHub for TC Members' work)
https://www.oasis-open.org/resources/open-repositories
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/who/staff.php#cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-839-6538
---------------------------------------------------------------------
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
|