[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[modeling-pmc] Committer boundaries
|
Bug 326381 [1] has me thinking about committer boundaries within the
Modeling project. I know that we keep butting up against this one UNIX
group per project issue and I'd like to take a run at solving it.
It has been suggested in the past that we automatically grant
committer-access to parent projects. This may work in Modeling, but does
not work in the general case (e.g. the Technology project does not want
every Technology subproject committer to have write access to the
Technology project's website). I don't think this will work, but we can
talk about it.
I'd like to better understand the root problem. Bug 326381 shows how
write access the parent project's (EMFT) www directory is required to
handle display information the downloads page. What is stopping us from
keeping this "extras" file in the project's own directory? Is it a
matter of providing a metadata entry in the portal (along with a
corresponding query to extract it) to provide a pointer? Can we join
this information to the "releases" metadata?
What other resources cause us grief here?
Wayne
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=326381
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
