Re: [Technology-pmc] tech-pmc dependency informal procedure

[Wayne Beaton <wayne@xxxxxxxxxxx>]

This might be a little heavyweight for all dependencies.

The IP policy requires PMC discussion for all "works with" or "exempt pre-req" dependencies. These are generally the types of dependencies that are either impractical or impossible to review; these types of dependencies should never be directly distributed by the project via any public-facing server (e.g. Git repositories, or project downloads). They can be used in builds.

For "pre-req" dependencies, the IP Policy requires only that the PMC approve the CQ. It's generally enough for a member of the PMC to approve the CQ on behalf of the entire PMC without further discussion. Before approving, the PMC member would need to make a call regarding the technical reasonableness, cursory license check, etc. (that sort of thing). In my experience with Eclipse projects, some pre-req dependencies do require some discussion. The overwhelming majority do not require discussion.

Having said all that, I don't think that this adds too much weight to the process; I think it's worth a go.

I've opened a bug [1] to set up automatic notification on this list when a CQ is created. This can serve as the starting point for discussion.

Wayne

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=411402

On 07/01/2013 06:23 PM, Jody Garnett wrote:

From earlier conversations it seems the Technology PMC is up to its own devices for handling dependency discussion.

Since we are just starting out I am going to try out the following convention. This is just a starting point, we can revise it over time as needed.

1. Email technology-pmc@xxxxxxxxxxxxxxxx for each dependency

- this gives a discussion thread to link to in the CQ

2. Hold the conversation open for three business days

- If the discussion finishes up the CQ can get a +1,-1 vote as appropriate

3. After three business days with no discussion I will self approve the CQ

I expect we will only have a decent discussion on new dependencies. For simple version upgrades the above cycle will act more as notification and opportunity to communicate.

Cheers

-- 

Jody Garnett

_______________________________________________
Technology-pmc mailing list
Technology-pmc@xxxxxxxxxxxxxxxx
https://locationtech.org/mailman/listinfo/technology-pmc

--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects