Is a vote really needed to add a PPMC ?

[jan i]

Hi

We (Corinthia) is currently having an interesting discussion about voting,
one of the questions
are about consensus instead of vote.

In a TLP the rules for sending a NOTICE mail to board are simple:
- The Chair can do it based on consensus or a vote, without mail reference
- Any PMC members can do it based on a vote, WITH a mail reference.

Now a PPMC does not have a chair, so I assumed a Vote is mandatory (see
also http://incubator.apache.org/guides/ppmc.html that talks about voting
in a new PPMC.

But doubt has been raised, whether the IPMC would also acknowledge
consensus ?

In my opinion, the IPMC "simulates" board, and should allow the podlings as
much freedom as possible, hence allow consensus even though a podling has
no chair.

Thoughts ?

rgds
jan i

Re: Please add my Wiki account to the ContributorsGroup

[Bertrand Delacretaz]

On Thu, May 21, 2015 at 11:23 AM, Jacopo Cappellato
 wrote:
> could you please add my Wiki account:
> JacopoCappellato
> to the ContributorsGroup?

Done.
-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add my Wiki account to the ContributorsGroup

[jler...@apache.org]

Hi Jacopo,

I guess it's https://wiki.apache.org/incubator/FreemarkerProposal.

I saw you are looking for mentors. I can help if needed...

Jacques
PS: my incubator wiki account is JacquesLeRoux


Le 21/05/2015 11:23, Jacopo Cappellato a écrit :

Hi all,

could you please add my Wiki account:

JacopoCappellato

to the ContributorsGroup? I would like to create a new page for a project 
proposal for the Incubator.

Thank you

Jacopo


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add my Wiki account to the ContributorsGroup

[Nick Burch]

On Mon, 8 Jun 2015, Pierre Smits wrote:

please add my wiki account to the ContributorsGroup.


Karma granted, enjoy!

Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add my Wiki account to the ContributorsGroup

[Pierre Smits]

Thanks Nick.

Best regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Mon, Jun 8, 2015 at 11:40 AM, Nick Burch  wrote:

> On Mon, 8 Jun 2015, Pierre Smits wrote:
>
>> please add my wiki account to the ContributorsGroup.
>>
>
> Karma granted, enjoy!
>
> Nick
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Permission to add a page to the Incubator wiki

[Klevenz, Stephan]

Hello,

May I have permission to add and edit OData proposal on the Incubator wiki?  My 
username is StephanKlevenz.

Thanks!

Stephan

Re: Please add me to the Incubator UNIX group

[Tim Williams]

On Tue, Apr 22, 2014 at 2:26 AM, Gagan Juneja  wrote:
> Hello,
>
> Can someone with the necessary karma please add me to the Incubator UNIX
> group so that I can finalize the release/site for project Blur? I'm the
> release manager and commiter on the project.

Hey Gagan,
Looks like you are a member, are you getting permission denied on
something specific?

twilliams@minotaur:~$ list_unix_group.pl incubator | grep gagz
gagz

Thanks,
--tim

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[Proposal] Add me as Mentor for ODF Toolkit Podling

[Rob Weir]

I looked around and did not see a process defined for adding a Mentor
to a podling.  I see how they are added at podling initiation, but not
after.  So apologies if I'm missing something.

It appears that we have at present zero active Mentors, so even with
the experimental release process we're unable to move forward, since
that requires Mentor sign off on the release manifest/checklist.

I am able and willing to help here.

Regards,

-Rob

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

May 2010 Incubator Board Report (Updated to add Clerezza)

[Noel J. Bergman]

ervice providers,
written in python. Libcloud joined the Incubator on November 3rd, 2009.

We're on the cusp of pushing 0.3.2 out the door, with our last release 0.3.1
on 10 May 2010.

Over the past few months we have:

 * Added driver support for new providers: Dreamhost, Eucalyptus, Enomaly
ECP, IBM Developer Cloud, and !SoftLayer
 * Improved multi-threaded handling in Rackspace and !RimuHosting
 * Created deployment and bootstrap API
 * Expanded test coverage
 * Augment documentation

We look forward to further improving documentation and lowering the barrier
to entry with tutorials and a guide for writing drivers.  We will continue
to add providers and keep the library updated with providers' changes.


= Lucene Connector Framework =

Description:

Lucene Connectors Framework is an incremental crawler framework and set of
connectors designed to pull documents from various kinds of repositories
into search engine indexes or other targets. The current bevy of connectors
includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Patriarch
(Memex), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web
content. Lucene Connectors Framework also provides components for individual
document security within a target search engine, so that repository security
access conventions can be enforced in the search results.

Lucene Connectors Framework has been in incubation since January, 2010.

A list of the three most important issues to address in the move towards
graduation:

1. End-user documentation conversion to usable form needs to be completed;
this is probably the biggest obstacle to developing a broader community at
this point 1. Javadoc and nightly builds need to be set up 1. The first
official release needs to be planned and executed

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

1. We'd like to know whether there is any official Apache position on
inclusion of NTLM implementations in ASF projects, since we've gotten mixed
signals on this from other developers. This represents a crucial piece of
functionality needed to support LiveLink, Meridio, SharePoint, RSS, and Web
connectors properly.

How has the community developed since the last report?

There's been a significant amount of discussion pertaining to the LCF
document security model, it's advantages and disadvantages.  Offers of
assistance and advice abound.  A non-Apache code submission has even been
made.

How has the project developed since the last report?

Preliminary security integration with Solr has been tackled.  Online
end-user documentation is coming along and is perhaps 60% complete.  Scripts
have been written to make using LCF easier for the less experienced
integrator.


= OODT =

Description:

OODT is a  grid middleware framework for science data processing,
information  integration, and retrieval. OODT is used on a number of
successful  projects at Jet  Propulsion Laboratory/ California Institute of
Technology (http://jpl.nasa.gov/, and many  other research institutions and
universities.

A  list of the three most important issues to address in the move towards
graduation:

 1. Port OODT  code and license headers into ASF license headers
 1. OODT contributions from at least 2 other  organizations besides JPL
 1. At  least one OODT incubating release, hopefully in the first few months

Any  issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

No, not at  this time.

How has the community developed since the last report?

Chris Mattmann mentioned OODT as a possible extension for Whirr, proposed by
Tom White in the Incubator. We had some input from Justin
(http://www.mail-archive.com/oodt-...@incubator.apache.org/msg00050.html)
progressing on OODT-3 (http://issues.apache.org/jira/browse/OODT-3), and
leveraging tools like RAT to do the license checking and verification needed
to close out the issue. Much of the other activity  continues to be from the
mentors and committers.

How  has the project developed since the last report?

OODT was voted into the Incubator by the IPMC]] on January 22, 2010.

Development over the last month has centered
on[[https://issues.apache.org/jira/browse/OODT-3|OODT-3]] (cleaning up the
OODT code and config license headers), with contributions from Sean
!McCleese, and on[[https://issues.apache.org/jira/browse/OODT-15|OODT-15]]
(one top-level build for OODT, and one trunk, tags and
branches).[[https://issues.apache.org/jira/browse/OODT-15|OODT-15]] in
particular included some community discussion and a lazy consensus to move
forward. Chris Mattmann is nearly complete on this reorganization, which,
coupled with[[https://issues.apache.org/jira/browse/OODT-3|OODT-3]] should
provide for a great 1st incubating release along with some documentation
transfering and getting the website up and running
(https://issues.apache.org/jira/browse/OODT-16), which Sean Kelly has
volunteered to spearhead.



= PhotArk =

Apache

Re: Add kelly and woollard to incubator UNIX group

[Joe Schaefer]

Done.



- Original Message 
> From: "Mattmann, Chris A (388J)" 
> To: "general@incubator.apache.org" 
> Cc: "oodt-...@incubator.apache.org" 
> Sent: Sun, August 8, 2010 4:52:48 PM
> Subject: Add kelly and woollard to incubator UNIX group
> 
> Hi Guys,
> 
> Over in OODT land, we've recently made our website [1]. Now, we  want folks
> on the OODT PPMC to have access to update the oodt site on  people.a.o. Can
> the following folks be added to the incubator UNIX group to  do this?
> 
> Sean Kelly (UNIX account: kelly)
> David Woollard (UNIX  account: woollard)
> 
> Those are the only folks trying to update the site for  now, but there may be
> more later, at which point I can always come back and  ask then.
> 
> Thanks!
> 
> Cheers,
> Chris
> 
> [1]  http://incubator.apache.org/oodt/
> 
> ++
> Chris  Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory  Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.mattm...@jpl.nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++
> Adjunct  Assistant Professor, Computer Science Department
> University of Southern  California, Los Angeles, CA 90089  USA
> ++
> 
> 
> 
> -
> To  unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For  additional commands, e-mail: general-h...@incubator.apache.org
> 
> 


  

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Add kelly and woollard to incubator UNIX group

[Mattmann, Chris A (388J)]

Dang, that was quick! Thanks Joe!

Cheers,
Chris


On 8/8/10 1:56 PM, "Joe Schaefer"  wrote:

Done.



- Original Message 
> From: "Mattmann, Chris A (388J)" 
> To: "general@incubator.apache.org" 
> Cc: "oodt-...@incubator.apache.org" 
> Sent: Sun, August 8, 2010 4:52:48 PM
> Subject: Add kelly and woollard to incubator UNIX group
>
> Hi Guys,
>
> Over in OODT land, we've recently made our website [1]. Now, we  want folks
> on the OODT PPMC to have access to update the oodt site on  people.a.o. Can
> the following folks be added to the incubator UNIX group to  do this?
>
> Sean Kelly (UNIX account: kelly)
> David Woollard (UNIX  account: woollard)
>
> Those are the only folks trying to update the site for  now, but there may be
> more later, at which point I can always come back and  ask then.
>
> Thanks!
>
> Cheers,
> Chris
>
> [1]  http://incubator.apache.org/oodt/
>
> ++
> Chris  Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory  Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.mattm...@jpl.nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++
> Adjunct  Assistant Professor, Computer Science Department
> University of Southern  California, Los Angeles, CA 90089  USA
> ++
>
>
>
> -
> To  unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For  additional commands, e-mail: general-h...@incubator.apache.org
>
>




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++

Re: Please add Enis Soztutar to Incubator UNIX group

[Craig L Russell]

Done.
modify_unix_group.pl incubator --add=enis
LDAP Password (^D aborts):
Done!
Notification sent to .

Craig

On Oct 15, 2010, at 12:24 PM, Mattmann, Chris A (388J) wrote:


Hi,

Can someone with the necessary karma please add Enis Soztutar to the
Incubator UNIX group so that he can deploy our Gora website?

Thanks,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Craig L Russell
Secretary, Apache Software Foundation
Chair, OpenJPA PMC
c...@apache.org http://db.apache.org/jdo










-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add Enis Soztutar to Incubator UNIX group

[Mattmann, Chris A (388J)]

Thanks Craig!


On 10/15/10 2:15 PM, "Craig L Russell"  wrote:

Done.
modify_unix_group.pl incubator --add=enis
LDAP Password (^D aborts):
Done!
Notification sent to .

Craig

On Oct 15, 2010, at 12:24 PM, Mattmann, Chris A (388J) wrote:

> Hi,
>
> Can someone with the necessary karma please add Enis Soztutar to the
> Incubator UNIX group so that he can deploy our Gora website?
>
> Thanks,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.mattm...@jpl.nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Craig L Russell
Secretary, Apache Software Foundation
Chair, OpenJPA PMC
c...@apache.org http://db.apache.org/jdo










-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++

Re: Please add me to the Incubator UNIX group

[Patrick Hunt]

Sorry, that is I'm trying to finalize the Whirr release. Thanks.

On Fri, Nov 12, 2010 at 10:16 PM, Patrick Hunt  wrote:
> Hello, a hand please?
>
> Can someone with the necessary karma please add me to the Incubator
> UNIX group so that I can finalize the release/site? I'm the release
> manager and commiter on the project.
>
> Thanks,
>
> Patrick
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add me to the Incubator UNIX group

[Joe Schaefer]

Done.



- Original Message 
> From: Patrick Hunt 
> To: general@incubator.apache.org
> Sent: Sat, November 13, 2010 1:17:45 AM
> Subject: Re: Please add me to the Incubator UNIX group
> 
> Sorry, that is I'm trying to finalize the Whirr release. Thanks.
> 
> On Fri,  Nov 12, 2010 at 10:16 PM, Patrick Hunt  wrote:
> > Hello, a  hand please?
> >
> > Can someone with the necessary karma please add me  to the Incubator
> > UNIX group so that I can finalize the release/site? I'm  the release
> > manager and commiter on the project.
> >
> >  Thanks,
> >
> >  Patrick
> >
> 
> -
> To  unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For  additional commands, e-mail: general-h...@incubator.apache.org
> 
> 


  

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add me to the Incubator UNIX group

[Patrick Hunt]

Thanks Joe!

On Fri, Nov 12, 2010 at 10:23 PM, Joe Schaefer  wrote:
> Done.
>
>
>
> - Original Message 
>> From: Patrick Hunt 
>> To: general@incubator.apache.org
>> Sent: Sat, November 13, 2010 1:17:45 AM
>> Subject: Re: Please add me to the Incubator UNIX group
>>
>> Sorry, that is I'm trying to finalize the Whirr release. Thanks.
>>
>> On Fri,  Nov 12, 2010 at 10:16 PM, Patrick Hunt  wrote:
>> > Hello, a  hand please?
>> >
>> > Can someone with the necessary karma please add me  to the Incubator
>> > UNIX group so that I can finalize the release/site? I'm  the release
>> > manager and commiter on the project.
>> >
>> >  Thanks,
>> >
>> >  Patrick
>> >
>>
>> -
>> To  unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For  additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add to Incubation table: Jena, Nuvem, OpenNLP

[Ross Gardler]

On 07/12/2010 07:16, David Crossley wrote:

To the new projects, e.g.
Jena, Nuvem, OpenNLP


Done for Jena - thanks for the prompt

(I've not rebuilt the site do I need to do so or will it happen on a 
schedule?)


Ross



Please add an entry for your project to
the "Currently in incubation" table:
http://incubator.apache.org/projects/

Some docs: http://incubator.apache.org/clutch.html#h-Sponsor

The incubator website docs are able to be edited by
any committers on incubating projects. So please don't
leave it to your mentors.

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add to Incubation table: Jena, Nuvem, OpenNLP

[Thilo Götz]

Done for OpenNLP.  I have rebuilt and committed
the site.  Need to check if I have permissions
to update the staging site...

--Thilo

On 07/12/10 11:51, Ross Gardler wrote:

On 07/12/2010 07:16, David Crossley wrote:

To the new projects, e.g.
Jena, Nuvem, OpenNLP


Done for Jena - thanks for the prompt

(I've not rebuilt the site do I need to do so or will it happen on a
schedule?)

Ross



Please add an entry for your project to
the "Currently in incubation" table:
http://incubator.apache.org/projects/

Some docs: http://incubator.apache.org/clutch.html#h-Sponsor

The incubator website docs are able to be edited by
any committers on incubating projects. So please don't
leave it to your mentors.

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add to Incubation table: Jena, Nuvem, OpenNLP

[Thilo Götz]

Staging area updated, we should see the updates for
Jena and OpenNLP with the next sync.

--Thilo

On 07/12/10 12:01, Thilo Götz wrote:

Done for OpenNLP.  I have rebuilt and committed
the site. Need to check if I have permissions
to update the staging site...

--Thilo

On 07/12/10 11:51, Ross Gardler wrote:

On 07/12/2010 07:16, David Crossley wrote:

To the new projects, e.g.
Jena, Nuvem, OpenNLP


Done for Jena - thanks for the prompt

(I've not rebuilt the site do I need to do so or will it happen on a
schedule?)

Ross



Please add an entry for your project to
the "Currently in incubation" table:
http://incubator.apache.org/projects/

Some docs: http://incubator.apache.org/clutch.html#h-Sponsor

The incubator website docs are able to be edited by
any committers on incubating projects. So please don't
leave it to your mentors.

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add me to incubator wiki contributor group

[Jukka Zitting]

Hi,

On Wed, Jul 4, 2012 at 11:05 AM, Reto Bachmann-Gmür  wrote:
> "Then send your username to general@incubator so that we can grant you
> write access by adding your account to the
> ContributorsGroup
> ."
>
> RetoBachmannGmuer

Done.

BR,

Jukka Zitting

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Can someone add me to the wiki Contributor Group?

[Noah Slater]

Hey,

I'm trying to sign off on a board report, but I don't have edit permission.

Can someone add me to the wiki Contributor Group?

Thanks,

-- 
NS

Please add me to the ContributorsGroup on wiki.apache.org/incubator

[Antoine Levy Lambert]

Hi,

please add me to the ContributorsGroup on wiki.apache.org/incubator.

I need to sign off a report for EasyAnt.

Regards,

Antoine

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Please add me to the ContributorsGroup on wiki.apache.org/incubator

[antoine]

Hi,

I forgot to write : my user id in the wiki is "antoine"

Regards,

Antoine


On Jan 9, 2013, at 9:30 PM, Antoine Levy Lambert wrote:

> Hi,
> 
> please add me to the ContributorsGroup on wiki.apache.org/incubator.
> 
> I need to sign off a report for EasyAnt.
> 
> Regards,
> 
> Antoine


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Permission to add a page to the Incubator wiki

[Rebecca Wood]

Hello,

May I have permission to add and edit the jclouds proposal on the Incubator 
wiki?  My username is RebeccaWood.

Thanks!

Becca
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add joestein to the Kafka SVN group

[Mattmann, Chris A (388J)]

Done!

[chipotle:~/tmp/authorization] mattmann% svn commit -m "Grant Joe Stein SVN 
karma for Kafka."
Sendingasf-authorization-template
Transmitting file data .
Committed revision 805086.
[chipotle:~/tmp/authorization] mattmann% 


Cheers,
Chris

On Feb 16, 2012, at 9:42 AM, Alan D. Cabrera wrote:

> Please add joestein to the Kafka SVN group.  Thanks!
> 
> 
> Regards,
> Alan
> 
> Preferred userid: joestein
> Full name: Joe Stein
> Forwarding email address: crypt...@gmail.com
> 
> Vote reference:
> https://mail-search.apache.org/members/private-arch/incubator-private/201201.mbox/%3ccaoejijhhbfawzgttsh1i8rq1x3xqxgpgcn71j3xj2er57+x...@mail.gmail.com%3e
> 
> -- 
> Submitted by https://id.apache.org/acreq/members/
> From 81.138.181.69.in-addr.arpa domain name pointer 
> c-69-181-138-81.hsd1.ca.comcast.net.
> Using Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/534.50.2 
> (KHTML, like Gecko) Version/5.0.6 Safari/533.22.3
> 


++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add joestein to the Kafka SVN group

[Alan D. Cabrera]

Thanks!

On Feb 16, 2012, at 10:55 AM, Mattmann, Chris A (388J) wrote:

> Done!
> 
> [chipotle:~/tmp/authorization] mattmann% svn commit -m "Grant Joe Stein SVN 
> karma for Kafka."
> Sendingasf-authorization-template
> Transmitting file data .
> Committed revision 805086.
> [chipotle:~/tmp/authorization] mattmann% 
> 
> 
> Cheers,
> Chris
> 
> On Feb 16, 2012, at 9:42 AM, Alan D. Cabrera wrote:
> 
>> Please add joestein to the Kafka SVN group.  Thanks!
>> 
>> 
>> Regards,
>> Alan
>> 
>> Preferred userid: joestein
>> Full name: Joe Stein
>> Forwarding email address: crypt...@gmail.com
>> 
>> Vote reference:
>> https://mail-search.apache.org/members/private-arch/incubator-private/201201.mbox/%3ccaoejijhhbfawzgttsh1i8rq1x3xqxgpgcn71j3xj2er57+x...@mail.gmail.com%3e
>> 
>> -- 
>> Submitted by https://id.apache.org/acreq/members/
>> From 81.138.181.69.in-addr.arpa domain name pointer 
>> c-69-181-138-81.hsd1.ca.comcast.net.
>> Using Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/534.50.2 
>> (KHTML, like Gecko) Version/5.0.6 Safari/533.22.3
>> 
> 
> 
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add joestein to the Kafka SVN group

[Mattmann, Chris A (388J)]

No probs...

Cheers,
Chris

On Feb 16, 2012, at 8:02 PM, Alan D. Cabrera wrote:

> Thanks!
> 
> On Feb 16, 2012, at 10:55 AM, Mattmann, Chris A (388J) wrote:
> 
>> Done!
>> 
>> [chipotle:~/tmp/authorization] mattmann% svn commit -m "Grant Joe Stein SVN 
>> karma for Kafka."
>> Sendingasf-authorization-template
>> Transmitting file data .
>> Committed revision 805086.
>> [chipotle:~/tmp/authorization] mattmann% 
>> 
>> 
>> Cheers,
>> Chris
>> 
>> On Feb 16, 2012, at 9:42 AM, Alan D. Cabrera wrote:
>> 
>>> Please add joestein to the Kafka SVN group.  Thanks!
>>> 
>>> 
>>> Regards,
>>> Alan
>>> 
>>> Preferred userid: joestein
>>> Full name: Joe Stein
>>> Forwarding email address: crypt...@gmail.com
>>> 
>>> Vote reference:
>>> https://mail-search.apache.org/members/private-arch/incubator-private/201201.mbox/%3ccaoejijhhbfawzgttsh1i8rq1x3xqxgpgcn71j3xj2er57+x...@mail.gmail.com%3e
>>> 
>>> -- 
>>> Submitted by https://id.apache.org/acreq/members/
>>> From 81.138.181.69.in-addr.arpa domain name pointer 
>>> c-69-181-138-81.hsd1.ca.comcast.net.
>>> Using Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/534.50.2 
>>> (KHTML, like Gecko) Version/5.0.6 Safari/533.22.3
>>> 
>> 
>> 
>> ++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattm...@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] Created: (INCUBATOR-88) Add podling to reporting schedule

[Niclas Hedhman (JIRA)]

Add podling to reporting schedule
-

 Key: INCUBATOR-88
 URL: https://issues.apache.org/jira/browse/INCUBATOR-88
 Project: Incubator
  Issue Type: Sub-task
Reporter: Niclas Hedhman


New podlings report every month for the first 3 months, then every quarter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (INCUBATOR-88) Add podling to reporting schedule

[Niclas Hedhman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Niclas Hedhman resolved INCUBATOR-88.
-

Resolution: Fixed

> Add podling to reporting schedule
> -
>
> Key: INCUBATOR-88
> URL: https://issues.apache.org/jira/browse/INCUBATOR-88
> Project: Incubator
>  Issue Type: Sub-task
>Reporter: Niclas Hedhman
>
> New podlings report every month for the first 3 months, then every quarter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (INCUBATOR-88) Add podling to reporting schedule

[Niclas Hedhman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Niclas Hedhman closed INCUBATOR-88.
---


> Add podling to reporting schedule
> -
>
> Key: INCUBATOR-88
> URL: https://issues.apache.org/jira/browse/INCUBATOR-88
> Project: Incubator
>  Issue Type: Sub-task
>Reporter: Niclas Hedhman
>
> New podlings report every month for the first 3 months, then every quarter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (INCUBATOR-94) Add project to /projects/index.html

[Niclas Hedhman (JIRA)]

Add project to /projects/index.html
---

 Key: INCUBATOR-94
 URL: https://issues.apache.org/jira/browse/INCUBATOR-94
 Project: Incubator
  Issue Type: Sub-task
Reporter: Niclas Hedhman


Etch needs to add a small description of the project to the Incubator's 
"projects" page, site-author/projects/index.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (INCUBATOR-94) Add project to /projects/index.html

[Niclas Hedhman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Niclas Hedhman reassigned INCUBATOR-94:
---

Assignee: Niclas Hedhman

> Add project to /projects/index.html
> ---
>
> Key: INCUBATOR-94
> URL: https://issues.apache.org/jira/browse/INCUBATOR-94
> Project: Incubator
>  Issue Type: Sub-task
>Reporter: Niclas Hedhman
>Assignee: Niclas Hedhman
>
> Etch needs to add a small description of the project to the Incubator's 
> "projects" page, site-author/projects/index.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (INCUBATOR-94) Add project to /projects/index.html

[Niclas Hedhman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Niclas Hedhman closed INCUBATOR-94.
---

Resolution: Fixed

> Add project to /projects/index.html
> ---
>
> Key: INCUBATOR-94
> URL: https://issues.apache.org/jira/browse/INCUBATOR-94
> Project: Incubator
>  Issue Type: Sub-task
>Reporter: Niclas Hedhman
>Assignee: Niclas Hedhman
>
> Etch needs to add a small description of the project to the Incubator's 
> "projects" page, site-author/projects/index.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (INCUBATOR-88) Add podling to reporting schedule

[Niclas Hedhman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Niclas Hedhman updated INCUBATOR-88:


Description: 
New podlings report every month for the first 3 months, then every quarter.

The Reporting Schedule is at; http://wiki.apache.org/incubator/ReportingSchedule

  was:New podlings report every month for the first 3 months, then every 
quarter.


> Add podling to reporting schedule
> -
>
> Key: INCUBATOR-88
> URL: https://issues.apache.org/jira/browse/INCUBATOR-88
> Project: Incubator
>  Issue Type: Sub-task
>Reporter: Niclas Hedhman
>
> New podlings report every month for the first 3 months, then every quarter.
> The Reporting Schedule is at; 
> http://wiki.apache.org/incubator/ReportingSchedule

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add Chris Hillery as a committer to AsterixDB

[Ted Dunning]

This is a mentor task more than a general@incubator task.

Let's redirect the conversation back to dev@ and see if we can wrassle up a
mentor with sufficient free time. (I am a mentor, in fact)


On Fri, Oct 16, 2015 at 1:16 AM, Jochen Wiedmann 
wrote:

> Hi,
>
> in a thread with the subject "[VOTE] Add Chris Hillery as a committer
> and PPMC member" the AsterixDB project has unanimously decided to
> invite Chris Hillery to become a committer. (Sorry, no quote, because
> the vote was happening on private@) Chris has already supplied a CLA.(
> he is listed on [1] under "Unlisted CLA's".) Howver, he doesn't yet
> appear on [2].
>
> I assume that someone on general@ with the necessary privileges must
> take some action. Would it be possible to do that now?
>
> Thanks,
>
> Jochen
>
> P.S: Btw, the preferred login id would be "ceej"
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>

Re: Add 'KarthikRamasamy' to the incubator wiki contributors group

[Marvin Humphrey]

On Thu, Oct 29, 2015 at 8:15 AM, Chris Aniszczyk  wrote:
> I would like to add 'KarthikRamasamy' to the incubator wiki contributors
> group

Done.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[John D. Ament]

Justin

Were LDAP and DNS entries created yet?

On Dec 18, 2017 12:11 AM, "Justin Mclean"  wrote:

> Hi,
>
> I was just just trying to set PLC4X podling PPMC membership [3]  but I
> can’t seem to edit the roster. This says [1] the $podlings.xml file is no
> longer used and the whimsey tool should be used instead [2]. I can edit
> other podling memberships but not PLC4X.
>
> I’m probably just being impatient, but how does someone get edit
> permission to add mentors in the first place? Does it need to be requested
> or is it part of the podling parent setup? [4] Also what exactly does this
> parent setup do?
>
> My understanding from the discussion here [5] was that any IPMC member
> could add mentors to a podling. Has this changed?
>
> Thanks,
> Justin
>
> 1. https://incubator.apache.org/guides/ppmc.html#maintaining_
> podling_roster
> 2. http://www.apache.org/dev/pmc.html#SVNWhimsy
> 3, https://whimsy.apache.org/roster/ppmc/plc4x
> 4. https://incubator.apache.org/guides/mentor.html#resources
> 5. https://lists.apache.org/thread.html/a6ce7e3a366490f04f5c66e9434aa2
> b7da9a763f040262f1b12407af@%3Cgeneral.incubator.apache.org%3E
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Clarifying on how to add initial PPMC members

[Justin Mclean]

Hi,

> Were LDAP and DNS entries created yet?

Probably not [1][2]  (hey I’m impatient) but it’s a little unclear to me what 
needs to be done to sort this or why it couldn’t  be automated. Creating a new 
podling should be as pushing a button IMO.

Thanks,
Justin

1. https://incubator.apache.org/guides/mentor.html#resources
2. https://issues.apache.org/jira/browse/INFRA-15682


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[John D. Ament]

Heyyy look at that, it's magic (check your email).  You should be all set.

But I should replace "requested" with "completed" to make sure people know
that it has to be done first.  And as far as I know, it is a button,
however only infra and secretary can push that button.

John

On Mon, Dec 18, 2017 at 6:33 AM Justin Mclean  wrote:

> Hi,
>
> > Were LDAP and DNS entries created yet?
>
> Probably not [1][2]  (hey I’m impatient) but it’s a little unclear to me
> what needs to be done to sort this or why it couldn’t  be automated.
> Creating a new podling should be as pushing a button IMO.
>
> Thanks,
> Justin
>
> 1. https://incubator.apache.org/guides/mentor.html#resources
> 2. https://issues.apache.org/jira/browse/INFRA-15682
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Clarifying on how to add initial PPMC members

[Sam Ruby]

On Mon, Dec 18, 2017 at 6:43 AM, John D. Ament  wrote:
> Heyyy look at that, it's magic (check your email).  You should be all set.
>
> But I should replace "requested" with "completed" to make sure people know
> that it has to be done first.  And as far as I know, it is a button,
> however only infra and secretary can push that button.

Correct.  The authority required to execute that request is the same
authority required to delete (or modify) any PMC or podling.

> John

- Sam Ruby

> On Mon, Dec 18, 2017 at 6:33 AM Justin Mclean  wrote:
>
>> Hi,
>>
>> > Were LDAP and DNS entries created yet?
>>
>> Probably not [1][2]  (hey I’m impatient) but it’s a little unclear to me
>> what needs to be done to sort this or why it couldn’t  be automated.
>> Creating a new podling should be as pushing a button IMO.
>>
>> Thanks,
>> Justin
>>
>> 1. https://incubator.apache.org/guides/mentor.html#resources
>> 2. https://issues.apache.org/jira/browse/INFRA-15682
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[Justin Mclean]

Hi,

And something is still not right here. When trying to add the new PPMC members 
all buttons are disabled and can’t be clicked. I think what is going on is that 
it’s enforcing the 72 hour waiting period and assuming that any PPMC member you 
add was voted in and not on the initial list.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[Dave Fisher]

Hi Justin,

IIRC you have to add the PPMC members to the Incubator committers group first, 
but then I know that Whimsy has had changes since I setup Pulsar PPMC 6 months 
ago.

Regards,
Dave

> On Dec 19, 2017, at 2:44 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> And something is still not right here. When trying to add the new PPMC 
> members all buttons are disabled and can’t be clicked. I think what is going 
> on is that it’s enforcing the 72 hour waiting period and assuming that any 
> PPMC member you add was voted in and not on the initial list.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Clarifying on how to add initial PPMC members

[Justin Mclean]

Hi,

> IIRC you have to add the PPMC members to the Incubator committers group first

Thanks for the suggestion but they are already listed as incubator committers. 
(e.g. kherings)

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[John D. Ament]

Justin

Did you click the box indicating the notice period expired?

On Dec 19, 2017 5:53 PM, "Justin Mclean"  wrote:

> Hi,
>
> > IIRC you have to add the PPMC members to the Incubator committers group
> first
>
> Thanks for the suggestion but they are already listed as incubator
> committers. (e.g. kherings)
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Clarifying on how to add initial PPMC members

[Justin Mclean]

Hi,

> Did you click the box indicating the notice period expired?

Yes I did and the button are still disabled. I tried in two seperate browser to 
make sure it wasn’t a browser issue as well.

I can add other ASF people as committers but that’s not what I want to do.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[John D. Ament]

Can you please share the username of one of the users that you're having
problems with?

John

On Tue, Dec 19, 2017 at 7:09 PM Justin Mclean  wrote:

> Hi,
>
> > Did you click the box indicating the notice period expired?
>
> Yes I did and the button are still disabled. I tried in two seperate
> browser to make sure it wasn’t a browser issue as well.
>
> I can add other ASF people as committers but that’s not what I want to do.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Clarifying on how to add initial PPMC members

[Justin Mclean]

Hi,

> Can you please share the username of one of the users that you're having
> problems with?

Try either Kai Herings (kherings) or Mark Keinhörster (keinmark).

Lukas Friedrichsen and Frank Stibane ICLAs has been accepted but don’t have 
apache id’s as yet but they would be next.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[Justin Mclean]

Hi,

And now it's working!

Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Clarifying on how to add initial PPMC members

[John D. Ament]

Weird,  the only odd thing now is it looks like both of us added him.
There were no code changes, so no idea.

On Tue, Dec 19, 2017 at 7:53 PM Justin Mclean 
wrote:

> Hi,
>
> And now it's working!
>
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[jira] Created: (INCUBATOR-28) Add sample podling web site

[Craig Russell (JIRA)]

Add sample podling web site
---

 Key: INCUBATOR-28
 URL: http://issues.apache.org/jira/browse/INCUBATOR-28
 Project: Incubator
  Issue Type: Improvement
  Components: site
Reporter: Craig Russell
Priority: Minor


A sample web site for podlings is provided, with commonly needed web pages.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (INCUBATOR-28) Add sample podling web site

[Craig Russell (JIRA)]

 [ http://issues.apache.org/jira/browse/INCUBATOR-28?page=all ]

Craig Russell updated INCUBATOR-28:
---

Attachment: INCUBATOR-28.txt

The attached patch adds a "samples/site" directory that can be copied by 
podlings to their own svn repository and used as a starter site.

> Add sample podling web site
> ---
>
> Key: INCUBATOR-28
> URL: http://issues.apache.org/jira/browse/INCUBATOR-28
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Craig Russell
>Priority: Minor
> Attachments: INCUBATOR-28.txt
>
>
> A sample web site for podlings is provided, with commonly needed web pages.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (INCUBATOR-28) Add sample podling web site

[Robert Burrell Donkin (JIRA)]

 [ http://issues.apache.org/jira/browse/INCUBATOR-28?page=all ]

Robert Burrell Donkin closed INCUBATOR-28.
--

Resolution: Fixed

Looks good :-)

Commited to http://svn.apache.org/repos/asf/incubator/public/samples/site/

Many Thanks

Robert

> Add sample podling web site
> ---
>
> Key: INCUBATOR-28
> URL: http://issues.apache.org/jira/browse/INCUBATOR-28
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Craig Russell
>Priority: Minor
> Attachments: INCUBATOR-28.txt
>
>
> A sample web site for podlings is provided, with commonly needed web pages.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Fwd: [VOTE] Add Rupert Smith as a Qpid Committer

[Marnie McCormack]

fyi

-- Forwarded message --
From: Marnie McCormack <[EMAIL PROTECTED]>
Date: Mar 6, 2007 11:18 AM
Subject: [VOTE] Add Rupert Smith as a Qpid Committer
To: qpid-dev@incubator.apache.org

I'd like to propose the addition of Rupert Smith as a Qpid committer.

He has contributed extensively on the .NET client and also to the Java code,
both in code and mailing list terms.

This vote will stay open until COP Tues 13th March. Please cast your votes.

[ ] Add Rupert as a Qpid committer


Regards,
Marnie

Fwd: [VOTE] Add Tomas Restrepo as a Qpid Committer

[Marnie McCormack]

fyi

-- Forwarded message --
From: Marnie McCormack <[EMAIL PROTECTED]>
Date: Mar 6, 2007 11:17 AM
Subject: [VOTE] Add Tomas Restrepo as a Qpid Committer
To: qpid-dev@incubator.apache.org

I'd like to propose the addition of Tomas Restrepo as a Qpid committer.

He has contributed extensively on the .NET client, both in code and mailing
list terms.

This vote will stay open until COP Tues 13th March. Please cast your votes.

[ ] Add Tomas as a Qpid committer


Regards,
Marnie

Fwd: [VOTE] Add Kevin Smith as a Qpid Committer

[Marnie McCormack]

fyi

-- Forwarded message --
From: Marnie McCormack <[EMAIL PROTECTED]>
Date: Mar 6, 2007 11:23 AM
Subject: [VOTE] Add Kevin Smith as a Qpid Committer
To: qpid-dev@incubator.apache.org

I'd like to propose the addition of Kevin Smith as a Qpid committer.

He has contributed significantly on the Java Broker & Client (particularly
in the thorny area of SSL/Config), both in code and mailing list terms.

This vote will stay open until COP Tues 13th March. Please cast your votes.

[ ] Add Kevin as a Qpid committer


Regards,
Marnie

Re: [RESULT] Add Rupert Smith as a Qpid Committer

[Cliff Schmidt]

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:

Thus, Rupert Smith should now be created as a committer on the Qpid project.

Cliff - is this something you can action from a practical perspective please
? If I can do it please let me know.


Just forwarded an old email I sent to qpid-dev with instructions for
the new committers and the PPMC.

Cliff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Tomas Restrepo as a Qpid Committer

[Cliff Schmidt]

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:

All,

This vote closed on Tuesday night and the result is as follows:

Votes Cast:

9+
0-

Thus, Tomas Restrepo should now be created as a committer on the Qpid
project.


Although this vote closed several weeks ago, I'm adding my +1 as one
of the mentors and a member of the Incubator PMC.

Cliff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Kevin Smith as a Qpid Committer

[Cliff Schmidt]

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:

All,

This vote closed on Tuesday night and the result is as follows:

Votes Cast:

6+
0-

Thus, Kevin Smith should now be created as a committer on the Qpid project.


Although this vote closed several weeks ago, I'm adding my +1 as the
mentor and member of the Incubator PMC.

Cliff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Rupert Smith as a Qpid Committer

[Cliff Schmidt]

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:

All,

This vote closed on Tuesday night and the result is as follows:

Votes Cast:

9+
0-

Thus, Rupert Smith should now be created as a committer on the Qpid project.


Although this vote closed several weeks ago, I'm adding my +1 as the
mentor and member of the Incubator PMC.

Cliff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Kevin Smith as a Qpid Committer

[Paul Fremantle]

+1 from me.

Paul

On 4/10/07, Cliff Schmidt <[EMAIL PROTECTED]> wrote:

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> All,
>
> This vote closed on Tuesday night and the result is as follows:
>
> Votes Cast:
>
> 6+
> 0-
>
> Thus, Kevin Smith should now be created as a committer on the Qpid project.

Although this vote closed several weeks ago, I'm adding my +1 as the
mentor and member of the Incubator PMC.

Cliff




--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Rupert Smith as a Qpid Committer

[Paul Fremantle]

+1 from me.

Paul

On 4/10/07, Cliff Schmidt <[EMAIL PROTECTED]> wrote:

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> All,
>
> This vote closed on Tuesday night and the result is as follows:
>
> Votes Cast:
>
> 9+
> 0-
>
> Thus, Rupert Smith should now be created as a committer on the Qpid project.

Although this vote closed several weeks ago, I'm adding my +1 as the
mentor and member of the Incubator PMC.

Cliff




--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Tomas Restrepo as a Qpid Committer

[Paul Fremantle]

+1 from me

Paul

On 4/10/07, Cliff Schmidt <[EMAIL PROTECTED]> wrote:

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> All,
>
> This vote closed on Tuesday night and the result is as follows:
>
> Votes Cast:
>
> 9+
> 0-
>
> Thus, Tomas Restrepo should now be created as a committer on the Qpid
> project.

Although this vote closed several weeks ago, I'm adding my +1 as one
of the mentors and a member of the Incubator PMC.

Cliff




--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Tomas Restrepo as a Qpid Committer

[Carl Trieloff]

Please could a IPMC member help us with the IPMC 3rd vote for this committer

Carl.



Paul Fremantle wrote:

+1 from me

Paul

On 4/10/07, Cliff Schmidt <[EMAIL PROTECTED]> wrote:

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> All,
>
> This vote closed on Tuesday night and the result is as follows:
>
> Votes Cast:
>
> 9+
> 0-
>
> Thus, Tomas Restrepo should now be created as a committer on the Qpid
> project.

Although this vote closed several weeks ago, I'm adding my +1 as one
of the mentors and a member of the Incubator PMC.

Cliff







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Rupert Smith as a Qpid Committer

[Carl Trieloff]

Please could a IPMC member help us with the IPMC 3rd vote for this committer

Carl.


Paul Fremantle wrote:

+1 from me.

Paul

On 4/10/07, Cliff Schmidt <[EMAIL PROTECTED]> wrote:

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> All,
>
> This vote closed on Tuesday night and the result is as follows:
>
> Votes Cast:
>
> 9+
> 0-
>
> Thus, Rupert Smith should now be created as a committer on the Qpid 
project.


Although this vote closed several weeks ago, I'm adding my +1 as the
mentor and member of the Incubator PMC.

Cliff







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Kevin Smith as a Qpid Committer

[Carl Trieloff]

Please could a IPMC member help us with the IPMC 3rd vote for this committer

Carl.


Paul Fremantle wrote:

+1 from me.

Paul

On 4/10/07, Cliff Schmidt <[EMAIL PROTECTED]> wrote:

On 3/15/07, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> All,
>
> This vote closed on Tuesday night and the result is as follows:
>
> Votes Cast:
>
> 6+
> 0-
>
> Thus, Kevin Smith should now be created as a committer on the Qpid 
project.


Although this vote closed several weeks ago, I'm adding my +1 as the
mentor and member of the Incubator PMC.

Cliff







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Rupert Smith as a Qpid Committer

[William A. Rowe, Jr.]

Carl Trieloff wrote:
> 
> Please could a IPMC member help us with the IPMC 3rd vote for this
> committer

I presume the Qpid PPMC raised no objections.  +1, welcome Rupert.

Bill

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Kevin Smith as a Qpid Committer

[William A. Rowe, Jr.]

Carl Trieloff wrote:
> 
> Please could a IPMC member help us with the IPMC 3rd vote for this
> committer

I presume the Qpid PPMC raised no objections.  +1, welcome Kevin.

Bill

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RESULT] Add Tomas Restrepo as a Qpid Committer

[William A. Rowe, Jr.]

Carl Trieloff wrote:
> 
> 
> Please could a IPMC member help us with the IPMC 3rd vote for this
> committer


I presume the Qpid PPMC raised no objections.  +1, welcome Tomas.

Bill

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT] [VOTE] Add Tomas Restrepo as a Qpid Committer

[Cliff Schmidt]

The Qpid PPMC already passed their vote in favor of making Tomas a
committer, but this email is to indicate that the vote is now official
with the following three +1s from Incubator PMC members (and no other
IPMC votes):

Paul Fremantle
William Rowe
Cliff Schmidt

Congratulations, Tomas.  I will now send the formal request to root to
set up your account.  Sorry for the mix-up with the delay in getting
the IPMC votes.

Cliff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT][VOTE] Add Rupert Smith as a Qpid Committer

[Cliff Schmidt]

The Qpid PPMC already passed their vote in favor of making Rupert a
committer, but this email is to indicate that the vote is now official
with the following three +1s from Incubator PMC members (and no other
IPMC votes):

Paul Fremantle
William Rowe
Cliff Schmidt

Congratulations, Rupert.  I will now send the formal request to root
to set up your account.  Sorry for the mix-up with the delay in
getting the IPMC votes.

Cliff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT][VOTE] Add Kevin Smith as a Qpid Committer

[Cliff Schmidt]

The Qpid PPMC already passed their vote in favor of making Kevin a
committer, but this email is to indicate that the vote is now official
with the following three +1s from Incubator PMC members (and no other
IPMC votes):

Paul Fremantle
William Rowe
Cliff Schmidt

Congratulations, Kevin.  I will now send the formal request to root to
set up your account.  Sorry for the mix-up with the delay in getting
the IPMC votes.

Cliff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Blue Sky Distance Collaboration System-Wish to add

[Niclas Hedhman]

On Tuesday 24 July 2007 15:11, Ting Peng wrote:
> For this is our first candidate project to Apache Foundation. We are
> grateful for your ideas!
>
> Waiting for your advice!

Where does the project live at the moment?? Has this been developed in a open 
fashion, i.e. mailing lists to communicate design and discussions? If so, are 
those records and codebase available for review?

I don't want to sound too negative, but I can imagine that a continue of this 
effort at ASF will be riddled with communication problems as a homogenous 
team now has to open up to running everything through public mailing lists 
possibly in a language everyone doesn't master.


Cheers
-- 
Niclas Hedhman, Software Developer

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Phil Steitz]

Roy T. Fielding wrote:
[Moved from the PMC list -- folks have got to stop proposing such
things on the wrong list.]
A long time ago, the name PMC was created in an attempt to genericize
the way that the Apache Group operated, using terminology that would be
easily understood by a judge or IRS inspector.  Unfortunately, the
name seems to have overwhelmed its history.  I described that in a
message to the members on March 12, 2003, which I'll include below.
However, I've been so overwhelmed with issues/fires this past year
that I never got around to fixing it.
Geir has proposed that we create practice PMCs (a.k.a. subprojects)
as part of incubation, and that we call them "Project Committers"
lists rather than PMCs.  I am +1 on the notion in general, but I
would prefer to call them core groups instead.  My rationale is that
"committer" privilege is a mechanism that we frequently give to
people on the basis of what they are planning to do, whereas the
core group are those people who have earned long-term voting rights
whether or not they happen to code.  Jakarta got into a weird state
wherein committer == voter and commit-access was given out like candy,
thus leading to the notion that committers run ASF projects.  I don't
believe it is appropriate to link voting with cvs access.
Are you proposing that committers who are not PMC members or "Project 
Committers" should not have voting rights?

The key thing to note is that voting is a decision-making process
and we want that decision to be an ASF decision.  Furthermore, we want
the decision to be made as close to the volunteers doing the work as
possible, preferably by the volunteers themselves, whatever that work
may be.
Seems to conflict with the statement above (unless I misunderstood).

The ability to make ASF decisions starts with the board and is
delegated to officers and their associated committees.  Anyone casting
binding votes (meaning votes that are counted toward making a decision)
must be listed as a member of the committee on which they are voting,
even if their votes are limited to a subcommittee.  Therefore, my
preference is for a fluid structure of incubating subprojects wherein
every voter is listed as being in one or more core groups and the
entire set of voters is listed as the incubator pmc.
I am aware that this would mean incubating projects would be able to
vote themselves out of incubation.  I think that if such a project had
their shit together to the extent that they could run such a vote and
get it past the majority of incubator members, then they no longer
need to be incubated.
Roy
Thanks for sharing the post below. This clears up a few things for me at 
least.  At the risk of appearing dense, however, I am still not 
understanding exactly why "The PMC must equal the voters on a given 
project"  It seems to me that it *might* be possible (safe?) to have 
all *decisions* approved by the PMC, while the process (voting) to 
arrive at those decisions could include [binding?] input from non-PMC 
members. What am I missing?

Phil
===
From: "Roy T. Fielding" <[EMAIL PROTECTED]>
Date: Wed Mar 12, 2003  9:46:04  PM America/Los_Angeles
To: members   at  apache.org
Subject: PMCs gone wild
I am getting a bit frustrated at what appears to be a serious attitude
problem within the Apache projects.  A lot of people seem to wait around
until "the man" makes a decision, sometimes doing nothing other than
gripe about the lack of concern that "the man" has for their pet issue,
or simply believing that they are not allowed to do anything until
"the man" says it's okay to start.  I am not just talking about the
newer Jakarta projects: this attitude has become endemic throughout
the ASF, and folks are far-too-frequently suggesting that decisions
should be relegated to "subprojects" or that projects should be
"managed" by only a subset of the voters.
"the man" is usually their perception of a PMC as some other-worldly
land where benevolent beings ponder deep issues and create solutions.
[Sometimes "the man" is the ASF board, but that is very rare -- most
people have the sense to realize that the board's solution to a
squeeky wheel is to yank it off, throw it away, and install a new
wheel -- which usually isn't the effect desired by most wheels.]
I think I know what is causing this attitude, and sadly it points
back to one of the decisions I thought was a good idea when we were
crafting the ASF bylaws.  You have to understand some background
on that first...
The ASF bylaws were crafted by Drew Wright using a Delaware
nonprofit template and a ton of input from more than a year of
discussion amongst the Apache Group (circa 1998), discussion at
the post-ApacheCon'98 group meeting, and yet more discussion on the
old apache-core mailing list.  Our goal was to create a legitimate
corporate infrastructure around Apache without changing how Apache
decisions were made or the volunteer nature of the foundation.
By legitimate, I mean something that w

Re: Add 'practice' PMC structure to projects in incubation

[Sam Ruby]

Roy T. Fielding wrote:

Geir has proposed that we create practice PMCs (a.k.a. subprojects)
as part of incubation, and that we call them "Project Committers"
lists rather than PMCs.  I am +1 on the notion in general, but I
would prefer to call them core groups instead.  My rationale is that
"committer" privilege is a mechanism that we frequently give to
people on the basis of what they are planning to do, whereas the
core group are those people who have earned long-term voting rights
whether or not they happen to code.  Jakarta got into a weird state
wherein committer == voter and commit-access was given out like candy,
thus leading to the notion that committers run ASF projects.  I don't
believe it is appropriate to link voting with cvs access.
I know of a case where an individual identified a code base that he 
avowed that he would never contribute to but active sought voting 
privileges to that codebase so that he could block items that he felt 
was harmful.  To me, requiring people to actually participate in the 
solution to problems that they identify is a good check and balance.

I also can't imagine a more profound way of voting on the direction that 
a project can take than by actually doing the work.  In fact, that is 
the essense of what at Apache appeals to me: whenever possible the 
responsibility for any given item is pushed down to the people who 
actually are doing the work.

Teasing apart these two concepts is difficult.  Let's face it: any 
formal system that we try to apply to the real world is going to have 
anomolies.  Officers who aren't members.  Members who contribute in ways 
other than code.

I for one, would rather we not focus on the exceptions, and try to make 
things more uniform - even if that ends up with giving people who have 
the right to vote the right to commit.  After all, if we trust them 
enough to vote, we should trust them enough to NOT commit changes that 
they are not qualified to make.

- Sam Ruby

P.S.  Can somebody explain to me why a number of core members of the 
HTTPD community feel so threatened by the non-HTTPD PMCS (generally 
lumped into the generic category of "Jakarta") that they feel the need 
to bash it at every opporunity?  It gets tiresome.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Berin Lautenbach]

Roy,

Thankyou.  Read with great interest, and it put a few things into 
perspective.  Particularly the fact that to me the Practice PMCs made no 
sense from my perspective (based in the XML project's world).  I think I 
now understand why.

Couple of things came to mind whilst I was ruminating on the contents.

Firstly - am not so sure that changing the name of PMC to Core Group is 
either necessary or sufficient to fix things.  I note that you mention 
the codification of the requirements placed on the Core Group into a 
universal Apache Guidelines document.  For this I am absolutely +1 - one 
of the biggest problems facing the PMCs is a lack of clear understanding 
of what is required.  The only way to overcome that problem is to 
clearly document requirements.  E-mails going over the issues every 6-12 
months 'aint going to cut it.  I suspect if there was a clear set of 
guidelines and a board that was brutal about enforcing them then things 
might change.

Secondly, given the original intent of the concept of a PMC, I am 
curious as to why the board permitted umbrella PMCs such as XML and 
Jakarta.  You can change the name of PMC to Core Group, and put strict 
guidelines in place, but the spirit what you want is not going to happen 
until everyone on a given PMC is on the -dev lists that the PMC is 
responsible for.  That sounds fair, but is impractical for the PMCs of 
the large, divided projects.

So a possible suggestion.  FWIW.  Maybe a step towards where things need 
to be?  (Evolution rather than revolution?)

Can we turn a project such as XML into a federation of projects rather 
than one big project?  In terms of infrastructure (web site, mailing 
lists, cvs etc.) leave it as it is, with maybe a bunch of volunteers 
from each member project helping out with those items.

Each sub-project gets turned into a formal TLP, but not in the sense 
that is implied today (where TLP = web site, = mailing lists etc.). 
Rather the TLPs simply report to the board, have their own PMCs and are 
responsible for the code decisions.  That puts the decision making 
requirements back where I think the board wants it to be.  With a small 
core group of individuals responsible for each particular code base.

It also helps the Foundation scale as it reduces the requirements placed 
on infrastructure@ (new web sites etc.)

As I said - FWIW.

Cheers,
Berin


Roy T. Fielding wrote:
[Moved from the PMC list -- folks have got to stop proposing such
things on the wrong list.]
A long time ago, the name PMC was created in an attempt to genericize
the way that the Apache Group operated, using terminology that would be
easily understood by a judge or IRS inspector.  Unfortunately, the
name seems to have overwhelmed its history.  I described that in a
message to the members on March 12, 2003, which I'll include below.
However, I've been so overwhelmed with issues/fires this past year
that I never got around to fixing it.
Geir has proposed that we create practice PMCs (a.k.a. subprojects)
as part of incubation, and that we call them "Project Committers"
lists rather than PMCs.  I am +1 on the notion in general, but I
would prefer to call them core groups instead.  My rationale is that
"committer" privilege is a mechanism that we frequently give to
people on the basis of what they are planning to do, whereas the
core group are those people who have earned long-term voting rights
whether or not they happen to code.  Jakarta got into a weird state
wherein committer == voter and commit-access was given out like candy,
thus leading to the notion that committers run ASF projects.  I don't
believe it is appropriate to link voting with cvs access.
The key thing to note is that voting is a decision-making process
and we want that decision to be an ASF decision.  Furthermore, we want
the decision to be made as close to the volunteers doing the work as
possible, preferably by the volunteers themselves, whatever that work
may be.
The ability to make ASF decisions starts with the board and is
delegated to officers and their associated committees.  Anyone casting
binding votes (meaning votes that are counted toward making a decision)
must be listed as a member of the committee on which they are voting,
even if their votes are limited to a subcommittee.  Therefore, my
preference is for a fluid structure of incubating subprojects wherein
every voter is listed as being in one or more core groups and the
entire set of voters is listed as the incubator pmc.
I am aware that this would mean incubating projects would be able to
vote themselves out of incubation.  I think that if such a project had
their shit together to the extent that they could run such a vote and
get it past the majority of incubator members, then they no longer
need to be incubated.
Roy

===
From: "Roy T. Fielding" <[EMAIL PROTECTED]>
Date: Wed Mar 12, 2003  9:46:04  PM America/Los_Angeles
To: members   at  apache.org
Subject: PMCs gone wild
I am getting a

Re: Add 'practice' PMC structure to projects in incubation

[Nicola Ken Barozzi]

Phil Steitz wrote:
...
Are you proposing that committers who are not PMC members or "Project 
Committers" should not have voting rights?
On the PMC list it has come out that we were misunderstanding each other 
over the term "binding votes".

Let me explain what we said.

Some talked about a vote made by committers (==ones with CVS access) on 
an incubating project, and called

 binding votes == votes by ones with CVS karma
 non-binding votes == votes by lurkers
Then it was replied that only PMC members can cast "binding" votes, and 
that these are thus all non-binding.

Why?

Because only the PMC members can make decisions on behalf of the 
foundation, and thus are the only ones who's votes are "binding".

So then it was said that it doesn't make sense, because the Incubator 
PMC cannot decide knowingly about what committers an incubating project 
wants.

So the only way out of this catch22 is that all project committers are 
PMC members (and hence the core-group proposal).  :-)

--
Nicola Ken Barozzi   [EMAIL PROTECTED]
- verba volant, scripta manent -
   (discussions get forgotten, just code remains)
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Nicola Ken Barozzi]

Sam Ruby wrote:
Roy T. Fielding wrote:
...
Jakarta got into a weird state
wherein committer == voter and commit-access was given out like candy,
thus leading to the notion that committers run ASF projects.  I don't
believe it is appropriate to link voting with cvs access.
...
P.S.  Can somebody explain to me why a number of core members of the 
HTTPD community feel so threatened by the non-HTTPD PMCS (generally 
lumped into the generic category of "Jakarta") that they feel the need 
to bash it at every opporunity?  It gets tiresome.
I don't see the bashing you are talking about in these comments, but I 
tool sometimes feel some diffidence from either side, which is normal 
given the lack of discussion about these issues between the communities 
in these years.

Some very interesting, balanced and fruitful discussion is going on here 
between members of projects all over Apache. Finally we are all 
discussing on these things and getting somewhere, and I'm positive that 
things will soon change. :-)

--
Nicola Ken Barozzi   [EMAIL PROTECTED]
- verba volant, scripta manent -
   (discussions get forgotten, just code remains)
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Nicola Ken Barozzi]

Roy T. Fielding wrote:
...
The ability to make ASF decisions starts with the board and is
delegated to officers and their associated committees.  Anyone casting
binding votes (meaning votes that are counted toward making a decision)
must be listed as a member of the committee on which they are voting,
even if their votes are limited to a subcommittee.  Therefore, my
preference is for a fluid structure of incubating subprojects wherein
every voter is listed as being in one or more core groups and the
entire set of voters is listed as the incubator pmc.
Having had basically all opinions about this in the past years, and 
having been on diverse projects, I have come to the conclusion that I 
basically agree.

In particular, the Incubator PMC has been since the start an "umbrella 
PMC", similar to what Jakarta and XML, mainly because it cannot easily 
be made in a different way. This has made me see the shortcoming of the 
approach in clearer detail.

These months of incubations have showed us in clear evidence some basic 
facts that cannot be forgotten. The funny thing is that it's what we all 
know, but applied to the incubator it was hard to understand.

 1 - oversight must be done by the as many people as possible, just
 like more eyes see more bugs -> more mentors
 2 - the "management" of a project must be done by those that run
 the project day by day -> PMC==committers
 3 - it's ok to create "subprojects" in a project as long as the
 project remains united as one in decision making -> core groups
Let's make for example Cocoon, which can IMHO take advantage right now 
of this way of doing things.

Cocoon has already a set of committers that are all on the PMC.
There are two projects with close ties to Cocoon, that are Forrest and 
Lenya, Forrest under XML and Lenya in Incubation. Let's assume that 
Forrest goes under Cocoon and that Lenya exits incubation.

Cocoon as a project could as well consist of all long-stating committers 
of these codebases, and take all decisions together. This is already in 
part a fact, as the Cocoon PMC has started to vote a Lenya release as 
they feel part of the project, and Cocoon committers have access to Forrest.

Then there would be three core groups, one for Cocoon, one for Lenya and 
one for Forrest. There would this be a single project, a single PMC, and 
just a partitioning of competence on parts of code.

There is only one thing that would *really* change and that has not been 
done till now.

Committers could be given commit access long before having project 
member status, and would thus be able to commit but not vote. This makes 
it possible to keep a high bar for membership of the project but a lower 
bar for committing.

Is this possible/wanted?

I am aware that this would mean incubating projects would be able to
vote themselves out of incubation.  I think that if such a project had
their shit together to the extent that they could run such a vote and
get it past the majority of incubator members, then they no longer
need to be incubated.
This is a possibility, that is ok for me.

Another possibility would be to define in the rules that the incubating 
project cannot voe itself out.

--
Nicola Ken Barozzi   [EMAIL PROTECTED]
- verba volant, scripta manent -
   (discussions get forgotten, just code remains)
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Roy T. Fielding]

Secondly, given the original intent of the concept of a PMC, I am 
curious as to why the board permitted umbrella PMCs such as XML and 
Jakarta.
The board did not create umbrella PMCs -- XML was Xerces and Jakarta
was Tomcat/Watchdog.  They grew beyond that because their names implied
more, and nobody wanted to slow them down just because they had moved
beyond their original scope.  In fact, I had to threaten to shut them
down before the groups were even willing to restate their charters to
reflect what they had grown into.
Ultimately, it is very difficult (and often unreasonable) to insist that
a group of volunteers adopt a more rational set of self-management
principles, even when they run smack into the problems caused by their
own disorganization.  Status quo is such a warm and fuzzy place, and
most people just want to code on their own projects.  Besides, everyone
likes growth, and very few people like restructuring.
What some folks fail to understand is that a hierarchical structure,
like XML and Jakarta, does not reduce the workload of the board at all.
In fact, in my entire history on the board, I never once had to deal
directly with an issue on any of the single-level projects -- those
projects have always been self-governing because everyone in them
knows *they* are responsible for making the decision, not some other
group in "management".
Roy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Leo Simons]

Nicola Ken Barozzi wrote:

Committers could be given commit access long before having project 
member status, and would thus be able to commit but not vote. This 
makes it possible to keep a high bar for membership of the project but 
a lower bar for committing.

Is this possible/wanted? 
I think I don't like it. If you're committing, you're doing the work. If 
you're
doing the work, you should have a say in everything that concerns your
work (meritocracy).

Yes, there is the "chicken-egg" problem where people are planning to do
the work, but haven't yet. Should they receive commit access but be denied
the right to vote? Don't think so. Its about trust...if you give 'em an 
account,
you trust 'em to not misuse voting privs either. If they violate that 
trust (rare
occassion!), its often easier to coach them as equals rather than from 
the top
down.

Its also about management...with commit priviledge comes management
responsibility. Don't want to take your share of the 'management overhead'?
Then you're not getting commit privs, either. I love that.
IMV, most apache people are coders at heart, and only get involved with
all the 'management' concerns when they are somehow forced to (like when
no-one does it for them but its needed anyway).
(This is also the 'code smell' surrounding incubator: many of the people
doing the coding @ incubator are not involved with doing the incubating,
and its the other way around as well.)
in summary:

+1 to a "core group" / "practice PMC" / "committer list" for incubating 
projects
+1 to self-management
-0 on all p&p which seperates priviledge from responsibility

back to my corner!

- Leo



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Nicola Ken Barozzi]

Leo Simons wrote:

Nicola Ken Barozzi wrote:

Committers could be given commit access long before having project 
member status, and would thus be able to commit but not vote. This 
makes it possible to keep a high bar for membership of the project but 
a lower bar for committing.

Is this possible/wanted? 
I think I don't like it. If you're committing, you're doing the work.
If you're doing the work, you should have a say in everything that
concerns your work (meritocracy).
This sets a bar higher for being able to start to commit.

I'm fine with it, as long as commit access/PMC membership is not handed 
out like candy.

There are groups here that AFAIK are much faster in giving commit access 
than others, so this would take their ways in consideration.

--
Nicola Ken Barozzi   [EMAIL PROTECTED]
- verba volant, scripta manent -
   (discussions get forgotten, just code remains)
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Leo Simons]

Noel made an interesting suggestion on the PMC list:
---
Alternatively, the PPMC could consist of the Incubator PMC, the destination
PMC (in cases where there is one), and project Committers.  In that case,
there is a single streamlined process, without additional interconnects.
This does have the advantage of providing PMC education to committers who
will someday have to form a PMC.  And it preserves the direct legal
oversight of the PMC.
	--- Noel

---
I think this is real nice. Streamlined!
We'll have to make clear to everyone that the final authority
(legally, the only authority) always remains the Incubator PMC,
but I see no problem with allowing the Incubator PMC to reach
decisions on a mailing list other than [EMAIL PROTECTED], if it so
pleases.
cheers!

- LSD



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Jim Jagielski]

On Nov 23, 2003, at 10:10 AM, Nicola Ken Barozzi wrote:
There is only one thing that would *really* change and that has not 
been done till now.

Committers could be given commit access long before having project 
member status, and would thus be able to commit but not vote. This 
makes it possible to keep a high bar for membership of the project but 
a lower bar for committing.

Is this possible/wanted?

I think the problem here is when:

   1. There is a significant delay between someone becoming a committer 
and
  a member
   2. When the committer has no desire to be a member.

The below is just for illustration purposes... it's NOT the way
it is, but is a good way to explain what we mean by "bar for
membership" (or whatever). Say to become a member you need 10
ASF points. My own personal feeling is that the number of
points "required" for committer-ship should be like 7
or maybe even 8. That is, the "higher bar" is for commit
privs, and *that* is a real accomplishment, and a significant
indication of trust, etc... ASF membership is a little
hop from there.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Add 'practice' PMC structure to projects in incubation

[Noel J. Bergman]

Nicola Ken Barozzi wrote:

> Committers could be given commit access long before having project
> member status, and would thus be able to commit but not vote. This
> makes it possible to keep a high bar for membership of the project but
> a lower bar for committing.
>
> Is this possible/wanted?

As I understand it, this was the initial structure.  A Contributor posts a
patch, the patch is reviewed and committed.  At some point, a frequent
Contributor is offered the opportunity to become a Committer.  The Committer
is allowed to commit a change, but the PMC is still responsible to review
the commit.  At some point, hopefully not too far down the pike, the
Committer is voted into the PMC.  Until that happens, the Committer does not
have a binding vote.  Cannot have a binding vote, because to have one
outside of the legal structure would expose the Committer.

Leo Simons wrote:
> I think I don't like it. If you're committing, you're doing the work.
> If you're doing the work, you should have a say in everything that
> concerns your work (meritocracy).

Because the PMC is responsible for reviewing every change (and because we
have SCM), it allows someone to be granted commit karma before they have
earned sufficient trust to be entrusted with managing the project.  If you
have an active newcomer, the process can be significantly hampered by having
to go through e-mailed patches, so you can grant commit karma to streamline
the process, without having to go straight to PMC status.

This is a simple structure.  It  simplifies a lot of the various sets of
rules and interactions, and it explains some of the oddities present in our
current conflicting rule sets.  My understanding is that this is the way
that the ASF was designed to work, but things got bent during expansion.
Ironically, the original "rules" scale better, since the PMC oversight
requirement cannot be removed.

--- Noel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Phil Steitz]

Noel J. Bergman wrote:
Nicola Ken Barozzi wrote:


Committers could be given commit access long before having project
member status, and would thus be able to commit but not vote. This
makes it possible to keep a high bar for membership of the project but
a lower bar for committing.
Is this possible/wanted?


As I understand it, this was the initial structure.  A Contributor posts a
patch, the patch is reviewed and committed.  At some point, a frequent
Contributor is offered the opportunity to become a Committer.  The Committer
is allowed to commit a change, but the PMC is still responsible to review
the commit.  At some point, hopefully not too far down the pike, the
Committer is voted into the PMC.  Until that happens, the Committer does not
have a binding vote.  Cannot have a binding vote, because to have one
outside of the legal structure would expose the Committer.
Can you explain exactly what you mean by the last sentence above?

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Add 'practice' PMC structure to projects in incubation

[Noel J. Bergman]

> > At some point, hopefully not too far down the pike, the
> > Committer is voted into the PMC.  Until that happens,
> > the Committer does not have a binding vote.  Cannot
> > have a binding vote, because to have one outside of the
> > legal structure would expose the Committer.

> Can you explain exactly what you mean by the last sentence above?

As I understand the situation, the ASF Bylaws are setup in a specific manner
so as to provide legal protection in the event that someone should want to
file a lawsuit.  The mechanism that affords that protection is the PMC.  For
more detail, see Roy's message:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
.org&msgNo=2642.

When the James project was initially looking at TLP status, Nicola Ken
forwarded a message from Roy that included a comment to the effect that if
Committers understood their legal exposure, they would demand TLP status,
rather than needing to be pushed into it.  At least that is my recollection
of it.  I don't believe that I really understood the whole issue until the
past few days, and I am only assuming that my understanding of it is correct
now.  But if I am right, the upshot is that in order to be protected, you
either cannot have a binding vote, or you have to be on the PMC.

Hopefully, Roy will either affirm this understanding, or correct my error.

--- Noel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Greg Stein]

On Tue, Nov 25, 2003 at 11:43:33PM -0500, Noel J. Bergman wrote:
>...
> When the James project was initially looking at TLP status, Nicola Ken
> forwarded a message from Roy that included a comment to the effect that if
> Committers understood their legal exposure, they would demand TLP status,
> rather than needing to be pushed into it.  At least that is my recollection
> of it.

Correct.

The premise here is that a TLP is "closer" to the code than any kind of
umbrella thing could ever be. Thus, the notion of oversight and,
therefore, protection is much easier to establish.

> I don't believe that I really understood the whole issue until the
> past few days, and I am only assuming that my understanding of it is correct
> now.  But if I am right, the upshot is that in order to be protected, you
> either cannot have a binding vote, or you have to be on the PMC.

Correct.

If you don't have a binding vote, then you are not responsible. The people
*with* the binding votes are. If you make a commit, then they have the
right to change it however they like, or to leave it. But it is at *their*
discretion.

And the theory is: by definition, the only binding votes [regarding a
codebase] come from people on the PMC.

Therefore, if you really want to have a say in the code that you're
working on, then you want to be part of the PMC.

All work is protected, as long as the above rules are followed. Things
break down when non-PMC committers have votes, or the PMC is not
exercising their discretion/oversight. In those cases, the committer is
"acting on their own" and cannot be covered by the ASF.

Note that while the *work* is protected, the ASF is only obligated to
(legally) indemnify Directors, officers, and Members (see section 12.1 of
the Bylaws). While the ASF may choose to defend PMC members, it is not
required to do so. Thus, any committer "should" want to seek out
Membership in the ASF or to become a PMC Chair (Chairs are officers). Also
note that the ASF doesn't have obligations towards non-PMC committers.

Cheers,
-g

-- 
[EMAIL PROTECTED] ... ASF Chairman ... http://www.apache.org/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Add 'practice' PMC structure to projects in incubation

[Conor MacNeill]

hi Greg,

Maybe it would be a good idea to forward this or somethign similar to the
committers list. I'd say there is a number of a committers who are not
aware of these legal issues.

Whaddayareckon?

Conor



> If you don't have a binding vote, then you are not responsible. The people
> *with* the binding votes are. If you make a commit, then they have the
> right to change it however they like, or to leave it. But it is at *their*
> discretion.
>
> And the theory is: by definition, the only binding votes [regarding a
> codebase] come from people on the PMC.
>
> Therefore, if you really want to have a say in the code that you're
> working on, then you want to be part of the PMC.
>
> All work is protected, as long as the above rules are followed. Things
> break down when non-PMC committers have votes, or the PMC is not
> exercising their discretion/oversight. In those cases, the committer is
> "acting on their own" and cannot be covered by the ASF.
>
> Note that while the *work* is protected, the ASF is only obligated to
> (legally) indemnify Directors, officers, and Members (see section 12.1 of
> the Bylaws). While the ASF may choose to defend PMC members, it is not
> required to do so. Thus, any committer "should" want to seek out
> Membership in the ASF or to become a PMC Chair (Chairs are officers). Also
> note that the ASF doesn't have obligations towards non-PMC committers.
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add 'practice' PMC structure to projects in incubation

[Nicola Ken Barozzi]

Conor MacNeill wrote:
hi Greg,

Maybe it would be a good idea to forward this or somethign similar to the
committers list. I'd say there is a number of a committers who are not
aware of these legal issues.
Whaddayareckon?
Add members to it too, please.

--
Nicola Ken Barozzi   [EMAIL PROTECTED]
- verba volant, scripta manent -
   (discussions get forgotten, just code remains)
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Fwd: [VOTE] Add Øyvind Bakksjø as a Derby committer]

[Daniel John Debrunner]

One more commiter vote notification to general@incubator.apache.org

Dan.

 Original Message 
Subject: [VOTE] Add Øyvind Bakksjø as a Derby committer
Date: Sat, 02 Jul 2005 07:50:17 -0700
From: Daniel John Debrunner <[EMAIL PROTECTED]>
Reply-To: Derby Development 
To: derby-dev 

Please vote on making Øyvind a committer on the Derby project. The
derby-ppmc believe Øyvind will be a great benefit to Derby.

[  ] - Add Øyvind Bakksjø <[EMAIL PROTECTED]> as a Derby committer

---

My vote: +1

Dan.





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT] [VOTE] Add Øyvind Bakksjø as a Derby committer

[Daniel John Debrunner]

Daniel John Debrunner wrote:

> Please vote on making Øyvind a committer on the Derby project. The
> derby-ppmc believe Øyvind will be a great benefit to Derby.
> 
> [  ] - Add Øyvind Bakksjø <[EMAIL PROTECTED]> as a Derby committer
> 

Vote passes, fourteen (14) +1 votes, no other votes.

Øyvind is now a committer on Derby, Derby PPMC members will ensure
Øyvind is hooked up with the right karma etc.

Dan.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (INCUBATOR-13) Add new content to faq

[Gavin (JIRA)]

Add new content to faq
--

 Key: INCUBATOR-13
 URL: http://issues.apache.org/jira/browse/INCUBATOR-13
 Project: Incubator
Type: Improvement
Reporter: Gavin
Priority: Minor


Mentioned on list, extra bullet points added to clarify initial code status and 
ownership.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (INCUBATOR-13) Add new content to faq

[Gavin (JIRA)]

 [ http://issues.apache.org/jira/browse/INCUBATOR-13?page=all ]

Gavin updated INCUBATOR-13:
---

Attachment: faq.xml.diff

Added points raised on list. Hope this is correct and in a suitable place, 
please check before comitting.

> Add new content to faq
> --
>
>  Key: INCUBATOR-13
>  URL: http://issues.apache.org/jira/browse/INCUBATOR-13
>  Project: Incubator
> Type: Improvement
> Reporter: Gavin
> Priority: Minor
>  Attachments: faq.xml.diff
>
> Mentioned on list, extra bullet points added to clarify initial code status 
> and ownership.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (INCUBATOR-13) Add new content to faq

[Jean T. Anderson (JIRA)]

[ 
http://issues.apache.org/jira/browse/INCUBATOR-13?page=comments#action_12363525 
] 

Jean T. Anderson commented on INCUBATOR-13:
---

Committed Gavin's patch, revision 371112. For reference, I think this is the 
post his description referred to: 
http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/[EMAIL 
PROTECTED]

> Add new content to faq
> --
>
>  Key: INCUBATOR-13
>  URL: http://issues.apache.org/jira/browse/INCUBATOR-13
>  Project: Incubator
> Type: Improvement
> Reporter: Gavin
> Priority: Minor
>  Attachments: faq.xml.diff
>
> Mentioned on list, extra bullet points added to clarify initial code status 
> and ownership.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (INCUBATOR-13) Add new content to faq

[Roy T. Fielding (JIRA)]

 [ http://issues.apache.org/jira/browse/INCUBATOR-13?page=all ]

Roy T. Fielding updated INCUBATOR-13:
-

Component: site

> Add new content to faq
> --
>
>  Key: INCUBATOR-13
>  URL: http://issues.apache.org/jira/browse/INCUBATOR-13
>  Project: Incubator
> Type: Improvement
>   Components: site
> Reporter: Gavin
> Priority: Minor
>  Attachments: faq.xml.diff
>
> Mentioned on list, extra bullet points added to clarify initial code status 
> and ownership.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (INCUBATOR-13) Add new content to faq

[Roy T. Fielding (JIRA)]

 [ http://issues.apache.org/jira/browse/INCUBATOR-13?page=all ]
 
Roy T. Fielding closed INCUBATOR-13:


Resolution: Fixed

> Add new content to faq
> --
>
>  Key: INCUBATOR-13
>  URL: http://issues.apache.org/jira/browse/INCUBATOR-13
>  Project: Incubator
> Type: Improvement
>   Components: site
> Reporter: Gavin
> Priority: Minor
>  Attachments: faq.xml.diff
>
> Mentioned on list, extra bullet points added to clarify initial code status 
> and ownership.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Could you please add my id (hzeller) as a contributor

[Hans Zeller]

Hi,

We are preparing the Trafodion report to the Incubator PMC and would like
to add it to the wiki page https://wiki.apache.org/incubator/June2016.

Could you please add my wiki id, hzeller to the Contributors group, so I
can add the report?

Thanks,

Hans Zeller

How to add an incubator report to an "Immutable Page"?

[Jim Apple]

I'd like to add our incubator report for Impala[0] to the report wiki
page[1]. However, the header of that page informs me, when logged in
with my username "JimApple" that it is an "Immutable Page".

What is the procedure for getting append access to that page? I see
that sometimes people ask on this list[2] and I see that some users
have been able to append already[3], so I suspect that the page is not
immutable to everyone.

0: 
http://mail-archives.apache.org/mod_mbox/incubator-impala-dev/201607.mbox/%3CCAC-pSX1MVPGnTXy-fkXd3DdXz-U%3DFrnB4kAejyi0wv9GzsRUfw%40mail.gmail.com%3E

1: http://wiki.apache.org/incubator/August2016

2: 
http://mail-archives.apache.org/mod_mbox/incubator-general/201607.mbox/%3CCANPnQjd7jRiNSBCgpgUaPrBA1NKq_u9_3Vw5aiZKkiMtDeR44A%40mail.gmail.com%3E

3: https://wiki.apache.org/incubator/August2016?action=info

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[REQUEST] Please add PR-related item to podling graduation checklist

[Sally Khudairi]

Hello Apache Incubator team --I hope you are all well.
John Ament (copied) suggested I write to you regarding promoting a podling's 
graduation.
Would it be possible to include a line item somewhere on 
http://incubator.apache.org/guides/graduation.html along the lines of: 
> "PPMCs: please contact ASF Marketing & Publicity at press(at)apache(dot)org 
> if your project is interested in a formal press release announcing your 
> graduation."

I ask because we need enough time to prepare press releases, getting 
testimonials, editing/review process, etc. And example of a TLP press release 
is https://s.apache.org/u67z
Too often what's happening is that once the submission request to the Board 
goes out, the podling starts tweeting that they're graduating 
(incorrect/inappropriate). Or that they're up for graduation (OK, but iffy).
When the Board passes the resolution, everyone tweets. OK, fine, it's time to 
celebrate.

Then the project comes to me saying "oops: we need press..." and I wind up 
scrambling to get everything done in a timely manner so that the press release 
doesn't happen weeks after the Board passes the resolution (= no longer "news").
The past several press releases that have gone out are a result of me seeing 
that the podling's proposal has gone to board@, and me writing the VP stating, 
"I see that you're preparing to graduate. Do you want a press release? If so, 
let's work together ..."

Seeing that most podlings need a couple of weeks to pull their content together 
--particularly if soliciting supporting testimonials from the community-- 
starting our preparations as part of their graduation checklist would be hugely 
helpful.
And, even if the graduation doesn't happen for some reason, at least we're 
ready.

Thanks in advance for your consideration. I look forward to hearing from you!
Kind regards,Sally
Vice President Marketing & PublicityThe Apache Software Foundation = = = = =  
vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi

Re: How to add a committer that is not incubator.

[John D. Ament]

On Tue Feb 24 2015 at 3:36:50 AM jan i  wrote:

> Hi.
>
> Maybe a stupid question, but I cannot find the answer.
>
> If we want to add a existing committer (one with an apache ID) to our
> project as PPMC and committer, we of course have the normal vote.
>

I'm assuming that the vote was forwarded to the private list of the IPMC at
some point and you waited the standard 72 hours?


>
> If that person is not a committer of Incubator, do we then need to do
> something additional to get the person added to incubator, like call a vote
> in IPMC ?
>

Tamaya added one recently.  Other than forwarding the vote, we simply added
him to the incubator group.  No other vote, as the IPMC had clearance that
the change was happening.  As you may recall, we had a discussion a couple
months back about common auth for the incubator, implying everyone has the
same level of access to all podlings.


>
> I ask because, I know by experience (I was IPMC but not
> incubator-committer) that you need to be incubator-committer to use the GIT
> repo.
>
> thanks in advance for a short answer.
> rgds
> jan i.
>

John