[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [technology-pmc] Requesting approval for code contributions?
|
> I'm thinking that we might consider adding the Bugzilla mail daemon to the
> PMC mailing list and inviting people to cc the technology-pmc on bugs that
> they want our input on. We could then do the short-term communication
> through the bug (copied on to the list, naturally) and then remove
> ourselves from cc when our input is no longer required.
+1
This should work pretty well for seeking PMC input on specific items without
having to subscribe to the mailing list.
- Konstantin
-----Original Message-----
From: technology-pmc-bounces@xxxxxxxxxxx
[mailto:technology-pmc-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Wednesday, November 26, 2008 11:05 AM
To: Technology PMC
Subject: Re: [technology-pmc] Requesting approval for code contributions?
"Code" means everything you check into CVS/SVN or make available as part
of a download. So images, XML, etc. are subject to IP review.
The easiest way to get PMC approval is to ask on this mailing list.
It occurs to me that this mailing list is relatively difficult to use
for these purposes. As a general rule, I don't imagine that there are
many non-PMC folks who really want/need to listen to this list. So... in
order to communicate with the PMC, you need to subscribe to this list
for the duration of your communcation. All the while, you have to listen
to our mindless banter on other topics.
I'm thinking that we might consider adding the Bugzilla mail daemon to
the PMC mailing list and inviting people to cc the technology-pmc on
bugs that they want our input on. We could then do the short-term
communication through the bug (copied on to the list, naturally) and
then remove ourselves from cc when our input is no longer required.
The architecture council does this currently.
Thoughts?
Wayne
Abel Muiño Vizcaino wrote:
> Hello PMC:
>
> I've just realized this sentence on the IP poster: "All Code Must be
> approved by your PMC".
>
> How should we handle that? We have several bugs with attached code
> from non-committers, some of them are small (<250 lines) and do not
> require IP review.
>
> Also, I'm not sure if by "code" it also refers to "non source code"
> (xml, images, build scripts...)
>
> Thanks!
> Abel.
>
> _______________________________________________
> technology-pmc mailing list
> technology-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/technology-pmc
>
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
