Community
Participate
Working Groups
(In reply to bug 282166 comment #23) > Not sure why this is dependent on bug 198541. The ldap group name for > EMF.compare was updated to be consistent with the standardized groups schema. That was just done to cause a "ping" to happen on that bug, since it's been sitting idle for a while, and we're still not 100% standardized in Modeling. > Am I missing something? Or is this the prelude to a new bug to bring the EMF > website into conformance? I'm happy with /cvsroot/org.eclipse/www/modeling/ being owned and ACL'd by anyone/everyone in modeling.website, but you (and the various Modeling PMCs) may prefer to split it by subproject: /cvsroot/org.eclipse/www/modeling/emf/ -> modeling.emf.website /cvsroot/org.eclipse/www/modeling/mdt/ -> modeling.mdt.website ... Note that modeling.mdt.website doesn't (yet) exist. Check *this* bit of inconsistency in group names: $ group khussey mdt 9: mdt-dev 10: mdt-home 11: mdtadmin 12: modeling.mdt.ocl 13: modeling.mdt.ocl-releng 14: mdt-uml2tools 15: mdt-uml2tools-releng 16: mdt-uml2 17: mdt-uml2-releng 18: mdt-xsd 19: mdt-xsd-releng 20: mdt-releng 21: modeling.mdt.imm-dev 22: modeling.mdt.imm-home 23: modeling.mdt.imm-admin 24: modeling.mdt.imm-releng 25: modeling.mdt.bpmn2-dev 26: modeling.mdt.bpmn2-releng 27: modeling.mdt.bpmn2-home 28: modeling.mdt.bpmn2-admin 32: modeling.mdt.mst 727 nickb@node4:~ $ group khussey website 29: modeling.emf.website where `group` is basically `groups | egrep`: #!/bin/bash filter=":"; if [[ $2 ]]; then filter=$2; fi if [[ $1 ]]; then for f in `groups $1`;do (( c++)); echo $c: $f | egrep "$filter"; done fi And that's just one example. Would you prefer this moved to a new bug?
Let's fix this. I don't expect that re-naming the groups will have any impact although compressing them may. When is a good time for the Modeling project? -M.
After Galileo SR1 is done, maybe? Dunno, depends on the MDT leads. Try firing a note at mdt-dev@ or mdt.dev@ and asking them. Or maybe Kenn has a preference? (Generally he shoots down every bug I open to make things more consistent, and those bugs sit idle for months thereafter. Perhaps this one will be different?)
Hey, I thought the group names made MDT hella cool. ;) (In reply to comment #2) > After Galileo SR1 is done, maybe? Dunno, depends on the MDT leads. > > Try firing a note at mdt-dev@ or mdt.dev@ and asking them. Or maybe Kenn has a > preference? It doesn't matter to me whether/when the (server) groups are renamed. > > (Generally he shoots down every bug I open to make things more consistent, and > those bugs sit idle for months thereafter. Perhaps this one will be different?) The only change I remember shooting down was renaming the mailing lists, since that would have an explicit impact.
Ok, I've mapped out the changes required to bring the MDT groups into alignment with the standards. I'll wait until monday and then clean up these groups. -M.
I've cleaned up all of the MDT related groups I can find. Please file a bug or send an email if something isn't working as expected. -M.
