Great, then I say lets get started!
On 12/4/13 2:30 PM, Chris Mattmann wrote:
Hey Kevin,
I don't think it's a blocker since you guys have released before. 0.3.1
can go out post graduation (or during or after) and they are independent.
Thanks and sorry I've been out of touch. I thought I could move from
Rancho Cucamonga, CA to Pasadena, CA take on a whole bunch more work
at JPL and other stuff and not see any drop-off. Hah!
I'm slowly coming back from the fog now and will be here to see this
project to its graduation!
Cheers,
Chris
-----Original Message-----
From: Kevin Minder <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Wednesday, December 4, 2013 11:28 AM
To: "[email protected]" <[email protected]>
Subject: Re: [DISCUSS] Graduation Vote Schedule (was Re: Project bylaws?)
Chris,
I'd love to start the process you outline. We ran into some
NOTICE/LICENSE file feedback about our 0.3.1 release. Should we take
care of that before proceeding?
Kevin.
On 12/4/13 2:24 PM, Chris Mattmann wrote:
Agree to points #1, #2, and #3.
Note that most projects simply agree to simple things like:
1. rotate the chair over some frequency of time X
2. abide by Apache voting policies
3. "be excellent to each other".
Where are we in terms of the graduation?
My proposal:
1. In the next 24 hours, I post up a draft graduation resolution
for [DISCUSS]
2. In 72 hours I call a VOTE (community one) on graduating via
the resolution
2a. if that vote passes, then we do 3
3. Post community vote tally on general@incubator along with draft
resolution, vote there for IPMC
4. If at least 3 IPMC +1s (from #2 or #3 or together) and more +1s
than -1s, it passes general@incubator VOTE after say 72 hours at least.
5. We post passed resolution into board agenda hopefully in time
for board meeting in Dec 2013.
Sound good?
Cheers,
Chris
-----Original Message-----
From: Kevin Minder <[email protected]>
Reply-To: "[email protected]"
<[email protected]>
Date: Tuesday, November 19, 2013 7:24 AM
To: "[email protected]" <[email protected]>
Subject: Re: Project bylaws?
I agree that
1) this should not gate graduation
2) that we should avoid creating our own legalese
3) that we should link to something that outlines the guidelines under
which we operate
On 11/19/13 9:58 AM, larry mccay wrote:
My understanding is that it isn't required that we have our own
by-laws
and
that most projects don't bother.
It is assumed that you adopt the httpd by-laws (guidelines) in the
absence
of your own.
If we can avoid crafting, interpreting and discussing our own legalese
- I
think that would be best.
That said - all contributors should be aware of the voting policy in
place
for our project.
A link to an authoritative definition of it - either in the httpd
project
(or ant for that matter) or to the glossary for definitions of
consensus,
etc would be good to have on our site.
On Tue, Nov 19, 2013 at 8:08 AM, Kevin Minder
<[email protected]>wrote:
Hi Everyone,
Several interesting threads occuring on general@incubator. One of
them
is about bylaws/voting. We probably need some more documentation
like
this
for graduation. From that thread, I thought the Ant bylaws (
http://ant.apache.org/bylaws.html) were a good example.
Kevin.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or
entity
to which it is addressed and may contain information that is
confidential,
privileged and exempt from disclosure under applicable law. If the
reader
of this message is not the intended recipient, you are hereby
notified
that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender
immediately
and delete it from your system. Thank You.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or
entity
to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the
reader
of this message is not the intended recipient, you are hereby notified
that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender
immediately
and delete it from your system. Thank You.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity
to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified
that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender
immediately
and delete it from your system. Thank You.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
