Issue 71 in xspec: Move XSpec to GitHub

2 views
Skip to first unread message

xs...@googlecode.com

unread,
Jun 6, 2015, 12:48:04 PM6/6/15
to xspe...@googlegroups.com
Status: New
Owner: dev....@menteithconsulting.com
Labels: Type-Other Priority-Medium

New issue 71 by dev....@menteithconsulting.com: Move XSpec to GitHub
https://code.google.com/p/xspec/issues/detail?id=71

I suggest that XSpec should move from GoogleCode to GitHub before
GoogleCode closes:
http://google-opensource.blogspot.ie/2015/03/farewell-to-google-code.html

There's already two copies of XSpec on GitHub:
https://github.com/search?utf8=%E2%9C%93&q=code.google.com%2Fp%2Fxspec&type=Repositories&ref=searchresults

I suggest that we make an 'XSpec' Organization on GitHub and migrate the
code there. The low overhead of accepting pull requests on GitHub may also
mean that we get more fixes from current non-committers for some of the
outstanding XSpec issues.

Regards,


Tony.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

xs...@googlecode.com

unread,
Jun 8, 2015, 11:49:33 AM6/8/15
to xspe...@googlegroups.com
Updates:
Status: Started
Labels: -Priority-Medium Priority-High

Comment #1 on issue 71 by fgeorges: Move XSpec to GitHub
https://code.google.com/p/xspec/issues/detail?id=71

Thank you for creating the ticket, Tony.

Using the integrated "export to GitHub" button created (yet) a new XSpec
repo under my own account.

I've created an XSpec organisation, invited Jeni and James, but could not
find you nor Michael.

I'm going to add the documentation and make sure nothing is left behind on
Google Code, then I will move the repo to the XSpec organisation.

xs...@googlecode.com

unread,
Jun 8, 2015, 11:50:33 AM6/8/15
to xspe...@googlegroups.com
Updates:
Owner: fgeorges

Comment #2 on issue 71 by fgeorges: Move XSpec to GitHub
https://code.google.com/p/xspec/issues/detail?id=71

(No comment was entered for this change.)
Reply all
Reply to author
Forward
0 new messages