Comment 1 Eclipse Webmaster 2007-06-14 09:46:57 EDT

Someone really needs to specify that these are in fact new groups that need to be  created, and what in cvs they should control.  

-M.

Comment 2 Nick Boldt 2007-06-14 10:13:49 EDT

Matt:

for g in m2t-jet m2t-jet-releng; do
 if [[ ! $g ]]; then create it; fi
 assign pelder > $g;
 assign jcheuoua > $g;
done

associate m2t-jet > /cvsroot/modeling/org.eclipse.m2t/org.eclipse.jet
associate m2t-jet-releng > /cvsroot/modeling/org.eclipse.m2t/org.eclipse.jet.releng

That said, looking at CVS I see that everyone in M2Tland is in group m2t-dev. If Paul doesn't want/need different groups for each component, then creating extra groups might be overkill (even if it *does* make M2T consistent w/ MDT and EMF).

Let's hold off on any changes until Paul +1's the pmc_approved box.

Comment 3 Nick Boldt 2008-01-31 03:46:21 EST

With the new components starting up in M2T, should the group permissions be split by component?

eg.,

m2t-jet, m2t-jet-releng
m2t-xpand, *-releng
m2t-core, *-releng
m2t-shared, *-releng
m2t-mtl, *-releng

Paul, your thoughts?

Comment 4 Paul Elder 2008-01-31 08:51:04 EST

Approved.