Community
Participate
Working Groups
The list of projects in the "Hudson HIPP Control" list includes archived projects. These should probably be excluded. The list also includes PolarSys and (I assume LocationTech) projects.
I also notice that I have, as a PMC member, ability to control the Mylyn HIPP. I'm okay with PMC members being granted this option. Is it entended to other relations? e.g. can an Emeritus Committer control the instance?
Indeed, I need to disable this for archived projects. I'll check on the Committer Emeritus, but since a PMC member is linked to a project, I don't see any harm in showing them the HIPP control UI.
Review is here: https://git.eclipse.org/r/#/c/18510 This is a change in eclipse.org-common, so I will percolate it to the "master" eclipse.org-common on www.eclipse.org
Thanks. I've pushed the eclipse.org-common change to www.eclipse.org/eclipse.org-common I have a "copy" of it on dev.eclipse.org since I need it there in the web root. Seemed just as easy to simply put it in Git.
(In reply to Denis Roy from comment #2) > I'll check on the Committer Emeritus, but since a PMC member is linked to a > project, I don't see any harm in showing them the HIPP control UI. For completeness, my original question was more a concern that the query was matching anybody who had any sort of project relation. Constraining it to PL and CM makes sense to me. It also makes sense to me to include the PMC relations. It just occurred to me, however, that the PMC relationships is effectively a NOOP for subprojects. Querying for PMC relationships between the project and people will only identify top-level projects.