I'm all in favor of consistency but please bear in mind JMS is not
exclusively a Java EE thing. Some people (like us at Kaazing) use it
extensively in Java SE. I think it's more valuable as a standard that
way ( meaning not just exclusively JEE).
Chris
On 2/29/2016 11:39 AM, arjan tijms wrote:
> Hi,
>
> On Mon, Feb 29, 2016 at 7:46 PM, Reza Rahman <reza_rahman_at_lycos.com
> <mailto:reza_rahman_at_lycos.com>> wrote:
>
> Personally this is a good idea. May be a way to make community
> contributions easier.
>
>
> I think so too.
>
> One thing I wonder if it wouldn't be a good idea to establish some
> consistency in the way repos are set up. Currently every repo on
> GitHub uses slightly different naming conventions.
>
> For instance:
>
> JSF:
> https://github.com/javaserverfaces
> /mojarra
> /samples
> /extensions
>
> Java EE security:
> https://github.com/javaee-security-spec
> /javaee-security-proposals
> /soteria
> /javaee-security-examples
> /spec-api
>
> MVC 1:
> https://github.com/spericas
> /ozark
> /mvc-spec
>
> MVC 2:
> https://github.com/mvc-spec
> /ozark
> /mvc-spec
> /mvc-spec.github.io <http://mvc-spec.github.io>
>
> JMS
> https://github.com/jms-spec
> /jms-proposals
> /jms-examples
> /jms-spec.github.io <http://jms-spec.github.io>
>
>
> Another thing is if it perhaps would not be a better idea to have a
> "javaee-spec" organisation and then put all specs below that?
>
> So:
>
> https://github.com/javaee-spec
> /jsf-proposals
> /jsf-samples
> /jsf-ri-mojarra
> /jms-proposals
> /jms-samples
>
> It would need some re-organising of already existing repos though, but
> MVC 2 and JMS have just been setup.
>
> Regardless, it may be an idea to setup a new GitHub repo for JSF as
> well, as the existing one is strictly a read-only mirror from the
> java.net <http://java.net> one and thus can't be used as public
> working repo.
>
> Yet another thing, what about a disclaimer for settling IP rights for
> pull requests from non-EG members? For Mojarra there's a disclaimer
> somewhere for if you mail a patch to the mailinglist, you donate it
> and give up IP (or something like that IANAL). The CDI mailing list
> has a similar disclaimer if I'm not mistaken.
>
> Finally, with a java.net <http://java.net> git repo and a github git
> repo, 2 way sync is quite doable by cloning one of the repos and
> adding the other as an extra remote. Specifically if you then also
> create a feature branch it's rather easily to merge changes from one
> repo to the local clone, and then push it out to the other repo.
> Still, it would probably be cleanest if all commits went through the
> GitHub repo. I'm not sure yet how it would work with a SVN java.net
> <http://java.net> repo if that SVN repo would also get committed to
> directly.
>
> Kind regards,
> Arjan Tijms
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Feb 29, 2016, at 1:40 PM, Chris Barrow
> <chris.barrow_at_kaazing.com <mailto: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 <http://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 <http://java.net>?
>>>
>>> * GitHub offers better support for collaboration and pull requests
>>> * I don't have access to create repositories on java.net
>>> <http://java.net>
>>> * The future of java.net <http://java.net> is uncertain (rumor
>>> has it...)
>>> * When and if we have a java.net <http://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
>>>
>>
>