| Summary: | Standardize GEF groups | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Anthony Hunter <ahunter.eclipse> |
| Component: | RelEng | Assignee: | Karl Matthias <karl.matthias> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | karl.matthias, nboldt |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Anthony Hunter
(In reply to comment #0) > All the other code is in the gef-dev group. Well I am confused, the files in org.eclipse.draw2d plug-in are group gef-dev and the files in org.eclipse.gef plug-in are group gef. Sorry for the three comment repeat: The server reported an error while performing the "cvs tag" command. org.eclipse.gef.releng: cvs [tag aborted]: could not open lock file `/cvsroot/tools/org.eclipse.gef/org.eclipse.gef.releng/,.project,': Permission denied Nick, I need you to chgrp g+w org.eclipse.gef.releng > The server reported an error while performing the "cvs tag" command.
> org.eclipse.gef.releng: cvs [tag aborted]: could not open lock file
> `/cvsroot/tools/org.eclipse.gef/org.eclipse.gef.releng/,.project,': Permission
> denied
> Nick, I need you to chgrp g+w org.eclipse.gef.releng
$ chmod -R g+w org.eclipse.gef.releng
Done.
BTW, Karl loves doing Standardized Group renames. :)
We just finished w/ EMF, with EMFT slated for next month. Fixing up GEF should be a total no-brainer, if you're interested. As GEF committers, you and I are both in 6 GEF-related groups...
$ group nickb gef
4: gef-dev
6: gef-releng
7: gef
8: releng-gef
12: gef-home
13: gefadmin
$ group ahunter gef
4: gef-dev
5: gef-releng
6: gef
7: releng-gef
8: gef-home
9: gefadmin
... when we really only need two:
tools.gef (includes gef, zest, draw2d & releng sources in /cvsroot/tools/org.eclipse.gef/)
tools.gef.website (includes web content in /cvsroot/org.eclipse/www/gef/ and /home/data/httpd/{download,archive}.eclipse.org/tools/gef/)
Karl, I'll happily throw together another Google Doc spreadsheet for this if you'd like.
(In reply to comment #3) > BTW, Karl loves doing Standardized Group renames. :) Oh yes, I loves it, yes I does. > ... when we really only need two: Nick, you know this will put a further dent in your attempt at total groups domination. > Karl, I'll happily throw together another Google Doc spreadsheet for this if > you'd like. That would be great, Nick! I have to do literally every project over about the next year or so, so willing candidates are welcome. Next quarter I have a few migrations to do. (In reply to comment #3) > ... when we really only need two: > > tools.gef (includes gef, zest, draw2d & releng sources in > /cvsroot/tools/org.eclipse.gef/) > tools.gef.website (includes web content in /cvsroot/org.eclipse/www/gef/ and > /home/data/httpd/{download,archive}.eclipse.org/tools/gef/) > > Karl, I'll happily throw together another Google Doc spreadsheet for this if > you'd like. > I would rather go with just one. tools.gef works for me. > Nick, you know this will put a further dent in your attempt at total groups > domination. That's fine, I can dominate in other ways. Undead cloning, perhaps. > > Karl, I'll happily throw together another Google Doc spreadsheet > That would be great, Nick! I have to do literally every project http://spreadsheets.google.com/ccc?key=pZbKyLy8DKkzoGdbCXilicQ&hl=en&pli=1 > I would rather go with just one. tools.gef works for me. Ah, but you see, it's Standardized Groups, so you get two. Unless you raise a holy stink in bug 198541 and get everyone there to agree with you, that is. Ed thought modeling.emf.website was silly too, but the rationale is that this allows projects to choose to allow access to the source code and the website separately. WTP, for example, follows that model. Reassigning to Karl for whenever he's free to tackle this. Renamed. (In reply to comment #6) > Ah, but you see, it's Standardized Groups, so you get two. Unless you raise a > holy stink in bug 198541 and get everyone there to agree with you, that is. Ed > thought modeling.emf.website was silly too, but the rationale is that this > allows projects to choose to allow access to the source code and the website > separately. WTP, for example, follows that model. The thing is that GEF has no components, right? So that's the issue with needing a separate component for a website. Since GEF only has one component, the project itself, then they can actually just use one if they want. Should you create a new component in the future, though, then you'd end up with three rather than two. (In reply to comment #8) > The thing is that GEF has no components, right? So that's the issue with > needing a separate component for a website. Since GEF only has one component, > the project itself, then they can actually just use one if they want. Should > you create a new component in the future, though, then you'd end up with three > rather than two. At this time, correct. The 5 committers on GEF-GEF, GEF-Draw2D and GEF-Zest are not partitioned into component buckets like EMF. So, I've updated the spreadsheet as per this clarification and Anthony's preference for one group for all: http://spreadsheets.google.com/ccc?key=pZbKyLy8DKkzoGdbCXilicQ&hl=en&pli=1 (In reply to comment #9) > So, I've updated the spreadsheet as per this clarification and Anthony's > preference for one group for all: > > http://spreadsheets.google.com/ccc?key=pZbKyLy8DKkzoGdbCXilicQ&hl=en&pli=1 > Just to confirm Karl that you can make this so. Thanks Anthony, Nick. There has been a lot going on this summer and I've not gotten to all the migrations I'd like to see done. I'll get on this as soon as I can. I'll be starting on this in the next couple of days. Are there any times that are bad for you? I don't want to conflict with any running builds or the like. Anytime should be good, our weekly I builds just completed last night, so we are quiet right now. Done! I also fixed the ownership on the staging-priv directory on build. Everything has been updated. Thanks once again to Nick for the very helpful spreadsheet. Sorry this took so long. |