Ivar/all,
Thanks for the initiative. We understand he might be as busy with other
tasks as his colleagues, but please also ask Nigel and for the sake of
proper setup offer him at least an Admin role in the GitHub repos/orga, too.
Similar to JSR 375 and others we hopefully get a GitHub mirror of the main
API some day, too? It's a bit more complicated, but at least one
sub-project of Apache DeviceMap has an SVN/Git mirror mechanism set up and
I believe it works 2-way, so SVN commits trigger a GitHub update and vice
versa. Therefore if the "source of truth" can't be migrated to Git on
java.net right now, we could still get a mirror on GitHub if necessary.
Cheers,
Werner
On Mon, Feb 29, 2016 at 1:06 PM, Ivar Grimstad <ivar.grimstad_at_gmail.com>
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
>
>