| Re: [udig-devel] initial CQ dependencies |
|
On 04/25/2013 07:11 PM, Jody wrote:
Frank approved this one on behalf of the PMC, so we're good to go. When you approve a CQ, or otherwise complete a task that you've been assigned, you need to click "Issues adressed, return CQ to IPTeam". I did that on your behalf, Frank. For "build only" dependencies, the PMC needs to have a transparent discussion. This is generally held on the PMC mailing list (since the IPZilla system is visible to committers only). Normally, this would be a list named "technology-pmc@xxxxxxxxxxxxxxxx"; it doesn't appear that this this has been created, so I'll ask Webmaster to make that happen. In the meantime... The Nullsoft Scriptable Installer System builder itself seems like a reasonable "build and test only" dependency, but what do you intend to do with the generated output? I assume that the intent is to distribute it from locationtech.org? In this case, while the builder itself may be exempt from the due diligence process, any code that ends up in the distributed bits (e.g. installer runtime) is subject to the full wrath of the process. I think that we can treat these separately. I recommend that we keep this CQ is for the builder technology, and open a second one for whatever runtime bits need to be distributed. Make sense? --
Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects |