[jakarta.ee-spec.committee] Jakarta EE repositories proposal for specifi

[David Blevins <dblevins@xxxxxxxxxxxxx>]

First, let me apologize as I didn't notice this in the agenda.  I hadn't realized that Google docs remembers your position and when I was clicking in the agenda doc it was showing me January -- before I flew to Ecuador.

I like the proposal.  The introduction of the jakartaee-wg repository to host administrative and working group things is good.  I wanted to see if we're on the same page in a key detail and ask for one change.

One of the motivations for the split was that anything owned by a Specification Project would live in github.com/jakartaee and there would be no repositories owned by a specification project in github.com/eclipse-ee4j.

The one ask for change is we allow Specification Projects can have proposal repos -- using the rule above, they'd be in github.com/jakartaee.  We had one for Java EE Security back in the day and we have one in Jakarta Messaging.  I frequently promoted those repos when doing talks on how to get involved with the Specification Project.

I'd really prefer to not have to point people at github.com/eclipse-ee4j as how to get involved with a specification project or eclipse-ee4j (which contains my competition) as the best onramp for getting involved in Specification Projects.

Are we ok with the goal that any repos, including proposals, that would owned by a spec project would be in github.com/jakartaee and disconnected from github.com/eclipse-ee4j?

Minus the proposals tweak, the current proposal looks in line, but I just wanted to confirm.


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com