We can think GIT as a de-facto standard for versioning system. I will be
happy to see Java (EE) specs in GIT, and also on Github.
2016-02-29 20:46 GMT+02:00 Reza Rahman <reza_rahman_at_lycos.com>:
> Personally this is a good idea. May be a way to make community
> contributions easier.
>
> On Feb 29, 2016, at 1:40 PM, Chris Barrow <chris.barrow_at_kaazing.com>
> wrote:
>
> Hi Ivar,
>
> Great idea. My github username is cmebarrow. Please add me.
>
> thanks,
> Chris
>
> On 2/29/2016 4:06 AM, Ivar Grimstad wrote:
>
> Hi all,
>
> What do you think of using this unfortunate "quiet period" to move from
> Subversion to Git?
>
> The way the java.net svn repo is organized does not allow for easy
> migration to Git, but here is a suggestion that should be feasible:
>
> - Migrate the jms2.1 folder to a new Git repository as the master
> branch.
> - Migrate the www folder to a new Git repository (separate from the
> above)
> - Keep the rest in the Subversion repo as is
>
> Why GitHub and not java.net?
>
> - GitHub offers better support for collaboration and pull requests
> - I don't have access to create repositories on java.net
> - The future of java.net is uncertain (rumor has it...)
> - When and if we have a java.net Git repo, we can move everything
> there, treat as master and use the GitHub repo as a mirror.
>
> Any objections? Or suggestions otherwise?
> I will be happy to fix this and for the purpose I have created a GitHub
> group/organization:
> (we have done the same thing with JSR 371 and JSR 375)
>
> https://github.com/jms-spec
>
> I will add all of you to this group if I can find your github user. Please
> email me your username if you don't get an invitation.
>
> Ivar
>
>
>
--
Rahman USTA
Istanbul JUG
https://github.com/rahmanusta <http://www.kodcu.com/>