atom feed30 messages in org.apache.maven.doxia-devRE: PMC change explanation?
FromSent OnAttachments
Jeff JensenJun 16, 2011 6:42 am 
Lukas TheusslJun 16, 2011 7:00 am 
Jason van ZylJun 16, 2011 8:10 am 
Manfred MoserJun 16, 2011 8:24 am 
Martin GaintyJun 16, 2011 12:08 pm 
Manfred MoserJun 16, 2011 12:14 pm 
Benson MarguliesJun 16, 2011 12:27 pm 
Jesse McConnellJun 16, 2011 12:32 pm 
Martin GaintyJun 16, 2011 12:36 pm 
Brett PorterJun 16, 2011 5:00 pm 
Daniel KulpJun 16, 2011 5:32 pm 
Jim JagielskiJun 17, 2011 4:36 am 
Doug CuttingJun 17, 2011 4:54 am 
Jason van ZylJun 17, 2011 6:03 am 
Jim JagielskiJun 17, 2011 6:09 am 
Doug CuttingJun 17, 2011 6:22 am 
Jason van ZylJun 17, 2011 6:23 am 
Jason van ZylJun 17, 2011 6:31 am 
Jim JagielskiJun 17, 2011 6:43 am 
Mark StrubergJun 17, 2011 6:45 am 
Jason van ZylJun 17, 2011 6:54 am 
Jason van ZylJun 17, 2011 7:07 am 
Jason van ZylJun 17, 2011 7:15 am 
Jim JagielskiJun 17, 2011 7:15 am 
Jason van ZylJun 17, 2011 7:45 am 
John CaseyJun 17, 2011 7:46 am 
Jim JagielskiJun 17, 2011 8:02 am 
Shane CurcuruJun 17, 2011 8:42 am 
Jason van ZylJun 17, 2011 10:21 am 
Jim JagielskiJun 17, 2011 10:49 am 
Subject:RE: PMC change explanation?
From:Martin Gainty (mgai@hotmail.com)
Date:Jun 16, 2011 12:08:26 pm
List:org.apache.maven.doxia-dev

Good Afternoon Manfred

from my understanding the maven hierarchy looks like: JASON (aka god) | v Everyone else

(pull up a pew)

Bedankt, Martin

______________________________________________ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note
de déni et de confidentialité Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt.

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.

Date: Thu, 16 Jun 2011 08:24:35 -0700 Subject: Re: PMC change explanation? From: manf@mosabuam.com To: de@maven.apache.org CC: boa@apache.org

I find it somewhat bewildering that there is no post of the vote or the results on the dev and users mailing lists I can see. Nor does the web site seem to be updated.

http://maven.apache.org/team-list.html

I would have expected more transparency from Apache.

Jeff,

I believe this strictly falls within the purview of the Apache Board to explain. In particular Jim, Doug and Shane.

Only the board has the right to reveal the business that has been transacted on private lists.

Rest assured that's Sonatype's commitment to Maven users and our pursuit of innovation with respect to Maven-related technologies has not stopped, and will not stop.

On Jun 16, 2011, at 9:42 AM, Jeff Jensen wrote:

Is there a forthcoming explanation for a seemingly Maven PMC shakeup? I find it odd that consistently excellent contributors such as Lukas, Brian, et al are suddenly not on the Maven PMC. This is concerning as these are people who have drastically improved and moved Maven forward. It's very concerning that a heavy committer such as Benjamin is no longer committing as he has done very useful, fantastic work. These events are very concerning for the forward progress of Maven. The strong temptations for competitive products, a la Gradle, do not allow Maven progress to stop; particularly the best progress to date of the past year. These events are detrimental. For us uninformed, what happened, why is it good, what is the plan forward behind this?

Thanks,

Jason

---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl

---------------------------------------------------------

We all have problems. How we deal with them is a measure of our worth.

-- Unknown