| Summary: | Masquerade as project lead should allow to enter requested infos | ||
|---|---|---|---|
| Product: | Community | Reporter: | Dani Megert <daniel_megert> |
| Component: | Project Management & Portal | Assignee: | Portal Bugzilla Dummy Inbox <portal-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Dani Megert
Ping. Just had another occasion where this would be useful. I'm not disagreeing, but shouldn't every project have at least 2 project leads to avoid this type of scenario? >shouldn't every project have at least 2 project leads
No. Normally there is one (that's why it's called "lead") ;-)
However, there are several PMC members that could step in. It's also the PMC who confirms the committer vote and there are already other tasks that the PMC can masquerade for, hence it would make sense to allow this as well. Also note that even the PMC has a "lead" which again is a single person but without any special/additional rights in the portal (I think).
For completeness, a project *may* have more than one lead. It makes sense. Really. However, there is no requirement to do so. It pains me to do so, but I have to mark this bug as WONTFIX. Unfortunately, this represents a significant amount of work and we do not have the resources required to make this change. The workaround is for you to send a request on behalf of the PMC to the EMO; we'll make the change for you. Another option is for us to make a temporary change in project leadership while the existing project lead is sick. You can effect this with a note to EMO; we'll make it happen (FWIW, this scenario is supported by the EDP). >The workaround is for you to send a request on
>behalf of the PMC to the EMO; we'll make the change for you.
Works for me. Thx.
|