Re: [PROPOSAL] Apache Click graduation

[ant elder]

On Fri, Apr 24, 2009 at 7:06 AM, Andrus Adamchik  wrote:
>> Additional concern, it does not appear that the mentors are planning to
>> be on the PMC. Why not?
>
> Why is this a concern? Mentors volunteer to do mentoring to ensure the
> project is viable and understands the Apache way, not necessarily to develop
> code. If you trace the existing Apache projects back to the incubator, I'd
> suspect 70% of them will not have their original mentors on the PMC.
>
> Andrus
> Apache Click Mentor
>

The incubator projects i've been involved in have all had at least
some of mentors stay on the PMC when graduating. It certainly wont
hurt having some extra people around who are familiar with both the
project and the ASF. In this case when the proposed PMC is so small i
can't see why you wouldn't want to add them, to avoid the problem of
needing 3 binding votes when someone is out on holiday, or even if
just to save getting bogged down in general@ debate on whether the PMC
is big enough to graduate.

It does look at little odd to enter incubation with 4 committers and
leave with only 3 on the PMC but still the original 4 are all active
enough to have just voted for graduation on the click dev list. Also,
about 10 people voted on click-dev for graduation, are any more of
those active enough to be made committers and pmc members?

What is the diversity of the three, do you all work for different companies?

   ...ant

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

Re: [PROPOSAL] Apache Click graduation

[Bob Schellink]

Hi Niall,

Niall Pemberton wrote:

Comparing the original proposal to the graduation resolution it seems
that click entered incubation with 4 committers and proposes to leave
with 3.



When the proposal was written, Ahmed Mohombe was a committer of the 
project at SourceForge, however he never actually joined the project 
at Apache because of personal health reasons.


Kind regards

Bob

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

Re: [PROPOSAL] Apache Click graduation

[Andrus Adamchik]

3 is the minimal number that is needed for a formal acceptance. So I  
see no problem with it. Click has been a successful open source  
project done the Apache way before entering Apache, so I think it is  
definitely ready to graduate now. While a possibility of a vote  
deadlock exists, it does exist for any other Apache project as well.


Interesting aspect of this though... say a PMC member X goes AWOL.  
Will it be valid for the 2 remaining members to vote another person in  
the PMC? I'd say yes, but definitely a non-standard situation...


Andrus


On Apr 24, 2009, at 1:25 AM, Niall Pemberton wrote:


Comparing the original proposal to the graduation resolution it seems
that click entered incubation with 4 committers and proposes to leave
with 3.

IMO a PMC of three is not enough - one person disappears and you can't
get the three votes required to do anything.

Niall

On Thu, Apr 23, 2009 at 8:10 PM, Bob Schellink   
wrote:

Hi all,

The Apache Click PPMC would like to have feedback on the following
graduation proposal before asking for a vote. The Click community  
already

votes in favor of graduation which is recorded here:

http://www.mail-archive.com/click-...@incubator.apache.org/msg00574.html

Click status page: http://incubator.apache.org/projects/click.html

Kind regards

Bob

--- Begin Proposed Board Resolution ---

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the Foundation's
 purpose to establish a Project Management Committee charged with
 the creation and maintenance of open-source software related to
 a framework for creating page and component oriented web
 applications, for distribution at no charge to the public.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Click Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Click Project be and hereby is
 responsible for the creation and maintenance of
 a page and component oriented web framework and related tools;
 and be it further

 RESOLVED, that the office of "Vice President, Apache Click" be and
 hereby is created, the person holding such office to serve at the
 direction of the Board of Directors as the chair of The Apache
 Click Project, and to have primary responsibility for
 management of the projects within the scope of responsibility of
 The Apache Click Project; and be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of The
 Apache Click Project:

   * Malcolm Edgar (med...@...)
   * Bob Schellink (sa...@...)
   * Naoki Takezoe (take...@...)

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Malcolm Edgar
 be and hereby is appointed to the office of Vice President,
 Apache Click, to serve in accordance with and subject to
 the direction of the Board of Directors and the Bylaws of the
 Foundation until death, resignation, retirement, removal or
 disqualification, or until a successor is appointed; and be it
 further

 RESOLVED, that the initial Apache Click Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Click podling; and be it further

 RESOLVED, that all responsibility pertaining to the Apache
 Incubator Click podling encumbered upon the Apache Incubator
 PMC are hereafter discharged.

--- End Proposed Board Resolution ---

-
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: [PROPOSAL] Apache Click graduation

[Andrus Adamchik]

Additional concern, it does not appear that the mentors are planning  
to

be on the PMC. Why not?


Why is this a concern? Mentors volunteer to do mentoring to ensure the  
project is viable and understands the Apache way, not necessarily to  
develop code. If you trace the existing Apache projects back to the  
incubator, I'd suspect 70% of them will not have their original  
mentors on the PMC.


Andrus
Apache Click Mentor



On Apr 24, 2009, at 1:28 AM, Upayavira wrote:


On Thu, 2009-04-23 at 23:25 +0100, Niall Pemberton wrote:

Comparing the original proposal to the graduation resolution it seems
that click entered incubation with 4 committers and proposes to leave
with 3.

IMO a PMC of three is not enough - one person disappears and you  
can't

get the three votes required to do anything.


Additional concern, it does not appear that the mentors are planning  
to

be on the PMC. Why not?

Upayavira



-
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: [PROPOSAL] Apache Click graduation

[Upayavira]

On Thu, 2009-04-23 at 23:25 +0100, Niall Pemberton wrote:
> Comparing the original proposal to the graduation resolution it seems
> that click entered incubation with 4 committers and proposes to leave
> with 3.
> 
> IMO a PMC of three is not enough - one person disappears and you can't
> get the three votes required to do anything.

Additional concern, it does not appear that the mentors are planning to
be on the PMC. Why not?

Upayavira



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

Re: [PROPOSAL] Apache Click graduation

[Niall Pemberton]

Comparing the original proposal to the graduation resolution it seems
that click entered incubation with 4 committers and proposes to leave
with 3.

IMO a PMC of three is not enough - one person disappears and you can't
get the three votes required to do anything.

Niall

On Thu, Apr 23, 2009 at 8:10 PM, Bob Schellink  wrote:
> Hi all,
>
> The Apache Click PPMC would like to have feedback on the following
> graduation proposal before asking for a vote. The Click community already
> votes in favor of graduation which is recorded here:
>
> http://www.mail-archive.com/click-...@incubator.apache.org/msg00574.html
>
> Click status page: http://incubator.apache.org/projects/click.html
>
> Kind regards
>
> Bob
>
> --- Begin Proposed Board Resolution ---
>
>  WHEREAS, the Board of Directors deems it to be in the best
>  interests of the Foundation and consistent with the Foundation's
>  purpose to establish a Project Management Committee charged with
>  the creation and maintenance of open-source software related to
>  a framework for creating page and component oriented web
>  applications, for distribution at no charge to the public.
>
>  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>  Committee (PMC), to be known as the "Apache Click Project",
>  be and hereby is established pursuant to Bylaws of the
>  Foundation; and be it further
>
>  RESOLVED, that the Apache Click Project be and hereby is
>  responsible for the creation and maintenance of
>  a page and component oriented web framework and related tools;
>  and be it further
>
>  RESOLVED, that the office of "Vice President, Apache Click" be and
>  hereby is created, the person holding such office to serve at the
>  direction of the Board of Directors as the chair of The Apache
>  Click Project, and to have primary responsibility for
>  management of the projects within the scope of responsibility of
>  The Apache Click Project; and be it further
>
>  RESOLVED, that the persons listed immediately below be and
>  hereby are appointed to serve as the initial members of The
>  Apache Click Project:
>
>    * Malcolm Edgar (med...@...)
>    * Bob Schellink (sa...@...)
>    * Naoki Takezoe (take...@...)
>
>  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Malcolm Edgar
>  be and hereby is appointed to the office of Vice President,
>  Apache Click, to serve in accordance with and subject to
>  the direction of the Board of Directors and the Bylaws of the
>  Foundation until death, resignation, retirement, removal or
>  disqualification, or until a successor is appointed; and be it
>  further
>
>  RESOLVED, that the initial Apache Click Project be and hereby
>  is tasked with the migration and rationalization of the Apache
>  Incubator Click podling; and be it further
>
>  RESOLVED, that all responsibility pertaining to the Apache
>  Incubator Click podling encumbered upon the Apache Incubator
>  PMC are hereafter discharged.
>
> --- End Proposed Board Resolution ---
>
> -
> 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: [VOTE] Release Apache Olio 0.1

[Shanti Subramanyam]

Thanks for the reversal of the -1. But I still need a +1 ?

Shanti

sebb wrote:

On 23/04/2009, Shanti Subramanyam  wrote:
  

sebb wrote:



On 23/04/2009, Shanti Subramanyam - PAE 
  

wrote:

  

On 04/22/09 10:35, sebb wrote:





On 16/04/2009, Shanti Subramanyam - PAE 


  

wrote:




On 04/15/09 18:15, sebb wrote:






On 16/04/2009, Shanti Subramanyam 
  

wrote:




  

Thank you very much for your very prompt review.
 Answers to your questions below.

 Shanti

 sebb wrote:







The OlioDriver.jar file contains a smaller OlioDriver.jar
  

file.


This is very confusing; one of the jars should be renamed.







  

 This is the format of the Faban (http://faban.sunsource.net)


Driver



jar




-





the user never has to do anything with it as the tool will




automatically




unjar and put everything in it's right place.







The binary olio file contains several .patch and .diff files.


  

These




don't seem correct for a binary file. What is their purpose?







  

 These files are part of the 3rd party plugin


fixture_replacement2.





Since we





tend to include 3rd party code as is (for easier upgrade),  I


think



it




might





be better to leave them as they are.






But why are they in the binary rails jar, rather than in just the


  

source




jar?




  

 There is no difference between the source and binary code for rails


(or



php




for that matter) since these are interpreted languages. The only




difference




between the source and binary packages of Olio is the geocoder and




workload




- these are written in Java so the binary packages have the




OlioDriver.jar




and geocoder.jar and the source packages have the corresponding


source



dirs.




That does not explain why the diffs and patch files are present in the
binary jar, because as far as I can tell they are not intended to be
interpreted by rails.

Are they actually *needed* at run-time?




  

 I really don't know. As I said, there is no concept of 'binary' for
scripting languages - the source is the binary. I will try and


investigate


this matter for the next release if it's not a major problem to leave


them


here for now.





I understand that there is no binary for scripting languages, and
therefore .js and .rb files appear in both source and binary archives.

However, the .diff and .patch files are scripts for a patch program,
which is used to modify source files.  Are such patches really applied
at run-time? Seems rather wasteful to me if so.

But I agree that could be fixed later.



  

The source PHP file contains several jars; I would expect
  

these to

  

be




in the binary archive only. It also contains the file
  

"event.pdf"


which does not seem to belong in the archive (or indeed in
  

SVN).







  

 These are third-party jars. They are included as a convenience


to



make




it





easier to build and run the source.






What about the event.pdf file?





  

 This is a resource file used by the web application. If you notice




there




are several image files as well - these are all static files used by


the



web




app.





What about the license for the event.pdf file? Is that also AL
  

licensed?




  

 All the resource files are created as part of the apache project, so


they


are all Apache licensed.




According to its properties, the event.pdf file was created in 1999
and last modified in 2004. AFAIK, that is well before the Apache
project started.
The file event.jpg was created in 2006, which was also before the
project, and is a picture of 5 real people. Hopefully they have given
permission for their photos to be published.



  

 This project was started a long time ago at Sun - all of the code including
these files was then donated to apache.



Neither appears to be present in the binary file, so I'm not sure how
the web application can use them.



  

 They do exist in the binary package - they are part of OlioDriver.jar.



Ah, OK, I see them now.

  

Note that there are other jpg files in the same di

Re: [VOTE] Accept Apache Ace into the Incubator

[Karl Pauls]

+1

regards,

Karl

On Mon, Apr 20, 2009 at 10:56 AM,   wrote:
> +1
> (non binding vote)
>
> francesco
>
>
>
> On 4/19/2009, "Karl Pauls"  wrote:
>
>>Please vote on accepting Apache Ace for incubation at the Apache
>>Incubator. The full proposal is available at the end of this message
>>and as a wiki page at http://wiki.apache.org/incubator/AceProposal. We
>>ask the Incubator PMC to sponsor it, with Karl as the Champion, and
>>Carsten, Niclas and Bertrand volunteering to be mentors.
>>
>>Please cast your votes:
>>
>>[ ]  +1, bring Ace into Incubator
>>[ ]  +0, I don't care either way,
>>[ ]  -1, do not bring Ace into Incubator, because...
>>
>>The vote is open for the next 72 hours and only votes from the
>>Incubator PMC are binding.
>>
>>- - - - - - - - - -
>>
>>Abstract
>>
>>Apache Ace is a software distribution framework based on OSGi that
>>allows you to manage and distribute artifacts, like e.g. software
>>components.
>>
>>
>>Proposal
>>
>>Apache Ace is a software distribution framework that allows you to
>>centrally manage and distribute software components, configuration
>>data and other artifacts to target systems. It is built using OSGi and
>>can be deployed in different topologies. The target systems are
>>usually also OSGi based, but don't have to be.
>>
>>
>>Background
>>
>>When assembling software out of reusable components, the task of
>>deploying software onto an ever increasing number of targets is not
>>trivial to solve. This becomes even harder when these targets require
>>different components based on who's using them.
>>
>>A key technology in the Java space for developing component based
>>applications is OSGi. The OSGi speciï¬ cation, which has been around
>>since 1999 and by now has matured into the de facto module system for
>>Java, allows you to write components that can interact through
>>services and that allows components to be updated individually,
>>without disturbing the rest of the components.
>>
>>Although the OSGi speciï¬ cation describes how software distribution
>>should be done, it does not actually prescribe any protocols or
>>implementations. Apache Ace implements a software distribution system
>>based on, but not limited to OSGi. It is setup so it can deal with
>>different target types, using different protocols. Also, it can handle
>>an extensible number of artifact types (bundles, configurations,
>>resources, ...).
>>
>>
>>Rationale
>>
>>When you start using OSGi to build reusable components, the task of
>>managing those components and their use in various applications
>>becomes non-trivial. Apache Ace allows you to group those components
>>and assign them to a managed set of targets. This allows you to
>>distribute updates and new components easily, while keeping a full
>>history of what was installed where during what period. It also helps
>>you setup an automated development, QA/testing, staging and production
>>environment.
>>
>>
>>Initial Goals
>>
>>The initial goals for Apache Ace are:
>>
>>* Donate the existing codebase and import it.
>>* Setup the incubation infrastructure (svn repository, build system,
>>website) so we can run continuous builds with automated tests and
>>publish all available documentation.
>>* Get people involved in advancing the code base in different
>>directions, integrating it with other projects at Apache.
>>* Prepare for an initial release that demonstrates the systems core
>>capabilities.
>>* Present the project to the community at ApacheCon 2009 US.
>>
>>
>>Current Status
>>
>>The current codebase is developed and tested in various
>>configurations. It was developed at luminis over the last couple of
>>years using Scrum, so we have internally demonstrated we can release
>>often and produce working code using a transparent process.
>>Documentation for the project is now available on an internal wiki,
>>which can be donated and converted to the Apache Ace website. We did
>>not yet use mailing lists as the primary colaborative process, as the
>>whole team met face to face on a daily basis.
>>
>>
>>Meritocracy
>>
>>Some of the core developers are already committers and PMC members at
>>Apache, so they understand what it means to have a process based on
>>meritocracy.
>>
>>
>>Community
>>
>>In the past, luminis has been talking to various interested users and
>>developers about Apache Ace, and we believe there is an interest in
>>this project. Feedback at ApacheCon EU 2009 and afterwards on the
>>Apache Felix mailing list confirmed that. The problem that is being
>>solved is one that many software developers run into, so it should
>>appeal to them. Our list of initial committers already includes people
>>from different backgrounds.
>>
>>
>>Core Developers
>>
>>The core development team is a mix of people that work for luminis and
>>have been involved in the project up til now and new committers, some
>>of which have previous experience at Apache.
>>
>>
>>Alignment
>>
>>The initial codebase makes use of Apache Felix as its core framework

Re: [VOTE][RESULT] Accept Apache Ace into the Incubator

[Karl Pauls]

Time to call the vote on accepting Apache Ace for incubation.

* +1 votes from (* indicates binding votes) Carsten Ziegeler*, Niclas
Hedhman*, Richard S. Hall, Niall Pemberton*, Robert Burrell Donkin*,
Bertrand Delacretaz*, Felix Meschberger, Francesco Furfari, and Karl
Pauls.

* No other votes.

The vote is successful. Thanks to everyone involved. We will get the
ball rolling asap.

>>Please vote on accepting Apache Ace for incubation at the Apache
>>Incubator. The full proposal is available at the end of this message
>>and as a wiki page at http://wiki.apache.org/incubator/AceProposal. We
>>ask the Incubator PMC to sponsor it, with Karl as the Champion, and
>>Carsten, Niclas and Bertrand volunteering to be mentors.
>>
>>Please cast your votes:
>>
>>[ ]  +1, bring Ace into Incubator
>>[ ]  +0, I don't care either way,
>>[ ]  -1, do not bring Ace into Incubator, because...
>>
>>The vote is open for the next 72 hours and only votes from the
>>Incubator PMC are binding.
>>
>>- - - - - - - - - -
>>
>>Abstract
>>
>>Apache Ace is a software distribution framework based on OSGi that
>>allows you to manage and distribute artifacts, like e.g. software
>>components.
>>
>>
>>Proposal
>>
>>Apache Ace is a software distribution framework that allows you to
>>centrally manage and distribute software components, configuration
>>data and other artifacts to target systems. It is built using OSGi and
>>can be deployed in different topologies. The target systems are
>>usually also OSGi based, but don't have to be.
>>
>>
>>Background
>>
>>When assembling software out of reusable components, the task of
>>deploying software onto an ever increasing number of targets is not
>>trivial to solve. This becomes even harder when these targets require
>>different components based on who's using them.
>>
>>A key technology in the Java space for developing component based
>>applications is OSGi. The OSGi speciï¬ cation, which has been around
>>since 1999 and by now has matured into the de facto module system for
>>Java, allows you to write components that can interact through
>>services and that allows components to be updated individually,
>>without disturbing the rest of the components.
>>
>>Although the OSGi speciï¬ cation describes how software distribution
>>should be done, it does not actually prescribe any protocols or
>>implementations. Apache Ace implements a software distribution system
>>based on, but not limited to OSGi. It is setup so it can deal with
>>different target types, using different protocols. Also, it can handle
>>an extensible number of artifact types (bundles, configurations,
>>resources, ...).
>>
>>
>>Rationale
>>
>>When you start using OSGi to build reusable components, the task of
>>managing those components and their use in various applications
>>becomes non-trivial. Apache Ace allows you to group those components
>>and assign them to a managed set of targets. This allows you to
>>distribute updates and new components easily, while keeping a full
>>history of what was installed where during what period. It also helps
>>you setup an automated development, QA/testing, staging and production
>>environment.
>>
>>
>>Initial Goals
>>
>>The initial goals for Apache Ace are:
>>
>>* Donate the existing codebase and import it.
>>* Setup the incubation infrastructure (svn repository, build system,
>>website) so we can run continuous builds with automated tests and
>>publish all available documentation.
>>* Get people involved in advancing the code base in different
>>directions, integrating it with other projects at Apache.
>>* Prepare for an initial release that demonstrates the systems core
>>capabilities.
>>* Present the project to the community at ApacheCon 2009 US.
>>
>>
>>Current Status
>>
>>The current codebase is developed and tested in various
>>configurations. It was developed at luminis over the last couple of
>>years using Scrum, so we have internally demonstrated we can release
>>often and produce working code using a transparent process.
>>Documentation for the project is now available on an internal wiki,
>>which can be donated and converted to the Apache Ace website. We did
>>not yet use mailing lists as the primary colaborative process, as the
>>whole team met face to face on a daily basis.
>>
>>
>>Meritocracy
>>
>>Some of the core developers are already committers and PMC members at
>>Apache, so they understand what it means to have a process based on
>>meritocracy.
>>
>>
>>Community
>>
>>In the past, luminis has been talking to various interested users and
>>developers about Apache Ace, and we believe there is an interest in
>>this project. Feedback at ApacheCon EU 2009 and afterwards on the
>>Apache Felix mailing list confirmed that. The problem that is being
>>solved is one that many software developers run into, so it should
>>appeal to them. Our list of initial committers already includes people
>>from different backgrounds.
>>
>>
>>Core Developers
>>
>>The core development team is a mix of peop

[PROPOSAL] Apache Click graduation

[Bob Schellink]

Hi all,

The Apache Click PPMC would like to have feedback on the following 
graduation proposal before asking for a vote. The Click community 
already votes in favor of graduation which is recorded here:


http://www.mail-archive.com/click-...@incubator.apache.org/msg00574.html

Click status page: http://incubator.apache.org/projects/click.html

Kind regards

Bob

--- Begin Proposed Board Resolution ---

  WHEREAS, the Board of Directors deems it to be in the best
  interests of the Foundation and consistent with the Foundation's
  purpose to establish a Project Management Committee charged with
  the creation and maintenance of open-source software related to
  a framework for creating page and component oriented web
  applications, for distribution at no charge to the public.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the "Apache Click Project",
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further

  RESOLVED, that the Apache Click Project be and hereby is
  responsible for the creation and maintenance of
  a page and component oriented web framework and related tools;
  and be it further

  RESOLVED, that the office of "Vice President, Apache Click" be and
  hereby is created, the person holding such office to serve at the
  direction of the Board of Directors as the chair of The Apache
  Click Project, and to have primary responsibility for
  management of the projects within the scope of responsibility of
  The Apache Click Project; and be it further

  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of The
  Apache Click Project:

* Malcolm Edgar (med...@...)
* Bob Schellink (sa...@...)
* Naoki Takezoe (take...@...)

  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Malcolm Edgar
  be and hereby is appointed to the office of Vice President,
  Apache Click, to serve in accordance with and subject to
  the direction of the Board of Directors and the Bylaws of the
  Foundation until death, resignation, retirement, removal or
  disqualification, or until a successor is appointed; and be it
  further

  RESOLVED, that the initial Apache Click Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator Click podling; and be it further

  RESOLVED, that all responsibility pertaining to the Apache
  Incubator Click podling encumbered upon the Apache Incubator
  PMC are hereafter discharged.

--- End Proposed Board Resolution ---

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

Re: [VOTE] Release Apache Olio 0.1

[Shanti Subramanyam]

Robert Burrell Donkin wrote:

On Thu, Apr 23, 2009 at 4:39 AM, sebb  wrote:
  

On 23/04/2009, Shanti Subramanyam  wrote:


sebb wrote:
  




  

But seriously, without these
files, we will have to somehow go out and manufacture image/pdf files at
install time - uploading files is a big part of a web2.0 workload these days
(and for sites like flickr the major workload).
  


FWIW for this kind of thing, i start with the Apache Software License,
Version 2.0 in an editor (with a save a PDF option) save to PDF then
convert to a binary image format

  
We will do that for the pdf file next time around. It is nice to have 
real pictures for the images though as they are visible if you use a 
browser for testing.

 Does anyone else see a serious issue with these files ?

  

I withdraw my -1 vote.



i'm now +1

  


Thank you.

- robert

-
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: [PROPOSAL] Apache SocialSite

[Otis Gospodnetic]

Another +1 from me, too.  SocialSite needs to live on and Apache could be a 
good home for it.

 
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch



- Original Message 
> From: Jamey Wood 
> To: general@incubator.apache.org
> Cc: Eduardo Pelegri-Llopart ; rovagn...@gmail.com; Robert 
> Bissett ; leandro.milma...@globant.com; 
> rodr...@globant.com; Tony Ng 
> Sent: Thursday, April 23, 2009 11:47:00 AM
> Subject: Re: [PROPOSAL] Apache SocialSite
> 
> I'm very much +1 on this.  I appreciate Sun's willingness to contribute the
> existing SocialSite code, and I hope that we'll have the opportunity to
> evolve it under the Incubator's established governance model and level
> playing field.
> 
> --Jamey
> 
> On Wed, Apr 8, 2009 at 7:41 PM, Dave wrote:
> 
> > Greetings to all,
> >
> > It's my pleasure to present to you a proposal for a new project Apache
> > SocialSite, a social networking service based on Apache Shindig
> > (incubating) with an end-user interface composed entirely of
> > OpenSocial gadgets and designed to add social networking features to
> > existing web applications (e.g. Roller, JSPWiki, your favorite webapp,
> > etc.). You can find the full proposal on the Incubator wiki:
> >
> >  http://wiki.apache.org/incubator/SocialSiteProposal
> >
> > I look forward to your comments and suggestions on this proposal.
> >
> > Thanks,
> > Dave
> >


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

Re: [PROPOSAL] Apache SocialSite

[Volz Raphael]

+1 from our companies side.

An essential building block for future Web applications that deserves  
the support from Apache !


Best

Raphael

Volz Innovation GmbH
Kirchhaldenweg 10, 76597 Loffenau, Germany

Tel: +49 18 03 55 18 51 075
Mail: r...@raphaelvolz.de
Web: www.raphaelvolz.de
Fax: +49 18 03 55 18 51 075

Company Seat / Sitz der Gesellschaft: Loffenau
		Company Register / Handelsregisternummer: HRB 704418, Amtsgericht  
Mannheim

Managing Director / Geschäftsführer: Dr. Raphael Volz, CEO


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

Re: [PROPOSAL] Apache SocialSite

[Ramesh Mandava]

+1

 And I am willing to contribute to SocialSite project in my own time.

Regards
-Ramesh



- Original Message 
From: Bobby Bissett 
To: Dave ; general@incubator.apache.org
Cc: Eduardo Pelegri-Llopart ; rovagn...@gmail.com; Jamey Wood 
; leandro.milma...@globant.com; rodr...@globant.com; Tony 
Ng 
Sent: Thursday, April 23, 2009 9:06:43 AM
Subject: Re: [PROPOSAL] Apache SocialSite

+1 from me. I want to see the project continue, and I think it will  
have a better chance with a fresh start at Apache.

Cheers,
Bobby

On Apr 8, 2009, at 9:41 PM, Dave wrote:

> Greetings to all,
>
> It's my pleasure to present to you a proposal for a new project Apache
> SocialSite, a social networking service based on Apache Shindig
> (incubating) with an end-user interface composed entirely of
> OpenSocial gadgets and designed to add social networking features to
> existing web applications (e.g. Roller, JSPWiki, your favorite webapp,
> etc.). You can find the full proposal on the Incubator wiki:
>
>   http://wiki.apache.org/incubator/SocialSiteProposal
>
> I look forward to your comments and suggestions on this proposal.
>
> Thanks,
> Dave


-
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: [PROPOSAL] Apache SocialSite

[Bobby Bissett]

+1 from me. I want to see the project continue, and I think it will  
have a better chance with a fresh start at Apache.


Cheers,
Bobby

On Apr 8, 2009, at 9:41 PM, Dave wrote:


Greetings to all,

It's my pleasure to present to you a proposal for a new project Apache
SocialSite, a social networking service based on Apache Shindig
(incubating) with an end-user interface composed entirely of
OpenSocial gadgets and designed to add social networking features to
existing web applications (e.g. Roller, JSPWiki, your favorite webapp,
etc.). You can find the full proposal on the Incubator wiki:

  http://wiki.apache.org/incubator/SocialSiteProposal

I look forward to your comments and suggestions on this proposal.

Thanks,
Dave



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

Re: [PROPOSAL] Apache SocialSite

[Chris Chabot]

+1 from a shindig ppmc, social site is an awesome product that fills various
needs (from being a demo of how to use shindig, to use in large scale
projects).

And as it depends on shindig, having it become an Apache project
Just-Makes-Sense(Tm).

   -- Chris

On Thu, Apr 23, 2009 at 5:47 PM, Jamey Wood  wrote:

> I'm very much +1 on this.  I appreciate Sun's willingness to contribute the
> existing SocialSite code, and I hope that we'll have the opportunity to
> evolve it under the Incubator's established governance model and level
> playing field.
>
> --Jamey
>
> On Wed, Apr 8, 2009 at 7:41 PM, Dave  wrote:
>
> > Greetings to all,
> >
> > It's my pleasure to present to you a proposal for a new project Apache
> > SocialSite, a social networking service based on Apache Shindig
> > (incubating) with an end-user interface composed entirely of
> > OpenSocial gadgets and designed to add social networking features to
> > existing web applications (e.g. Roller, JSPWiki, your favorite webapp,
> > etc.). You can find the full proposal on the Incubator wiki:
> >
> >   http://wiki.apache.org/incubator/SocialSiteProposal
> >
> > I look forward to your comments and suggestions on this proposal.
> >
> > Thanks,
> > Dave
> >
>

Re: [VOTE] Release Apache Olio 0.1

[Robert Burrell Donkin]

On Thu, Apr 23, 2009 at 4:39 AM, sebb  wrote:
> On 23/04/2009, Shanti Subramanyam  wrote:
>> sebb wrote:



>> But seriously, without these
>> files, we will have to somehow go out and manufacture image/pdf files at
>> install time - uploading files is a big part of a web2.0 workload these days
>> (and for sites like flickr the major workload).

FWIW for this kind of thing, i start with the Apache Software License,
Version 2.0 in an editor (with a save a PDF option) save to PDF then
convert to a binary image format

>>  Does anyone else see a serious issue with these files ?
>>
>
> I withdraw my -1 vote.

i'm now +1

- robert

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

Re: [PROPOSAL] Apache SocialSite

[Jamey Wood]

I'm very much +1 on this.  I appreciate Sun's willingness to contribute the
existing SocialSite code, and I hope that we'll have the opportunity to
evolve it under the Incubator's established governance model and level
playing field.

--Jamey

On Wed, Apr 8, 2009 at 7:41 PM, Dave  wrote:

> Greetings to all,
>
> It's my pleasure to present to you a proposal for a new project Apache
> SocialSite, a social networking service based on Apache Shindig
> (incubating) with an end-user interface composed entirely of
> OpenSocial gadgets and designed to add social networking features to
> existing web applications (e.g. Roller, JSPWiki, your favorite webapp,
> etc.). You can find the full proposal on the Incubator wiki:
>
>   http://wiki.apache.org/incubator/SocialSiteProposal
>
> I look forward to your comments and suggestions on this proposal.
>
> Thanks,
> Dave
>

Re: Apache Wink Proposal

[Nicholas L Gallardo]

Remaining IBM CLAs have been signed and faxed in.  I've updated the wiki as
well.

-Nick



Nicholas Gallardo
WebSphere  -  REST & WebServices Development
nlgal...@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016


   
 Davanum Srinivas  
  To
   general@incubator.apache.org
 04/23/2009 06:28   cc
 AM
   Subject
   Re: Apache Wink Proposal
 Please respond to 
 gene...@incubator 
.apache.org
   
   
   




Niclas,

We will try the best to make the community dynamics happen. When we get
around to looking at the source, you will see
the existing cxf code packages and classes as-is. So theoretically we will
be able to get some value out of it in terms
of contributing back to cxf.

On a related note, would any pmc folks / asf members (including Dan!) like
to mentor us? or join us as committers?
Please let us know

thanks,
dims

On 04/23/2009 07:19 AM, Niclas Hedhman wrote:
> On Thu, Apr 23, 2009 at 1:07 AM, Greg Truty  wrote:
>> Hello all, I would like to formally present the incubator proposal for
>> Apache Wink, stand-alone REST toolkit supporting JAX-RS (JSR 311), a
>> client runtime and test cases (as well as other items).
>
> I hear Dan's concerns, but *I* don't think they matter much. If this
> new community takes off, and turns out to get along well enough with
> the CXF community, wonders may happen. If they don't get along,
> forcing the merge won't work.
> And I am personally interested in seeing a light-weight (if anything
> is nowadays) API become available...
>
> So, +1 to submission of a formal proposal.
>
> Cheers

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

Re: Apache Wink Proposal

[Davanum Srinivas]

Niclas,

We will try the best to make the community dynamics happen. When we get around to looking at the source, you will see 
the existing cxf code packages and classes as-is. So theoretically we will be able to get some value out of it in terms 
of contributing back to cxf.


On a related note, would any pmc folks / asf members (including Dan!) like to mentor us? or join us as committers? 
Please let us know


thanks,
dims

On 04/23/2009 07:19 AM, Niclas Hedhman wrote:

On Thu, Apr 23, 2009 at 1:07 AM, Greg Truty  wrote:

Hello all, I would like to formally present the incubator proposal for
Apache Wink, stand-alone REST toolkit supporting JAX-RS (JSR 311), a
client runtime and test cases (as well as other items).


I hear Dan's concerns, but *I* don't think they matter much. If this
new community takes off, and turns out to get along well enough with
the CXF community, wonders may happen. If they don't get along,
forcing the merge won't work.
And I am personally interested in seeing a light-weight (if anything
is nowadays) API become available...

So, +1 to submission of a formal proposal.

Cheers


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

Re: Apache Wink Proposal

[Niclas Hedhman]

On Thu, Apr 23, 2009 at 1:07 AM, Greg Truty  wrote:
> Hello all, I would like to formally present the incubator proposal for
> Apache Wink, stand-alone REST toolkit supporting JAX-RS (JSR 311), a
> client runtime and test cases (as well as other items).

I hear Dan's concerns, but *I* don't think they matter much. If this
new community takes off, and turns out to get along well enough with
the CXF community, wonders may happen. If they don't get along,
forcing the merge won't work.
And I am personally interested in seeing a light-weight (if anything
is nowadays) API become available...

So, +1 to submission of a formal proposal.

Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

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: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: how do you find a Champion?

[Niclas Hedhman]

On Thu, Apr 23, 2009 at 3:52 AM, Upayavira  wrote:
> On Wed, 2009-04-22 at 14:04 -0500, Thomas Anderson wrote:
>> According to 
>> ,
>> "a Champion should be found before the proposal is formally
>> submitted."  My question is...  how do you find one?  Is emailing
>> general@incubator.apache.org, saying "hi - I'm looking for a Champion
>> for " sufficient?
>
> Depends on whether it works! But yes, asking on general@ is the right
> place to ask, as I would expect many/most of the folks who would be in a
> position to act as champions/mentors to be hanging out there.

You could also ask yourself, "Who else in the ASF family would be
interested in this technology? Which Apache project are we the most
associated with?" and then go to their dev@ list and ask there, or if
you are too shy ask one of the community members directly, such as the
PMC Chair, with the risk of him (her?) becoming annoyed. ;-)


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

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: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Suggestion regarding improvement of iCLA submission process

[Marcel Offermans]

On Apr 23, 2009, at 8:39 , Robert Burrell Donkin wrote:


IMHO this means using JIRA to record and track these documents and the
associated workflow. the easiest way to do this would be by finding a
way to allow contributors to submit an iCLA via JIRA. AIUI the
requirement for submission by fax, email or mail is a legal one, so
the first step you need to take is to subscribe to legal-discuss and
ask what steps apache needs to take to allow submission of iCLAs via
JIRA.


It is possible to let JIRA monitor a mailbox and translate incoming  
mails to issues. That might help in satisfying the legal requirement.


Greetings, Marcel


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

Re: Getting Log4PHP going again.

[Christian Grobmeier]

Just want to confirm my interest in response.
My apache id is "grobmeier" - feel free to add me to the log4php project :-)
Cheers
Christian

On Wed, Apr 22, 2009 at 11:24 AM, Gavin  wrote:
> Hi All,
>
> Well things seem to be dying down here, ApacheCon well and truly over, board
> meeting is done and this thread celebrates 1 month today :)
>
> So, just checking in, can we do something about this Log4PHP revival ?
>
> Thanks
>
> Gav...
>
>
>> -Original Message-
>> From: Gavin [mailto:ga...@16degrees.com.au]
>> Sent: Monday, 30 March 2009 7:19 PM
>> To: general@incubator.apache.org
>> Subject: RE: Getting Log4PHP going again.
>>
>>
>>
>> > -Original Message-
>> > From: Christian Grobmeier [mailto:grobme...@gmail.com]
>> > Sent: Monday, 30 March 2009 3:29 PM
>> > To: general@incubator.apache.org
>> > Subject: Re: Getting Log4PHP going again.
>> >
>> > Hi folks,
>> >
>> > any news on the log4php "issue"?
>>
>> I posted this thread originally on the 22nd, 1 day before ApacheCon week
>> started, today is the first working day since ApacheCon ended. Incubator
>> in
>> general has been a ghost town during this time, so I expect (hope) that
>> this
>> will be picked up and acted on this week sometime.
>>
>> >
>> > I have now been elected by Apache Commons as a Comitter and can help
>> > more easy now.
>>
>> Excellent, congrats!
>>
>> > Is it possible to volunteer for comit access and help
>> > log4php directly?
>>
>> I hope that is the case, lets wait to here.
>>
>> To recap, we have now :-
>>
>> myself (gmcdonald) - (see start of thread for what I offered to do)
>> Grobmeier - main code dude
>> Niclas hedhman - has offered to mentor and commit patches as necessary.
>>
>> Jim is still a Mentor so we need one more.
>>
>> Looking forward to showing that the road to the attic is a two way street
>> -
>> we don't need to go that way!
>>
>> Gav...
>>
>> >
>> > Best,
>> > Christian
>> >
>> > On Sun, Mar 22, 2009 at 6:37 AM, Niclas Hedhman 
>> > wrote:
>> > > On Sat, Mar 21, 2009 at 11:29 PM, Christian Grobmeier
>> > >  wrote:
>> > >
>> > >> The log4php code is quite stable, but since the last big changes some
>> > >> time has gone. PHP4, in which the code has been written, has reached
>> > >> the end of its life in august 2008. No development will be done here.
>> > >>
>> > >> I really think that we should finish the development of the php4
>> > >> branch in log4php too and just do bugfixes, if necessary. For the
>> php4
>> > >> branch could have a incubator release quite soon, i guess.
>> > >>
>> > >> We should concentrate in PHP5 and for this we need helping hands and
>> a
>> > bit time.
>> > >
>> > > I am not a PHP guy at all, but AFAIUI (only from the package
>> > > resolution issues in Debian) the PHP4 and PHP5 is incompatible and
>> > > that a port require substantial work.
>> > >
>> > > If so, that is a good thing and give some hope that it can be revived.
>> > > The main issue about community is still a troublesome one, and IMHO a
>> > > lot of blogosphere and article activities would be needed to get some
>> > > attention to the project and hopefully some fresh souls.
>> > >
>> > > I support the idea of get going again, and can volunteer a Mentor role
>> > > (thanks to Etch and Pivot being excellent podlings and require little
>> > > time now). I can also assist in patch application, but can't review
>> > > the code per se...
>> > >
>> > >
>> > > Cheers
>> > > Niclas
>> > > --
>> > > http://www.qi4j.org - New Energy for Java
>> > >
>> > > -
>> > > 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
>> >
>> >
>> >
>> > --
>> > No virus found in this incoming message.
>> > Checked by AVG.
>> > Version: 7.5.557 / Virus Database: 270.11.31/2028 - Release Date:
>> > 3/28/2009 7:16 AM
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>>
>> --
>> No virus found in this incoming message.
>> Checked by AVG.
>> Version: 7.5.557 / Virus Database: 270.11.31/2028 - Release Date:
>> 3/28/2009 7:16 AM
>
>
> -
> 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: PPMC Member list

[Noel J. Bergman]

> AFAICT we udpdate the poddling status page with the PPMC members.

Yes, every project has a STATUS page, and we really should consoldate to there, 
and stop having redundant meta-data spewed all over the place.

Frankly, I'd like to see the reporting schedule added to the STATUS file, too, 
or perhaps best to the project index.

--- Noel



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

Re: Suggestion regarding improvement of iCLA submission process

[Richard Hirsch]

I just posted the question to legal-discuss. Let's see what they say.

D.

On Thu, Apr 23, 2009 at 9:03 AM, Upayavira  wrote:

> I personally would just ask the secretary what he thinks - mail
> secret...@.
>
> He's responsible for managing this stuff, and it might be easy for him
> to automate sending mails. Dunno.
>
> Upayavira
>
> On Thu, 2009-04-23 at 08:56 +0200, Richard Hirsch wrote:
> > I like the idea of using JIRA to track the iCLA status. It is already
> > possible to submit attachments with Jira items, so that would deal with
> > submissions by email. For mailed and faxed submissions, I could imagine
> > volunteers scanning these items, adding them to Jira and then mailing the
> > submitter the link to Jira item.
> >
> > I'll move the discussion to legal-discuss and see what happens.
> >
> > D.
> >
> > On Thu, Apr 23, 2009 at 8:39 AM, Robert Burrell Donkin <
> > robertburrelldon...@gmail.com> wrote:
> >
> > >  On Thu, Apr 23, 2009 at 7:16 AM, Richard Hirsch <
> hirsch.d...@gmail.com>
> > > wrote:
> > > > The current CLA submission process is described here:
> > > > http://www.apache.org/dev/committers.html#cla-registration
> > > >
> > > > I'd like to make a suggestion that emails be sent to people to
> submitting
> > > > iCLAs so that they have idea of the status of their submission. I'd
> > > suggest
> > > > sending emails when an iCLA has been received, when it has been
> > > > acknowledged and finally when it has been registered.
> > > >
> > > > This would improve the process and avoid emails in the podling
> mailing
> > > lists
> > > > asking about the status of individual iCLA submissions.
> > > >
> > > > I've just submitted an iCLA via email and I have no way to check its
> > > status
> > > > besides looking at the Committers' page (
> > > > http://people.apache.org/~jim/committers.html) on a daily basis.
> > > >
> > > > Thanks.
> > >
> > > don't be so quick to thanks us ;-) the price of submitting ideas is
> > > being willing to actively help to make it happen :-)
> > >
> > > IMO asking the secretary to send more mails would just add more strain
> > > to our key volunteer infrastructure. so, the some means of automation
> > > would be needed.
> > >
> > > IMHO this means using JIRA to record and track these documents and the
> > > associated workflow. the easiest way to do this would be by finding a
> > > way to allow contributors to submit an iCLA via JIRA. AIUI the
> > > requirement for submission by fax, email or mail is a legal one, so
> > > the first step you need to take is to subscribe to legal-discuss and
> > > ask what steps apache needs to take to allow submission of iCLAs via
> > > JIRA.
> > >
> > > - robert
> > >
> > > -
> > > 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: Suggestion regarding improvement of iCLA submission process

[Upayavira]

I personally would just ask the secretary what he thinks - mail
secret...@.

He's responsible for managing this stuff, and it might be easy for him
to automate sending mails. Dunno.

Upayavira

On Thu, 2009-04-23 at 08:56 +0200, Richard Hirsch wrote:
> I like the idea of using JIRA to track the iCLA status. It is already
> possible to submit attachments with Jira items, so that would deal with
> submissions by email. For mailed and faxed submissions, I could imagine
> volunteers scanning these items, adding them to Jira and then mailing the
> submitter the link to Jira item.
> 
> I'll move the discussion to legal-discuss and see what happens.
> 
> D.
> 
> On Thu, Apr 23, 2009 at 8:39 AM, Robert Burrell Donkin <
> robertburrelldon...@gmail.com> wrote:
> 
> >  On Thu, Apr 23, 2009 at 7:16 AM, Richard Hirsch 
> > wrote:
> > > The current CLA submission process is described here:
> > > http://www.apache.org/dev/committers.html#cla-registration
> > >
> > > I'd like to make a suggestion that emails be sent to people to submitting
> > > iCLAs so that they have idea of the status of their submission. I'd
> > suggest
> > > sending emails when an iCLA has been received, when it has been
> > > acknowledged and finally when it has been registered.
> > >
> > > This would improve the process and avoid emails in the podling mailing
> > lists
> > > asking about the status of individual iCLA submissions.
> > >
> > > I've just submitted an iCLA via email and I have no way to check its
> > status
> > > besides looking at the Committers' page (
> > > http://people.apache.org/~jim/committers.html) on a daily basis.
> > >
> > > Thanks.
> >
> > don't be so quick to thanks us ;-) the price of submitting ideas is
> > being willing to actively help to make it happen :-)
> >
> > IMO asking the secretary to send more mails would just add more strain
> > to our key volunteer infrastructure. so, the some means of automation
> > would be needed.
> >
> > IMHO this means using JIRA to record and track these documents and the
> > associated workflow. the easiest way to do this would be by finding a
> > way to allow contributors to submit an iCLA via JIRA. AIUI the
> > requirement for submission by fax, email or mail is a legal one, so
> > the first step you need to take is to subscribe to legal-discuss and
> > ask what steps apache needs to take to allow submission of iCLAs via
> > JIRA.
> >
> > - robert
> >
> > -
> > 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