Hi David!
On Mon, Feb 29, 2016 at 11:50 PM, David Blevins <dblevins_at_tomitribe.com>
wrote:
> Hello from an airport!
The wonders of modern telecommunication ;)
> Chiming in to show support for the proposal. In reference to one big org
> for all of EE, I'd be in favor of separate orgs to
>
> 1) give spec leads the most control. Aggregating control/authority to a
> center usually slows things down.
>
True, but if all EG members or at least spec leads got full control of all
repos it wouldn't matter that much. It's just a working repo anyway, and
only java.net (in case of Oracle led JSRs) would be this often mentioned
"The Truth".
But the one big org was just an idea I wanted to throw out there, separate
orgs would work too. To make the user aware of the other orgs, every org
could list the others in their readme.md with the current one in bold or so.
> That said there still could be a javaee repo with forks of the other
> repos. Though perhaps not worth the overhead.
>
If the separate repos are the main thing, then the javaee one would likely
not be worth the overhead. Especially since there's already the java.net
ones and then not rarely you have the GitHub mirrors of the java.net repos
as well.
Kind regards,
Arjan Tijms
>
> The other item that would be great to see is converting the word spec to
> asciidoc using the same setup as CDI
>
> -David
>
> On Monday, February 29, 2016, 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
>>
>>
>
> --
> Sent from Gmail Mobile
>