Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335206

Summary:

"Source Packages" for new committers is shamefully out of date

Product:

Community

Reporter:

David Williams <david_williams>

Component:

Project Management & Portal

Assignee:

Portal Bugzilla Dummy Inbox <portal-inbox>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

normal

Priority:

CC:

janet.campbell, wayne.beaton

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
"Source Packages" component	none

Description David Williams

2011-01-24 10:56:12 EST

I say "shamefully out of date" since it has probably always been wrong ... at least as long as I can remember ... but remains a constant source of confusion for Project Leads. I could not find an existing bugzilla, so thought I'd open this one. Guess everyone just kind of gets used to it and adapts ... but, would be nice to have it documented and at least some hope of fixing some day.

The issue is that once a new committer is elected, the PL gets a note, and a form on the portal to fill in the "Source Packages" new committers should have access to. First, it seems like that should already be "known", via Foundation databases ... all committers on a project get access to the same stuff. Second, if anything, it seems the question should be "what group" the new committer should be a member of, not literally the "source packages".

I know in WTP, we always dutifully fill in the "top most" directory for a project, For example, for Dali,
org.eclipse.jpa

But seems like that should be known already.

Perhaps a "stop gap" improvement would be to change the wording, from

"Please enter the names of the packages to which you would like to grant access. For legal accounting purposes "

"Please enter the top-most repository directory to which you would like to grant access. Just to confirm what we have in our databases:"

But, eventually, I'd think should be completely automatic? Or, perhaps PL given a form that says "is there any exceptions to the normal access privileges" ... or something.

I just wanted to get this on the books so it can be discussed, prioritized and scheduled along with other bugs/enhancements.

Thanks,

Comment 1 David Williams

2011-01-25 00:42:13 EST

Or ... following up on what what someone told me in an email :) ... perhaps instructions could just say "Use '*' if all defaults should apply". :)

Comment 2 Wayne Beaton

2011-01-25 19:27:12 EST

Created attachment 187599 [details]
"Source Packages" component

I'm attaching a screenshot of the component as a point of reference.

Comment 3 Wayne Beaton

2011-01-25 19:33:02 EST

Janet, 

I believe that this part of the process is historical. Today, all committers on a project get full access to all resources. I've been entering "*" into both of these fields for some time (I've attached a screenshot for context).

Are the "legal accounting purposes" still valid?

Can we just do away with this step, or do we still need it?

If we still need it, can I add words to the effect of "just put '*' into these fields and get on with it"? :-) (perhaps there might be better words to use)

Comment 4 Wayne Beaton

2011-03-07 15:10:15 EST

I've committed an interim fix that changes the message as part of Bug 332534. Marking this bug as a duplicate.

*** This bug has been marked as a duplicate of bug 332534 ***