Community
Participate
Working Groups
Webmasters, I will need your help fixing up some of the terminology and specifics of below ... but, pretty sure you'll get the idea ... Through our long history, the webtools project has ended up with a project called "webtools.website" specifically to control the resources in cvs, in www/webtools For, you might guess, our website at www.eclipse.org/webtools The project was originally set up so we could permit "extra" people, not otherwise a wtp committer, to get commit rights to our general website area. (was used once, and is not currently used for that purpose). Normally, as a matter of policy, we say that any wtp committer can automatically be a commmiter on webtools.website (though, not many do contribute to it). While some other projects do this too, in 2010 the EDP was changed so that the top level "container" project can "own resources" so this same role could be played by the "webtools" project. The "webtools" project currently just has a few PMC members in it as committers, and does not currently serve any purpose. Plus we have a custom group (named webtoolsadmin) to control our downloads area, which could also be governed by the webools group (which I assume can be called webtools-dev? or just webtools?) So, we are proposing to do away with "webtools.website" project, but add some committers to the "webtools" project. Plus, Chuck Bridgham should be the lead of the "webtools" project, instead of myself. According to Wayne, through an exploratory email, sounds like we can do this sort of "clean up to standard groups" without any fanfare. (no proposals/termination reviews, etc.). I will, though, send a note to wtp-dev since technically speaking, some people who did have commit rights to "webtools.website" will no longer be committers on "webtools" (though, as far as I can tell, none of these people have ever contributed anything to webtools, so would be "removed" due to inactivity anyway ... but, I'll make sure with note to wtp-dev). The initial "webtools" members will be current PMC members and Project Leads (of non-incubating sub-projects). Any future additions/removals will then be handled by the normal process. Thus, the members of 'webtools' unix group would be Chuck Bridgham (to be "lead", instead of 'david williams' David Williams Naci Dai Timothy Deboer Neil Hauge Kaloyan Raev Raghunathan Srinivasan Carl Anderson David Carver Nitin Dahyabhai Elson Yuen Keith Chong To allow time for some sanity checking and committer review, please wait to make this change on or after 9/14.
For the record, I wanted to document those who currently have "commit rights" to website and downloads area -- so, after the change to a new 'webtools' group, with 12 members, as above, there will be slightly more that can access downloads area, and substantially fewer that can write to website files. $ getent group webtoolsadmin [downloads] webtoolsadmin:*:8415:david_williams,ndai,rsrinivasan,nhauge,kraev,tle,canderson,dacarver $ getent group webtools-home [website] webtools-home:*:8189:cbridgha,cvswww,david_williams,deboer,gercan,ndai,nitind,skonya,vpelyushenko,kchong,jeffliu,rsrinivasan,gkessler,kprice,nhauge,jeff,vbaciu,pstephen,kraev,kkomissarchik,lisaacs,canderson,dacarver,avera,gkarasiu,cbateman,dgiormov,ssmith,nsandonato,dschadow,sclarke,ohurley,cjaun,mgandhi,mschmied,rstryker,gpetrovay,mrennie,sdimov,crogers,fthienel,lvillard,icampista,ddonchev,dtenev,nmanova,gkonstantin,eyuen,esimeonov,mhutchinson,psabeva
I remembered that to truly reflect access, I'd need to use 'getfacl' also, so, just to document it, there are those results ... the significant part being the jsf and dali groups added (though, I won't bother to recurse). default:group:jsf-dev:rwx default:group:dali-dev:rwx = = = = = = = $ getfacl /home/data/cvs/org.eclipse/www/webtools getfacl: Removing leading '/' from absolute path names # file: home/data/cvs/org.eclipse/www/webtools # owner: david_williams # group: webtools-home # flags: -s- user::rwx user:jeff:rwx user:cvswww:rwx group::rwx group:jsf-dev:rwx group:dali-dev:rwx group:8416:rwx mask::rwx other::r-x default:user::rwx default:user:jeff:rwx default:user:cvswww:rwx default:group::rwx default:group:jsf-dev:rwx default:group:dali-dev:rwx default:group:8416:rwx default:mask::rwx default:other::r-x $ getfacl ~/downloads/webtools getfacl: Removing leading '/' from absolute path names # file: home/data/users/david_williams/downloads/webtools # owner: david_williams # group: webtoolsadmin # flags: -s- user::rwx group::rwx other::r-x
Legal paperwork has been checked and there are no barriers for the following folks to be added as per David's request: Chuck Bridgham (to be "lead", instead of 'david williams' David Williams Naci Dai Timothy Deboer Neil Hauge Kaloyan Raev Raghunathan Srinivasan Carl Anderson David Carver Nitin Dahyabhai Elson Yuen Keith Chong Over to Wayne/Webmaster.... Thanks, Sharon
(In reply to comment #2) Are all of these ACLs still required or can we replace them by giving ownership of the /dali and /jsf areas to the relevant project groups? This could(should) also apply to /ejb and /jee and any other 'sub' projects that have directories within webtools( which technically should be moved up to be under www.eclipse.org/). -M.
(In reply to comment #4) > (In reply to comment #2) > > Are all of these ACLs still required or can we replace them by giving ownership > of the /dali and /jsf areas to the relevant project groups? This could(should) > also apply to /ejb and /jee and any other 'sub' projects that have directories > within webtools( which technically should be moved up to be under > www.eclipse.org/). > > -M. I'm not sure of what's being asked here ... seems there's several questions in one. The ACLs do not need to be part of webtools or webtools.website. As to whether or not they are needed elsewhere, I do not know. I'd prefer to handle any other proposed directory changes in other bugzillas. As far as I know, there is no desire to change or move other directories such as 'ejb' or 'jee' -- that would just be more work, and there is no need for fine-level control. The jsf and dali directories are probably a more complicated story. I don't think they are being used (but, "point back" to /webtools URLs), but not sure they want to "give up" the URLs as that might break some links?
Neil, Tran, Raghu ... I've added you to CC, in case you can weigh-in on JSF and Dali questions.
(In reply to comment #5) > I'm not sure of what's being asked here ... seems there's several questions in > one. Sorry about that. > The ACLs do not need to be part of webtools or webtools.website Ok, that was really my primary question. > I'd prefer to handle any other proposed directory changes in other bugzillas. No problem, I was simply suggesting them. > desire to change or move other directories such as 'ejb' or 'jee' -- that > would just be more work, Ok. > and there is no need for fine-level control. Ok, just checking. >I don't think they are being used (but, "point back" to /webtools URLs), > but not sure they want to "give up" the URLs as that might break some links? Again just a suggestion. -M.
Just to "close the loop", I originally asked " ... please wait to make this change on or after 9/14." so just wanted to document we are good to go from our point of view. No concerns or discussion have been raised so we in webtools are ready for this tiny simplification. But, the way things have been going ... maybe we should wait until the first week in October, just because of SR1 and Juno M2 coming up ... I guess there is some tiny risk that something would break or get in the way, though, I am also sure, it's pretty unlikely. So, first week of October ok?
(In reply to comment #6) > Neil, Tran, Raghu ... I've added you to CC, in case you can weigh-in on JSF and > Dali questions. Just to follow up on this, we would like to retain the old /dali location if it isn't a problem. But as you mentioned David, anything done regarding this issue could be handled in a separate bug.
(In reply to comment #8) > So, first week of October ok? Ok. -M.
We are all set ... change at your convenience ... but some time this week would be good.
Ok, I've cleaned the group membership for 'webtools', removed webtools-home and webtoolsadmin, and given the files owned by those groups to webtools. I think that's it. -M.
I think we ... well, me ... overlooked one. Tran Le ('tle') should also be a member of "webtools" since he needs to put things on "downloads".
No barrier to add Tran as indicated...
Also, I see that the "Eclipse Foundation project", webtools.website, still shows up on portal and similar pages, such as http://www.eclipse.org/projects/project.php?id=webtools.website Does this bugzilla suffice to clean that up? Let me know of you'd like a new bugzilla entry for that part of the "database" work.
(In reply to comment #14) > No barrier to add Tran as indicated... Done. I've also updated our backend DB to indicate the webtools.website project is 'archived' which should remove it from the portal list(when the data syncs later on) -M.
(In reply to comment #15) > Also, I see that the "Eclipse Foundation project", webtools.website, still > shows up on portal and similar pages, such as > > http://www.eclipse.org/projects/project.php?id=webtools.website > > Does this bugzilla suffice to clean that up? Let me know of you'd like a new > bugzilla entry for that part of the "database" work. It looks like Matt beat me to it. The project is marked as inactive in the database. Since it is still in our DB, you can still view it from the project summary page. It doesn't appear in the project list. I will update the project summary page indicate that the project has been archived (Bug 359934)
Thanks everyone ... all looks "fixed" to me.
