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