Add section describing PMC role and responsibilities
Submitted by Wayne Beaton @wbeaton
Link to original bug (#529388)
Description
Consider adding some discussion regarding the role of the PMC.
e.g. [1]
-- There are a few reason we believe the review of the PMC is still helpful, such as:
- avoid mistakes by new/unexperienced projects
- help projects identify the proper CQ type (for distribution, pre-req, works-with, re-use)
- avoid pollution of the IP work queue with unnecessary CQs --
More PMC responsibility [2]:
-- That's right, the PMC +1 was never intended as a legal review. It was intended as a check on the technical merits of the 3rd party library. For example is another similar library already in use, or an alternative approach possible that doesn't use the library. Does the library have a healthy community with consistent releases and responsive developers, etc. The PMC also determines the relationship of the library to the project - a hard dependency vs works-with dependency, etc. Maybe it varies across top level projects whether the PMC is actually in a position to know or care about this, and in some cases the sub-project lead is in a better position to figure this out (although I would argue in this case the sub-project lead should be on the PMC).
[1] https://dev.eclipse.org/mhonarc/lists/incubation/msg00034.html [2] https://dev.eclipse.org/mhonarc/lists/incubation/msg00033.html
Depends on
Activity
@wbeatonsaid:More input:
-- The PMC's primary role in the IP process is to ensure that the IP requests are technically sound. It's entirely up to the PMC to determine what that means (e.g. some PMCs try to carefully manage a stack, software versions, etc.) Unless you see something glaringly wrong with license or have some inside track on an provenance issue, you can leave that sort of thing to the IP Team.
@wbeatonsaid:PMC reponsibilities in a committer election:
-- ==What is the PMC's Responsibility Regarding New Committers?== The PMC educates the new Committer on their responsibilities for safeguarding the intellectual property of Eclipse and that they have read, understood, and agree to follow the [http://www.eclipse.org/legal/committerguidelines.php Committer Guidelines]. Being a Committer at Eclipse is more than just having write-access to the Git repository and/or website - there are specific IP due diligence and record keeping activities that Committers ''must'' follow. The PMC is responsible for ensuring that their Committers understand and execute on these responsibilities.
@wbeatonclosed a related bug:*** Bug 514657 has been marked as a duplicate of this bug. ***
@geniesaid:This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.
If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
-- The automated Eclipse Genie.
