List Info

Thread: MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+




MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+
user name
2006-03-06 08:47:36
Hi,

On 3/6/06, Torben Nehmer <torbennehmer.net> wrote:
> The vote is now closed, with only four participiants
(including myself...)
> voting +1 for the MRFC. It is thus rejected according
to the rules of our
> community process.

A situation calling for an update to the mRFC process. How
about
adopting the Apache lazy consensus rules?

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - infoyukatan.fi
Software craftsmanship, JCR consulting, and Java
development
MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+
user name
2006-03-06 08:53:27
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Jukka Zitting wrote on 2006-03-06 09:47:
>> The vote is now closed, with only four
participiants (including myself...)
>> voting +1 for the MRFC. It is thus rejected
according to the rules of our
>> community process.
> 
> A situation calling for an update to the mRFC process.
How about
> adopting the Apache lazy consensus rules?

In short: What it is about?


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syn
tronics.de, mailto:torbennehmer.net
PGP Public Key: https://www.li
nk-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


iD8DBQFEC/iGJPh4Kn6d5FYRAs1CAJ9pT93uD/STRsGdRQAOvSNj9080UwCg
h+jF
Rey2rdidCe9+zjUU+n1rkKk=
=PbbF
-----END PGP SIGNATURE-----

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribemidgard-project.org
For additional commands, e-mail: dev-helpmidgard-project.org

MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+
user name
2006-03-06 08:50:12
On man, 2006-03-06 at 10:47 +0200, Jukka Zitting wrote:
> Hi,
> 
> On 3/6/06, Torben Nehmer <torbennehmer.net> wrote:
> > The vote is now closed, with only four
participiants (including myself...)
> > voting +1 for the MRFC. It is thus rejected
according to the rules of our
> > community process.
> 
> A situation calling for an update to the mRFC process.
How about
> adopting the Apache lazy consensus rules?
+1 
> BR,
> 
> Jukka Zitting
> 
> --
> Yukatan - http://yukatan.fi/ - infoyukatan.fi
> Software craftsmanship, JCR consulting, and Java
development
-- 
Tarjei Huse <tarjeinu.no>


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribemidgard-project.org
For additional commands, e-mail: dev-helpmidgard-project.org

MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+
user name
2006-03-06 09:03:47
Hi,

On 3/6/06, Torben Nehmer <torbennehmer.net> wrote:
> > A situation calling for an update to the mRFC
process. How about
> > adopting the Apache lazy consensus rules?
>
> In short: What it is about?

The Apache voting rules for code modifications (essentially
what mRFCs
are for) normally require three +1 votes and no -1 votes
(all
committers have a veto right). Lazy consensus is a relaxed
form of
these rules where at least a single +1 and no -1 votes will
be enough
to pass a vote.

See http://w
ww.apache.org/foundation/voting.html for more details.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - infoyukatan.fi
Software craftsmanship, JCR consulting, and Java
development
MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+
user name
2006-03-06 09:09:19
+1 

/Johan

On Mon, 2006-03-06 at 11:03 +0200, Jukka Zitting wrote:
> Hi,
> 
> On 3/6/06, Torben Nehmer <torbennehmer.net> wrote:
> > > A situation calling for an update to the mRFC
process. How about
> > > adopting the Apache lazy consensus rules?
> >
> > In short: What it is about?
> 
> The Apache voting rules for code modifications
(essentially what mRFCs
> are for) normally require three +1 votes and no -1
votes (all
> committers have a veto right). Lazy consensus is a
relaxed form of
> these rules where at least a single +1 and no -1 votes
will be enough
> to pass a vote.
> 
> See http://w
ww.apache.org/foundation/voting.html for more details.
> 
> BR,
> 
> Jukka Zitting
> 
> --
> Yukatan - http://yukatan.fi/ - infoyukatan.fi
> Software craftsmanship, JCR consulting, and Java
development
-- 
Johan Bernhardsson

Linux/CMS/Network Consultant

Phone:  +46-13-73244
Mobile: +46-705-111751
Fax:    +46-13-73190
Email/Jabber/Sip:  johananykey.se
Web:    www.anykey.se
MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+
user name
2006-03-06 09:04:11
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Torben Nehmer wrote on 2006-03-06 09:53:
>>>> The vote is now closed, with only four
participiants (including myself...)
>>>> voting +1 for the MRFC. It is thus rejected
according to the rules of our
>>>> community process.
>>> 
>>> A situation calling for an update to the mRFC
process. How about
>>> adopting the Apache lazy consensus rules?
> 
> In short: What it is about?

Just found it here: http:/
/www.apache.org/foundation/glossary.html (Thanks
Tarjei). So:

+1


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syn
tronics.de, mailto:torbennehmer.net
PGP Public Key: https://www.li
nk-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


iD8DBQFEC/sLJPh4Kn6d5FYRAoiQAKD9ZHjPbKDpt4Y/hZK1ukBsHfiF1gCd
E3Iz
6xI0TBy/4ZmjMq+TmeN9AzQ=
=Skcr
-----END PGP SIGNATURE-----

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribemidgard-project.org
For additional commands, e-mail: dev-helpmidgard-project.org

MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+
user name
2006-03-06 09:27:10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+1 for more Apache-compatible process. Who shall revise the
mRFC  
process mRFC?


On Mar 6, 2006, at 11:09, Johan Bernhardsson wrote:

> +1 
>
> /Johan
>
> On Mon, 2006-03-06 at 11:03 +0200, Jukka Zitting wrote:
>> Hi,
>>
>> On 3/6/06, Torben Nehmer <torbennehmer.net> wrote:
>>>> A situation calling for an update to the
mRFC process. How about
>>>> adopting the Apache lazy consensus rules?
>>>
>>> In short: What it is about?
>>
>> The Apache voting rules for code modifications
(essentially what  
>> mRFCs
>> are for) normally require three +1 votes and no -1
votes (all
>> committers have a veto right). Lazy consensus is a
relaxed form of
>> these rules where at least a single +1 and no -1
votes will be enough
>> to pass a vote.
>>
>> See http://w
ww.apache.org/foundation/voting.html for more details.
>>
>> BR,
>>
>> Jukka Zitting
>>
>> --
>> Yukatan - http://yukatan.fi/ - infoyukatan.fi
>> Software craftsmanship, JCR consulting, and Java
development
> -- 
> Johan Bernhardsson
>
> Linux/CMS/Network Consultant
>
> Phone:  +46-13-73244
> Mobile: +46-705-111751
> Fax:    +46-13-73190
> Email/Jabber/Sip:  johananykey.se
> Web:    www.anykey.se

Henri Bergius
Consultant Partner, Nemein
henri.bergiusnemein.com

Midgard CMS
www.midgard-project.org



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEDABwNkT8k497k9IRAuR5AKDUNbpnJsvkwJKdhlZZHX87seNJkACb
BYNh
wrZrCXsR8mKkmZfQrnjLHp8=
=LTLP
-----END PGP SIGNATURE-----

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribemidgard-project.org
For additional commands, e-mail: dev-helpmidgard-project.org

[1-7]

about | contact  Other archives ( Real Estate discussion Medical topics )