Re: [VOTE] Accept Rave into the Incubator

[Franklin, Matthew B.]

+1 

-Matt


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

[VOTE] Release Apache Rave 0.1-incubating

[Franklin, Matthew B.]

This is the first incubator release for Apache Rave, with the artifacts
being versioned as 0.1-incubating.

We are requesting a lazy consensus vote, as we have already received 3
binding IPMC +1 votes during the release voting on rave-dev -

Vote thread: 
http://apache.markmail.org/message/vmgwtdoueobdmc2g?q=list:org%2Eapache%2Ei
ncubator%2Erave-dev+%5BVOTE%5D+Apache+order:date-backward&page=3s

Result: 
http://apache.markmail.org/message/lq6n7jgkhhlntqig?q=list:org%2Eapache%2Ei
ncubator%2Erave-dev+%5BVOTE%5D+Apache+order:date-backward&page=1

Release notes:
https://svn.apache.org/repos/asf/incubator/rave/tags/0.1-incubating/CHANGEL
OG

SVN source tag (master) (r1141150):
https://svn.apache.org/repos/asf/incubator/rave/rave-master-pom/tags/0.1-in
cubating/

SVN source tag (project)(r1141160)
https://svn.apache.org/repos/asf/incubator/rave/tags/0.1-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapacherave-004/


Staged Source releases:
https://repository.apache.org/content/repositories/orgapacherave-004/org/ap
ache/rave/rave-master/0.1-incubating/rave-master-0.1-incubating-source-rele
ase.zip
https://repository.apache.org/content/repositories/orgapacherave-004/org/ap
ache/rave/rave-project/0.1-incubating/rave-project-0.1-incubating-source-re
lease.zip

Staged Binary releases
http://people.apache.org/builds/incubator/rave/0.1-incubating/rave-0.1-incu
bating-bin.zip
http://people.apache.org/builds/incubator/rave/0.1-incubating/rave-0.1-incu
bating-bin.tar.gz

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS


Lazy consensus, vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


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

RE: [VOTE] Release Apache Amber 0.22-incubating

[Franklin, Matthew B.]

>-Original Message-
>From: Tommaso Teofili [mailto:tommaso.teof...@gmail.com]
>Sent: Wednesday, July 25, 2012 3:55 AM
>To: general@incubator.apache.org
>Subject: Re: [VOTE] Release Apache Amber 0.22-incubating
>
>Anyone else from the IPMC willing to review this ?

I will try to review this before the weekend.

>Thanks in advance,
>Tommaso
>
>2012/7/21 Raymond Feng 
>
>> +1 from me.
>>
>> Thanks,
>> Raymond
>>
>> On Jul 18, 2012, at 12:33 AM, Simone Tripodi wrote:
>>
>> > Good morning IPMC,
>> >
>> > I'm writing today to submit you the VOTE of the first release ever of
>> > Apache Amber 0.22 under the Incubator.
>> >
>> > PPMC vote already passed on amber-dev@ 
>with
>> > already 1 IPMC binding vote.
>> >
>> > We solved 28 issues:
>> >
>>
>http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311100&;
>styleName=Html&version=12322240
>> >
>> > There are still 14 issues left in JIRA:
>> >
>>
>http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12
>311100&status=1
>> >
>> > SVN source tag (r1359173):
>> >
>> https://svn.apache.org/repos/asf/incubator/amber/tags/amber-0.22-
>incubating/
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/orgapacheamber-
>039/
>> >
>> > Staging binaries:
>> > http://people.apache.org/builds/incubator/amber/
>> >
>> > Staging site:
>> > http://incubator.apache.org/amber/0.22-incubating/
>> >
>> > PGP release keys (signed using 19FEA27D):
>> > http://www.apache.org/dist/incubator/amber/KEYS
>> >
>> > Vote will be open for 72 hours and will close ~ on July the 21th at
>> 7:30am GMT
>> >
>> > [ ] +1, let's get it rmblee!!!
>> > [ ] +/-0, fine, but consider to fix few issues before...
>> > [ ] -1, nope, because... (and please explain why)
>> >
>> > Many thanks in advance, all the best!
>> > -Simo
>> >
>> > http://people.apache.org/~simonetripodi/
>> > http://simonetripodi.livejournal.com/
>> > http://twitter.com/simonetripodi
>> > http://www.99soft.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: Fwd: [ANN] Apache Syncope 1.0.0-RC3-incubating released

[Franklin, Matthew B.]

>-Original Message-
>From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On
>Behalf Of Simone Tripodi
>Sent: Friday, July 27, 2012 6:23 AM
>To: general@incubator.apache.org; elecha...@apache.org
>Subject: Re: Fwd: [ANN] Apache Syncope 1.0.0-RC3-incubating released
>
>Aplogize for joining the discussion late, but
>
>> Here, I would argue that unless we have some written direction about what
>> release numbering scheme  the incubating should use at The ASF, then
>> whatever a project decides to use is fine.
>
>+1

+1.  Designating a release 'RC' is common enough in industry that I don't think 
we should arbitrarily restrict it just because we refer to releases undergoing 
a VOTE as 'release candidates'.

>
>nothing to add :)
>-Simo
>
>http://people.apache.org/~simonetripodi/
>http://simonetripodi.livejournal.com/
>http://twitter.com/simonetripodi
>http://www.99soft.org/
>
>
>On Fri, Jul 27, 2012 at 11:55 AM, Emmanuel Lécharny 
>wrote:
>
>>
>> I wish the proposal made my Jukka includes this matter.
>>
>>
>> Le 7/27/12 11:32 AM, sebb a écrit :
>>
>>> On 27 July 2012 08:22, Francesco Chicchiriccò 
>wrote:

 On 27/07/2012 08:13, Emmanuel Lécharny wrote:
>
> Le 7/27/12 1:02 AM, Joe Schaefer a écrit :
>>
>> I believe Bill is complaining not about the venue,
>> but the choice of referring to this package as
>> a "release candidate" instead of simply dropping
>> the "RC" portion of the package name like other
>> projects typically do with approved candidates.
>
>
> Ah, ok. Makes sense then.
>
> My perception is that the Syncope guys are trying to cut a 1.0.0,
> instead
> of going through many 0.x.0 before, therefore they are iterating on RC
> atm.


 Indeed, yes.


> It's pretty much semantic, IMHO.
>>>
>>> In other ASF projects I've seen, the convention is to use -alpha1 or
>>> -beta2 etc. to designate such stages.
>>>
>>> Release Candidate (RC) has a specific meaning in the ASF, as it is
>>> what is voted on before release.
>>>
>>> So one would vote on
>>>
>>> 1.0.0-beta3-incubating-RCn
>>>
>>> and a successful vote would result in the release of
>>>
>>> 1.0.0-beta3-incubating
>>>
>>> A failed vote for RCn would normally result in trying again with RCn+1
>>> to address the cause of the failure.
>>>
 Thanks!


> Do incubator peeps think it's a wrong approach?


 I hope it's not: anyway, this RC3 should be the last one before actual
 1.0.0-incubating.

 Regards.

 --
 Francesco Chicchiriccò

 ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
 http://people.apache.org/~ilgrosso/



 -
 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
>>>
>>
>>
>> --
>> Regards,
>> Cordialement,
>> Emmanuel Lécharny
>> www.iktek.com
>>
>>
>> -
>> 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 Amber 0.22-incubating

[Franklin, Matthew B.]

+1. 

Good job Amber team.  The sigs check out, headers look good with the exception 
of the .json files (as expected), LICENSE & NOTICE look like due diligence was 
performed.

One note to Simone You need to get your key signed :) 

-Matt

>-Original Message-
>From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On
>Behalf Of Simone Tripodi
>Sent: Wednesday, July 18, 2012 3:34 AM
>To: general@incubator.apache.org
>Subject: [VOTE] Release Apache Amber 0.22-incubating
>
>Good morning IPMC,
>
>I'm writing today to submit you the VOTE of the first release ever of
>Apache Amber 0.22 under the Incubator.
>
>PPMC vote already passed on amber-dev@  with
>already 1 IPMC binding vote.
>
>We solved 28 issues:
>http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311100&;
>styleName=Html&version=12322240
>
>There are still 14 issues left in JIRA:
>http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12
>311100&status=1
>
>SVN source tag (r1359173):
>https://svn.apache.org/repos/asf/incubator/amber/tags/amber-0.22-
>incubating/
>
>Staging repo:
>https://repository.apache.org/content/repositories/orgapacheamber-039/
>
>Staging binaries:
>http://people.apache.org/builds/incubator/amber/
>
>Staging site:
>http://incubator.apache.org/amber/0.22-incubating/
>
>PGP release keys (signed using 19FEA27D):
>http://www.apache.org/dist/incubator/amber/KEYS
>
>Vote will be open for 72 hours and will close ~ on July the 21th at 7:30am GMT
>
>[ ] +1, let's get it rmblee!!!
>[ ] +/-0, fine, but consider to fix few issues before...
>[ ] -1, nope, because... (and please explain why)
>
>Many thanks in advance, all the best!
>-Simo
>
>http://people.apache.org/~simonetripodi/
>http://simonetripodi.livejournal.com/
>http://twitter.com/simonetripodi
>http://www.99soft.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] Drill for the Apache Incubator

[Franklin, Matthew B.]

>-Original Message-
>From: Marvin Humphrey [mailto:mar...@rectangular.com]
>Sent: Monday, August 06, 2012 12:25 PM
>To: general@incubator.apache.org
>Cc: Grant Ingersoll; Isabel Drost
>Subject: Re: [PROPOSAL] Drill for the Apache Incubator
>
>On Thu, Aug 2, 2012 at 3:12 PM, Ted Dunning 
>wrote:
>
>> Initial Source
>> ==
>> There is no initial source code. All source code will be developed within
>> the Apache Incubator.
>
>Coming in without any source code is going to pose a challenge to this
>podling.
>
>http://www.apache.org/foundation/how-it-works.html#incubator
>
>The incubator filters projects on the basis of the likeliness of
>them becoming
>successful meritocratic communities. The basic requirements for incubation
>are:
>
>* a working codebase -- over the years and after several failures, the
>  foundation came to understand that without an initial working
>  codebase, it is generally hard to bootstrap a community. This is
>  because merit is not well recognized by developers without a working
>  codebase. Also, the friction that is developed during the initial
>  design stage is likely to fragment the community.

It seems like there could be flexibility in this requirement, based on a few 
factors.  In this case, a design discussion has been ongoing; but I would also 
think that any community coming in with enough people who know the Apache way 
may also not need as much of a solid starting point code wise.

>
>That last line in particular seems like something to watch out for.
>
>Marvin Humphrey
>
>-
>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

Amber - A Shepherd's View

[Franklin, Matthew B.]

Community looks well on the way to graduation.  Congratulations on the
recent release.

There are a few things on the status page that need to be filled in and
processes [1] like suitable name search need to be completed prior to
graduation vote at the IPMC level.

[1]:http://incubator.apache.org/guides/graduation.html#checklist


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

RE: [VOTE] Accept Drill into the Apache Incubator

[Franklin, Matthew B.]

+1 (binding)

>-Original Message-
>From: Ted Dunning [mailto:ted.dunn...@gmail.com]
>Sent: Tuesday, August 07, 2012 10:41 PM
>To: general@incubator.apache.org
>Subject: [VOTE] Accept Drill into the Apache Incubator
>
>I would like to call a vote for accepting Drill for incubation in the
>Apache Incubator. The full proposal is available below.  Discussion
>over the last few days has been quite positive.
>
>Please cast your vote:
>
>[ ] +1, bring Drill into Incubator
>[ ] +0, I don't care either way,
>[ ] -1, do not bring Drill into Incubator, because...
>
>This vote will be open for 72 hours and only votes from the Incubator
>PMC are binding.  The start of the vote is just before 3AM UTC on 8
>August so the closing time will be 3AM UTC on 11 August.
>
>Thank you for your consideration!
>
>Ted
>
>http://wiki.apache.org/incubator/DrillProposal
>
>= Drill =
>
>== Abstract ==
>Drill is a distributed system for interactive analysis of large-scale
>datasets, inspired by
>[[http://research.google.com/pubs/pub36632.html|Google's Dremel]].
>
>== Proposal ==
>Drill is a distributed system for interactive analysis of large-scale
>datasets. Drill is similar to Google's Dremel, with the additional
>flexibility needed to support a broader range of query languages, data
>formats and data sources. It is designed to efficiently process nested
>data. It is a design goal to scale to 10,000 servers or more and to be
>able to process petabyes of data and trillions of records in seconds.
>
>== Background ==
>Many organizations have the need to run data-intensive applications,
>including batch processing, stream processing and interactive
>analysis. In recent years open source systems have emerged to address
>the need for scalable batch processing (Apache Hadoop) and stream
>processing (Storm, Apache S4). In 2010 Google published a paper called
>"Dremel: Interactive Analysis of Web-Scale Datasets," describing a
>scalable system used internally for interactive analysis of nested
>data. No open source project has successfully replicated the
>capabilities of Dremel.
>
>== Rationale ==
>There is a strong need in the market for low-latency interactive
>analysis of large-scale datasets, including nested data (eg, JSON,
>Avro, Protocol Buffers). This need was identified by Google and
>addressed internally with a system called Dremel.
>
>In recent years open source systems have emerged to address the need
>for scalable batch processing (Apache Hadoop) and stream processing
>(Storm, Apache S4). Apache Hadoop, originally inspired by Google's
>internal MapReduce system, is used by thousands of organizations
>processing large-scale datasets. Apache Hadoop is designed to achieve
>very high throughput, but is not designed to achieve the sub-second
>latency needed for interactive data analysis and exploration. Drill,
>inspired by Google's internal Dremel system, is intended to address
>this need.
>
>It is worth noting that, as explained by Google in the original paper,
>Dremel complements MapReduce-based computing. Dremel is not intended
>as a replacement for MapReduce and is often used in conjunction with
>it to analyze outputs of MapReduce pipelines or rapidly prototype
>larger computations. Indeed, Dremel and MapReduce are both used by
>thousands of Google employees.
>
>Like Dremel, Drill supports a nested data model with data encoded in a
>number of formats such as JSON, Avro or Protocol Buffers. In many
>organizations nested data is the standard, so supporting a nested data
>model eliminates the need to normalize the data. With that said, flat
>data formats, such as CSV files, are naturally supported as a special
>case of nested data.
>
>The Drill architecture consists of four key components/layers:
> * Query languages: This layer is responsible for parsing the user's
>query and constructing an execution plan.  The initial goal is to
>support the SQL-like language used by Dremel and
>[[https://developers.google.com/bigquery/docs/query-reference|Google
>BigQuery]], which we call DrQL. However, Drill is designed to support
>other languages and programming models, such as the
>[[http://www.mongodb.org/display/DOCS/Mongo+Query+Language|Mongo
>Query
>Language]], [[http://www.cascading.org/|Cascading]] or
>[[https://github.com/tdunning/Plume|Plume]].
> * Low-latency distributed execution engine: This layer is responsible
>for executing the physical plan. It provides the scalability and fault
>tolerance needed to efficiently query petabytes of data on 10,000
>servers. Drill's execution engine is based on research in distributed
>execution engines (eg, Dremel, Dryad, Hyracks, CIEL, Stratosphere) and
>columnar storage, and can be extended with additional operators and
>connectors.
> * Nested data formats: This layer is responsible for supporting
>various data formats. The initial goal is to support the column-based
>format used by Dremel. Drill is designed to support schema-based
>formats such as Protocol Buffers/Dremel, Avro/AVRO-806/Trevn

RE: Preparing for August report

[Franklin, Matthew B.]

I reviewed droids and thought their report adequately represented the project 
state.






-Original Message-
From: Jukka Zitting [jukka.zitt...@gmail.com]
Sent: Wednesday, August 08, 2012 06:37 PM Eastern Standard Time
To: general
Subject: Re: Preparing for August report


Hi,

On Mon, Aug 6, 2012 at 12:14 PM, Jukka Zitting  wrote:
> That leaves only the reviews to be done. Here's the latest TODO list:

And an updated one:

  Benson Margulies - Syncope, Nuvem
  Dave Fisher  - DeltaSpike
  Matt Franklin- Droids
  Matt Hogstrom- SIS, Wookie
  Mohammad Nour- Airavata
  Ross Gardler - Wink

That's quite a few reports still to review and the report deadline is
close. Please let me know if you're still on it (or update the wiki
page directly), otherwise I'll take over tomorrow to review any
remaining reports.

BR,

Jukka Zitting

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

RE: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1

[Franklin, Matthew B.]

If no one else beats me to it, I will review this before the end of the weekend.

-Matt

>-Original Message-
>From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com]
>Sent: Friday, August 10, 2012 7:28 AM
>To: general@incubator.apache.org
>Cc: openmeetings-...@incubator.apache.org
>Subject: Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating
>Release Candidate 1
>
>Thanks Alexei!
>
>Still 1 IPMC vote missing
>
>Thanks
>Sebastian
>
>2012/8/10 Alexei Fedotov 
>
>> +1
>>
>>
>> --
>> With best regards / с наилучшими пожеланиями,
>> Alexei Fedotov / Алексей Федотов,
>> http://dataved.ru/
>> +7 916 562 8095
>>
>>
>> On Fri, Aug 10, 2012 at 11:32 AM, seba.wag...@gmail.com
>>  wrote:
>> > Yegor & Jukka thanks for review and voting!
>> >
>> > We still need one IPMC vote to approve that release.
>> >
>> > Those are just integration plugins for the ELearning Platform Moodle.
>> > roughly 20 files zipped to packages, ~40KByte each, zero dependencies,
>> > 2 minutes to check :)
>> >
>> > Release artefacts:
>> > http://people.apache.org/~sebawagner/moodle-plugin-1.4-incubating/
>> >
>> > Thanks!
>> > Sebastian
>> >
>> > 2012/8/9 Yegor Kozlov 
>> >
>> >> +1
>> >>
>> >> Yegor
>> >>
>> >> On Mon, Aug 6, 2012 at 4:44 PM, seba.wag...@gmail.com
>> >>  wrote:
>> >> > Dear Incubator Members,
>> >> >
>> >> > I would like to start a vote about releasing Apache OpenMeetings
>> Moodle
>> >> > Plugin 1.4 Incubating Release Candidate 1
>> >> >
>> >> > There was already a positive vote on the developer mailing list:
>> >> > +1 PPMC:
>> >> > solomax, albus, eschwert, german, aaf(mentor), sebawagner
>> >> >
>> >> > Vote Thread:
>> >> > http://markmail.org/thread/db4bhkroe6yun5bi
>> >> >
>> >> > Changes are in the Changelog:
>> >> >
>> >>
>>
>http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo
>dle/1.4RC1/CHANGELOG
>> >> >
>> >> > Release artefacts:
>> >> > http://people.apache.org/~sebawagner/moodle-plugin-1.4-
>incubating/
>> >> >
>> >> > Tag:
>> >> >
>> >>
>>
>http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo
>dle/1.4RC1/
>> >> >
>> >> > PGP release keys (signed using 93A30395):
>> >> > http://www.apache.org/dist/incubator/openmeetings/KEYS
>> >> >
>> >> > Vote will be open for 72 hours.
>> >> >
>> >> > [ ] +1  approve
>> >> > [ ] +0  no opinion
>> >> > [ ] -1  disapprove (and reason why)
>> >> >
>> >> >
>> >> > Thanks!
>> >> > Sebastian
>> >> > --
>> >> > Sebastian Wagner
>> >> > https://twitter.com/#!/dead_lock
>> >> > http://www.webbase-design.de
>> >> > http://www.wagner-sebastian.com
>> >> > seba.wag...@gmail.com
>> >>
>> >
>> >
>> >
>> > --
>> > Sebastian Wagner
>> > https://twitter.com/#!/dead_lock
>> > http://www.webbase-design.de
>> > http://www.wagner-sebastian.com
>> > seba.wag...@gmail.com
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
>
>--
>Sebastian Wagner
>https://twitter.com/#!/dead_lock
>http://www.webbase-design.de
>http://www.wagner-sebastian.com
>seba.wag...@gmail.com

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

Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1

[Franklin, Matthew B.]

+1 (binding) for the release.

On 8/10/12 7:47 AM, "Franklin, Matthew B."  wrote:

>If no one else beats me to it, I will review this before the end of the
>weekend.

 s/the weekend/Monday  (apologies)

>
>-Matt
>
>>-Original Message-
>>From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com]
>>Sent: Friday, August 10, 2012 7:28 AM
>>To: general@incubator.apache.org
>>Cc: openmeetings-...@incubator.apache.org
>>Subject: Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating
>>Release Candidate 1
>>
>>Thanks Alexei!
>>
>>Still 1 IPMC vote missing
>>
>>Thanks
>>Sebastian
>>
>>2012/8/10 Alexei Fedotov 
>>
>>> +1
>>>
>>>
>>> --
>>> With best regards / с наилучшими пожеланиями,
>>> Alexei Fedotov / Алексей Федотов,
>>> http://dataved.ru/
>>> +7 916 562 8095
>>>
>>>
>>> On Fri, Aug 10, 2012 at 11:32 AM, seba.wag...@gmail.com
>>>  wrote:
>>> > Yegor & Jukka thanks for review and voting!
>>> >
>>> > We still need one IPMC vote to approve that release.
>>> >
>>> > Those are just integration plugins for the ELearning Platform Moodle.
>>> > roughly 20 files zipped to packages, ~40KByte each, zero
>>>dependencies,
>>> > 2 minutes to check :)
>>> >
>>> > Release artefacts:
>>> > http://people.apache.org/~sebawagner/moodle-plugin-1.4-incubating/
>>> >
>>> > Thanks!
>>> > Sebastian
>>> >
>>> > 2012/8/9 Yegor Kozlov 
>>> >
>>> >> +1
>>> >>
>>> >> Yegor
>>> >>
>>> >> On Mon, Aug 6, 2012 at 4:44 PM, seba.wag...@gmail.com
>>> >>  wrote:
>>> >> > Dear Incubator Members,
>>> >> >
>>> >> > I would like to start a vote about releasing Apache OpenMeetings
>>> Moodle
>>> >> > Plugin 1.4 Incubating Release Candidate 1
>>> >> >
>>> >> > There was already a positive vote on the developer mailing list:
>>> >> > +1 PPMC:
>>> >> > solomax, albus, eschwert, german, aaf(mentor), sebawagner
>>> >> >
>>> >> > Vote Thread:
>>> >> > http://markmail.org/thread/db4bhkroe6yun5bi
>>> >> >
>>> >> > Changes are in the Changelog:
>>> >> >
>>> >>
>>>
>>http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo
>>dle/1.4RC1/CHANGELOG
>>> >> >
>>> >> > Release artefacts:
>>> >> > http://people.apache.org/~sebawagner/moodle-plugin-1.4-
>>incubating/
>>> >> >
>>> >> > Tag:
>>> >> >
>>> >>
>>>
>>http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo
>>dle/1.4RC1/
>>> >> >
>>> >> > PGP release keys (signed using 93A30395):
>>> >> > http://www.apache.org/dist/incubator/openmeetings/KEYS
>>> >> >
>>> >> > Vote will be open for 72 hours.
>>> >> >
>>> >> > [ ] +1  approve
>>> >> > [ ] +0  no opinion
>>> >> > [ ] -1  disapprove (and reason why)
>>> >> >
>>> >> >
>>> >> > Thanks!
>>> >> > Sebastian
>>> >> > --
>>> >> > Sebastian Wagner
>>> >> > https://twitter.com/#!/dead_lock
>>> >> > http://www.webbase-design.de
>>> >> > http://www.wagner-sebastian.com
>>> >> > seba.wag...@gmail.com
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Sebastian Wagner
>>> > https://twitter.com/#!/dead_lock
>>> > http://www.webbase-design.de
>>> > http://www.wagner-sebastian.com
>>> > seba.wag...@gmail.com
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>>
>>--
>>Sebastian Wagner
>>https://twitter.com/#!/dead_lock
>>http://www.webbase-design.de
>>http://www.wagner-sebastian.com
>>seba.wag...@gmail.com
>
>-
>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] Graduate Airavata from the incubator

[Franklin, Matthew B.]

+1 

>-Original Message-
>From: Suresh Marru [mailto:sma...@apache.org]
>Sent: Friday, September 07, 2012 6:59 AM
>To: general@incubator.apache.org
>Subject: [VOTE] Graduate Airavata from the incubator
>
>Hi All,
>
>Since entering Incubation in May 2011, the Airavata community has evolved
>and has been steadily growing. The project has made 3 releases, added 6 new
>committers and PPMC members. The podling has been very actively using
>mailing list and JIRA and all communication is in open. Thanks to very hands-on
>mentors, the project has learned to self-govern and has been following the
>Apache Way.
>
>The project incubator status page [1] is up to date and trademarks has
>approved Airavata as a name for TLP [2]. The community has discussed
>graduation and prepared a board charter [3]. The initial PMC has been opted
>in on the private mailing list and PMC chair has been elected on the dev list
>[4]. The community feels ready to graduate [5] and voted 19 positives votes
>and no negative votes.
>
>We request the IPMC to vote on the resolution to establish Airavata and to
>recommend the resolution to the board.
>
>Please cast your vote :
>
>[  ] +1 Graduate Airavata podling from Apache Incubator
>[  ] -1 Airavata podling is not yet ready to graduate because 
>
>This vote will be open for at least 72 hours. Please find the proposed board
>resolution below.
>
>Cheers,
>Suresh
>
>[1] http://incubator.apache.org/projects/airavata.html
>[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-14
>[3] http://markmail.org/message/gsq3jnwi6lpnz7tq
>[4] http://markmail.org/message/7ngzcbvpzhl2phlp
>[5] http://markmail.org/message/s3tubyx7bpxwbqiz
>
>
>
>X. Establish the Apache Airavata Project
>
>   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 executing and managing
>   computational jobs on distributed computing resources
>   including local clusters, supercomputers, national grids,
>   academic and commercial clouds and 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 Airavata Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Airavata Project be and hereby is
>   responsible for the creation and maintenance of  software
>   related to executing and managing computational jobs on
>   distributed computing resources including local clusters,
>   supercomputers, national grids, academic and commercial clouds;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Airavata" 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 Airavata Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Airavata 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 Airavata Project:
>
>   Aleksander Slominski  
>   Ate Douma 
>   Chathura Herath   
>   Eran Chinthaka
>   Srinath Perera
>   Heshan Suriyaarachchi 
>   Lahiru Gunathilake
>   Marlon Pierce 
>   Patanachai Tangchaisin
>   Raminderjeet Singh
>   Saminda Wijeratne 
>   Shahani Weerawarana   
>   Suresh Marru  
>   Thilina Gunarathne
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Suresh Marru
>   be appointed to the office of Vice President, Apache Airavata, 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 Airavata PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Airavata Project; and be it further
>
>   RESOLVED, that the Apache Airavata Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Airavata podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Airavata podling encumbered upon the Apache Inc

RE: Usage of JRebel in Apache projects

[Franklin, Matthew B.]

>-Original Message-
>From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com]
>Sent: Wednesday, September 12, 2012 3:06 AM
>To: general@incubator.apache.org
>Cc: openmeetings-...@incubator.apache.org
>Subject: Usage of JRebel in Apache projects
>
>Hi,
>
>JRebel already offers a 1 year for free license for OSS projects. But
>I wonder if there is already a License for the Apache Foundation that
>committers can use?

My understanding of their terms is that it is a per-project license.  Unless 
other IPMC members have better information, I think you can just request a 
license on behalf of your project and manage its distribution via a private SVN 
location.

>
>Thanks!
>Sebastian
>--
>Sebastian Wagner
>https://twitter.com/#!/dead_lock
>http://www.webbase-design.de
>http://www.wagner-sebastian.com
>seba.wag...@gmail.com
>
>-
>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: September Reports

[Franklin, Matthew B.]

>-Original Message-
>From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
>Sent: Thursday, September 13, 2012 10:54 AM
>To: general@incubator.apache.org
>Subject: Re: September Reports
>
>Hi,
>
>On Thu, Sep 13, 2012 at 12:53 PM, Mohammad Nour El-Din
> wrote:
>> I have some time tonight is there something I can help in ?
>
>Sure, thanks! It would be great if you could take a look at some of
>the following reports unless the previously assigned shepherds beat
>you to it:
>
>  Matt Franklin- Isis, NPanday, Wave

I am in progress with these and will have reviewed them by end of day.  
Additional eyes don't hurt though.

>  Matt Hogstrom- Bigtop, Openmeetings
>
>BR,
>
>Jukka Zitting
>
>-
>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

Isis: A Shepherd's View

[Franklin, Matthew B.]

Good report.  Two questions/comments:
  - Why not just propose the committers and see what the PPMC thinks before 
holding an official vote?  Is there a reason for waiting?
  - The incubator status page needs to be completed.  It appears that more has 
happened than the page reflects.

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

Wave: A Shepherd's View

[Franklin, Matthew B.]

Is there anything that could be released, even in alpha/beta form?  Code 
completeness or maturity is not a barrier to graduation so long as the 
community can demonstrate an understanding of the Apache release process.  IMO, 
it is best to get early, alpha releases out on a regular basis.  You don't have 
to advertise them as completely ready for prime time.

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

NPanday: A Shepherd's View

[Franklin, Matthew B.]

I am concerned about the level of engagement of the community.  The vast 
majority of mail traffic has been from automated build failures and even a 
question from a potential user saw no response from the committers/PPMC. 

IMHO, there needs to be a significant increase in engagement over time before 
the project would be ready to graduate.

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

RE: September Reports

[Franklin, Matthew B.]

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Thursday, September 13, 2012 11:58 AM
>To: general@incubator.apache.org
>Subject: RE: September Reports
>
>>-Original Message-
>>From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
>>Sent: Thursday, September 13, 2012 10:54 AM
>>To: general@incubator.apache.org
>>Subject: Re: September Reports
>>
>>Hi,
>>
>>On Thu, Sep 13, 2012 at 12:53 PM, Mohammad Nour El-Din
>> wrote:
>>> I have some time tonight is there something I can help in ?
>>
>>Sure, thanks! It would be great if you could take a look at some of
>>the following reports unless the previously assigned shepherds beat
>>you to it:
>>
>>  Matt Franklin- Isis, NPanday, Wave
>
>I am in progress with these and will have reviewed them by end of day.
>Additional eyes don't hurt though.

Apologies.  Yesterday turned out to be impractical for me.  I have finished my 
reviews and posted to the wiki & list.

>
>>  Matt Hogstrom- Bigtop, Openmeetings
>>
>>BR,
>>
>>Jukka Zitting
>>
>>-
>>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: key signing

[Franklin, Matthew B.]

>-Original Message-
>From: Marvin Humphrey [mailto:mar...@rectangular.com]
>Sent: Friday, October 05, 2012 8:54 PM
>To: general@incubator.apache.org
>Subject: Re: key signing
>
>On Fri, Oct 5, 2012 at 8:55 AM, Jukka Zitting  wrote:
>> It's good to recommend people to get their keys signed by someone in
>> the Apache web of trust and I think we could do more in that area,
>
>Maybe if we didn't insist on face-to-face meetings we'd get better adoption
>rates.
>
>Apache dev docs:
>
>http://www.apache.org/dev/openpgp.html#wot-link-in
>
>How To Link Into A Public Web Of Trust
>
>In short, expect that:
>
>*   this will involve a face-to-face meeting
>
>GnuPG docs:
>
>http://www.gnupg.org/gph/en/manual.html#AEN84
>
>A key's fingerprint is verified with the key's owner.  This may be done in
>person or over the phone or through any other means as long as you can
>guarantee that you are communicating with the key's true owner.

+1.  I think with technologies like Skype & Google Hangout, we can get the same 
level of assurance of a person's identity as a physical key signing party.

What if we held a regular Google Hangout Key Signing party?  We can always ask 
participants to show IDs :)

>
>Marvin Humphrey
>
>-
>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: Preparing for the October reports

[Franklin, Matthew B.]

>-Original Message-
>From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
>Sent: Wednesday, October 10, 2012 7:28 PM
>To: general
>Subject: Re: Preparing for the October reports
>
>Hi,
>
>On Mon, Sep 24, 2012 at 10:34 PM, Jukka Zitting 
>wrote:
>> It would be nice if we had all reviews ready by Tuesday, October 9th,
>> to give one extra day for unexpected delays.
>
>I'm again running a bit late on completing the Incubator report. I
>hope to have it finished and submitted already tomorrow, but for that
>we still need the following shepherd reviews:
>
>   Dave Fisher  - Celix
>   Jukka Zitting- EasyAnt
>   Matt Franklin- CloudStack, Tashi
>   Matt Hogstrom- VXQuery
>   Ross Gardler - DeviceMap, JSPWiki
>
>Let us know if you won't have time to do the review by tomorrow, so I
>or someone else can jump in where needed.

I will have mine in tomorrow morning.  Apologies for the tardiness. 

>
>BR,
>
>Jukka Zitting
>
>-
>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

Tashi: A Shepherd's View

[Franklin, Matthew B.]

I am concerned about the lack of mail list and JIRA activity for the podling 
since the last reporting period.  There has been very little activity, but the 
report indicates a lot of work was completed.  I did see a bunch of commits in 
August, but the only e-mails on the list were from the committing developer and 
there were only 2 at that.

In short, it appears that Tashi does not currently have sufficient community 
activity to be on a path to graduation.

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

RE: Preparing for the October reports

[Franklin, Matthew B.]

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Wednesday, October 10, 2012 9:18 PM
>To: general
>Subject: RE: Preparing for the October reports
>
>>-Original Message-
>>From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
>>Sent: Wednesday, October 10, 2012 7:28 PM
>>To: general
>>Subject: Re: Preparing for the October reports
>>
>>Hi,
>>
>>On Mon, Sep 24, 2012 at 10:34 PM, Jukka Zitting 
>>wrote:
>>> It would be nice if we had all reviews ready by Tuesday, October 9th,
>>> to give one extra day for unexpected delays.
>>
>>I'm again running a bit late on completing the Incubator report. I
>>hope to have it finished and submitted already tomorrow, but for that
>>we still need the following shepherd reviews:
>>
>>   Dave Fisher  - Celix
>>   Jukka Zitting- EasyAnt
>>   Matt Franklin- CloudStack, Tashi
>>   Matt Hogstrom- VXQuery
>>   Ross Gardler - DeviceMap, JSPWiki
>>
>>Let us know if you won't have time to do the review by tomorrow, so I
>>or someone else can jump in where needed.
>
>I will have mine in tomorrow morning.  Apologies for the tardiness.

I have reviewed both communities and sent notes regarding Tashi.  Cloudstack 
looks to be settling in nicely.

>
>>
>>BR,
>>
>>Jukka Zitting
>>
>>-
>>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: [VOTE] Ripple Emulator to be admitted to the incubator

[Franklin, Matthew B.]

+1 (binding)

>-Original Message-
>From: Gord Tanner [mailto:gtan...@gmail.com]
>Sent: Thursday, October 11, 2012 12:04 PM
>To: general@incubator.apache.org
>Subject: [VOTE] Ripple Emulator to be admitted to the incubator
>
>Please cast your votes!
>
>[ ] +1, recommend Ripple to move into the incubator
>[ ] +0, abstain/don't care
>[ ] -1, do not recommend Ripple to move into the incubator,because...
>
>
>
>Ripple, A Mobile Environment Emulator
>=
>
>Abstract
>
>
>Ripple is a browser based mobile phone emulator designed to aid in the
>development
>of HTML5 based mobile applications.  Ripple is a cross platform and cross
>runtime testing/debugging tool. It currently supports such runtimes as
>Cordova, WebWorks
>and the Mobile Web.
>
>Proposal
>
>
>Ripple is going to be (in some circles already is) the goto emulator
>for rapid development of mobile web applications. This
>will be accomplished by quickly keeping up with the mobile web
>platforms as they arise (Cordova, Tizen, WAC, WebWorks, etc).
>
>Background
>==
>
>Ripple started as a product of tinyHippos and was aquired by Research
>in Motion in late March 2011.  Ripple was then open sourced
>under the Apache 2.0 License and hosted on the blackberry github
>account (http://github.com/blackberry/Ripple-UI).
>
>Ripple is a browser based mobile phone emulator that runs as a chrome
>extension.  It fills the gap for developers between
>developing on their desktops/laptops and having to test on platform
>specific emulators or physical devices. Ripple allows develors
>to quickly edit-refresh-test in Chrome on their desktops/laptops while
>working on web content that will be embedded and distributed
>as a native application.
>
>Rationale
>=
>
>The project is currently opensourced and managed by a small team at
>Research in Motion.  We are starting to have some
>more community engagement but the project could benefit from greater
>exposure in the open source cummunity.  Our team
>overlaps highly with the Cordova group. Watching the success for that
>project in Apache has inspired us to contribute
>Ripple to the ASF as well.
>
>Ripple fills a large gap in the toolset for most mobile web developers
>between development on the desktop and testing
>on the physical device.
>
>Current Status
>==
>
>Currently all development is managed on github via the issues and the
>direction of the project is strongly influenced by
>Research in Motion.  A more clear project plan and more open
>communication will be needed by this project to abide by
>the apache guidelines.
>
>Metriocracy
>===
>
>Ripple has been very accepting of letting in patches from 3rd party
>developers and has been functioning like apache in requiring a CLA
>for code to be pulled in. The core team is hoping to grow and include more
>developers.
>
>Community
>=
>
>The development community of Ripple is a small but tight knit group but
>the users of the project number more than 40,000. With the launch
>ofemulate.phonegap.com (which is a portal for installing ripple) we
>are
>getting approx 5000 hits a day to that site.
>
>
>Core Developers
>===
>
>See Inital Committers below.
>
>Alignment
>=
>
>Apache is a good match for this project due to it's close ties
>to the Cordova Project. Cordova has been very successful as a project
>since joining Apache and we hope Ripple will follow suit.
>
>Known Risks
>===
>
>Orphaned Products
>-
>
>Ripple is a core component to the toolset at RIM and the Cordova /
>Phonegap community has embrased ripple into their tooling
>as well. This project has been under active development for 3 years
>and a lot of vested interest from both RIM and the
>community is already present to keep the tool up to date.
>
>Inexperience with Open Source
>-
>
>Ripple has been opensourced at RIM for the last year.  All of the work
>is done in the open. There are a few extra measures we need to learn
>how to take (mailing lists, project planning) for working within the
>ASF community.
>However the team has a good understanding of what needs to happen, as
>some of the
>team are also contributers to the Apache Cordova Incubator project.
>
>Homogenous Developers
>--
>
>Ripple's core team currently all works at RIM with contributions for
>some features done by third parties.  There is a
>backlog of features currently done / being put in by third parties
>such as Adobe and IBM.
>
>Reliance on Salaried Developers
>---
>
>Most of the developers are paid by their employer to contribute to
>this project but are all highly involved on a personal
>level with this project as well as the mobile web community.
>
>Relationships with Other Apache Products
>
>
>There is a strong overlap and relationship between the ripple and
>cordova teams.  Gord Tanner is an active

RE: [VOTE] Graduate Wookie podling from the incubator

[Franklin, Matthew B.]

+1 

>-Original Message-
>From: Scott Wilson [mailto:scott.bradley.wil...@gmail.com]
>Sent: Wednesday, October 24, 2012 2:33 PM
>To: general@incubator.apache.org
>Subject: [VOTE] Graduate Wookie podling from the incubator
>
>This is a call for vote to graduate the Wookie podling from Apache Incubator.
>
>Wookie entered the Incubator in July of 2009. During incubation, Wookie has:
>
>* Produced 5 releases
>* Added 3 new Committer/PPMC members
>* Cleared IP on all donations
>* Learned to self-govern and engage the community
>* Received and applied multiple community patches
>
>The Wookie community has voted to proceed with graduation [1] and the
>result
>can be found at [2].
>
>Please VOTE on the resolution below:
>
>[ ] +1 Graduate Wookie from the Incubator per the resolution below.
>[ ] +0 Don't care.
>[ ] -1  Don't graduate Wookie from the Incubator because..
>
>This vote will be open for at least 72 hours.
>
>[1] http://markmail.org/message/jcgdcacn535jqwqy
>[2] http://markmail.org/message/hp2bggjhec7vpdch
>
>==
>
>X. Establish the Apache Wookie Project
>
>   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 an implementation of the
>   W3C Widgets family of specifications 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 Wookie Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Wookie Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to implementation of the W3C Widgets family of
>   specifications; and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Wookie" 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 Wookie Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Wookie 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 Wookie Project:
>
>   * Scott Wilson
>   * Ate Douma   
>   * Ross Gardler
>   * Matt Franklin   
>   * Paul Sharples   
>   * Kris Popat  
>   * Raido Kuli  
>   * Hoang Minh Tien 
>
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Scott Wilson
>   be appointed to the office of Vice President, Apache Wookie, 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 Wookie PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Wookie Project; and be it further
>
>   RESOLVED, that the Apache Wookie Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Wookie podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Wookie podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.


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

[PROPOSAL] Apache Steams Project

[Franklin, Matthew B.]

I would like to propose a new Activity Streams server project to the
Incubator.  The proposal is on the wiki at the following location:

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


Streams is a collaborative effort from multiple organizations and
individuals working with and around the Activity Streams specification
(http://activitystrea.ms).

We are looking forward to your feedback and suggestions.

-Matt Franklin

- COPY OF PROPOSAL FROM
http://wiki.apache.org/incubator/StreamsProposal -


Apache Streams Proposal
 
== Abstract ==

Apache Streams will be a lightweight server for ActivityStreams. The role
of Apache Streams is to provide a central point of aggregation, filtering
and querying for Activities that have been submitted by disparate systems.
 Apache Streams also intends to include a mechanism for intelligent
filtering and recommendation to reduce the noise to end users.

== Proposal ==

Apache Streams will bring together individuals who are or are looking to
increase and centralize the production, consumption and federation of
ActivityStreams throughout enterprise organizations and the Internet as a
whole.  The target features include:

 * Publication of Activities from multiple systems via HTTP
 * Aggregation and syndication of streams
 * Support for security trimming of streams by social graph
 * Noise reduction and intelligent filtering
 * Federation of streams across disparate systems
 * Provide libraries for easy integration in source systems

== Background ==

The ActivityStreams specification standardizes a generic format for
describing event-based data.  Many social web companies have adopted the
format and it has been included in the OpenSocial specification as the
preferred method for delivery of activity data.  During discussions of
ActivityStreams at OpenSocial events earlier in the year, it became clear
that multiple organizations are facing similar issues as to the
publication and filtering of their activities and would benefit from a
commonly-developed, open-source ActivityStreams server.

== Rationale ==

In deployment, activities are generated from multiple sources.  This is
particularly true within the enterprise where disparate systems create and
manage activities in stove pipes.  What is needed is a central point for
consumption, aggregation and exposure of activities generated within these
systems.

== Initial Goals ==

The initial goal of the project is to survey donated code and develop a
common, high-level architecture for an initial release.  The project will
then work toward that release in a new code base, pulling in pieces of
donated code as necessary.

== Current Status ==

The MITRE Corporation will donate its prototype code to the project.
Aside from this, the project is new and will need bootstrap time to
develop an initial architecture and roadmap.

 Meritocracy 

As a new project with many team members who are seasoned Apache veterans,
Apache Streams is prepared to build the project under the Apache Way.
   
 Community 

The Apache Streams community combines multiple individuals from different
organizations, many of which have collaborated before in an open
environment.  Apache Streams is committed to expanding this community and
adhering to Apache principles of openness and collaboration.

== Known Risks ==

An exercise in self-knowledge. Risks don't mean that a project is
unacceptable. If they are recognized and noted then they can be addressed
during incubation.

 Inexperience with Open Source 

Most of the initial committers have worked in open source and many are
familiar with the ASF and the Apache Way; but, not all.  Additionally,
many of the committers have not worked on a software project together and
will need time to familiarize themselves with each other.

 Speed of Development 

This project is dependent upon contributions made on company time. For
this approach to succeed, the project must deliver a workable system in a
timeframe acceptable to those companies. The initial parties have the
intention of releasing a first version within 6 months after starting the
Incubator. Failure to do so could prevent the project reaching critical
mass, and could prevent the project from being in a position to attract
new developers.

 Reliance on Salaried Developers 

At present, the vast majority of contributors will be doing so as a part
of their day jobs. Therefore, as already alluded to, there is a risk that
the project won't gain enough traction to be of use to their employers.
However, given the centrality of these codebases to the participating
companies, it is clearly in their best interests to transition to an
openly developed alternative.

 Relationships with Other Apache Products 

Many of the initial committers will be integrating this software with
Apache Rave & Apache Shindig.  A possibility exists that code is developed
by either or both of the projects to support integration with Ap

Re: [VOTE][PROPOSAL] Hadoop Development Tools

[Franklin, Matthew B.]

+1 (binding)

On 11/6/12 10:57 AM, "Adam Berry"  wrote:

>Hello,
> 
>This proposal has been open for discussion for a a few weeks, so now
>submitting for a vote for this project to be accepted into the incubator.
>
>Cheers,
>Adam Berry
>
>= HDT (Hadoop Development Tools) =
> 
>== Abstract ==
>Tools to support developing applications that use Apache Hadoop from
>within Eclipse.
> 
>== Proposal ==
>Hadoop Development Tools are a set of extensions to Eclipse providing
>support for creating, launching and debugging distributed applications,
>as well as interacting with HDFS filesystems. This work will build on the
>existing Map Reduce Tools present in the Apache Hadoop project.
> 
>== Background ==
>Map Reduce Tools have existed as part of contrib for Apache Hadoop.
>Unfortunately they are source tied to a single version of Hadoop, and
>development has stalled, with little movement past the Hadoop 0.20 line.
> 
>== Rationale ==
>Support for newer versions of Hadoop from within Eclipse is regularly
>raised on the Hadoop mailing lists, so there is a clear need to drive
>these tools forward. Development tools generally are worked on separate
>from the target tools/platform, separating the tools out will allow for
>supporting multiple versions, so a developer could work with a
>heterogeneous environment.
> 
>== Initial Goals ==
> * Give the tools project a home of its own.
> * Port current MapReduce tools feature set to all current release lines
>of Hadoop in a single Eclipse install.
> * Documentation and tutorials for all features.
> * Publish Eclipse update site, and join Eclipse marketplace listing.
> * Establish release cycle that combines support for Hadoop and Eclipse
>release cycles.
> * Look to build support for YARN, MRUnit and possibly other
>Hadoop-related projects.
> 
>== Current Status ==
>The source for the current MapReduceTools lives in the contrib section of
>the Hadoop source. In its current implementation it is tied to the
>version of Hadoop against which it is compiled. The layout and API that
>it was developed with means that it can only be used with the 0.20 or 1.0
>Hadoop releases, the new layout and YARN api introduced with the 0.23 and
>2.0 lines are not supported.
>
>
>=== Meritocracy ===
>Several people and companies have already expressed an interest in
>contributing to this project, and we hope to attract additional interest
>during the proposal discussion. We plan to invest and support a
>meritocracy that attracts, invites, and supports newcomers to build a
>vibrant and  diverse community.
>
>=== Community ===
>The target community is developers who are working developing Map/Reduce
>applications against Hadoop. Given the success of Hadoop the target group
>is likely to be quite large. Separation from the Hadoop community would
>make it easier to support multiple versions of hadoop, as well as merging
>the release cycles of Hadoop and Eclipse to provide predictable iteration
>and improvement in the toolset.
>
>=== Core Developers ===
>The initial list of developers includes people experienced with Hadoop
>and developing against the Eclipse platform.
> * Adam Berry (amberry at yahoo-inc dot com)
> * Jeffrey Zemerick (jeffrrey at mtnfog dot com)
> * Evert Lammerts (Evert dot Lammerts at sara dot nl)
> * Simone Gianni (simoneg at apache dot org)
>
>=== Alignment ===
>Hadoop Development Tools aligns with both Hadoop and Eclipse. Hadoop as
>the platform for the development target, and Eclipse as the IDE platform
>used as the base for the tools.
> 
>== Known Risks ==
>
>=== Orphaned Products ===
>
>=== Inexperience with Open Source ===
>The committers have experience with Apache and Eclipse open source
>development.
>
>=== Reliance on Salaried Developers ===
>Hadoop Development Tools will be developed with a mix of salaried and
>volunteer time.
>
>=== Relationships with Other Apache Projects ===
>Hadoop Development Tools is closely related to Apache Hadoop.
>
>=== An Excessive Fascination with the Apache Brand ===
>Given the success of Hadoop and associated projects, Apache is the
>natural place for the Hadoop Development Tools. Chris Mattman suggested
>the Apache Incubator as appropriate on the Hadoop general mailing list
>following the success that MRUnit had taking the path from Hadoop contrib
>to an Apache top level project.
> 
>== Documentation ==
>Documentation for the current tools can be found at
>http://wiki.apache.org/hadoop/EclipsePlugIn
>
>== Initial Source ==
>http://svn.apache.org/repos/asf/hadoop/common/trunk/hadoop-mapreduce-proje
>ct/src/contrib/eclipse-plugin/
> 
>==  Source and Intellectual Property Submission Plan ==
>The source, and any suggested initial patches, are already hosted either
>in Apache¹s Subversion or JIRA.
> 
>==  External Dependencies ==
>Eclipse Platform
>Eclipse Java Development Tools
> 
>==  Cryptography ==
>Hadoop Development Tools likely does not fall into this area.
> 
>==  Required Resources ==
>=== Mailing lists ===
> * hdt-dev
> * hdt-commits
>

RE: [VOTE] [PROPOSAL] Apache Steams Project

[Franklin, Matthew B.]

Hi Jason,

It is a little early for the vote. We want to make sure everyone has sufficient 
time to comment. The vote will be held shortly.

Matt



Sent from a mobile device

-Original Message-
From: Jason Letourneau [jletournea...@gmail.com]
Sent: Wednesday, November 07, 2012 05:18 PM Eastern Standard Time
To: general@incubator.apache.org
Subject: [VOTE] [PROPOSAL] Apache Steams Project


+1 (non-binding)

Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)

[Franklin, Matthew B.]

On 11/5/12 6:38 AM, "Joachim Dreimann" 
wrote:

>+1 (non-binding)
>
>Is there precedent on releasing with less than three +1s from IPMC members
>if there are no 0s or -1s from anyone at all?
>The minimum required 72 hours have also passed.

Unfortunately, a release requires at least 3 IPMC members to vote +1.

I am looking at it now and will cast a vote when I have properly reviewed
the release.

>
>We'd really like to establish a frequent release cycle, Bloodhound 0.3 is
>already ready to be packaged up as soon as 0.2 has been released.
>
>Thanks,
>Joe
>
>
>On 31 October 2012 21:49, Marvin Humphrey  wrote:
>
>> On Mon, Oct 29, 2012 at 7:22 AM, Joachim Dreimann
>>  wrote:
>> > The result of the vote is summarised here:
>> >   http://markmail.org/thread/zrgkleendiqvanzs
>>
>> This message didn't include an IPMC tally, but I see that Mentor Branko
>> Čibej
>> voted on the bloodhound-dev thread.  That makes one IPMC member voting
>>+1;
>> two
>> more are needed.
>>
>> > The vote will be open for at least 72 hours.
>>
>> Less than a day left... any takers?
>>
>> Marvin Humphrey
>>
>
>
>
>-- 
>Joe Dreimann
>UX Designer | WANdisco 
>*
>*
>*Transform your software development department. Register for a free SVN
>HealthCheck  *


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

Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)

[Franklin, Matthew B.]

Apologies for the delay, the conference wifi was taken down before I could
send the e-mail.

Unfortunately, when I ran a license header check, the report came back
with some minified css & js files in the source release.  As far as I am
aware, minified files are not considered source and therefore should not
be in the distribution.

-Matt
On 10/29/12 10:22 AM, "Joachim Dreimann" 
wrote:

>Hi,
>
>I would like to request the beginning of the vote for the second release
>of
>Apache Bloodhound in the incubator following the successful vote by the
>Bloodhound PPMC.
>
>The result of the vote is summarised here:
>  http://markmail.org/thread/zrgkleendiqvanzs
>
>The artefacts for the release including the source distribution and KEYS
>can be found here:
>  https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
>
>The release itself is created from:
>  https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2
>  (r1394550)
>
>Issues identified to be fixed for the next release are listed here:
>  https://issues.apache.org/bloodhound/ticket/246
>  https://issues.apache.org/bloodhound/ticket/245
>
>The vote will be open for at least 72 hours.
>
>[ ] +1 Release this package as Apache Bloodhound 0.2
>[ ] +0 Don't care
>[ ] -1 Do not release this package (please explain)
>
>Cheers,
>Joe


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

RE: [PROPOSAL] Apache Steams Project

[Franklin, Matthew B.]

>-Original Message-
>From: Jason Letourneau [mailto:jletournea...@gmail.com]
>Sent: Thursday, November 08, 2012 8:19 AM
>To: general@incubator.apache.org
>Subject: Re: [PROPOSAL] Apache Steams Project
>
>Hi Andrew -
>
>Sounds great - we'd love to have you onboard.

Just add your name to the proposal as an initial committer.

>
>The current MITRE prototype is Java/Spring based and leveraging the
>Shindig and Rave projects.  We are also using a reference
>implementation of the pubsubhubbub protocol.
>
>Jason
>
>On Wed, Nov 7, 2012 at 7:03 PM, Andrew Hart  wrote:
>> Hi Matt,
>>
>> I've worked on several side projects over the years that utilize the
>> Activity Streams specification, and I would love to get involved and help
>> out with this. Out of curiousity, what language(s) is the Mitre prototype
>> implemented in?
>>
>> Cheers,
>> - Andrew
>>
>> On 11/06/2012 09:06 AM, Franklin, Matthew B. wrote:
>>>
>>> I would like to propose a new Activity Streams server project to the
>>> Incubator.  The proposal is on the wiki at the following location:
>>>
>>> http://wiki.apache.org/incubator/StreamsProposal
>>>
>>>
>>> Streams is a collaborative effort from multiple organizations and
>>> individuals working with and around the Activity Streams specification
>>> (http://activitystrea.ms).
>>>
>>> We are looking forward to your feedback and suggestions.
>>>
>>> -Matt Franklin
>>>
>>> - COPY OF PROPOSAL FROM
>>> http://wiki.apache.org/incubator/StreamsProposal -
>>>
>>>
>>> Apache Streams Proposal
>>>
>>> == Abstract ==
>>>
>>> Apache Streams will be a lightweight server for ActivityStreams. The role
>>> of Apache Streams is to provide a central point of aggregation, filtering
>>> and querying for Activities that have been submitted by disparate systems.
>>>   Apache Streams also intends to include a mechanism for intelligent
>>> filtering and recommendation to reduce the noise to end users.
>>>
>>>
>>> == Proposal ==
>>>
>>> Apache Streams will bring together individuals who are or are looking to
>>> increase and centralize the production, consumption and federation of
>>> ActivityStreams throughout enterprise organizations and the Internet as a
>>> whole.  The target features include:
>>>
>>>   * Publication of Activities from multiple systems via HTTP
>>>   * Aggregation and syndication of streams
>>>   * Support for security trimming of streams by social graph
>>>   * Noise reduction and intelligent filtering
>>>   * Federation of streams across disparate systems
>>>   * Provide libraries for easy integration in source systems
>>>
>>> == Background ==
>>>
>>> The ActivityStreams specification standardizes a generic format for
>>> describing event-based data.  Many social web companies have adopted
>the
>>> format and it has been included in the OpenSocial specification as the
>>> preferred method for delivery of activity data.  During discussions of
>>> ActivityStreams at OpenSocial events earlier in the year, it became clear
>>> that multiple organizations are facing similar issues as to the
>>> publication and filtering of their activities and would benefit from a
>>> commonly-developed, open-source ActivityStreams server.
>>>
>>> == Rationale ==
>>>
>>> In deployment, activities are generated from multiple sources.  This is
>>> particularly true within the enterprise where disparate systems create and
>>> manage activities in stove pipes.  What is needed is a central point for
>>> consumption, aggregation and exposure of activities generated within
>these
>>> systems.
>>>
>>> == Initial Goals ==
>>>
>>> The initial goal of the project is to survey donated code and develop a
>>> common, high-level architecture for an initial release.  The project will
>>> then work toward that release in a new code base, pulling in pieces of
>>> donated code as necessary.
>>>
>>> == Current Status ==
>>>
>>> The MITRE Corporation will donate its prototype code to the project.
>>> Aside from this, the project is new and will need bootstrap time to
>>> develop an initial architecture and roadmap.
>>>
>>>  Meritocracy 
>>>
>>> As a new project with many team members who are 

RE: [PROPOSAL] Apache Steams Project

[Franklin, Matthew B.]

>-Original Message-
>From: Davide Palmisano [mailto:dpalmis...@gmail.com]
>Sent: Tuesday, November 06, 2012 12:17 PM
>To: general@incubator.apache.org
>Subject: Re: [PROPOSAL] Apache Steams Project
>
>Hi there,
>
>I'm working to something[1] (not yet fully open source released) which
>could somehow overlap with Streams.
>I'm also one of the authors of the Activity Streams Ontology[2] which
>is the rdf-ish version of activitystrea.ms.
>
>I'll be really happy to contribute on Streams.

Feel free to add yourself as an initial committer to the proposal on the wiki.

>
>cheers,
>
>[1] http://www.slideshare.net/dpalmisano/semtech2012-finalpdf
>[2] http://xmlns.notu.be/aair/
>
>On Tue, Nov 6, 2012 at 6:06 PM, Franklin, Matthew B.
> wrote:
>> I would like to propose a new Activity Streams server project to the
>> Incubator.  The proposal is on the wiki at the following location:
>>
>> http://wiki.apache.org/incubator/StreamsProposal
>>
>>
>> Streams is a collaborative effort from multiple organizations and
>> individuals working with and around the Activity Streams specification
>> (http://activitystrea.ms).
>>
>> We are looking forward to your feedback and suggestions.
>>
>> -Matt Franklin
>>
>> - COPY OF PROPOSAL FROM
>> http://wiki.apache.org/incubator/StreamsProposal -
>>
>>
>> Apache Streams Proposal
>>
>> == Abstract ==
>>
>> Apache Streams will be a lightweight server for ActivityStreams. The role
>> of Apache Streams is to provide a central point of aggregation, filtering
>> and querying for Activities that have been submitted by disparate systems.
>>  Apache Streams also intends to include a mechanism for intelligent
>> filtering and recommendation to reduce the noise to end users.
>>
>> == Proposal ==
>>
>> Apache Streams will bring together individuals who are or are looking to
>> increase and centralize the production, consumption and federation of
>> ActivityStreams throughout enterprise organizations and the Internet as a
>> whole.  The target features include:
>>
>>  * Publication of Activities from multiple systems via HTTP
>>  * Aggregation and syndication of streams
>>  * Support for security trimming of streams by social graph
>>  * Noise reduction and intelligent filtering
>>  * Federation of streams across disparate systems
>>  * Provide libraries for easy integration in source systems
>>
>> == Background ==
>>
>> The ActivityStreams specification standardizes a generic format for
>> describing event-based data.  Many social web companies have adopted the
>> format and it has been included in the OpenSocial specification as the
>> preferred method for delivery of activity data.  During discussions of
>> ActivityStreams at OpenSocial events earlier in the year, it became clear
>> that multiple organizations are facing similar issues as to the
>> publication and filtering of their activities and would benefit from a
>> commonly-developed, open-source ActivityStreams server.
>>
>> == Rationale ==
>>
>> In deployment, activities are generated from multiple sources.  This is
>> particularly true within the enterprise where disparate systems create and
>> manage activities in stove pipes.  What is needed is a central point for
>> consumption, aggregation and exposure of activities generated within these
>> systems.
>>
>> == Initial Goals ==
>>
>> The initial goal of the project is to survey donated code and develop a
>> common, high-level architecture for an initial release.  The project will
>> then work toward that release in a new code base, pulling in pieces of
>> donated code as necessary.
>>
>> == Current Status ==
>>
>> The MITRE Corporation will donate its prototype code to the project.
>> Aside from this, the project is new and will need bootstrap time to
>> develop an initial architecture and roadmap.
>>
>>  Meritocracy 
>>
>> As a new project with many team members who are seasoned Apache
>veterans,
>> Apache Streams is prepared to build the project under the Apache Way.
>>
>>  Community 
>>
>> The Apache Streams community combines multiple individuals from
>different
>> organizations, many of which have collaborated before in an open
>> environment.  Apache Streams is committed to expanding this community
>and
>> adhering to Apache principles of openness and collaboration.
>>
>> == Known Risks ==
>>
>> An exercise in self-knowledge. Risks

[VOTE] Accept Apache Streams as an Incubator Project

[Franklin, Matthew B.]

Given the feedback received so far I think the Streams proposal is in good 
shape so I am calling for a vote to accept Streams into the Incubator.

The proposal is at: http://wiki.apache.org/incubator/StreamsProposal and also 
copied as text below.

Please vote.

[ ] +1 Accept Streams into the incubator
[ ] +0 Don't care'
[ ] -1 Reject for the following reason:

I'll close the vote at Monday morning on November 19th EST. 

- COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/StreamsProposal 
-

Apache Streams Proposal
 
== Abstract ==

Apache Streams will be a lightweight server for ActivityStreams. The role
of Apache Streams is to provide a central point of aggregation, filtering
and querying for Activities that have been submitted by disparate systems.
 Apache Streams also intends to include a mechanism for intelligent
filtering and recommendation to reduce the noise to end users.

== Proposal ==

Apache Streams will bring together individuals who are or are looking to
increase and centralize the production, consumption and federation of
ActivityStreams throughout enterprise organizations and the Internet as a
whole.  The target features include:

 * Publication of Activities from multiple systems via HTTP
 * Aggregation and syndication of streams
 * Support for security trimming of streams by social graph
 * Noise reduction and intelligent filtering
 * Federation of streams across disparate systems
 * Provide libraries for easy integration in source systems

== Background ==

The ActivityStreams specification standardizes a generic format for
describing event-based data.  Many social web companies have adopted the
format and it has been included in the OpenSocial specification as the
preferred method for delivery of activity data.  During discussions of
ActivityStreams at OpenSocial events earlier in the year, it became clear
that multiple organizations are facing similar issues as to the
publication and filtering of their activities and would benefit from a
commonly-developed, open-source ActivityStreams server.

== Rationale ==

In deployment, activities are generated from multiple sources.  This is
particularly true within the enterprise where disparate systems create and
manage activities in stove pipes.  What is needed is a central point for
consumption, aggregation and exposure of activities generated within these
systems.

== Initial Goals ==

The initial goal of the project is to survey donated code and develop a
common, high-level architecture for an initial release.  The project will
then work toward that release in a new code base, pulling in pieces of
donated code as necessary.

== Current Status ==

The MITRE Corporation will donate its prototype code to the project.
Aside from this, the project is new and will need bootstrap time to
develop an initial architecture and roadmap.

 Meritocracy 

As a new project with many team members who are seasoned Apache veterans,
Apache Streams is prepared to build the project under the Apache Way.
   
 Community 

The Apache Streams community combines multiple individuals from different
organizations, many of which have collaborated before in an open
environment.  Apache Streams is committed to expanding this community and
adhering to Apache principles of openness and collaboration.

== Known Risks ==

An exercise in self-knowledge. Risks don't mean that a project is
unacceptable. If they are recognized and noted then they can be addressed
during incubation.

 Inexperience with Open Source 

Most of the initial committers have worked in open source and many are
familiar with the ASF and the Apache Way; but, not all.  Additionally,
many of the committers have not worked on a software project together and
will need time to familiarize themselves with each other.

 Speed of Development 

This project is dependent upon contributions made on company time. For
this approach to succeed, the project must deliver a workable system in a
timeframe acceptable to those companies. The initial parties have the
intention of releasing a first version within 6 months after starting the
Incubator. Failure to do so could prevent the project reaching critical
mass, and could prevent the project from being in a position to attract
new developers.

 Reliance on Salaried Developers 

At present, the vast majority of contributors will be doing so as a part
of their day jobs. Therefore, as already alluded to, there is a risk that
the project won't gain enough traction to be of use to their employers.
However, given the centrality of these codebases to the participating
companies, it is clearly in their best interests to transition to an
openly developed alternative.

 Relationships with Other Apache Products 

Many of the initial committers will be integrating this software with
Apache Rave & Apache Shindig.  A possibility exists that code is developed
by either or both of the projects to support integration with Ap

Re: November reports

[Franklin, Matthew B.]

On 11/14/12 6:14 AM, "Jukka Zitting"  wrote:

>Hi,
>
>We still have two missing reports: Helix and Syncope. Helix, since
>you're only just starting, a very simple report like the one from
>Ripple is quite enough for now. Syncope, you already passed the
>graduation vote, so there isn't that much to report anymore, but for
>the record it would still be nice if you could mention the graduation
>process as having been completed on your side.
>
>I finally got around to assigning shepherds for this months podling
>reports:
>
>  Dave Fisher  - Amber
>  Jukka Zitting- Ambari, NPanday
>  Matt Franklin- Clerezza, PhotArk

Somehow I missed my assignments for November.  Thanks for covering Jukka.

>  Matt Hogstrom- Crunch, Wink
>  Ross Gardler - DeltaSpike
>  Benson Margulies - Droids, Wookie
>  Roman Shaposhnik - Nuvem
>
>It would be great if you could review the reports by tomorrow,
>Thursday, so that we can submit the Incubator report on Friday.
>Luckily we don't have too many reports to review this month, so just
>let me know if you won't have time for the reviews and I'm sure we'll
>find a replacement.
>
>When reviewing, note especially any progress from previous reports:
>
>  Starting: Crunch
>  No release: Ambari
>  Low activity:  Clerezza, Droids, Nuvem, NPanday
>  Low diversity: PhotArk
>  Ready to graduate: Amber, DeltaSpike, Wink, Wookie
>
>BR,
>
>Jukka Zitting
>
>-
>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] Accept Apache Streams as an Incubator Project

[Franklin, Matthew B.]

+1 (binding)

On 11/14/12 7:37 AM, "Franklin, Matthew B."  wrote:

>Given the feedback received so far I think the Streams proposal is in
>good shape so I am calling for a vote to accept Streams into the
>Incubator.
>
>The proposal is at: http://wiki.apache.org/incubator/StreamsProposal and
>also copied as text below.
>
>Please vote.
>
>[ ] +1 Accept Streams into the incubator
>[ ] +0 Don't care'
>[ ] -1 Reject for the following reason:
>
>I'll close the vote at Monday morning on November 19th EST.
>
>- COPY OF PROPOSAL FROM
>http://wiki.apache.org/incubator/StreamsProposal -
>
>Apache Streams Proposal
> 
>== Abstract ==
>
>Apache Streams will be a lightweight server for ActivityStreams. The role
>of Apache Streams is to provide a central point of aggregation, filtering
>and querying for Activities that have been submitted by disparate systems.
> Apache Streams also intends to include a mechanism for intelligent
>filtering and recommendation to reduce the noise to end users.
>
>== Proposal ==
>
>Apache Streams will bring together individuals who are or are looking to
>increase and centralize the production, consumption and federation of
>ActivityStreams throughout enterprise organizations and the Internet as a
>whole.  The target features include:
>
> * Publication of Activities from multiple systems via HTTP
> * Aggregation and syndication of streams
> * Support for security trimming of streams by social graph
> * Noise reduction and intelligent filtering
> * Federation of streams across disparate systems
> * Provide libraries for easy integration in source systems
>
>== Background ==
>
>The ActivityStreams specification standardizes a generic format for
>describing event-based data.  Many social web companies have adopted the
>format and it has been included in the OpenSocial specification as the
>preferred method for delivery of activity data.  During discussions of
>ActivityStreams at OpenSocial events earlier in the year, it became clear
>that multiple organizations are facing similar issues as to the
>publication and filtering of their activities and would benefit from a
>commonly-developed, open-source ActivityStreams server.
>
>== Rationale ==
>
>In deployment, activities are generated from multiple sources.  This is
>particularly true within the enterprise where disparate systems create and
>manage activities in stove pipes.  What is needed is a central point for
>consumption, aggregation and exposure of activities generated within these
>systems.
>
>== Initial Goals ==
>
>The initial goal of the project is to survey donated code and develop a
>common, high-level architecture for an initial release.  The project will
>then work toward that release in a new code base, pulling in pieces of
>donated code as necessary.
>
>== Current Status ==
>
>The MITRE Corporation will donate its prototype code to the project.
>Aside from this, the project is new and will need bootstrap time to
>develop an initial architecture and roadmap.
>
> Meritocracy 
>
>As a new project with many team members who are seasoned Apache veterans,
>Apache Streams is prepared to build the project under the Apache Way.
>   
> Community 
>
>The Apache Streams community combines multiple individuals from different
>organizations, many of which have collaborated before in an open
>environment.  Apache Streams is committed to expanding this community and
>adhering to Apache principles of openness and collaboration.
>
>== Known Risks ==
>
>An exercise in self-knowledge. Risks don't mean that a project is
>unacceptable. If they are recognized and noted then they can be addressed
>during incubation.
>
> Inexperience with Open Source 
>
>Most of the initial committers have worked in open source and many are
>familiar with the ASF and the Apache Way; but, not all.  Additionally,
>many of the committers have not worked on a software project together and
>will need time to familiarize themselves with each other.
>
> Speed of Development 
>
>This project is dependent upon contributions made on company time. For
>this approach to succeed, the project must deliver a workable system in a
>timeframe acceptable to those companies. The initial parties have the
>intention of releasing a first version within 6 months after starting the
>Incubator. Failure to do so could prevent the project reaching critical
>mass, and could prevent the project from being in a position to attract
>new developers.
>
> Reliance on Salaried Developers 
>
>At present, the vast majority of contributors will be doing so as a part
>of their day jobs. Therefo

[RESULT] [VOTE] Accept Apache Streams as an Incubator Project

[Franklin, Matthew B.]

The voting period has now closed.  The results are as follows:

IPMC Member Votes

-1: 0
 0: 0
+1: 8

Non-binding Votes

-1:  0
 0:  0
+1:  7

The vote is ***SUCCESSFUL***


Voting Record (* denotes an IPMC Member):

Jason Letourneau:  +1
* Suresh Marru:+1
* Jukka Zitting:   +1
* Ross Gardler:+1
Sander van der Waal: +1
Scott Wilson:  +1
Andrew Hart:   +1
James Snell:   +1
Ryan Baxter:   +1
* Mohammad Nour El-Din: +1
* Ate Douma:   +1
* Ralph Goers: +1
Raminder Singh:+1
* Matt Franklin:   +1
* Jakob Homan: +1


On 11/14/12 7:37 AM, "Franklin, Matthew B."  wrote:

>Given the feedback received so far I think the Streams proposal is in
>good shape so I am calling for a vote to accept Streams into the
>Incubator.
>
>The proposal is at: http://wiki.apache.org/incubator/StreamsProposal and
>also copied as text below.
>
>Please vote.
>
>[ ] +1 Accept Streams into the incubator
>[ ] +0 Don't care'
>[ ] -1 Reject for the following reason:
>
>I'll close the vote at Monday morning on November 19th EST.
>
>- COPY OF PROPOSAL FROM
>http://wiki.apache.org/incubator/StreamsProposal -
>
>Apache Streams Proposal
> 
>== Abstract ==
>
>Apache Streams will be a lightweight server for ActivityStreams. The role
>of Apache Streams is to provide a central point of aggregation, filtering
>and querying for Activities that have been submitted by disparate systems.
> Apache Streams also intends to include a mechanism for intelligent
>filtering and recommendation to reduce the noise to end users.
>
>== Proposal ==
>
>Apache Streams will bring together individuals who are or are looking to
>increase and centralize the production, consumption and federation of
>ActivityStreams throughout enterprise organizations and the Internet as a
>whole.  The target features include:
>
> * Publication of Activities from multiple systems via HTTP
> * Aggregation and syndication of streams
> * Support for security trimming of streams by social graph
> * Noise reduction and intelligent filtering
> * Federation of streams across disparate systems
> * Provide libraries for easy integration in source systems
>
>== Background ==
>
>The ActivityStreams specification standardizes a generic format for
>describing event-based data.  Many social web companies have adopted the
>format and it has been included in the OpenSocial specification as the
>preferred method for delivery of activity data.  During discussions of
>ActivityStreams at OpenSocial events earlier in the year, it became clear
>that multiple organizations are facing similar issues as to the
>publication and filtering of their activities and would benefit from a
>commonly-developed, open-source ActivityStreams server.
>
>== Rationale ==
>
>In deployment, activities are generated from multiple sources.  This is
>particularly true within the enterprise where disparate systems create and
>manage activities in stove pipes.  What is needed is a central point for
>consumption, aggregation and exposure of activities generated within these
>systems.
>
>== Initial Goals ==
>
>The initial goal of the project is to survey donated code and develop a
>common, high-level architecture for an initial release.  The project will
>then work toward that release in a new code base, pulling in pieces of
>donated code as necessary.
>
>== Current Status ==
>
>The MITRE Corporation will donate its prototype code to the project.
>Aside from this, the project is new and will need bootstrap time to
>develop an initial architecture and roadmap.
>
> Meritocracy 
>
>As a new project with many team members who are seasoned Apache veterans,
>Apache Streams is prepared to build the project under the Apache Way.
>   
> Community 
>
>The Apache Streams community combines multiple individuals from different
>organizations, many of which have collaborated before in an open
>environment.  Apache Streams is committed to expanding this community and
>adhering to Apache principles of openness and collaboration.
>
>== Known Risks ==
>
>An exercise in self-knowledge. Risks don't mean that a project is
>unacceptable. If they are recognized and noted then they can be addressed
>during incubation.
>
> Inexperience with Open Source 
>
>Most of the initial committers have worked in open source and many are
>familiar with the ASF and the Apache Way; but, not all.  Additionally,
>many of the committers have not worked on a software project together and
>will need time to familiarize themselves with each other.
>
> Speed of Development 
>
>This project is dependent upon contributions made on company time. For
>this approach to s

Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany

[Franklin, Matthew B.]

+1 (binding)

On 11/20/12 12:41 AM, "Luciano Resende"  wrote:

>Apache Nuvem will define an open application programming interface
>for common cloud application services, allowing applications to be
>easily ported across the most popular cloud platforms. It is
>currently composed of multiple cloud SCA components (Data, Queue, Chat),
>and supports multiple cloud platforms such as AWS, GAE, etc as well
>as standalone deployment. Nuvem was accepted for Incubation on June, 2010,
>and several of the active committers are already part of the Tuscany PMC.
>
>Nuvem was accepted for Incubation on June 2010, and is currently a small
>community, where the contributions are 100% done by volunteers in their
>own
>free time, which makes the level of activity
>low, compared to what is required for graduating it as a TLP.
>
>Having said that, Nuvem has a great synergy with Apache Tuscany, and after
>discussion between the two projects, we are seeking IPMC approval to allow
>graduation of Apache Nuvem as a sub-project under Apache Tuscany.
>
>Nuvem Graduation Vote thread
>*http://s.apache.org/nuvem-graduation*
>*http://s.apache.org/nuvem-graduation-result*
>
>Tuscany Graduation Vote thread
>*http://s.apache.org/tuscany-accept-nuvem*
>*http://s.apache.org/tuscany-accept-nuvem-result*
>
>Please cast your votes:
>
>[ ] +1 Graduate Nuvem as a sub-project under Apache Tuscany
>
>[ ] - 1 Nuvem is not ready to graduate as a sub-project under Apache
>Tuscany, because ...
>
>
>-- 
>Luciano Resende
>http://people.apache.org/~lresende
>http://twitter.com/lresende1975
>http://lresende.blogspot.com/


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

Re: Sub-projects - when are they acceptable? (was Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany)

[Franklin, Matthew B.]

On 11/21/12 7:26 AM, "Benson Margulies"  wrote:

>On Wed, Nov 21, 2012 at 5:40 AM, Ross Gardler
> wrote:
>> On 21 November 2012 10:36, Bertrand Delacretaz
>>wrote:
>>
>>> On Tue, Nov 20, 2012 at 3:47 PM, Mattmann, Chris A (388J)
>>>  wrote:
>>> > ...sub-"products", or the ability for a PMC to release multiple
>>> "products", like e.g.,
>>> > like Lucene does now (Lucene-Java is a product; Solr is a product;
>>> PyLucene is a product),
>>> > that works b/c the sets of individuals that make up those interested
>>>in
>>> the sub "products" are
>>> > not separate communities, they just release different portions of the
>>> software that they scratch
>>> > their itch on
>>>
>>> Agreed, that's what I meant - a PMC that groups multiple communities
>>> is not good, whereas one that oversees several products is fine.
>>>
>>
>> +1 this is a good way of restating my intention too.
>>
>> Seems we have lots of agreement so far.
>
>So, permit me to ask another, related, question. It seems to me that
>the IPMC is concerned with the fact that a project is ready to leave,
>but not so much which where it is going. A proposal to form a new TLP
>is, I think, a straightforward question to the board, and the IPMC's
>action is to make a recommendation to the board.
>
>A proposal to be integrated into an existing project is, I think,
>within the authority of the existing product's PMC. If Project A
>wishes to invite the members of Podling B to join and integrate their
>code, then this looks to me like it could just happen without any
>approval in advance from the board or even the IPMC. Voting in
>committers is a PMC task, voting in PMC members is a PMC task with
>board lazy approval, and copying (ip-cleared) code from one place in
>ASF source control to another is a PMC task.
>
>I think that IPMC graduation votes in this case are a nice thing, but
>it seems by this logic that they are not necessary.
>
>Does this make sense?

I think your statement makes sense, but I see the votes as a way for IPMC
members to assert that they believe all due diligence in IP clearance has
been performed and that a sanity check has been done as to whether or not
the podling is to be fully integrated into the PMC of the target project.
>From this perspective the Incubator serves to provide a convenience to the
target PMC in regards to releasability of code they are assuming and as a
foundation preventative measure for ensuring we don't end up with massive,
disconnected umbrellas comprised of former incubator podlings.

>
>
>>
>> Ross
>>
>>
>>>
>>> -Bertrand
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>>
>> --
>> Ross Gardler (@rgardler)
>> Programme Leader (Open Development)
>> OpenDirective http://opendirective.com
>
>-
>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] Retire Chukwa from incubation

[Franklin, Matthew B.]

+1

>-Original Message-
>From: Alan Cabrera [mailto:l...@toolazydogs.com]
>Sent: Sunday, November 25, 2012 6:00 PM
>To: general@incubator.apache.org
>Subject: [VOTE] Retire Chukwa from incubation
>
>Hi,
>
>The Chukwa community has voted to retire the project.
>
>Following the retirement guide [1], I now call the Incubator PMC to vote on
>confirming this decision.
>
>  [ ] +1 Retire the Chukwa project
>  [ ] -1 Do not retire the project, because ...
>
>[1] http://incubator.apache.org/guides/retirement.html
>
>
>Regards,
>Alan


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

RE: [VOTE] Graduate OpenMeetings from Incubator

[Franklin, Matthew B.]

+1

>-Original Message-
>From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com]
>Sent: Sunday, December 02, 2012 1:51 AM
>To: general@incubator.apache.org
>Cc: openmeetings-...@incubator.apache.org
>Subject: [VOTE] Graduate OpenMeetings from Incubator
>
>Dear Incubation members,
>
>During incubation, OpenMeetings has :
> * Produced 1 Release
> * Added 5 new Committer/PPMC members and shows constant community
>activities
> * Cleared IP on all code
> * Developed Roadmap(s) for the next major and minor releases in a
>community process and started working on that
>
>Given these accomplishments, I propose that we submit the following
>graduation resolution to the incubator PMC.
>We organized already a community vote:
>http://markmail.org/thread/wnxvkvukdqgdddpn
>
>The vote received:
>1x +1 Yegor IPMC
>5x +1 solomax, aaf, sebawagner, greenes PMC
>1x +1 Irina
>
>Please VOTE over the next 72 hours on the resolution below:
>
>[ ] +1 Graduate OpenMeetings from the Incubator per the resolution below.
>[ ] +0 Don't care.
>[ ] -1 Don't graduate OpenMeetings from the Incubator because:
>
>===
>==
>Charter here:
>https://cwiki.apache.org/confluence/display/OPENMEETINGS/Draft+Charter
>
>and copied below:
>X. Establish the Apache OpenMeetings Project
>
>   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, for distribution at no charge to
>   the public, related to OpenMeetings Web-Conferencing tool.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache OpenMeetings Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache OpenMeetings Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to the OpenMeetings Web-Conferencing tool;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache OpenMeetings" 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 OpenMeetings Project, and to have primary
>responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache OpenMeetings 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 OpenMeetings Project:
>
> * Alexei Fedotov
> * Sebastian Wagner  
> * Maxim Solodovnik  
> * Oliver Becherer  
> * Rodion Volkov
> * Eugen Schwert   
> * German Grekhov
> * Timur Tleukenov 
> * Alvaro Bustos Ruiz  
> * George Kirkham  
> * Stephen Cottham
> * Sascha Xander   
> * Evgeny Rovinsky
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sebastian Wagner
>   be appointed to the office of Vice President, Apache OpenMeetings, 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 OpenMeetings PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache OpenMeetings Project; and be it further
>
>   RESOLVED, that the Apache OpenMeetings Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator OpenMeetings podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator OpenMeetings podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.

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

RE: checking on the shepherd inventory (or, 3.14159 IPMC members ...)

[Franklin, Matthew B.]

>From: Dave Fisher [mailto:dave2w...@comcast.net]
>I liked that Jukka assigned me to random podlings as this exposes me to new
>ideas.

+1


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

RE: Incubator report reminders sent for Dec 2012

[Franklin, Matthew B.]

>-Original Message-
>From: Daniel Shahaf [mailto:danie...@apache.org]
>Sent: Saturday, December 01, 2012 1:41 PM
>To: general@incubator.apache.org
>Subject: Re: Incubator report reminders sent for Dec 2012
>
>On Sat, Dec 01, 2012 at 07:20:35PM +0100, Christian Grobmeier wrote:
>> I miss Onami and Ripple from the reminders.
>>
>
>Helix and HDT are also missing; these four are all set up as
>${podling}.incubator.apache.org - related?

Streams has the same e-mail format and was not listed either.  

>
>> But they are listed here:
>> http://incubator.apache.org/report-next-month.html#onami
>>
>> What do I need to fix to get these reminders?
>> I just know the old "wiki"-styled process
>>
>>
>> On Sat, Dec 1, 2012 at 4:26 PM, Marvin  wrote:
>> >
>> >
>> > The next board meeting is scheduled for Wed, 19 December 2012, 10:00:00
>PST.
>> >
>> > I have just sent reminder emails to the below addresses, requesting them
>> > to supply board reports 2 weeks before the above date (Wed, Dec 5th).
>> >
>> > Please recall that the Incubator report is due Wed, Dec 12th.
>> >
>> > Allura Developers   
>> > Bloodhound Developers   
>> > Blur Developers 
>> > cTAKES Developers   
>> > Drill Developers
>> > Etch Developers 
>> > Flex Developers 
>> > Hadoop Development Tools Developers
>
>> > HCatalog Developers 
>> > Kalumet Developers  
>> > Openmeetings Developers d...@incubator.apache.org>
>> > S4 Developers   
>> > Wave Developers 
>> >
>> > -
>> > To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: private-h...@incubator.apache.org
>> >
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> -
>> 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: Some missing things for the December report

[Franklin, Matthew B.]

>-Original Message-
>From: Benson Margulies [mailto:bimargul...@gmail.com]
>
>hcatalog: no report!

[Dropped other podling dev lists]

HCatalog still has no report for December and no discussion about it on the DEV 
list.  The last Shepherd also recommended in September that the podling look 
toward Graduation; but I did not find any discussion of the topic on the list.  

Aside from the immediate need for a report, I don't see anything alarming about 
the community health.   I strongly recommend the community put together a 
graduation plan and present it as part of the board report (this or next).  

One minor nit, the downloads page needs to list links for the signature and 
checksum files for each release.

-Matt

[RESULT] [VOTE] Release Apache Rave 0.1-incubating

[Franklin, Matthew B.]

72 hours has elapsed and the lazy consensus vote is now closed.

There were no additional votes from IPMC members regarding this release.  

Please see the rave-dev vote thread for a list of the 3 IPMC members who cast 
+1 for the release.

-Original Message-
From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] 
Sent: Tuesday, July 05, 2011 8:38 AM
To: general@incubator.apache.org
Cc: rave-...@incubator.apache.org
Subject: [VOTE] Release Apache Rave 0.1-incubating

This is the first incubator release for Apache Rave, with the artifacts
being versioned as 0.1-incubating.

We are requesting a lazy consensus vote, as we have already received 3
binding IPMC +1 votes during the release voting on rave-dev -

Vote thread: 
http://apache.markmail.org/message/vmgwtdoueobdmc2g?q=list:org%2Eapache%2Ei
ncubator%2Erave-dev+%5BVOTE%5D+Apache+order:date-backward&page=3s

Result: 
http://apache.markmail.org/message/lq6n7jgkhhlntqig?q=list:org%2Eapache%2Ei
ncubator%2Erave-dev+%5BVOTE%5D+Apache+order:date-backward&page=1

Release notes:
https://svn.apache.org/repos/asf/incubator/rave/tags/0.1-incubating/CHANGEL
OG

SVN source tag (master) (r1141150):
https://svn.apache.org/repos/asf/incubator/rave/rave-master-pom/tags/0.1-in
cubating/

SVN source tag (project)(r1141160)
https://svn.apache.org/repos/asf/incubator/rave/tags/0.1-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapacherave-004/


Staged Source releases:
https://repository.apache.org/content/repositories/orgapacherave-004/org/ap
ache/rave/rave-master/0.1-incubating/rave-master-0.1-incubating-source-rele
ase.zip
https://repository.apache.org/content/repositories/orgapacherave-004/org/ap
ache/rave/rave-project/0.1-incubating/rave-project-0.1-incubating-source-re
lease.zip

Staged Binary releases
http://people.apache.org/builds/incubator/rave/0.1-incubating/rave-0.1-incu
bating-bin.zip
http://people.apache.org/builds/incubator/rave/0.1-incubating/rave-0.1-incu
bating-bin.tar.gz

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS


Lazy consensus, vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)



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

Re: *** Missing reports - POST IMMEDIATELY!

[Franklin, Matthew B.]

On 7/18/11 12:17 PM, "Noel J. Bergman"  wrote:

>OGNL, Olio (2 cycles in a row), Rave, VXQuery (also two cycles in a row)
>are
>all missing.

We (Rave) completed three monthly reports (April, May, June) and were
moved to the March, June, September, December reporting schedule. (see
discussion on rave-dev
http://markmail.org/message/6nyuahchalzvrx2h?q=Rave+list:org%2Eapache%2Einc
ubator%2Erave-dev+Re:+Incubator+PMC/Board+report+for+July+2011)

Is there another list we need to update?

-Matt

>
>   --- Noel
>
>
>
>-
>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 Wookie 0.9.0-incubating (General Incubation List)

[Franklin, Matthew B.]

+1 (non-binding).  Is there another IPMC member that can take a look at this 
release and vote on it?  It is a blocker for one of our major features on Rave.

>-Original Message-
>From: Paul Sharples [mailto:p.sharp...@bolton.ac.uk]
>Sent: Monday, August 22, 2011 11:37 AM
>To: general@incubator.apache.org
>Cc: wookie-...@incubator.apache.org
>Subject: [VOTE] Release Apache Wookie 0.9.0-incubating (General Incubation
>List)
>
>This is the first incubator release for Apache Wookie, with the artifacts being
>versioned as 0.9.0-incubating.
>
>We have already received 2 IPMC +1 votes (plus an additional 3 PPMC +1
>votes) during the release voting on wookie-dev.
>
>Vote thread:
>http://incubator.markmail.org/search/?q=wookie-dev#query:wookie-
>dev%20date%3A201107%20+page:1+mid:64f4jbbr2ifunry2+state:results
>
>Result:
>http://incubator.markmail.org/search/?q=wookie-dev#query:wookie-
>dev%20date%3A201107%20+page:1+mid:2k34v5hddl4ihv4x+state:results
>
>Svn source tag:
>https://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.0-incubating/
>
>Release notes:
>https://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.0-
>incubating/RELEASE_NOTES
>
>Release artifacts:
>http://people.apache.org/~psharples/wookie/staging-area/0p9p0/rc3/
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.0-
>incubating/KEYS
>
>Vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>
>
>-
>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

[VOTE] Release Apache Rave 0.3-incubating

[Franklin, Matthew B.]

This is the second incubator release for Apache Rave, with the artifacts being 
versioned as 0.3-incubating.

We are requesting at least one IPMC member vote, as we have already received 2 
binding IPMC +1 votes during the release voting on rave-dev -
VOTE:  http://goo.gl/VH5ok
RESULT:  http://goo.gl/b9hxh

Release notes:
https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-incubating/CHANGELOG

SVN source tag (r1163402):
https://svn.apache.org/repos/asf/incubator/rave/rave-master-pom/tags/0.3-incubating/

SVN source tag (r1163411):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapacherave-002/

Source releases:
https://repository.apache.org/content/repositories/orgapacherave-002/org/apache/rave/rave-master/0.3-incubating/rave-master-0.3-incubating-source-release.zip
https://repository.apache.org/content/repositories/orgapacherave-002/org/apache/rave/rave-project/0.3-incubating/rave-project-0.3-incubating-source-release.zip

Demo Artifacts
http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-incubating-bin.zip

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


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

[RESULT] [VOTE] Release Apache Rave 0.3-incubating

[Franklin, Matthew B.]

The voting period has elapsed and the vote is now closed.

Result Summary:
+1   [1] 
  0[0]
-1[0]

With the two IPMC member votes from mentors on the dev list and the +1 from 
this list, the vote succeeds.  

Voter Record:

Hadrian Zbarcea:  +1


>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Monday, September 05, 2011 9:02 AM
>To: general@incubator.apache.org
>Cc: rave-...@incubator.apache.org
>Subject: [VOTE] Release Apache Rave 0.3-incubating
>
>This is the second incubator release for Apache Rave, with the artifacts being
>versioned as 0.3-incubating.
>
>We are requesting at least one IPMC member vote, as we have already
>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>VOTE:  http://goo.gl/VH5ok
>RESULT:  http://goo.gl/b9hxh
>
>Release notes:
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-
>incubating/CHANGELOG
>
>SVN source tag (r1163402):
>https://svn.apache.org/repos/asf/incubator/rave/rave-master-
>pom/tags/0.3-incubating/
>
>SVN source tag (r1163411):
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-incubating/
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapacherave-002/
>
>Source releases:
>https://repository.apache.org/content/repositories/orgapacherave-
>002/org/apache/rave/rave-master/0.3-incubating/rave-master-0.3-
>incubating-source-release.zip
>https://repository.apache.org/content/repositories/orgapacherave-
>002/org/apache/rave/rave-project/0.3-incubating/rave-project-0.3-
>incubating-source-release.zip
>
>Demo Artifacts
>http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-
>incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-
>incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>


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

RE: [RESULT] [VOTE] Release Apache Rave 0.3-incubating

[Franklin, Matthew B.]

>-Original Message-
>From: sebb [mailto:seb...@gmail.com]
>Sent: Friday, September 16, 2011 10:15 AM
>To: general@incubator.apache.org
>Subject: Re: [RESULT] [VOTE] Release Apache Rave 0.3-incubating
>
>On 16 September 2011 12:58, Franklin, Matthew B. 
>wrote:
>> The voting period has elapsed and the vote is now closed.
>>
>> Result Summary:
>> +1   [1]
>>  0    [0]
>> -1    [0]
>>
>> With the two IPMC member votes from mentors on the dev list and the +1
>from this list, the vote succeeds.
>>
>> Voter Record:
>>
>> Hadrian Zbarcea:  +1
>>
>
>The vote result needs to list all the votes, with the names please.

Hadrian was the only person to cast a vote on this list.  We noted the IPMC 
members who cast their vote on the dev results thread (Sylvain & Ate; RESULT:  
http://goo.gl/b9hxh)

>
>>>-Original Message-
>>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>>Sent: Monday, September 05, 2011 9:02 AM
>>>To: general@incubator.apache.org
>>>Cc: rave-...@incubator.apache.org
>>>Subject: [VOTE] Release Apache Rave 0.3-incubating
>>>
>>>This is the second incubator release for Apache Rave, with the artifacts
>being
>>>versioned as 0.3-incubating.
>>>
>>>We are requesting at least one IPMC member vote, as we have already
>>>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>>>VOTE:      http://goo.gl/VH5ok
>>>RESULT:  http://goo.gl/b9hxh
>>>
>>>Release notes:
>>>https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-
>>>incubating/CHANGELOG
>>>
>>>SVN source tag (r1163402):
>>>https://svn.apache.org/repos/asf/incubator/rave/rave-master-
>>>pom/tags/0.3-incubating/
>>>
>>>SVN source tag (r1163411):
>>>https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-incubating/
>>>
>>>Maven staging repo:
>>>https://repository.apache.org/content/repositories/orgapacherave-002/
>>>
>>>Source releases:
>>>https://repository.apache.org/content/repositories/orgapacherave-
>>>002/org/apache/rave/rave-master/0.3-incubating/rave-master-0.3-
>>>incubating-source-release.zip
>>>https://repository.apache.org/content/repositories/orgapacherave-
>>>002/org/apache/rave/rave-project/0.3-incubating/rave-project-0.3-
>>>incubating-source-release.zip
>>>
>>>Demo Artifacts
>>>http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-
>>>incubating-bin.tar.gz
>>>http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-
>>>incubating-bin.zip
>>>
>>>PGP release keys:
>>>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>>
>>>Vote open for 72 hours.
>>>
>>>[ ] +1  approve
>>>[ ] +0  no opinion
>>>[ ] -1  disapprove (and reason why)
>>>
>>
>>
>> -
>> 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

[UPDATED] [RESULT] [VOTE] Release Apache Rave 0.3-incubating

[Franklin, Matthew B.]

The voting period has elapsed and the vote is now closed.

Result Summary:
+1   [1] 
  0[0]
-1[0]

With the two IPMC member votes from mentors on the dev list and the +1 from 
this list, the vote succeeds.  

Voter Record:

Hadrian Zbarcea:  +1
**Ate Douma:  +1
**Sylvain Wallez:  +1

**Denotes an IPMC member who voted on the dev list for the release

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Monday, September 05, 2011 9:02 AM
>To: general@incubator.apache.org
>Cc: rave-...@incubator.apache.org
>Subject: [VOTE] Release Apache Rave 0.3-incubating
>
>This is the second incubator release for Apache Rave, with the artifacts being
>versioned as 0.3-incubating.
>
>We are requesting at least one IPMC member vote, as we have already
>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>VOTE:  http://goo.gl/VH5ok
>RESULT:  http://goo.gl/b9hxh
>
>Release notes:
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-
>incubating/CHANGELOG
>
>SVN source tag (r1163402):
>https://svn.apache.org/repos/asf/incubator/rave/rave-master-
>pom/tags/0.3-incubating/
>
>SVN source tag (r1163411):
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-incubating/
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapacherave-002/
>
>Source releases:
>https://repository.apache.org/content/repositories/orgapacherave-
>002/org/apache/rave/rave-master/0.3-incubating/rave-master-0.3-
>incubating-source-release.zip
>https://repository.apache.org/content/repositories/orgapacherave-
>002/org/apache/rave/rave-project/0.3-incubating/rave-project-0.3-
>incubating-source-release.zip
>
>Demo Artifacts
>http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-
>incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-
>incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>


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

[VOTE] Release Apache Rave 0.4-incubating

[Franklin, Matthew B.]

This is the third incubator release for Apache Rave, with the artifacts being 
versioned as 0.4-incubating.

We are requesting a lazy consensus vote, as we have already received 3 binding 
IPMC +1 votes during the release voting on rave-dev -
VOTE:  http://goo.gl/AoTDp
RESULT:  http://goo.gl/btRbz

Release notes:
http://svn.apache.org/repos/asf/incubator/rave/tags/0.4-incubating/CHANGELOG

SVN source tag (r114):
http://svn.apache.org/repos/asf/incubator/rave/tags/0.4-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapacherave-015/

Source releases:
https://repository.apache.org/content/repositories/orgapacherave-015/org/apache/rave/rave-project/0.4-incubating/rave-project-0.4-incubating-source-release.zip

Binary releases
http://people.apache.org/builds/incubator/rave/0.4-incubating/apache-rave-0.4-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.4-incubating/apache-rave-0.4-incubating-bin.zip

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Lazy consensus, vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

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

[RESULT] [VOTE] Release Apache Rave 0.4-incubating

[Franklin, Matthew B.]

The voting period has now closed.  There were no additional votes on this list; 
thus, the vote is successful.

The following are the IPMC members who voted +1 on the DEV list:

Ate Douma:  +1
Ross Gardler: +1
Hadrian Zbarcea:  +1

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Wednesday, October 05, 2011 5:17 PM
>To: general@incubator.apache.org
>Subject: [VOTE] Release Apache Rave 0.4-incubating
>
>This is the third incubator release for Apache Rave, with the artifacts being
>versioned as 0.4-incubating.
>
>We are requesting a lazy consensus vote, as we have already received 3
>binding IPMC +1 votes during the release voting on rave-dev -
>VOTE:  http://goo.gl/AoTDp
>RESULT:  http://goo.gl/btRbz
>
>Release notes:
>http://svn.apache.org/repos/asf/incubator/rave/tags/0.4-
>incubating/CHANGELOG
>
>SVN source tag (r114):
>http://svn.apache.org/repos/asf/incubator/rave/tags/0.4-incubating/
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapacherave-015/
>
>Source releases:
>https://repository.apache.org/content/repositories/orgapacherave-
>015/org/apache/rave/rave-project/0.4-incubating/rave-project-0.4-
>incubating-source-release.zip
>
>Binary releases
>http://people.apache.org/builds/incubator/rave/0.4-incubating/apache-rave-
>0.4-incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.4-incubating/apache-rave-
>0.4-incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Lazy consensus, vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>-
>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] Accept Apache Callback for incubation

[Franklin, Matthew B.]

+1 (non-binding).  


>-Original Message-
>From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
>Sent: Tuesday, October 11, 2011 5:10 PM
>To: general
>Subject: [VOTE] Accept Apache Callback for incubation
>
>Hi,
>
>As discussed, the PhoneGap project would like to enter the Incubator
>under the Apache Callback name (potential alternative names to be
>discussed during incubation). The initial proposal has been well
>received and there are no major open issues, so it's time to vote!
>
>Thus I'm now calling a formal VOTE on the Apache Callback proposal as
>included below. The proposal is also available at
>http://wiki.phonegap.com/w/page/46311152/apache-callback-proposal on
>the PhoneGap wiki, and I'll place a copy for our archives on the
>Incubator wiki as soon as it stops giving me internal server errors.
>
>Please VOTE:
>
>[ ] +1 Accept Apache Callback for incubation
>[ ] -1  Don't accept Apache Callback for incubation because...
>
>This vote is open for the next 72 hours. Everyone is welcome to
>participate, but only votes from the Incubator PMC members are
>binding.
>
>Thanks! My vote is +1.
>
>Best regards,
>
>Jukka Zitting
>
>
>
>Apache Callback Proposal
>
>
>Abstract
>
>
>Apache Callback is a platform for building native mobile applications
>using HTML, CSS and JavaScript.
>
>Proposal
>
>
>Apache Callback allows web developers to natively target Apple iOS, Google
>Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia
>Symbian
>and Samsung Bada with a single codebase. The Callback APIs are based on
>open web standards. The Callback bridge technology enables access to native
>device capabilities. Utilizing the Callback bridge native plugins allow
>for any type of native access from the embedded webview.
>
>Background
>--
>
>Apache Callback is the free software evolution of the popular PhoneGap
>project.
>
>PhoneGap evolved from a hack that enabled a FFI (Foreign Function
>Interface)
>to an embedded WebView on iOS to a complete suite of tools for tackling
>parity across many mobile device and desktop platforms.
>
>PhoneGap has always focused on two complementary goals. Our first goal,
>is to see the web as a first class development platform. Not a sandbox
>without a filesystem but a real first class platform that includes access
>to the local system apis, sensors and data, in addition to first class
>tooling such as system debuggers. The second goal of PhoneGap  is for
>the project to cease to exist. This is not a nihilistic sentiment, rather
>we at the PhoneGap project are providing a reference implementation for
>web browsers to assist and guide the standardization process of browser
>APIs.
>
>The name and trademark of PhoneGap will become the commercial entity for
>the project. The source, code, documentation and related assets will all
>be contributed to the Apache Foundation as Callback.
>
>The Callback name comes from the event of the same name that is fired
>when the FFI bridge is established.
>
>Rationale
>-
>
>The dominate window to the web is quickly becoming devices, mostly
>phones.
>The manufacturers of devices, creators of mobile operating systems, and
>authors of web browsers are consolidating. (In many cases these are all
>already the same company.) Those stakeholders may see a future for the
>web but their bottom line is not necessarily motivated to participate in
>an open web. It is especially clear that while many of these platforms
>have been seeing some level of strategic neglect in favor of enhanced
>experiences at the price locking developers into their respective
>platforms. The Callback project exists to bring the focus back to an
>open and accessible web.
>
>Initial Goals
>-
>
>* License all PhoneGap source code and documentation to the Apache
>  Software Foundation. (We already name the Apache license in our CLA.)
>* Setup and standardize the open governance of the Callback project.
>* Rename all assets from PhoneGap to Callback in project src, docs,
>  tests and related infrastructure.
>
>Current Status
>--
>
>Callback is a mature software project recently shipping 1.0 on July 29, 2011.
>
>Meritocracy
>---
>
>Callback has always been a project driven by merit and, in a sense, our
>solution is brute force requiring many collaborating developers to
>solve our goals.
>
>It would be far easier, and perhaps more "correct", for the Callback
>project to port a single web browser codebase, and API bindings, across
>platforms but our executable size would be appreciably larger, unacceptably
>so for mobile, and our target abstraction would be only tertiary to
>maintaining a codebase of that size. By relying on the platform browser,
>exposed by the platform SDK, we get a quick win to the browser and only
>have to focus on our bridge. This means the project requires developers
>with proficiency on each platform: collaboration is a natural side effect.
>
>Community
>-

[VOTE] Release Apache Rave 0.5-incubating

[Franklin, Matthew B.]

This is the fourth incubator release for Apache Rave, with the artifacts being 
versioned as 0.5-incubating.

We are requesting a lazy consensus vote, as we have already received 3 binding 
IPMC +1 votes during the release voting on rave-dev -

VOTE:  http://s.apache.org/N7d
RESULT:  http://s.apache.org/zb

Release notes:
http://svn.apache.org/repos/asf/incubator/rave/tags/0.5-incubating/CHANGELOG

SVN source tag (r1195758):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.5-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapacherave-133/

Source release:
https://repository.apache.org/content/repositories/orgapacherave-133/org/apache/rave/rave-project/0.5-incubating/rave-project-0.5-incubating-source-release.zip
 
Binary releases
http://people.apache.org/builds/incubator/rave/0.5-incubating/apache-rave-0.5-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.5-incubating/apache-rave-0.5-incubating-bin.zip

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Lazy consensus, vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

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

[RESULT] [VOTE] Release Apache Rave 0.5-incubating

[Franklin, Matthew B.]

The voting period has now closed.  There were no additional votes on this list; 
thus, the vote is successful.

The following are the IPMC members who voted +1 on the DEV list:

Ate Douma:  +1
Ross Gardler: +1
Hadrian Zbarcea:  +1

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Friday, November 04, 2011 9:40 AM
>To: general@incubator.apache.org
>Subject: [VOTE] Release Apache Rave 0.5-incubating
>
>This is the fourth incubator release for Apache Rave, with the artifacts being
>versioned as 0.5-incubating.
>
>We are requesting a lazy consensus vote, as we have already received 3
>binding IPMC +1 votes during the release voting on rave-dev -
>
>VOTE:  http://s.apache.org/N7d
>RESULT:  http://s.apache.org/zb
>
>Release notes:
>http://svn.apache.org/repos/asf/incubator/rave/tags/0.5-
>incubating/CHANGELOG
>
>SVN source tag (r1195758):
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.5-incubating/
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapacherave-133/
>
>Source release:
>https://repository.apache.org/content/repositories/orgapacherave-
>133/org/apache/rave/rave-project/0.5-incubating/rave-project-0.5-
>incubating-source-release.zip
>
>Binary releases
>http://people.apache.org/builds/incubator/rave/0.5-incubating/apache-rave-
>0.5-incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.5-incubating/apache-rave-
>0.5-incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Lazy consensus, vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>-
>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] Accept Openmeetings to Apache Incubator

[Franklin, Matthew B.]

+1 (non-binding)

>-Original Message-
>From: Andrus Adamchik [mailto:and...@objectstyle.org]
>Sent: Tuesday, November 08, 2011 1:54 AM
>To: general@incubator.apache.org
>Subject: [VOTE] Accept Openmeetings to Apache Incubator
>
>Opemeetings proposal has been discussed a few times here before. The
>group of developers behind it worked hard (and succeeded) to address all
>potential obstacles to the Incubator acceptance and to the following
>incubation. They even went an extra mile and collected all ICLAs in adbvance.
>
>So now I am starting the vote to accept Openmeetings to Apache Incubator.
>
>The proposal is also available at:
>http://wiki.apache.org/incubator/OpenmeetingsProposal
>
>Please cast your votes:
>
>[ ] +1 Accept Openmeetings for incubation
>[ ] +0 Don't care
>[ ] -1 Reject for the following reason:
>
>The vote is open for 72 hours.
>
>Andrus
>
>---
>Andrus Adamchik
>Apache Cayenne ORM: http://cayenne.apache.org/
>Twitter: http://twitter.com/andrus_a
>
>
>
>---
>
>== OpenMeetings Project Proposal ==
>
>== Abstract ==
>Openmeetings is a web conferencing solution.
>
>== Proposal ==
>Openmeetings provides video conferencing, instant messaging, white board,
>collaborative document editing and other groupware tools using API functions
>of the Red5 Streaming Server for Remoting and Streaming.
>
>== Background ==
>Openmeetings was developed since 2007 by Sebastian Wagner and willing
>developers. The project ships a release approximately once per quarter. It
>was developed using LGPL license, and developers are currently thinking of
>re-licensing it under Apache License 2.0.
>
>The project started as module by Sebastian Wagner for an ELearning platform
>(Dokeos) and was then split into a separated project. That is the reason why
>there is a strong relation to educational institutions that are using
>OpenMeetings and there are integrations for platforms like Moodle, ATutor,
>Sakai, STudIP or ILias available
>(http://code.google.com/p/openmeetings/wiki/MoodlePlugins). The relation
>to educational institutions also subsequently lead to some projects funded by
>the EU where OpenMeetings was involved, for example by the
>Swedish/Finnish Centre of Open-Source !OpenKarken (Case-Study about the
>EU project at OSOR.eu: http://www.osor.eu/studies/finland-and-sweden-
>collaborate-using-oss )
>
>The integration and internationalization of the project was a primary focus
>right from the start of the project. Since Version 0.5 there is a 
>Language-Editor
>(http://code.google.com/p/openmeetings/wiki/LanguageEditor) to edit
>labels, export and import them as XML and you can use those XML files for
>future installations (or contribute it to the community). There are currently
>around 30 languages available.  Since version 0.5.1 there is also a SOAP API to
>integrate !OpenMeetings. We constantly improve this SOAP/REST API
>(http://code.google.com/p/openmeetings/wiki/SoapMethods) with new
>functionality with a strong focus on security and usability. The auth-mechnism
>is quite similar to OAuth, you create some token and then assign rights to the
>token. (Documentation for Single Sign On:
>http://code.google.com/p/openmeetings/wiki/DirectLoginSoapGeneralFlow)
>
>The project name "!OpenMeetings" and logos are inspired by Ludovic Gasc
>who has been the project manager at Dokeos at the time Sebastian split
>!OpenMeetings as separated project.
>
>Red5 Server provides an "Edge-Orion-Clustering"
>(http://trac.red5.org/wiki/Documentation/Tutorials/EdgeOriginClusteringCon
>figuration).  We hope to extend this clustering solution with support for rtmpt
>and  rtmps and integrate that into our application as native clustering  
>option.
>
>== Rationale ==
>Last year most major vendors started commercial web conferencing solutions.
>This is an important part of software ecosystem, and there is an urge to
>consolidate open source development efforts in this direction.
>
>According to several studies demand for synchronous Communication, in
>opposite to asynchronous Communication like wiki's or email, will raise the
>upcoming years. For example Gartner promises that 2011 the market will grow
>20% according to their "Magic Quadrant" report 2010 (
>http://www.gartner.com/DisplayDocument?doc_cd=205941 ).
>
>Openmeetings is a unique solution in terms of patent purity and potentially
>can grow into solution built on top of the fully open source stack. That is 
>why it
>is a good candidate for consolidating web conferencing community efforts.
>
>== Initial Goals ==
>Each of project committers has their own set of goals, but we all share the
>following.
>
> * Move to Apache.
> * Become popular.
>
>To become popular we plan to do the following.
>
> * Improve ecosystem around the project.
> * Improve release process.
> * Improve project testing and stability.
> * Apply modular architecture/SOA for better integration with other projects.
>
>== Current Status ==
>We have agreed on applying for the Apache Foundation and pr

[VOTE] Release Apache Rave 0.6-incubating

[Franklin, Matthew B.]

This is the fifth incubator release for Apache Rave, with the artifacts being 
versioned as 0.6-incubating.

We are requesting at least one additional IPMC member vote, as we have received 
2 binding IPMC +1 votes during the release voting on rave-dev -

VOTE:  http://s.apache.org/Czr
RESULT:  http://s.apache.org/yIQ

IPMC member votes from the rave-dev list:
Ate Douma:   +1
Ross Gardler: +1

Release notes:
http://svn.apache.org/repos/asf/incubator/rave/tags/0.6-incubating/CHANGELOG

SVN source tag (r1208867):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.6-incubating/

Maven staging repos:
https://repository.apache.org/content/repositories/orgapacherave-278/
https://repository.apache.org/content/repositories/orgapacherave-279/

Source release:
https://repository.apache.org/content/repositories/orgapacherave-278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6-incubating-source-release.zip

Binary releases
http://people.apache.org/builds/incubator/rave/0.6-incubating/apache-rave-0.6-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.6-incubating/apache-rave-0.6-incubating-bin.zip

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

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

RE: [VOTE] Release Apache Rave 0.6-incubating

[Franklin, Matthew B.]

>-Original Message-
>From: sebb [mailto:seb...@gmail.com]
>Sent: Tuesday, January 03, 2012 7:06 AM
>To: general@incubator.apache.org
>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>
>On 28 December 2011 19:15, Franklin, Matthew B. 
>wrote:
>> This is the fifth incubator release for Apache Rave, with the artifacts being
>versioned as 0.6-incubating.
>>
>> We are requesting at least one additional IPMC member vote, as we have
>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>>
>> VOTE:      http://s.apache.org/Czr
>> RESULT:  http://s.apache.org/yIQ
>>
>> IPMC member votes from the rave-dev list:
>> Ate Douma:   +1
>> Ross Gardler: +1
>>
>> Release notes:
>> http://svn.apache.org/repos/asf/incubator/rave/tags/0.6-
>incubating/CHANGELOG

Apparently, I didn't commit back the CHANGELOG for 0.6 .  Here is the issue 
list from JIRA 

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311290&version=12317563

>
>which says:
>
>Release Notes - Rave - Version 0.5-INCUBATING
>
>So what was changed for 0.6?
>
>> SVN source tag (r1208867):
>> https://svn.apache.org/repos/asf/incubator/rave/tags/0.6-incubating/
>>
>> Maven staging repos:
>> https://repository.apache.org/content/repositories/orgapacherave-278/
>> https://repository.apache.org/content/repositories/orgapacherave-279/
>>
>> Source release:
>> https://repository.apache.org/content/repositories/orgapacherave-
>278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6-
>incubating-source-release.zip
>>
>> Binary releases
>> http://people.apache.org/builds/incubator/rave/0.6-incubating/apache-
>rave-0.6-incubating-bin.tar.gz
>> http://people.apache.org/builds/incubator/rave/0.6-incubating/apache-
>rave-0.6-incubating-bin.zip
>>
>> PGP release keys:
>> https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>
>> Vote open for 72 hours.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> -
>> 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: [VOTE] Release Apache Rave 0.6-incubating

[Franklin, Matthew B.]

Does my answer below suffice?   It would be nice to close this vote out one way 
or another


>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Tuesday, January 03, 2012 12:19 PM
>To: general@incubator.apache.org
>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>
>>-Original Message-
>>From: sebb [mailto:seb...@gmail.com]
>>Sent: Tuesday, January 03, 2012 7:06 AM
>>To: general@incubator.apache.org
>>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>>
>>On 28 December 2011 19:15, Franklin, Matthew B. 
>>wrote:
>>> This is the fifth incubator release for Apache Rave, with the artifacts 
>>> being
>>versioned as 0.6-incubating.
>>>
>>> We are requesting at least one additional IPMC member vote, as we have
>>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>>>
>>> VOTE:      http://s.apache.org/Czr
>>> RESULT:  http://s.apache.org/yIQ
>>>
>>> IPMC member votes from the rave-dev list:
>>> Ate Douma:   +1
>>> Ross Gardler: +1
>>>
>>> Release notes:
>>> http://svn.apache.org/repos/asf/incubator/rave/tags/0.6-
>>incubating/CHANGELOG
>
>Apparently, I didn't commit back the CHANGELOG for 0.6 .  Here is the issue
>list from JIRA
>
>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311290
>&version=12317563
>
>>
>>which says:
>>
>>Release Notes - Rave - Version 0.5-INCUBATING
>>
>>So what was changed for 0.6?
>>
>>> SVN source tag (r1208867):
>>> https://svn.apache.org/repos/asf/incubator/rave/tags/0.6-incubating/
>>>
>>> Maven staging repos:
>>> https://repository.apache.org/content/repositories/orgapacherave-278/
>>> https://repository.apache.org/content/repositories/orgapacherave-279/
>>>
>>> Source release:
>>> https://repository.apache.org/content/repositories/orgapacherave-
>>278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6-
>>incubating-source-release.zip
>>>
>>> Binary releases
>>> http://people.apache.org/builds/incubator/rave/0.6-incubating/apache-
>>rave-0.6-incubating-bin.tar.gz
>>> http://people.apache.org/builds/incubator/rave/0.6-incubating/apache-
>>rave-0.6-incubating-bin.zip
>>>
>>> PGP release keys:
>>> https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>>
>>> Vote open for 72 hours.
>>>
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> -
>>> 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: [VOTE] Release Apache Rave 0.6-incubating

[Franklin, Matthew B.]

>-Original Message-
>From: sebb [mailto:seb...@gmail.com]
>Sent: Monday, January 09, 2012 8:21 AM
>To: general@incubator.apache.org
>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>
>On 9 January 2012 13:09, Franklin, Matthew B.  wrote:
>> Does my answer below suffice?   It would be nice to close this vote out one
>way or another
>>
>
>The answer describes what happened.
>However, it does not fix the problem, which is that the end-user sees
>a file with conflicting information.

Thanks.  This is what I was looking for, so that we can have the discussion as 
to whether or not to cancel the release (we won't do a re-release).

>
>Not a blocker, but you may find it takes less time overall to fix the
>issue before release rather than dealing with user queries afterwards.
>
>It may also lessen confidence in the release: if there is such an
>obvious error, what other errors are lurking?

While I agree that it doesn't look great, the CHANGELOG is distributed with the 
source release and is probably not viewed as much as the release notes sent out 
with the announcement (which will be the JIRA list I linked).  I will take this 
back to our dev list, but if they don't see it as a blocker, would you be 
comfortable voting +1?

>
>>>-Original Message-
>>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>>Sent: Tuesday, January 03, 2012 12:19 PM
>>>To: general@incubator.apache.org
>>>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>>>
>>>>-Original Message-
>>>>From: sebb [mailto:seb...@gmail.com]
>>>>Sent: Tuesday, January 03, 2012 7:06 AM
>>>>To: general@incubator.apache.org
>>>>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>>>>
>>>>On 28 December 2011 19:15, Franklin, Matthew B. 
>>>>wrote:
>>>>> This is the fifth incubator release for Apache Rave, with the artifacts
>being
>>>>versioned as 0.6-incubating.
>>>>>
>>>>> We are requesting at least one additional IPMC member vote, as we
>have
>>>>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>>>>>
>>>>> VOTE:      http://s.apache.org/Czr
>>>>> RESULT:  http://s.apache.org/yIQ
>>>>>
>>>>> IPMC member votes from the rave-dev list:
>>>>> Ate Douma:   +1
>>>>> Ross Gardler: +1
>>>>>
>>>>> Release notes:
>>>>> http://svn.apache.org/repos/asf/incubator/rave/tags/0.6-
>>>>incubating/CHANGELOG
>>>
>>>Apparently, I didn't commit back the CHANGELOG for 0.6 .  Here is the issue
>>>list from JIRA
>>>
>>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123112
>90
>>>&version=12317563
>>>
>>>>
>>>>which says:
>>>>
>>>>Release Notes - Rave - Version 0.5-INCUBATING
>>>>
>>>>So what was changed for 0.6?
>>>>
>>>>> SVN source tag (r1208867):
>>>>> https://svn.apache.org/repos/asf/incubator/rave/tags/0.6-incubating/
>>>>>
>>>>> Maven staging repos:
>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>278/
>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>279/
>>>>>
>>>>> Source release:
>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>>>>278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6-
>>>>incubating-source-release.zip
>>>>>
>>>>> Binary releases
>>>>> http://people.apache.org/builds/incubator/rave/0.6-
>incubating/apache-
>>>>rave-0.6-incubating-bin.tar.gz
>>>>> http://people.apache.org/builds/incubator/rave/0.6-
>incubating/apache-
>>>>rave-0.6-incubating-bin.zip
>>>>>
>>>>> PGP release keys:
>>>>> https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>>>>
>>>>> Vote open for 72 hours.
>>>>>
>>>>> [ ] +1  approve
>>>>> [ ] +0  no opinion
>>>>> [ ] -1  disapprove (and reason why)
>>>>>
>>>>> -
>>>>> 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
>>
>
>-
>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: Maven coordinate for incubating podlings

[Franklin, Matthew B.]

>-Original Message-
>From: Alan D.Cabrera [mailto:l...@toolazydogs.com]
>Sent: Monday, January 09, 2012 3:47 PM
>To: general@incubator.apache.org
>Subject: Maven coordinate for incubating podlings
>
>It's my understanding that the group and artifact id do not include the token
>"incubating" or "incubator" but that "-incubating" is suffixed to the version
>number.
>
>Do I understand the requirements correctly?

That is how we do it in Rave at the guidance of our mentors.

>
>
>Regards,
>Alan
>
>
>-
>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 Rave 0.6-incubating

[Franklin, Matthew B.]

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Monday, January 09, 2012 8:45 AM
>To: general@incubator.apache.org
>Cc: rave-...@incubator.apache.org
>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>
>>-Original Message-
>>From: sebb [mailto:seb...@gmail.com]
>>Sent: Monday, January 09, 2012 8:21 AM
>>To: general@incubator.apache.org
>>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>>
>>On 9 January 2012 13:09, Franklin, Matthew B. 
>wrote:
>>> Does my answer below suffice?   It would be nice to close this vote out one
>>way or another
>>>
>>
>>The answer describes what happened.
>>However, it does not fix the problem, which is that the end-user sees
>>a file with conflicting information.
>
>Thanks.  This is what I was looking for, so that we can have the discussion as 
>to
>whether or not to cancel the release (we won't do a re-release).
>
>>
>>Not a blocker, but you may find it takes less time overall to fix the
>>issue before release rather than dealing with user queries afterwards.
>>
>>It may also lessen confidence in the release: if there is such an
>>obvious error, what other errors are lurking?
>
>While I agree that it doesn't look great, the CHANGELOG is distributed with
>the source release and is probably not viewed as much as the release notes
>sent out with the announcement (which will be the JIRA list I linked).  I will
>take this back to our dev list, but if they don't see it as a blocker, would 
>you be
>comfortable voting +1?

The community was presented with the issue and via lazy consensus agreed to 
move forward with the release, even though the CHANGELOG file is incorrect.  We 
still need 1 final IPMC vote to release.

[ Community discussion on proceeding:  
http://markmail.org/message/tp5nyqh24tdpybw6 ]

>
>>
>>>>-Original Message-
>>>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>>>Sent: Tuesday, January 03, 2012 12:19 PM
>>>>To: general@incubator.apache.org
>>>>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>>>>
>>>>>-Original Message-
>>>>>From: sebb [mailto:seb...@gmail.com]
>>>>>Sent: Tuesday, January 03, 2012 7:06 AM
>>>>>To: general@incubator.apache.org
>>>>>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>>>>>
>>>>>On 28 December 2011 19:15, Franklin, Matthew B.
>
>>>>>wrote:
>>>>>> This is the fifth incubator release for Apache Rave, with the artifacts
>>being
>>>>>versioned as 0.6-incubating.
>>>>>>
>>>>>> We are requesting at least one additional IPMC member vote, as we
>>have
>>>>>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>>>>>>
>>>>>> VOTE:      http://s.apache.org/Czr
>>>>>> RESULT:  http://s.apache.org/yIQ
>>>>>>
>>>>>> IPMC member votes from the rave-dev list:
>>>>>> Ate Douma:   +1
>>>>>> Ross Gardler: +1
>>>>>>
>>>>>> Release notes:
>>>>>> http://svn.apache.org/repos/asf/incubator/rave/tags/0.6-
>>>>>incubating/CHANGELOG
>>>>
>>>>Apparently, I didn't commit back the CHANGELOG for 0.6 .  Here is the
>issue
>>>>list from JIRA
>>>>
>>>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311
>2
>>90
>>>>&version=12317563
>>>>
>>>>>
>>>>>which says:
>>>>>
>>>>>Release Notes - Rave - Version 0.5-INCUBATING
>>>>>
>>>>>So what was changed for 0.6?
>>>>>
>>>>>> SVN source tag (r1208867):
>>>>>> https://svn.apache.org/repos/asf/incubator/rave/tags/0.6-incubating/
>>>>>>
>>>>>> Maven staging repos:
>>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>>278/
>>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>>279/
>>>>>>
>>>>>> Source release:
>>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>>>>>278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6-
>>>>>incubating-source-release.zip
>>>>>>
>>>>>> Binary rele

RE: Small but otherwise happy podlings

[Franklin, Matthew B.]

>-Original Message-
>From: Niclas Hedhman [mailto:nic...@hedhman.org]
>Sent: Tuesday, January 10, 2012 11:25 PM
>To: general@incubator.apache.org; Joe Schaefer
>Subject: Re: Small but otherwise happy podlings
>
>I like Joe's suggestion of having Mentors writing a report. But I
>would like the PPMC get some experience as well, since once they
>graduate they are tossed into the fire of producing "real" board
>reports on their own.
>
>Possible extension of Joe's suggestion; The PPMC produce the Board
>report as if they were a top level project. Mentor produce separately
>the "road map to graduation" report, covering what has been done, what
>is going on right now and what is left to do. IPMC will quickly see
>AWOL Mentors and which podlings need help, without taking away the
>"training" of the PPMC...

>From my perspective as a podling PPMC member, I disagree with this approach.  
>From what I have learned, it is the Incubator's responsibility to develop a 
>self-sustaining community.  IMO, any viable community should be responsible 
>for managing their own destiny.  Mentors should prod, poke, suggest, 
>influence, coach and verify everything the podling does, but the PPMC should 
>be responsible for developing and reporting out a graduation roadmap.

>
>
>Cheers
>Niclas
>
>On Wed, Jan 11, 2012 at 5:52 AM, Joe Schaefer 
>wrote:
>> I don't know about you, but in the podlings I mentor I am subscribed
>> to most if not all of the mailing lists and try to read the bulk of
>> it all.  I could easily write status reports for them if it was my
>> responsibility to do so, and for the initial 6 months would prefer
>> that mentors showed their podlings and their fellow mentors what can
>> be done with a properreport before passing that duty along to the PPMC.
>>
>>
>>
>> - Original Message -
>>> From: ant elder 
>>> To: general@incubator.apache.org
>>> Cc:
>>> Sent: Tuesday, January 10, 2012 4:47 PM
>>> Subject: Re: Small but otherwise happy podlings
>>>
>>> I like the idea of mentors being expected to signoff on the wiki just
>>> to show that they are paying attention, but i also agree that it might
>>> be useful to have along with the poddling reports to have comments
>>> from the mentors. So how about doing both? Just extend the mentor
>>> signoff section to include comments so a poddling report is the
>>> poddling comments, mentor comments about whats going on and what
>>> they'd like to see the poddling doing in the next months and a signoff
>>> from all active mentors.
>>>
>>> Or Joe are you saying that we should scrap the poddling comments bit
>>> entirely? I think its useful to get a quick overview of whats going on
>>> and it gets them used to the TLP board report requirement.
>>>
>>>   ...ant
>>>
>>> On Mon, Jan 9, 2012 at 6:27 PM, Joe Schaefer 
>>> wrote:
  Lame.  I would actually like to see mentors WRITING the reports
  at least for the first 6 months to a year, then going to sign-off
  on the wiki.



  - Original Message -
>  From: William A. Rowe Jr. 
>  To: general@incubator.apache.org
>  Cc: Upayavira 
>  Sent: Monday, January 9, 2012 1:23 PM
>  Subject: Re: Small but otherwise happy podlings
>
>  On 1/9/2012 11:40 AM, Upayavira wrote:
>>   Regarding attrition of mentors, it was discussed having mentors
>  'sign'
>>   the board report for their podling. Could that be encouraged, and
>>> used
>>   as a sign of minimum 'activity' for a mentor?
>
>  How about simply sign off on podling-dev@?  Even if it is "Thanks
>>> for
>  drafting this!  No edits from me."
>
>
>  -
>  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
>>
>
>
>
>--
>Niclas Hedhman, Software Developer
>http://www.qi4j.org - New Energy for Java
>
>I live here; http://tinyurl.com/3xugrbk
>I work here; http://tinyurl.com/6a2pl4j
>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

[1 IPMC VOTE NEEDED] [VOTE] Release Apache Rave 0.6-incubating

[Franklin, Matthew B.]

We still need to get one more IPMC vote to close this vote.  If someone could 
take a look, it would be greatly appreciated.

-Matt

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Wednesday, January 11, 2012 8:03 AM
>To: general@incubator.apache.org
>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>
>>-Original Message-
>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>Sent: Monday, January 09, 2012 8:45 AM
>>To: general@incubator.apache.org
>>Cc: rave-...@incubator.apache.org
>>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>>
>>>-Original Message-
>>>From: sebb [mailto:seb...@gmail.com]
>>>Sent: Monday, January 09, 2012 8:21 AM
>>>To: general@incubator.apache.org
>>>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>>>
>>>On 9 January 2012 13:09, Franklin, Matthew B. 
>>wrote:
>>>> Does my answer below suffice?   It would be nice to close this vote out
>one
>>>way or another
>>>>
>>>
>>>The answer describes what happened.
>>>However, it does not fix the problem, which is that the end-user sees
>>>a file with conflicting information.
>>
>>Thanks.  This is what I was looking for, so that we can have the discussion as
>to
>>whether or not to cancel the release (we won't do a re-release).
>>
>>>
>>>Not a blocker, but you may find it takes less time overall to fix the
>>>issue before release rather than dealing with user queries afterwards.
>>>
>>>It may also lessen confidence in the release: if there is such an
>>>obvious error, what other errors are lurking?
>>
>>While I agree that it doesn't look great, the CHANGELOG is distributed with
>>the source release and is probably not viewed as much as the release notes
>>sent out with the announcement (which will be the JIRA list I linked).  I will
>>take this back to our dev list, but if they don't see it as a blocker, would 
>>you
>be
>>comfortable voting +1?
>
>The community was presented with the issue and via lazy consensus agreed
>to move forward with the release, even though the CHANGELOG file is
>incorrect.  We still need 1 final IPMC vote to release.
>
>[ Community discussion on proceeding:
>http://markmail.org/message/tp5nyqh24tdpybw6 ]
>
>>
>>>
>>>>>-Original Message-
>>>>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>>>>Sent: Tuesday, January 03, 2012 12:19 PM
>>>>>To: general@incubator.apache.org
>>>>>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>>>>>
>>>>>>-Original Message-
>>>>>>From: sebb [mailto:seb...@gmail.com]
>>>>>>Sent: Tuesday, January 03, 2012 7:06 AM
>>>>>>To: general@incubator.apache.org
>>>>>>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>>>>>>
>>>>>>On 28 December 2011 19:15, Franklin, Matthew B.
>>
>>>>>>wrote:
>>>>>>> This is the fifth incubator release for Apache Rave, with the artifacts
>>>being
>>>>>>versioned as 0.6-incubating.
>>>>>>>
>>>>>>> We are requesting at least one additional IPMC member vote, as we
>>>have
>>>>>>received 2 binding IPMC +1 votes during the release voting on rave-dev
>-
>>>>>>>
>>>>>>> VOTE:      http://s.apache.org/Czr
>>>>>>> RESULT:  http://s.apache.org/yIQ
>>>>>>>
>>>>>>> IPMC member votes from the rave-dev list:
>>>>>>> Ate Douma:   +1
>>>>>>> Ross Gardler: +1
>>>>>>>
>>>>>>> Release notes:
>>>>>>> http://svn.apache.org/repos/asf/incubator/rave/tags/0.6-
>>>>>>incubating/CHANGELOG
>>>>>
>>>>>Apparently, I didn't commit back the CHANGELOG for 0.6 .  Here is the
>>issue
>>>>>list from JIRA
>>>>>
>>>>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231
>1
>>2
>>>90
>>>>>&version=12317563
>>>>>
>>>>>>
>>>>>>which says:
>>>>>>
>>>>>>Release Notes - Rave - Version 0.5-INCUBATING
>>>>>>
>>>>>>So what was changed for 0.6?
>>>>>>
>>

[RESULT] [VOTE] Release Apache Rave 0.6-incubating

[Franklin, Matthew B.]

The voting period is now closed.  Thanks to everyone who took the time to 
review the release. 

Result Summary for this List:

+1   [1]
  0[1]
-1[0]

With the two IPMC member votes from mentors on the dev list and the +1 from 
this list, the vote succeeds.

IPMC member voting record:
* Ate Douma:+1
* Ross Gardler: +1
Ant Elder:   +1

*Denotes an IPMC member vote cast on the rave-dev list

>-Original Message-
>From: ant elder [mailto:ant.el...@gmail.com]
>Sent: Friday, January 13, 2012 3:53 AM
>To: general@incubator.apache.org
>Subject: Re: [1 IPMC VOTE NEEDED] [VOTE] Release Apache Rave 0.6-
>incubating
>
>I've had a look, the only issue i see is I don't think the NOTICE file
>in the binary distribution is correct as it has many things which i
>expect are not required. When we last discussed this on general@ we
>said this is not strictly a blocking problem, so
>
>+1
>
>but i think you should do a complete review of whats in the NOTICE
>file with your mentors and remove everything which doesn't need to be
>there.
>
>   ...ant
>
>On Thu, Jan 12, 2012 at 2:16 PM, Franklin, Matthew B.
> wrote:
>> We still need to get one more IPMC vote to close this vote.  If someone
>could take a look, it would be greatly appreciated.
>>
>> -Matt
>>
>>>-Original Message-
>>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>>Sent: Wednesday, January 11, 2012 8:03 AM
>>>To: general@incubator.apache.org
>>>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>>>
>>>>-Original Message-
>>>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>>>Sent: Monday, January 09, 2012 8:45 AM
>>>>To: general@incubator.apache.org
>>>>Cc: rave-...@incubator.apache.org
>>>>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>>>>
>>>>>-----Original Message-
>>>>>From: sebb [mailto:seb...@gmail.com]
>>>>>Sent: Monday, January 09, 2012 8:21 AM
>>>>>To: general@incubator.apache.org
>>>>>Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
>>>>>
>>>>>On 9 January 2012 13:09, Franklin, Matthew B. 
>>>>wrote:
>>>>>> Does my answer below suffice?   It would be nice to close this vote out
>>>one
>>>>>way or another
>>>>>>
>>>>>
>>>>>The answer describes what happened.
>>>>>However, it does not fix the problem, which is that the end-user sees
>>>>>a file with conflicting information.
>>>>
>>>>Thanks.  This is what I was looking for, so that we can have the discussion
>as
>>>to
>>>>whether or not to cancel the release (we won't do a re-release).
>>>>
>>>>>
>>>>>Not a blocker, but you may find it takes less time overall to fix the
>>>>>issue before release rather than dealing with user queries afterwards.
>>>>>
>>>>>It may also lessen confidence in the release: if there is such an
>>>>>obvious error, what other errors are lurking?
>>>>
>>>>While I agree that it doesn't look great, the CHANGELOG is distributed
>with
>>>>the source release and is probably not viewed as much as the release
>notes
>>>>sent out with the announcement (which will be the JIRA list I linked).  I 
>>>>will
>>>>take this back to our dev list, but if they don't see it as a blocker, would
>you
>>>be
>>>>comfortable voting +1?
>>>
>>>The community was presented with the issue and via lazy consensus
>agreed
>>>to move forward with the release, even though the CHANGELOG file is
>>>incorrect.  We still need 1 final IPMC vote to release.
>>>
>>>[ Community discussion on proceeding:
>>>http://markmail.org/message/tp5nyqh24tdpybw6 ]
>>>
>>>>
>>>>>
>>>>>>>-Original Message-
>>>>>>>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>>>>>>>Sent: Tuesday, January 03, 2012 12:19 PM
>>>>>>>To: general@incubator.apache.org
>>>>>>>Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
>>>>>>>
>>>>>>>>-Original Message-
>>>>>>>>From: sebb [mailto:seb...@gmail.com]
>>>>>>>>Sent: Tuesday, January 03, 2012 7:06 AM
>>>>>>>>To: general@

RE: [1 IPMC VOTE NEEDED] [VOTE] Release Apache Rave 0.6-incubating

[Franklin, Matthew B.]

>I've had a look, the only issue i see is I don't think the NOTICE file
>in the binary distribution is correct as it has many things which i
>expect are not required. When we last discussed this on general@ we
>said this is not strictly a blocking problem, so
>
>+1
>
>but i think you should do a complete review of whats in the NOTICE
>file with your mentors and remove everything which doesn't need to be
>there.

Thanks for taking a look.  I will take your suggestion back to the DEV list and 
see if our mentors find any changes that need to be made.



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

[ANNOUNCE] Apache Rave 0.6-INCUBATING Release

[Franklin, Matthew B.]

The Apache Rave (Incubating) team is pleased to announce the immediate
availability of the Rave 0.6-INCUBATING Alpha release.

Apache Rave is a new web and social mashup engine. It will provide an
out-of-the-box, as well as extendible, lightweight Java platform to
host, serve and manage OpenSocial, W3C and other web widgets. Rave is
targeted as an engine for internet and intranet portals and as a building
block to provide context-aware personalization and collaboration
features for multi-site/multi-channel (mobile) oriented and content
driven websites.

The release can be obtained from the Apache Rave download page
(http://incubator.apache.org/rave/downloads.html).

Release Notes for this release are available at http://s.apache.org/ZZY.


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

RE: [VOTE] Release apache-manifoldcf-0.4-incubating, RC2

[Franklin, Matthew B.]

>-Original Message-
>From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
>Sent: Wednesday, January 18, 2012 3:51 PM
>To: general@incubator.apache.org
>Subject: Re: [VOTE] Release apache-manifoldcf-0.4-incubating, RC2
>
>Hi,
>
>On Wed, Jan 18, 2012 at 8:50 PM, Joe Schaefer 
>wrote:
>> The solution is simple, bring more IPMC members
>> in from the ManifoldCF podling.
>
>Simple and obvious, yet I never thought about this. Thanks for bringing it up!

Having been through 5 incubator releases, I can tell you that having sufficient 
IPMC members on the project to review the release and cast binding votes makes 
the process much smoother.  However, 2 out of the 5 have required at least one 
additional vote from an IPMC member on the general list, which requires someone 
unfamiliar with the project to invest the time to thoroughly review the 
release.  IMO it is important to have enough mentors/IPMC members to be able to 
release, but that is only a partial solution.  The general list still needs to 
have IPMC members willing to take on the sometimes daunting task of digging 
through an unfamiliar project to properly review the release.

>
>BR,
>
>Jukka Zitting
>
>-
>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

[VOTE] Release Apache Rave 0.7-incubating

[Franklin, Matthew B.]

This is the sixth incubator release for Apache Rave, with the artifacts being 
versioned as 0.7-incubating.

We are requesting a lazy consensus vote, as we have already received 3 binding 
IPMC +1 votes during the release voting on rave-dev -

VOTE:  http://s.apache.org/xqH   
RESULT:  http://s.apache.org/rg

Release notes:
http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGELOG

SVN source tag (r1227377):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/

Maven staging repo: 
https://repository.apache.org/content/repositories/orgapacherave-015/

Source release: 
https://repository.apache.org/content/repositories/orgapacherave-015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-source-release.zip

Binary releases
http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.zip

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Lazy consensus, vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

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

Re: [VOTE] Release Apache Rave 0.7-incubating

[Franklin, Matthew B.]

On 1/23/12 3:29 PM, "sebb"  wrote:

>On 23 January 2012 15:17, Franklin, Matthew B. 
>wrote:
>> This is the sixth incubator release for Apache Rave, with the artifacts
>>being versioned as 0.7-incubating.
>>
>> We are requesting a lazy consensus vote, as we have already received 3
>>binding IPMC +1 votes during the release voting on rave-dev -
>>
>> VOTE:  http://s.apache.org/xqH
>> RESULT:  http://s.apache.org/rg
>>
>> Release notes:
>> 
>>http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGE
>>LOG
>>
>> SVN source tag (r1227377):
>> https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/
>
>NOTICE file says:
>
>Apache Rave
>Copyright 2011 The Apache Software Foundation
>
>Is this still correct?

The release was spun on January 4th of 2012 and there were 4 minor changes
made between 2012 & the release.  Based on prior discussions on this list,
minor changes don't seem to be a blocker [1].  Additionally, I have
created a JIRA ticket for updating the copyright date on all NOTICE files
[2].

[1] :  http://markmail.org/message/3b776xpdzijynypc
[2] :  https://issues.apache.org/jira/browse/RAVE-439

>
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapacherave-015/
>>
>> Source release:
>> 
>>https://repository.apache.org/content/repositories/orgapacherave-015/org/
>>apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-sourc
>>e-release.zip
>>
>> Binary releases
>> 
>>http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave
>>-0.7-incubating-bin.tar.gz
>> 
>>http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave
>>-0.7-incubating-bin.zip
>>
>> PGP release keys:
>> https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>
>> Lazy consensus, vote open for 72 hours.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> -
>> 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: [VOTE] Release Apache Rave 0.7-incubating

[Franklin, Matthew B.]

>-Original Message-
>From: Ate Douma [mailto:a...@douma.nu]
>Sent: Monday, January 23, 2012 5:14 PM
>To: rave-...@incubator.apache.org
>Cc: general@incubator.apache.org
>Subject: Re: [VOTE] Release Apache Rave 0.7-incubating
>
>On 01/23/2012 10:56 PM, Ate Douma wrote:
>> On 01/23/2012 10:30 PM, Franklin, Matthew B. wrote:
>>> On 1/23/12 3:29 PM, "sebb" wrote:
>>>
>>>> On 23 January 2012 15:17, Franklin, Matthew B.
>>>> wrote:
>>>>> This is the sixth incubator release for Apache Rave, with the artifacts
>>>>> being versioned as 0.7-incubating.
>>>>>
>>>>> We are requesting a lazy consensus vote, as we have already received 3
>>>>> binding IPMC +1 votes during the release voting on rave-dev -
>>>>>
>>>>> VOTE: http://s.apache.org/xqH
>>>>> RESULT: http://s.apache.org/rg
>>>>>
>>>>> Release notes:
>>>>>
>>>>> http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-
>incubating/CHANGE
>>>>> LOG
>>>>>
>>>>> SVN source tag (r1227377):
>>>>> https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/
>>>>
>>>> NOTICE file says:
>>>>
>>>> Apache Rave
>>>> Copyright 2011 The Apache Software Foundation
>>>>
>>>> Is this still correct?
>>>
>>> The release was spun on January 4th of 2012 and there were 4 minor
>changes
>>> made between 2012& the release. Based on prior discussions on this list,
>>> minor changes don't seem to be a blocker [1]. Additionally, I have
>>> created a JIRA ticket for updating the copyright date on all NOTICE files
>>> [2].
>>>
>>> [1] : http://markmail.org/message/3b776xpdzijynypc
>>> [2] : https://issues.apache.org/jira/browse/RAVE-439
>>>
>>
>> Besides this being a minor and certainly non-blocker issue, a similar 
>> question
>> came up just last week on legal-discuss@ where the question was if every
>> copyright statement would need to be 'bumped' to adjust for the new year.
>Greg
>> Stein provided IMO a nice and clear (follow up) answer about the
>importance of
>> how and when to do this [3]:
>>
>> 
>> Actually, the shorter answer is "get it close, but don't worry about it."
>> (per a lawyer friend of mine)
>>
>> What you put in the header is advisory. If you end up in court, it has zero
>> impact compared to the actual commit history that demonstrates it is your
>> work. "Your work" is the operative issue; not when you happened to do that
>> work."
>> 
>> Original message and thread link:
>http://markmail.org/message/v3n7vyd4anxmgzbn
>
>On second thought, the above quote might not be relevant in *this* context,
>as
>in this case it concerns the NOTICE file, not some copyrighted resource itself.
>
>Nonetheless, the fact this was a release cut on January 4th, I think it truely
>isn't of much concern anyway, and for subsequent releases we'll adjust the
>copyright date.
>
>I do however very much appreciate the proper review and feedback from
>sebb, and
>others on general@ alike, because all these tiny issues are soo easy to
>overlook!

+1.  Much better to catch it on January 23rd, 2012 than on January 23rd, 2015.  
Thanks, Sebb.

>
>Thanks, Ate
>
>>
>> So I see no reason at all to worry about these now.
>>
>> And, for the record, none of the NOTICE files in this release themselves
>were
>> modified since 2011.
>>
>> Ate
>>
>>>>
>>>>> Maven staging repo:
>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>015/
>>>>>
>>>>> Source release:
>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>015/org/
>>>>> apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-
>sourc
>>>>> e-release.zip
>>>>>
>>>>> Binary releases
>>>>>
>>>>> http://people.apache.org/builds/incubator/rave/0.7-
>incubating/apache-rave
>>>>> -0.7-incubating-bin.tar.gz
>>>>>
>>>>> http://people.apache.org/builds/incubator/rave/0.7-
>incubating/apache-rave
>>>>> -0.7-incubating-bin.zip
>>>>>
>>>>> PGP release keys:
>>>>> https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>>>>
>>>>> Lazy consensus, vote open for 72 hours.
>>>>>
>>>>> [ ] +1 approve
>>>>> [ ] +0 no opinion
>>>>> [ ] -1 disapprove (and reason why)
>>>>>
>>>>> -
>>>>> 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

[RESULT] [VOTE] Release Apache Rave 0.7-incubating

[Franklin, Matthew B.]

The voting period is now closed.  Thanks to everyone who took the time to review
the release. 

Result Summary for this List:

Binding IPMC Member Votes
+1   [0]
  0[0]
-1[0]

Non-binding Community Votes 
+1   [1]
  0[0]
-1[0]

With the three IPMC member votes from mentors on the dev list  the vote 
succeeds.

IPMC member voting record:
* Ate Douma:  +1
* Hadrian Zbarcea : +1
* Ross Gardler: +1

Community voting record:
Andreas Kuckartz:  +1

*Denotes an IPMC member vote cast on the rave-dev list

>-Original Message-
>From: Franklin, Matthew B.
>Sent: Monday, January 23, 2012 10:18 AM
>To: general@incubator.apache.org
>Subject: [VOTE] Release Apache Rave 0.7-incubating
>
>This is the sixth incubator release for Apache Rave, with the artifacts being
>versioned as 0.7-incubating.
>
>We are requesting a lazy consensus vote, as we have already received 3
>binding IPMC +1 votes during the release voting on rave-dev -
>
>VOTE:  http://s.apache.org/xqH
>RESULT:  http://s.apache.org/rg
>
>Release notes:
>http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-
>incubating/CHANGELOG
>
>SVN source tag (r1227377):
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapacherave-015/
>
>Source release:
>https://repository.apache.org/content/repositories/orgapacherave-
>015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7-
>incubating-source-release.zip
>
>Binary releases
>http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-
>0.7-incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-
>0.7-incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Lazy consensus, vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)

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

RE: [DISCUSSION] Regular rotation PMC chair

[Franklin, Matthew B.]

>-Original Message-
>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>Sent: Monday, January 30, 2012 7:30 AM
>To: general@incubator.apache.org
>Subject: Re: [DISCUSSION] Regular rotation PMC chair
>
>On Mon, Jan 30, 2012 at 11:46 AM, Ate Douma  wrote:
>> ...I just realize something not clear from this proposal: are we *only* 
>> talking
>> about the Incubator PMC Chair here, or is this a proposal for every PMC
>> Chair?
>> I presumed (and propose) the latter, but maybe that wasn't the intend
>(yet)...
>
>We're talking only about the Incubator PMC chair, no need to
>generalize this IMO and this list wouldn't be the right place anyway.

I can understand why you wouldn't want to generalize this to existing PMCs; 
but, IMO there is value in graduating podlings following this example.  If the 
IPMC institutes this policy & I think it should recommend the model to the 
podlings undergoing the transition to TLP PMC.  
>
>-Bertrand
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org

RE: [DISCUSSION] Regular rotation PMC chair

[Franklin, Matthew B.]

>-Original Message-
>From: Ross Gardler [mailto:rgard...@opendirective.com]
>Sent: Monday, January 30, 2012 8:21 AM
>To: general@incubator.apache.org
>Subject: Re: [DISCUSSION] Regular rotation PMC chair
>
>On 30 January 2012 13:00, Franklin, Matthew B.  wrote:
>>>-Original Message-
>>>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>>>Sent: Monday, January 30, 2012 7:30 AM
>>>To: general@incubator.apache.org
>>>Subject: Re: [DISCUSSION] Regular rotation PMC chair
>>>
>>>On Mon, Jan 30, 2012 at 11:46 AM, Ate Douma  wrote:
>>>> ...I just realize something not clear from this proposal: are we *only*
>talking
>>>> about the Incubator PMC Chair here, or is this a proposal for every PMC
>>>> Chair?
>>>> I presumed (and propose) the latter, but maybe that wasn't the intend
>>>(yet)...
>>>
>>>We're talking only about the Incubator PMC chair, no need to
>>>generalize this IMO and this list wouldn't be the right place anyway.
>>
>> I can understand why you wouldn't want to generalize this to existing
>> PMCs; but, IMO there is value in graduating podlings following this example.
>> If the IPMC institutes this policy & I think it should recommend the model
>> to the podlings undergoing the transition to TLP PMC.
>
>We try to avoid "one-size-fits-all" policies in the ASF, usually for
>good reason. The IPMC is a special case and, speaking personally, I
>don't want to set precedents for podlings based on that special case.
>It really needs to be up to individual communities, with the guidance
>of their mentors, to decide on their chair appointment policy.

I agree that it shouldn't be a requirement, which is why I was thinking 
recommendation; but, I see your point that the new PMCs need to be 
self-determining.  I was looking more for exposure to the concept for the new 
PMCs; which, as you noted, is something that the mentors can work to provide.

>
>Ross
>
>-
>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: Evolution instead of a revolution (Was: Time to vote the chair?)

[Franklin, Matthew B.]

>-Original Message-
>From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
>Sent: Friday, February 03, 2012 12:27 PM
>To: general@incubator.apache.org
>Subject: Evolution instead of a revolution (Was: Time to vote the chair?)
>
>Hi,
>
>[Forking a new thread thread to make this easier to track.]
>
>On Fri, Feb 3, 2012 at 5:22 PM, Mattmann, Chris A (388J)
> wrote:
>> http://wiki.apache.org/incubator/IncubatorDeconstructionProposal
>
>As already mentioned by others, instead of deconstructing everything
>in one go, wouldn't it make more sense to gradually shift into a new
>way of doing things?

+1

>
>You're proposing that podlings should start as full TLPs (with ASF
>members on board for mentoring) right from the beginning. Instead of
>changing the rules on all podlings at the same time, how about we try
>this out by giving interested podlings (or new proposals) this "direct
>to TLP" option?
>
>If that works out better than the current Incubator model, we can stop
>accepting more old-style podlings and just direct them into TLPs right
>from the beginning. Meanwhile any existing podlings should have a
>chance to graduate under the existing rules unless they rather choose
>to use this "direct to TLP" option.
>
>If as a result there's no more podlings in the Incubator, that's IMHO
>then the right time to shut down the IPMC, not before. And if it turns
>out that the proposed new model doesn't work as expected, we still
>have the current processes and structures to fall back to.
>
>The current Incubator model certainly has flaws, but it also does a
>lot of things right. There are good reasons for things like the extra
>publicity and release constraints placed on podlings, and the proposed
>model doesn't address how such restrictions would still work without
>the incubator. I note that many of the original constraints of the
>Incubator (no releases, etc.) turned out to be unnecessarily strict in
>practice, so it could well be that everything will work out smoothly
>also without the extra red tape. But small, reversible steps into such
>unknown territory are clearly preferable to major leaps of faith.
>

In my year working in an incubator podling, I have come to see that there are a 
lot of very valuable aspects to the organization; some IMO critical to the 
success and growth of Apache as a whole.  IMHO, any changes made must be 
cognizant of all aspects of the incubator and not be a reaction to specific 
pain points.  That isn't to say that new things shouldn't be tried and new 
direction isn't important.  Likewise, these revolution style proposals 
themselves hold value as they explore out-of-the-box approaches that can be 
incorporated into an evolutionary roadmap or maybe even adopted wholesale if 
the entire community agrees on the approach.  

>From what I can tell from the 4+ threads, thousands of written words and 
>multitudes of opinions there is a need to address some issues that haven't 
>scaled with the incubator.  I think Leo in a different thread attempted to 
>catalog some invariants and desires that highlight these points.  I personally 
>favor the evolutionary approach Jukka is suggesting; but I am having a hard 
>time keeping up with where, how and when to participate in these discussions.

So that everyone affected by these proposals has the opportunity to engage in 
the discussion, I recommend that we pull these out of e-mail for a while and 
ask everyone who has a new "plan" for the incubator to draft proposals on the 
wiki as Chris did.  At that point, we could have a bake-off discussion where 
the community has the ability to evaluate and chime in with their 
concerns/comments/suggestions.

Thoughts?

>BR,
>
>Jukka Zitting
>
>-
>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: Evolution instead of a revolution (Was: Time to vote the chair?)

[Franklin, Matthew B.]

>-Original Message-
>From: Greg Stein [mailto:gst...@gmail.com]
>Sent: Friday, February 03, 2012 2:13 PM
>To: general@incubator.apache.org
>Subject: Re: Evolution instead of a revolution (Was: Time to vote the chair?)
>
>On Fri, Feb 3, 2012 at 14:04, William A. Rowe Jr. 
>wrote:
>> On 2/3/2012 12:51 PM, Franklin, Matthew B. wrote:
>>>
>>> So that everyone affected by these proposals has the opportunity to
>engage in the discussion, I recommend that we pull these out of e-mail for a
>while and ask everyone who has a new "plan" for the incubator to draft
>proposals on the wiki as Chris did.  At that point, we could have a bake-off
>discussion where the community has the ability to evaluate and chime in with
>their concerns/comments/suggestions.
>>
>> Funny you mention it, the Incubator itself was the product of a bake off
>> between two proposed resolutions, still recorded in the board minutes :)
>
>http://www.apache.org/foundation/records/minutes/2002/board_minutes_
>2002_10_16.txt

Interesting.  What are your thoughts on using this approach for our current 
discussion?  

As I said, staying abreast of all the threads where these discussions are 
occurring is difficult
at best and I feel like some are treating certain ideas as foregone conclusions 
because the 
entire community hasn't been given the time and opportunity to engage without 
joining  
the melee.  In the end, I imagine we will end up compromising, but I think it 
is important  
to take a step back and let others propose a few strategies without it adding 
to the current frenzy.  

>
>-
>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: Evolution instead of a revolution (Was: Time to vote the chair?)

[Franklin, Matthew B.]

On 2/3/12 9:28 PM, "Mattmann, Chris A (388J)"
 wrote:

>On Feb 3, 2012, at 6:11 PM, Ralph Goers wrote:
>
>> 
>> On Feb 3, 2012, at 6:05 PM, William A. Rowe Jr. wrote:
>> 
>>> On 2/3/2012 7:40 PM, Ralph Goers wrote:
 
> My interest goes beyond any of those topics, though.  Incubator is
>very
> tedious.  Very little is resolved.  Deck chairs are shuffled.  But at
> the end of the day, projects don't have ownership of their code, many
> micro-managers do, we aren't necessarily creating better projects
>than
> Chris's proposed structure, and the entire process and participation
>is
> simply not enjoyable (except to the sadists or masochists).
 
 As Ross said, while the proposal gets rid of the tediousness it also
removes much of the oversight and practically all of the help and
support.  
>>> 
>>> One of my problems is that most of the biggest fans of micromanagement
>>> and endless debate here at incubator spend nearly no time looking over
>>> the graduated projects throughout the foundation to ensure they are
>>> being overseen.  If that doesn't happen, the ASF will suffer the death
>>> of 1000 fractures.
>>> 
>>> This proposal suggests that every project throughout the ASF needs the
>>> support of the ASF's members, that incubating projects simply need to
>>> pay extra attentions to each and every one of those requirements at
>>> first, in order to prove they are likely to succeed.  Then they can
>>> move on to operating as a full TLP, going back to the very same
>>>resources
>>> they enjoyed during their incubation during the rough patches.
>> 
>> Your statement above could just as easily be applied to having each
>>podling be a subproject of the IPMC (as it is today), but be given the
>>authority and responsibility they are missing today. You don't need to
>>blow away the IPMC to fix this problem.
>
>So, let me get this straight.
>
>"Make incoming projects have the authority and responsibility that they
>are missing today?"
>
>Sounds a ton like my existing proposal. With some kitchen sink (the IPMC)
>added in.
>
>If incoming projects have the authority and responsibility that they lack
>have today, there is
>no IPMC.

Personally, I feel that walking in the door as a full PMC with authority
could be just as problematic in the long run as not granting it once the
community has demonstrated viability.  Having watched the Rave community
(and myself) grow into the Apache way under the incubator, I can tell you
that we needed time to figure out who we as a community were before we
were ready to have any authority.  I will also say that we wouldn't have
been able to grow as quickly if there wasn't something like this community
to watch and engage with as needed.  If every project came as essentially
a TLP, we lose some of the teaching advantages that the incubator
currently offers.  

I do agree with some of your concerns and feel that we moved through this
early phase quickly and were ready to assume some authority; but, I can't
say that we were ready day 0.  I think your proposal perfectly targets
communities that have demonstrated that they are engaging in the Apache
Way; but, if you assume that, then what we need is a restructuring of the
incubator, not a dismantling of it.

In the end, I think you can meet your goals and maybe even reach some
approximation of for proposal, so long as you don't forget the valuable
parts of the incubator while planning the future.


>
>Cheers,
>Chris
>
>++
>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: Evolution instead of a revolution (Was: Time to vote the chair?)

[Franklin, Matthew B.]

On 2/4/12 12:28 AM, "William A. Rowe Jr."  wrote:

>On 2/3/2012 9:01 PM, Franklin, Matthew B. wrote:
>> 
>> Personally, I feel that walking in the door as a full PMC with authority
>> could be just as problematic in the long run as not granting it once the
>> community has demonstrated viability.
>
>I think that everyone here agrees.  These would not be 'full PMC's... the
>ASF has a general 'set your own policies, hands off until it's broke'
>policy
>towards projects.
>
>Nobody is suggesting that an incoming 'project under incubation' would be
>free of such rules, policies or oversight.  Where usual TLP's are free to
>set the most flexible policies that suit their participants, any project
>under incubation has a more stringent set of ComDev defined 'best
>practices'
>that they must and will follow.  If as a full TLP they decide a tweak here
>or there help their community, it's up to the board to permit that.  And
>generally, the board is flexibly permissive.
>
>But with one Champion not of the project itself, but of the ASF, and
>several
>additional mentors/overseers/ombudsmen, no incubating effort is going to
>enjoy the free reign that TLP's have.  If only all projects had that sort
>of supervision, the foundation would be quite secure in knowing that all
>projects are running as non-factional, non-partisan and non-commercial
>efforts to create software for the public good.

I think the disconnect I was trying to point out is that the proposal
itself assumes that the new PMC is fully functional so long as at least 3
ASF members are a part of it and the PMC chair is the champion.  Taking
Rave as an example, we walked in the door with ~20 non-ASF member PPMC
members.  Not that it would have happened in our instance, but I can
envision a case where a project enters the ASF and isn't forced to
understand how things are done here (bad releases, policies, etc).  At
that point, the board is forced to step in and rectify the situation, when
the same outcome could have been avoided by gradually stepping the
community up in authority.

I have no real opinion as to whether the IPMC stays, or changes structure,
or any of the other possibilities discussed; but, I do think there is an
important oversight mechanism that can't be lost.  If you were to tell me
that the incoming PMC would ONLY be comprised of ASF members, and new
community members are voted in as they demonstrate an understanding of the
Apache Way, then that is a different story.  However, that is not what the
proposal in the wiki states.  Also, if that were to be the case, what
happens when the "mentors" aren't available for release voting (A case
that has happened to us 3 times even with 5 ASF member mentors)?

Again, I am not saying change isn't important or needed, just that we need
to take a breath and look at what we are trying to solve and why.  To that
end, I intend on putting together a counter proposal and posting it to the
wiki that addresses some of the concerns I (and others) have voiced.

>
>Good concerns to raise, but i think they are unfounded in light of the
>current proposal[s].
>
>Bill


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

Re: TL;DR

[Franklin, Matthew B.]

On 2/4/12 1:11 AM, "Scott Wilson"  wrote:

>On 3 Feb 2012, at 23:17, Benson Margulies wrote:
>
>> A number of people are asking for the incubator PMC to take a deep
>> breath and allow room to digest and contemplate the various issues
>> that have led to a bumper crop of email. These are complex questions,
>> and even if we could avoid intemperate exchanges, there is still going
>> to be a lot to read and think about.
>
>+1
>
>I'm a committer on 3 incubator projects, so I have quite a lot of
>ASF-related email already. I don't understand most of the points being
>discussed on the general list as I don't really have time to read and
>make sense of it all

>
>The incubator doesn't feel particularly broken and in need of fixing at
>my level of engagement, so most of the tone of the conversation does
>little other than give me a nagging worry that I'm missing something
>important that might affect the projects I work on.
>
>I expect many more on this list will just filter these discussions out
>and trust everyone concerned to do whats sensible.
>
>So, slow down please, there's no need to rush.

+1 I think quite a few people have suggested we slow down.  This is an
important step that needs to be thought out fully.

>
>> 
>> One way to make the load lighter is to try to make one decision at a
>> time. Entirely selfishly, I suggest looking at the chair election
>> first.
>
>+1
>
>
>> 
>> -
>> 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: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair)

[Franklin, Matthew B.]

+1 

>-Original Message-
>From: Mattmann, Chris A (388J) [mailto:chris.a.mattm...@jpl.nasa.gov]
>Sent: Thursday, February 09, 2012 10:16 AM
>To: general@incubator.apache.org
>Subject: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for
>Incubator PMC Chair)
>
>Hi Folks,
>
>OK there has been enough discussion here. It's time to VOTE for a new IPMC
>chair and it looks like the remaining folks (including me) that were in the
>running
>have aligned beyond the following nominee: Jukka Zitting. Suffice to say, he
>was
>*my first choice* :)
>
>In the interest of moving the current discussion matters forward, please VOTE
>on this recommendation to the board by the IPMC. I'll leave the VOTE open
>for at least the next 72 hours:
>
>[ ] +1 Recommend Jukka Zitting for the IPMC chair position.
>[ ] +0 Don't care.
>[ ]  -1 Don't recommend Jukka Zitting for the IPMC chair position because...
>
>Note that only VOTEs from the Incubator PMC members are binding, but
>all are welcome to voice their opinion and it will be recorded in the final
>tallies.
>
>Finally, just to note, these VOTEs on personnel are normally the only
>thing in Apache that is discussed in private (human/social issues), but
>in the interest of openness and transparency that has been demonstrated
>here during these discussions, I will hold this VOTE on the public list.
>
>Thanks!
>
>Cheers,
>Chris
>
>P.S. Here's my +1. Thanks buddy.
>
>On Feb 8, 2012, at 3:11 PM, Benson Margulies wrote:
>
>> I am happy to step out of the way for Jukka. He was clever enough to
>> stay out of the email s*** storm, and that alone, in my mind, renders
>> him most qualified.
>>
>> On Wed, Feb 8, 2012 at 6:02 PM, Christian Grobmeier
> wrote:
>>> I already mentioned that I would have nominated you, and so I am
>>> delighted to read your message. It will be very difficult to choose
>>> between all these strong candidates.
>>>
>>> Cheers
>>>
>>> On Wed, Feb 8, 2012 at 11:49 PM, Jukka Zitting 
>wrote:
 Hi,

 After consideration and some convincing (thanks!), I've decided to
 throw also my hat into the ring as a candidate to be the next chairman
 of the IPMC.

 I believe in that role I could be more effective in focusing more of
 our collective attention at where I think it would do most good - at
 the actual podlings we're here to help.

 That said, the current incubation process clearly has problems and I
 very much support efforts to improve the way we work (even if the
 result is to replace the Incubator with something better). However,
 I'd like to leave the leadership on these efforts to others and, as
 mentioned elsewhere, rather try to act as a balancing force that helps
 achieve consensus where possible.

 Should I be elected, I'd resign as the chairman of the Jackrabbit PMC.
 In fact I think it's in any case high time for Jackrabbit to be
 rotating that role.

 Finally, if elected (and assuming the IPMC still exists), I'd serve
 for at most two years before calling for a re-election, or possibly
 much less if I don't find enough free cycles to perform the duty as
 well as it should.

 BR,

 Jukka Zitting

>
>
>+++
>+++
>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

[VOTE] Release Apache Rave 0.8-incubating

[Franklin, Matthew B.]

This is the seventh incubator release for Apache Rave, with the artifacts
being versioned as 0.8-incubating.

We are requesting at least one additional IPMC member vote, as we have
received 2 binding IPMC +1 votes during the release voting on rave-dev -

VOTE: http://s.apache.org/U8G
RESULT: http://s.apache.org/Fcv

IPMC member votes from the rave-dev list:
Ate Douma:   +1
Ross Gardler: +1

Release notes:
http://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/CHANGELO
G

SVN source tag (r1163402):
https://svn.apache.org/repos/asf/incubator/rave/rave-master-pom/tags/0.8-in
cubating/

SVN source tag (r1163411):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/

Maven staging repos:
https://repository.apache.org/content/repositories/orgapacherave-195/

Source releases:
https://repository.apache.org/content/repositories/orgapacherave-195/org/ap
ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-source-rele
ase.zip
https://repository.apache.org/content/repositories/orgapacherave-195/org/ap
ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-source-re
lease.zip

Binary releases
http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-0
.8-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-0
.8-incubating-bin.zip

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)








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

[VOTE] Release Apache Rave 0.8-incubating

[Franklin, Matthew B.]

We still need one more IPMC member vote for the release.  Does anyone have
time to take a look?

Thanks in advance, 
-Matt

On 2/12/12 9:29 PM, "Franklin, Matthew B."  wrote:

>This is the seventh incubator release for Apache Rave, with the artifacts
>being versioned as 0.8-incubating.
>
>We are requesting at least one additional IPMC member vote, as we have
>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>
>VOTE: http://s.apache.org/U8G
>RESULT: http://s.apache.org/Fcv
>
>IPMC member votes from the rave-dev list:
>Ate Douma:   +1
>Ross Gardler: +1
>
>Release notes:
>http://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/CHANGEL
>O
>G
>
>SVN source tag (r1163402):
>https://svn.apache.org/repos/asf/incubator/rave/rave-master-pom/tags/0.8-i
>n
>cubating/
>
>SVN source tag (r1163411):
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/
>
>Maven staging repos:
>https://repository.apache.org/content/repositories/orgapacherave-195/
>
>Source releases:
>https://repository.apache.org/content/repositories/orgapacherave-195/org/a
>p
>ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-source-rel
>e
>ase.zip
>https://repository.apache.org/content/repositories/orgapacherave-195/org/a
>p
>ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-source-r
>e
>lease.zip
>
>Binary releases
>http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-
>0
>.8-incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-
>0
>.8-incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>
>
>
>
>
>
>
>-
>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 Rave 0.8-incubating

[Franklin, Matthew B.]

We only distribute that jar as part of  the binary release and the LICENCE & 
NOTICE files have the appropriate attribution and license.

-Matt

>-Original Message-
>From: Karl Wright [mailto:daddy...@gmail.com]
>Sent: Thursday, February 16, 2012 10:05 AM
>To: general@incubator.apache.org
>Subject: Re: [VOTE] Release Apache Rave 0.8-incubating
>
>What is the license on ecj-3.7.jar (Eclipse JDT Java compiler)?  If
>you are going to redistribute it you should provide that info
>somewhere unless it's Apache licensed.
>
>Thanks,
>Karl
>
>
>On Thu, Feb 16, 2012 at 10:00 AM, Karl Wright  wrote:
>> I'll have a look at it.  Stay tuned...
>> Karl
>>
>> On Thu, Feb 16, 2012 at 9:20 AM, Franklin, Matthew B.
>>  wrote:
>>> We still need one more IPMC member vote for the release.  Does anyone
>have
>>> time to take a look?
>>>
>>> Thanks in advance,
>>> -Matt
>>>
>>> On 2/12/12 9:29 PM, "Franklin, Matthew B."  wrote:
>>>
>>>>This is the seventh incubator release for Apache Rave, with the artifacts
>>>>being versioned as 0.8-incubating.
>>>>
>>>>We are requesting at least one additional IPMC member vote, as we have
>>>>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>>>>
>>>>VOTE: http://s.apache.org/U8G
>>>>RESULT: http://s.apache.org/Fcv
>>>>
>>>>IPMC member votes from the rave-dev list:
>>>>Ate Douma:   +1
>>>>Ross Gardler: +1
>>>>
>>>>Release notes:
>>>>http://svn.apache.org/repos/asf/incubator/rave/tags/0.8-
>incubating/CHANGEL
>>>>O
>>>>G
>>>>
>>>>SVN source tag (r1163402):
>>>>https://svn.apache.org/repos/asf/incubator/rave/rave-master-
>pom/tags/0.8-i
>>>>n
>>>>cubating/
>>>>
>>>>SVN source tag (r1163411):
>>>>https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/
>>>>
>>>>Maven staging repos:
>>>>https://repository.apache.org/content/repositories/orgapacherave-195/
>>>>
>>>>Source releases:
>>>>https://repository.apache.org/content/repositories/orgapacherave-
>195/org/a
>>>>p
>>>>ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-
>source-rel
>>>>e
>>>>ase.zip
>>>>https://repository.apache.org/content/repositories/orgapacherave-
>195/org/a
>>>>p
>>>>ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-
>source-r
>>>>e
>>>>lease.zip
>>>>
>>>>Binary releases
>>>>http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-
>rave-
>>>>0
>>>>.8-incubating-bin.tar.gz
>>>>http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-
>rave-
>>>>0
>>>>.8-incubating-bin.zip
>>>>
>>>>PGP release keys:
>>>>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>>>
>>>>Vote open for 72 hours.
>>>>
>>>>[ ] +1  approve
>>>>[ ] +0  no opinion
>>>>[ ] -1  disapprove (and reason why)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>-
>>>>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: [VOTE] Release Apache Rave 0.8-incubating

[Franklin, Matthew B.]

>-Original Message-
>From: Karl Wright [mailto:daddy...@gmail.com]
>Sent: Thursday, February 16, 2012 10:32 AM
>To: general@incubator.apache.org
>Subject: Re: [VOTE] Release Apache Rave 0.8-incubating
>
>Thanks - I did not realize that the source LICENSE and the binary
>LICENSE were different. ;-)
>
>+1 from me (binding)

Thanks Karl!

>Karl
>
>
>On Thu, Feb 16, 2012 at 10:17 AM, Ate Douma  wrote:
>> On 02/16/2012 04:05 PM, Karl Wright wrote:
>>>
>>> What is the license on ecj-3.7.jar (Eclipse JDT Java compiler)?  If
>>> you are going to redistribute it you should provide that info
>>> somewhere unless it's Apache licensed.
>>
>>
>> The ecj is EPL 1.0 license, and explicitly mentioned and covered in the root
>> LICENSE file of the binary distribution.
>>
>>
>>>
>>> Thanks,
>>> Karl
>>>
>>>
>>> On Thu, Feb 16, 2012 at 10:00 AM, Karl
>Wright  wrote:
>>>>
>>>> I'll have a look at it.  Stay tuned...
>>>> Karl
>>>>
>>>> On Thu, Feb 16, 2012 at 9:20 AM, Franklin, Matthew B.
>>>>   wrote:
>>>>>
>>>>> We still need one more IPMC member vote for the release.  Does
>anyone
>>>>> have
>>>>> time to take a look?
>>>>>
>>>>> Thanks in advance,
>>>>> -Matt
>>>>>
>>>>> On 2/12/12 9:29 PM, "Franklin, Matthew
>B."  wrote:
>>>>>
>>>>>> This is the seventh incubator release for Apache Rave, with the
>>>>>> artifacts
>>>>>> being versioned as 0.8-incubating.
>>>>>>
>>>>>> We are requesting at least one additional IPMC member vote, as we
>have
>>>>>> received 2 binding IPMC +1 votes during the release voting on rave-
>dev
>>>>>> -
>>>>>>
>>>>>> VOTE: http://s.apache.org/U8G
>>>>>> RESULT: http://s.apache.org/Fcv
>>>>>>
>>>>>> IPMC member votes from the rave-dev list:
>>>>>> Ate Douma:   +1
>>>>>> Ross Gardler: +1
>>>>>>
>>>>>> Release notes:
>>>>>>
>>>>>> http://svn.apache.org/repos/asf/incubator/rave/tags/0.8-
>incubating/CHANGEL
>>>>>> O
>>>>>> G
>>>>>>
>>>>>> SVN source tag (r1163402):
>>>>>>
>>>>>> https://svn.apache.org/repos/asf/incubator/rave/rave-master-
>pom/tags/0.8-i
>>>>>> n
>>>>>> cubating/
>>>>>>
>>>>>> SVN source tag (r1163411):
>>>>>> https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/
>>>>>>
>>>>>> Maven staging repos:
>>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>195/
>>>>>>
>>>>>> Source releases:
>>>>>>
>>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>195/org/a
>>>>>> p
>>>>>>
>>>>>> ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-
>source-rel
>>>>>> e
>>>>>> ase.zip
>>>>>>
>>>>>> https://repository.apache.org/content/repositories/orgapacherave-
>195/org/a
>>>>>> p
>>>>>>
>>>>>> ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-
>source-r
>>>>>> e
>>>>>> lease.zip
>>>>>>
>>>>>> Binary releases
>>>>>>
>>>>>> http://people.apache.org/builds/incubator/rave/0.8-
>incubating/apache-rave-
>>>>>> 0
>>>>>> .8-incubating-bin.tar.gz
>>>>>>
>>>>>> http://people.apache.org/builds/incubator/rave/0.8-
>incubating/apache-rave-
>>>>>> 0
>>>>>> .8-incubating-bin.zip
>>>>>>
>>>>>> PGP release keys:
>>>>>> https://svn.apache.org/repos/asf/incubator/rave/KEYS
>>>>>>
>>>>>> Vote open for 72 hours.
>>>>>>
>>>>>> [ ] +1  approve
>>>>>> [ ] +0  no opinion
>>>>>> [ ] -1  disapprove (and reason why)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -
>>>>>> 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
>>
>
>-
>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

[RESULT] [VOTE] Release Apache Rave 0.8-incubating

[Franklin, Matthew B.]

The voting period is now closed.  Thanks to everyone who took the time to 
review the release. 

Result Summary for this List:

Binding IPMC Member Votes
+1   [1]
  0[0]
-1[0]

With the vote from this list and the two IPMC member votes from mentors on the 
dev list,  the vote succeeds.

IPMC member voting record:
* Ate Douma:  +1
* Ross Gardler: +1
Karl Wright:  +1

*Denotes an IPMC member vote cast on the rave-dev list

>-Original Message-
>From: Franklin, Matthew B. [mailto:mfrank...@mitre.org]
>Sent: Sunday, February 12, 2012 9:30 PM
>To: general@incubator.apache.org
>Subject: [VOTE] Release Apache Rave 0.8-incubating
>
>This is the seventh incubator release for Apache Rave, with the artifacts
>being versioned as 0.8-incubating.
>
>We are requesting at least one additional IPMC member vote, as we have
>received 2 binding IPMC +1 votes during the release voting on rave-dev -
>
>VOTE: http://s.apache.org/U8G
>RESULT: http://s.apache.org/Fcv
>
>IPMC member votes from the rave-dev list:
>Ate Douma:   +1
>Ross Gardler: +1
>
>Release notes:
>http://svn.apache.org/repos/asf/incubator/rave/tags/0.8-
>incubating/CHANGELO
>G
>
>SVN source tag (r1163402):
>https://svn.apache.org/repos/asf/incubator/rave/rave-master-
>pom/tags/0.8-in
>cubating/
>
>SVN source tag (r1163411):
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/
>
>Maven staging repos:
>https://repository.apache.org/content/repositories/orgapacherave-195/
>
>Source releases:
>https://repository.apache.org/content/repositories/orgapacherave-
>195/org/ap
>ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-source-
>rele
>ase.zip
>https://repository.apache.org/content/repositories/orgapacherave-
>195/org/ap
>ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-source-re
>lease.zip
>
>Binary releases
>http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-
>0
>.8-incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-
>0
>.8-incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>
>
>
>
>
>
>
>-
>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 Hama 0.4-incubating RC6

[Franklin, Matthew B.]

-1 at the moment due to source distribution and license concerns noted
below.

On 2/20/12 8:54 AM, "Edward J. Yoon"  wrote:

>Hi,
>
>I've create RC6 for the Apache Hama 0.4-incubating release. This fixes
>the license header issue and adds rat-plugin.
>
>Signing KEYS: 
>http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/fi
>les/KEYS
>Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/

Do you have a source artifact that is a simple archive of the SVN?

Also, you can stage your artifacts at
http://people.apache.org/builds/incubator/ rather than your own public
html folder, but this is not required.

>Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/
>NOTICE.txt: 
>http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.txt
>LICENSE.txt: 
>http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt

The LICENSE file in the binary distribution needs to include 3rd party
licenses included in the libs that are being re-distributed as part of
your release.  Your binary release artifacts include ant 1.7 (and
potentially others) that has source covered by 3rd party licenses which I
don't see in your LICENSE file.

>Staging website: http://people.apache.org/~edwardyoon/site/
>
>You can run the "mvn apache-rat:check" command to check for license
>headers.
>
>I tested this RC6 builds, single mode, and distributed mode on my 16
>nodes cluster and 5 VMs with EC2.
>
>Please retry, check signatures, licenses, and vote!
>
>I hope this will be a final, and +1.
>
>Thanks.
>-- 
>Best Regards, Edward J. Yoon
>@eddieyoon
>
>-
>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 Hama 0.4-incubating RC6

[Franklin, Matthew B.]

For the packaging, a clean source package and a separate binary release is
preferred [1].  This isn't the blocker in my opinion, but something that
you should look at.

[1]: 
http://incubator.apache.org/guides/releasemanagement.html#best-practice-typ
es

On 2/25/12 2:52 AM, "Edward J. Yoon"  wrote:

>>> The LICENSE file in the binary distribution needs to include 3rd party
>>> licenses included in the libs that are being re-distributed as part of
>>> your release.  Your binary release artifacts include ant 1.7 (and
>>> potentially others) that has source covered by 3rd party licenses
>>>which I
>>> don't see in your LICENSE file.
>
>The ant is released under the Apache Software License and LICENSE.txt
>file contains the Apache license v2.0.
>
>http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt
>
>I don't see any missed 3rd party licenses. Could you please check it
>again?


Ant itself includes code under a separate license.  Since your binary
release includes the Ant jar, you are redistributing that code and need to
include its license.

http://svn.apache.org/repos/asf/ant/core/tags/ANT_171/LICENSE



>
>And, the distributions contains both source code and compiled jar files.
>
>> Anyways, if we have to go to a RC7, let's merge the new jiras from
>>trunk to
>> 0.4.0, compression and stuff can be great improvement.
>
>I don't think we have to create new one. Moreover, new stuffs are not
>tested enough yet.
>
>On Sat, Feb 25, 2012 at 3:44 PM, Thomas Jungblut
> wrote:
>> Hmm- I always thought it is Apache Ant and therefore Apache 2.0
>>license. If
>> we have to add all transitive licenses we are going to release until the
>> overnext year.
>> What is wrong packaging the source within a binary distribution?
>>
>> Anyways, if we have to go to a RC7, let's merge the new jiras from
>>trunk to
>> 0.4.0, compression and stuff can be great improvement.
>>
>> 2012/2/25 Franklin, Matthew B. 
>>
>>> -1 at the moment due to source distribution and license concerns noted
>>> below.
>>>
>>> On 2/20/12 8:54 AM, "Edward J. Yoon"  wrote:
>>>
>>> >Hi,
>>> >
>>> >I've create RC6 for the Apache Hama 0.4-incubating release. This fixes
>>> >the license header issue and adds rat-plugin.
>>> >
>>> >Signing KEYS:
>>> >
>>> 
>>>http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/
>>>fi
>>> >les/KEYS
>>> >Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/
>>>
>>> Do you have a source artifact that is a simple archive of the SVN?
>>>
>>> Also, you can stage your artifacts at
>>> http://people.apache.org/builds/incubator/ rather than your own public
>>> html folder, but this is not required.
>>>
>>> >Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/
>>> >NOTICE.txt:
>>> >http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.txt
>>> >LICENSE.txt:
>>> 
>>>>http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt
>>>
>>> The LICENSE file in the binary distribution needs to include 3rd party
>>> licenses included in the libs that are being re-distributed as part of
>>> your release.  Your binary release artifacts include ant 1.7 (and
>>> potentially others) that has source covered by 3rd party licenses
>>>which I
>>> don't see in your LICENSE file.
>>>
>>> >Staging website: http://people.apache.org/~edwardyoon/site/
>>> >
>>> >You can run the "mvn apache-rat:check" command to check for license
>>> >headers.
>>> >
>>> >I tested this RC6 builds, single mode, and distributed mode on my 16
>>> >nodes cluster and 5 VMs with EC2.
>>> >
>>> >Please retry, check signatures, licenses, and vote!
>>> >
>>> >I hope this will be a final, and +1.
>>> >
>>> >Thanks.
>>> >--
>>> >Best Regards, Edward J. Yoon
>>> >@eddieyoon
>>> >
>>> >-
>>> >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> >For additional commands, e-mail: general-h...@incubator.apache.org
>>> >
>>>
>>>
>>
>>
>> --
>> Thomas Jungblut
>> Berlin 
>
>
>
>-- 
>Best Regards, Edward J. Yoon
>@eddieyoon
>
>-
>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 Hama 0.4-incubating RC6

[Franklin, Matthew B.]

On 2/25/12 8:12 PM, "Edward J. Yoon"  wrote:

>Thanks. Actually we're trying to separate them but there's some issues
>related with packaging web resources e.g.,
>https://issues.apache.org/jira/browse/HAMA-494
>
>If it's not a blocker, I'd like to fix this issue in the next release.

As I understand it the only requirement is that you have a source release;
which your combined one does.  As I said it isn't optimal.

The blocker as I see it is that the LICENSE file is incomplete as I
mentioned earlier.

>
>On Sat, Feb 25, 2012 at 9:22 PM, Franklin, Matthew B.
> wrote:
>> For the packaging, a clean source package and a separate binary release
>>is
>> preferred [1].  This isn't the blocker in my opinion, but something that
>> you should look at.
>>
>> [1]:
>> 
>>http://incubator.apache.org/guides/releasemanagement.html#best-practice-t
>>yp
>> es
>>
>> On 2/25/12 2:52 AM, "Edward J. Yoon"  wrote:
>>
>>>>> The LICENSE file in the binary distribution needs to include 3rd
>>>>>party
>>>>> licenses included in the libs that are being re-distributed as part
>>>>>of
>>>>> your release.  Your binary release artifacts include ant 1.7 (and
>>>>> potentially others) that has source covered by 3rd party licenses
>>>>>which I
>>>>> don't see in your LICENSE file.
>>>
>>>The ant is released under the Apache Software License and LICENSE.txt
>>>file contains the Apache license v2.0.
>>>
>>>http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt
>>>
>>>I don't see any missed 3rd party licenses. Could you please check it
>>>again?
>>
>>
>> Ant itself includes code under a separate license.  Since your binary
>> release includes the Ant jar, you are redistributing that code and need
>>to
>> include its license.
>>
>> http://svn.apache.org/repos/asf/ant/core/tags/ANT_171/LICENSE
>>
>>
>>
>>>
>>>And, the distributions contains both source code and compiled jar files.
>>>
>>>> Anyways, if we have to go to a RC7, let's merge the new jiras from
>>>>trunk to
>>>> 0.4.0, compression and stuff can be great improvement.
>>>
>>>I don't think we have to create new one. Moreover, new stuffs are not
>>>tested enough yet.
>>>
>>>On Sat, Feb 25, 2012 at 3:44 PM, Thomas Jungblut
>>> wrote:
>>>> Hmm- I always thought it is Apache Ant and therefore Apache 2.0
>>>>license. If
>>>> we have to add all transitive licenses we are going to release until
>>>>the
>>>> overnext year.
>>>> What is wrong packaging the source within a binary distribution?
>>>>
>>>> Anyways, if we have to go to a RC7, let's merge the new jiras from
>>>>trunk to
>>>> 0.4.0, compression and stuff can be great improvement.
>>>>
>>>> 2012/2/25 Franklin, Matthew B. 
>>>>
>>>>> -1 at the moment due to source distribution and license concerns
>>>>>noted
>>>>> below.
>>>>>
>>>>> On 2/20/12 8:54 AM, "Edward J. Yoon"  wrote:
>>>>>
>>>>> >Hi,
>>>>> >
>>>>> >I've create RC6 for the Apache Hama 0.4-incubating release. This
>>>>>fixes
>>>>> >the license header issue and adds rat-plugin.
>>>>> >
>>>>> >Signing KEYS:
>>>>> >
>>>>>
>>>>>http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resource
>>>>>s/
>>>>>fi
>>>>> >les/KEYS
>>>>> >Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/
>>>>>
>>>>> Do you have a source artifact that is a simple archive of the SVN?
>>>>>
>>>>> Also, you can stage your artifacts at
>>>>> http://people.apache.org/builds/incubator/ rather than your own
>>>>>public
>>>>> html folder, but this is not required.
>>>>>
>>>>> >Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/
>>>>> >NOTICE.txt:
>>>>> 
>>>>>>http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.tx
>>>>>>t
>>>>> >LICENSE.txt:
>>>>>
>>>>>>http://svn.

RE: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project

[Franklin, Matthew B.]

+1 

>-Original Message-
>From: Robert Burrell Donkin [mailto:rdon...@apache.org]
>Sent: Sunday, February 26, 2012 11:03 AM
>To: rat-...@incubator.apache.org
>Cc: general@incubator.apache.org
>Subject: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
>
>The graduation guide[1] recommends that the Rat community demonstrates
>it's willingness to govern itself through a free VOTE before asking the
>IPMC to approve graduation. So, here it is :-)
>
>See [2] for a draft of the charter, excluding the list of initial
>committers. Unless anyone jumps into this thread, I'll assume that the
>current list of committers would be fine. Please read, review and jump
>in - but this is a vote on the principle of graduating now.
>
>This VOTE is open to all, and I'll tally this no early than Wednesday,
>29 Feb 2012 17:00 UTC.
>
>Robert
>
>--8<---
>[ ] +1 the RAT community feels ready to graduate as Apache Creadur
>[ ] +0
>[ ] -0
>[ ] -1 Do not graduate RAT at this time
>---
>
>
>[1] http://incubator.apache.org/guides/graduation.html#toplevel
>[2] Suggested Draft Charter:
>
>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 the comprehension and
>auditing of software distributions 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 Creadur Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Creadur Project be and hereby is
>responsible for the creation and maintenance of open-source
>software related to the comprehension and auditing of software
>distributions for distribution at no charge to the public
>
>RESOLVED, that the office of "Vice President, Apache Creadur" 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 Creadur Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Creadur 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 Creadur Project:
>
>...
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell
>Donkin be appointed to the office of Vice President, Apache
>Creadur, 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 Creadur PMC be and hereby is
>tasked with the creation of a set of bylaws intended to
>encourage open development and increased participation in the
>Apache Creadur Project; and be it further
>
>RESOLVED, that the Apache Creadur Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator RAT podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator RAT podling encumbered upon the Apache Incubator
>Project are hereafter discharged.
>
>-
>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

[VOTE] Release Apache Rave 0.9-incubating

[Franklin, Matthew B.]

This is the eighth incubator release for Apache Rave, with the artifacts
being versioned as 0.9-incubating.

We are requesting a lazy consensus vote, as we have already received 3
binding IPMC +1 votes during the release voting on rave-dev -

VOTE:   http://markmail.org/message/3ipmolpl66j3dc34
RESULT: http://markmail.org/message/7udo2duh75gjylle

Release notes:
http://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/CHANGELO
G

SVN source tag (r1296695):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapacherave-049/


Source release: 
https://repository.apache.org/content/repositories/orgapacherave-049/org/ap
ache/rave/rave-project/0.9-incubating/rave-project-0.9-incubating-source-re
lease.zip

Binary releases
http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave-0
.9-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave-0
.9-incubating-bin.zip

PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Lazy consensus, vote open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)




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

[RESULT] [VOTE] Release Apache Rave 0.9-incubating

[Franklin, Matthew B.]

The voting period is now closed.

Result Summary for this List:

Binding IPMC Member Votes
+1   [0]
  0  [0]
-1[0]

With the three IPMC member votes on the dev list,  the vote succeeds.

IPMC member voting record:
* Ate Douma: +1
* Matt Franklin: +1
* Ross Gardler:  +1

*Denotes an IPMC member vote cast on the rave-dev list



On 3/10/12 7:49 PM, "Franklin, Matthew B."  wrote:

>This is the eighth incubator release for Apache Rave, with the artifacts
>being versioned as 0.9-incubating.
>
>We are requesting a lazy consensus vote, as we have already received 3
>binding IPMC +1 votes during the release voting on rave-dev -
>
>VOTE:   http://markmail.org/message/3ipmolpl66j3dc34
>RESULT: http://markmail.org/message/7udo2duh75gjylle
>
>Release notes:
>http://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/CHANGEL
>O
>G
>
>SVN source tag (r1296695):
>https://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapacherave-049/
>
>
>Source release: 
>https://repository.apache.org/content/repositories/orgapacherave-049/org/a
>p
>ache/rave/rave-project/0.9-incubating/rave-project-0.9-incubating-source-r
>e
>lease.zip
>
>Binary releases
>http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave-
>0
>.9-incubating-bin.tar.gz
>http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave-
>0
>.9-incubating-bin.zip
>
>PGP release keys:
>https://svn.apache.org/repos/asf/incubator/rave/KEYS
>
>Lazy consensus, vote open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>
>
>
>-
>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][IPMC] Graduate RAT as Apache Creadur Project

[Franklin, Matthew B.]

+1 (binding)

>-Original Message-
>From: Robert Burrell Donkin [mailto:rdon...@apache.org]
>Sent: Sunday, March 11, 2012 3:42 PM
>To: general@incubator.apache.org
>Cc: rat-...@incubator.apache.org
>Subject: [VOTE][IPMC] Graduate RAT as Apache Creadur Project
>
>As recommended[1]:
>
>  * the Rat community has indicated that its readiness[2] to graduate as
>the Apache Creadur Project
>  * the proposed charter has been reviewed[3]
>
>The penultimate stage is this VOTE by the incubator community. The VOTE
>is open to all but only IPMC votes are binding.
>
>I will tally the results no earlier than noon UTC on Thursday, March 22,
>2012[4].
>
>Robert
>
>[1] http://incubator.apache.org/guides/graduation.html#toplevel
>[2]
>http://mail-archives.apache.org/mod_mbox/incubator-
>general/201203.mbox/%3C4F53968D.7070908%40apache.org%3E
>[3]
>http://mail-archives.apache.org/mod_mbox/incubator-
>general/201203.mbox/%3C4F53B9FB.4030404%40apache.org%3E
>[4]
>http://www.worldtimeserver.com/convert_time_in_UTC.aspx?y=2012&mo=
>3&d=22&h=12&mn=0
>
>-8<---
>[ ] +1 Recommend The Apache Creadur Proposal To The Board (below)
>[ ] +0
>[ ] -0
>[ ] -1 Do not graduate Rat podling
>--
>
>-8<--
>
>  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 the comprehension and
>  auditing of software distributions 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 Creadur Project",
>  be and hereby is established pursuant to Bylaws of the
>  Foundation; and be it further
>
>  RESOLVED, that the Apache Creadur Project be and hereby is
>  responsible for the creation and maintenance of open-source
>  software related to the comprehension and auditing of software
>  distributions; and be it further
>
>  RESOLVED, that the office of "Vice President, Apache Creadur" 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 Creadur Project, and to have primary responsibility
>  for management of the projects within the scope of
>  responsibility of the Apache Creadur 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 Creadur Project:
>
>   * Stefan Bodewig 
>   * Brian E Fox 
>   * David Crossley 
>   * David Blevins 
>   * Dennis Lundberg 
>   * Gavin McDonald 
>   * Jochen Wiedmann 
>   * Niall Pemberton 
>   * Robert Burrell Donkin 
>   * Ross Duncan Gardler 
>   * Sebastian Bazley 
>
>  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell
>  Donkin be appointed to the office of Vice President, Apache
>  Creadur, 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 Creadur PMC be and hereby is
>  tasked with the creation of a set of bylaws intended to
>  encourage open development and increased participation in the
>  Apache Creadur Project; and be it further
>
>  RESOLVED, that the Apache Creadur Project be and hereby
>  is tasked with the migration and rationalization of the Apache
>  Incubator RAT podling; and be it further
>
>  RESOLVED, that all responsibilities pertaining to the Apache
>  Incubator RAT podling encumbered upon the Apache Incubator
>  Project are hereafter discharged.
>
>-
>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: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project

[Franklin, Matthew B.]

+1.  Congrats

>-Original Message-
>From: Andy Seaborne [mailto:andy.seaborne.apa...@gmail.com] On Behalf
>Of Andy Seaborne
>Sent: Monday, April 02, 2012 5:11 AM
>To: general@incubator.apache.org
>Subject: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project
>
>This is a call for vote to graduate the Apache Jena podling from Apache
>Incubator to be a top level project.
>
>Jena entered incubation in November 2010.  The project has added two new
>committers and PPMC members, made several releases and has a diverse
>committer base.  The user and development communities are active.  The
>PPMC has indicated [1,2,3] that it believes the project is ready to
>graduate as a top-level project with the resolution draft below.
>
>We ask that the IPMC approve this graduation request though this VOTE.
>
>[1] Vote:   http://s.apache.org/jena-graduation-vote
>[2] Result: http://s.apache.org/jena-graduation
>[3] Request for comments:
>http://mail-archives.apache.org/mod_mbox/incubator-
>general/201203.mbox/%3C5C4A33CB-B122-43A8-B082-
>CBD63B526DE7%40cray.com%3E
>
>On behalf of the Apache Jena PPMC,
>
>   Andy
>
>-
>
>[ ] +1 Recommend to the ASF Board that Apache Jena Proposal
>is ready to graduate to being a top level project.
>[ ] 0
>[ ] -1 Do not graduate Apache Jena because ...
>
>The vote will be tallied no earlier than:
>
>Thursday April 5th, at 23:59 UTC.
>
>-
>
>X. Establish the Apache Jena Project
>
>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 accessing, storing, querying,
>publishing and reasoning with semantic web data while
>adhering to relevant W3C and community standards.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Jena Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Jena Project be and hereby is
>responsible for the creation and maintenance of software
>related to accessing, storing, querying,
>publishing and reasoning with semantic web data while
>adhering to relevant W3C and community standards;
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache Jena" 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 Jena Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Jena 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 Jena Project:
>
>  * Andy Seaborne  (andy)
>  * Benson Marguilies  (bimargulies)
>  * Chris Dollin   (chrisdollin)
>  * Damian Steer   (damian)
>  * Dave Reynolds  (der)
>  * Ian Dickinson  (ijd)
>  * Paolo Castagna (castagna)
>  * Rob Vesse  (rvesse)
>  * Stephen Allen  (sallen)
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andy Seaborne
>be appointed to the office of Vice President, Apache Jena, 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 Jena PMC be and hereby is
>tasked with the creation of a set of bylaws intended to
>encourage open development and increased participation in the
>Apache Jena Project; and be it further
>
>RESOLVED, that the Apache Jena Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Jena podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Jena podling encumbered upon the Apache Incubator
>Project are hereafter discharged.
>
>-
>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: Question about downloading binaries

[Franklin, Matthew B.]

>-Original Message-
>From: Karl Wright [mailto:daddy...@gmail.com]
>Sent: Tuesday, April 03, 2012 1:24 PM
>To: general@incubator.apache.org
>Subject: Re: Question about downloading binaries
>
>"Also, making sure the other comments on NOTICEs are addressed as well."
>
>I have gotten extremely confusing advice in this area in the past, and
>the available documentation does not help.  I believe I am adhering to
>Roy's principles, but before we spin another release candidate, I'd
>like it very much if someone with a (hopefully accurate) idea of how
>things are supposed to work reviewed our license and notice files.
>You can find them here:
>
>https://svn.apache.org/repos/asf/incubator/lcf/trunk/LICENSE.txt
>https://svn.apache.org/repos/asf/incubator/lcf/trunk/NOTICE.txt

Just looking quickly, the LICENSE file contains a lot of licenses for the jars 
you were distributing.  For the source release, the ONLY L&N attributions 
needed are the ones for code that you are including in your source. 

If, like many projects, you have no 3rd party source inclusion, the LICENSE 
file should only contain ASL 2.0 and the NOTICE should have the standard 
developed at apache note.

For the binary releases, we have been adding entries for any jars we include, 
as you have done.  There are a couple of tweaks I would suggest, I propose that 
you get an agreeable source L&N first as I think there is (yet again) a wider 
discussion to be had regarding convenience binaries...

>
>Thanks!
>Karl
>
>On Tue, Apr 3, 2012 at 1:11 PM, Matt Hogstrom  wrote:
>>> Hope that helps...  The question is, will Roy (or anyone else) be
>>> unwilling to vote for the first option?
>>
>> Having been one of the people that commented and started the thread, I
>feel like I was wearing loose clothing while operating machinery, per Roy's
>guidance on the source being the thing that is voted on and the other binaries
>are merely convenience items, I would support the first option.  Also, making
>sure the other comments on NOTICEs are addressed as well.
>>
>> Unfortunate that you god dog piled on but hopefully we're all better
>prepared going forward.
>>
>> Matt Hogstrom
>> m...@hogstrom.org
>>
>> A Day Without Nuclear Fusion Is a Day Without Sunshine
>>
>> On Apr 3, 2012, at 11:04 AM, Karl Wright wrote:
>
>-
>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: ERR 0194 ...StreamResult of target/current.ent building incubator.a.o site

[Franklin, Matthew B.]

On 4/9/12 9:38 PM, "David Crossley"  wrote:

>Shane Curcuru wrote:
>> Tips on building the main incubator.a.o site appreciated.
>
>There is some doc at [1] http://incubator.apache.org/guides/website.html
>but since moving to use the Apache Content Management System (CMS)
>that page might need some revision.
>Here is how i do it:
>* Local checkout of the incubator SVN
>https://svn.apache.org/repos/asf/incubator/public/trunk

For the record, you can also use the web UI accessible by clicking "Get
Incubator Working Copy" on https://cms.apache.org/incubator/ or using the
bookmarklet from http://incubator.apache.org/

>* Make source changes in the "content" directory.
>* Do 'svn diff', review, commit those.
>* Wait a bit.
>* Visit https://cms.apache.org/incubator/publish
>* Review the generated diffs, press the button.
>* Wait a bit, then see the published site.
>
>The notes at [1], and some linked notes, do explain how to
>review the CMS generated stuff at a staging site.
>They also show how to build the site locally for review.
>
>-David
>
>>  I'm hoping to 
>> cleanup some links and better describe the PMC things, along with
>> figuring where to include the branding requirements for graduation.
>> 
>> Using two different versions of IBM Java (tried a 1.6 and a 1.7) I get
>> errors trying to process podling.xml:
>> 
>>  [xslt] : Fatal Error! [ERR 0194] The
>> javax.xml.transform.stream.StreamResult associated with the
>> xsl:result-document with href 'target/current.ent' and base output URI
>> 'file:/C:/a/incubator/public/target/index.tmp' has neither its Writer
>> nor its OutputStream set.
>>  [xslt] : Fatal Error! [ERR 0629] A redirect instruction failed to
>> create a file. Cause: [ERR 0629] A redirect instruction failed to
>>create 
>> a file.
>>  [xslt] Failed to process C:\a\incubator\public\content\podlings.xml
>> 
>> Thanks!
>> - Shane
>> 
>> 
>> C:\a\incubator\public>ver
>> 
>> Microsoft Windows [Version 6.1.7601]
>> 
>> C:\a\incubator\public>java -version
>> java version "1.7.0"
>> Java(TM) SE Runtime Environment (build pwa6470-20110906_01)
>> IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 amd64-64 20110810_88604 (JIT
>> enabled,
>> AOT enabled)
>> J9VM - R26_Java726_GA_20110810_1208_B88592
>> JIT  - r11_20110810_20466
>> GC   - R26_Java726_GA_20110810_1208_B88592
>> J9CL - 20110810_88604)
>> JCL - 20110809_01 based on Oracle 7b147
>> 
>> C:\a\incubator\public>build
>> 
>>CLASSPATH=".\lib\werken-xpath-0.9.4.jar;.\lib\velocity-tools-generic-1.4.
>>jar;.\l
>> 
>>ib\velocity-1.6.1.jar;.\lib\texen-1.0.jar;.\lib\oro-2.0.8.jar;.\lib\log4j
>>-1.2.12
>> 
>>.jar;.\lib\jdom-1.0.jar;.\lib\commons-logging-1.1.jar;.\lib\commons-lang-
>>2.4.jar
>> 
>>;.\lib\commons-collections-3.2.1.jar;.\lib\avalon-logkit-2.1.jar;.\lib\an
>>tlr-2.7
>> 
>>.5.jar;.\lib\ant-trax-1.7.1.jar;.\lib\ant-launcher-1.7.1.jar;.\lib\ant-ja
>>vamail-
>> 1.7.1.jar;.\lib\ant-1.7.1.jar;.\lib\anakia-1.0.jar;"
>> Buildfile: build.xml
>> 
>> prepare:
>> 
>> prepare-error:
>> 
>> _prepare-texen:
>> 
>> generate-site-map:
>>[delete] Deleting directory C:\a\incubator\public\target\texen
>> [mkdir] Created dir: C:\a\incubator\public\target\texen
>>  [xslt] Transforming into C:\a\incubator\public\target\texen
>>  [xslt] Processing C:\a\incubator\public\content\clutch.xml to
>> C:\a\incubato
>> r\public\target\texen\clutch.xml
>>  [xslt] Loading stylesheet
>> C:\a\incubator\public\content\stylesheets\sitemap
>> \index.xsl
>>  [xslt] Processing C:\a\incubator\public\content\faq.xml to
>> C:\a\incubator\p
>> ublic\target\texen\faq.xml
>>  [xslt] Processing
>> C:\a\incubator\public\content\guides\branding.xml to C:\a
>> \incubator\public\target\texen\guides\branding.xml
>>  [xslt] Processing C:\a\incubator\public\content\guides\chair.xml
>> to C:\a\in
>> cubator\public\target\texen\guides\chair.xml
>>  [xslt] Processing
>> C:\a\incubator\public\content\guides\committer.xml to C:\
>> a\incubator\public\target\texen\guides\committer.xml
>>  [xslt] Processing
>> C:\a\incubator\public\content\guides\community.xml to C:\
>> a\incubator\public\target\texen\guides\community.xml
>>  [xslt] Processing C:\a\incubator\public\content\guides\entry.xml
>> to C:\a\in
>> cubator\public\target\texen\guides\entry.xml
>>  [xslt] Processing
>> C:\a\incubator\public\content\guides\graduation.xml to C:
>> \a\incubator\public\target\texen\guides\graduation.xml
>>  [xslt] Processing C:\a\incubator\public\content\guides\index.xml
>> to C:\a\in
>> cubator\public\target\texen\guides\index.xml
>>  [xslt] Processing C:\a\incubator\public\content\guides\lists.xml
>> to C:\a\in
>> cubator\public\target\texen\guides\lists.xml
>>  [xslt] Processing C:\a\incubator\public\content\guides\mentor.xml
>> to C:\a\i
>> ncubator\public\target\texen\guides\mentor.xml
>>  [xslt] Processing C:\a\incubator\public\content\guides\names.xml
>> to C:\a\in
>> cubator\public\target\texen\guides\names.xml
>>  [xslt] Processing
>> C:\a\

RE: [VOTE] CloudStack for Apache Incubator

[Franklin, Matthew B.]

+1 (binding)

>-Original Message-
>From: Kevin Kluge [mailto:kevin.kl...@citrix.com]
>Sent: Monday, April 09, 2012 9:32 PM
>To: general@incubator.apache.org
>Subject: [VOTE] CloudStack for Apache Incubator
>
>Hi All.  I'd like to call for a VOTE for CloudStack to enter the Incubator.  
>The
>proposal is available at [1] and I have also included it below.   Please vote 
>with:
>+1: accept CloudStack into Incubator
>+0: don't care
>-1: do not accept CloudStack into Incubator (please explain the objection)
>
>The vote is open for at least 72 hours from now (until at least 19:00 US-PST on
>April 12, 2012).
>
>Thanks for the consideration.
>
>-kevin
>
>[1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
>Abstract
>
>CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
>platform.
>
>Proposal
>
>CloudStack provides control plane software that can be used to create an IaaS
>cloud. It includes an HTTP-based API for user and administrator functions and
>a web UI for user and administrator access. Administrators can provision
>physical infrastructure (e.g., servers, network elements, storage) into an
>instance of CloudStack, while end users can use the CloudStack self-service
>API and UI for the provisioning and management of virtual machines, virtual
>disks, and virtual networks.
>
>Citrix Systems, Inc. submits this proposal to donate the CloudStack source
>code, documentation, websites, and trademarks to the Apache Software
>Foundation ("ASF").
>
>Background
>
>Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
>provide virtual machines to end users. CloudStack additionally provides
>baremetal OS installation to end users via a self-service interface. The
>management of physical resources to provide the larger goal of cloud service
>delivery is known as "orchestration". IaaS clouds are usually described as
>"elastic" -- an elastic service is one that allows its user to rapidly scale 
>up or
>down their need for resources.
>
>A number of open source projects and companies have been created to
>implement IaaS clouds. Cloud.com started CloudStack in 2008 and released
>the source under GNU General Public License version 3 ("GPL v3") in 2010.
>Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed 
>the
>CloudStack source under Apache License v2 in April, 2012.
>
>Rationale
>
>IaaS clouds provide the ability to implement datacenter operations in a
>programmable fashion. This functionality is tremendously powerful and
>benefits the community by providing:
>
>- More efficient use of datacenter personnel
>- More efficient use of datacenter hardware
>- Better responsiveness to user requests
>- Better uptime/availability through automation
>
>While there are several open source IaaS efforts today, none are governed by
>an independent foundation such as ASF. Vendor influence and/or proprietary
>implementations may limit the community's ability to choose the hardware
>and software for use in the datacenter. The community at large will benefit
>from the ability to enhance the orchestration layer as needed for particular
>hardware or software support, and to implement algorithms and features that
>may reduce cost or increase user satisfaction for specific use cases. In this
>respect the independent nature of the ASF is key to the long term health and
>success of the project.
>
>Initial Goals
>
>The CloudStack project has two initial goals after the proposal is accepted and
>the incubation has begun.
>
>The Cloudstack Project's first goal is to ensure that the CloudStack source
>includes only third party code that is licensed under the Apache License or
>open source licenses that are approved by the ASF for use in ASF projects.
>The CloudStack Project has begun the process of removing third party code
>that is not licensed under an ASF approved license. This is an ongoing process
>that will continue into the incubation period. Third party code contributed to
>CloudStack under the CloudStack contribution agreement was assigned to
>Cloud.com in exchange for distributing CloudStack under GPLv3. The
>CloudStack project has begun the process of amending the previous
>CloudStack contribution agreements to obtain consent from existing
>contributors to change the CloudStack project's license. In the event that an
>existing contributor does not consent to this change, the project is prepared
>to remove that contributor's code. Additionally, there are binary
>dependencies on redistributed libraries that are not provided with an ASF-
>approved license. Finally, the CloudStack has source files incorporated from
>third parties that were not provided with an ASF-approved license. We have
>begun the process of re-writing this software. This is an ongoing process that
>will extend into the incubation period. These issues are discussed in more
>detail later in the proposal.
>
>Although CloudStack is open source, many design documents and discussions
>that sho

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC6

[Franklin, Matthew B.]

On 4/12/12 3:35 PM, "Karl Wright"  wrote:

>I should also mention that Jukka voted +1 during the community voting
>on this RC, so his vote should be binding here as well.

For future reference, it is a best practice to include a link to the PPMC
VOTE thread [1].  It has also been suggested that the RM include in the
IPMC VOTE thread any IPMC members who have voted +1 on the PPMC VOTE
thread.

[1] : 
http://incubator.apache.org/guides/releasemanagement.html#best-practice-inc
ubator-release-vote


>
>Karl
>
>On Thu, Apr 12, 2012 at 5:45 AM, Tommaso Teofili
> wrote:
>> +1 (binding),
>> Tommaso
>>
>> 2012/4/12 Karl Wright 
>>
>>> +1 from me (binding).
>>>
>>> Karl
>>>
>>> On Wed, Apr 11, 2012 at 11:16 PM, Shinichiro Abe
>>>  wrote:
>>> > Hi,
>>> >
>>> > Please vote on whether or not to release ManifoldCF 0.5-incubating,
>>>RC6.
>>> > This RC has passed our podling vote and awaits your inspection.
>>> >
>>> > You can download the release candidate from
>>> >
>>> 
>>>http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC
>>>6/
>>> > and there is also a tag in svn under
>>> >
>>> 
>>>https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.5-incubati
>>>ng-RC6/
>>> .
>>> >
>>> > It has done improvements for its distribution(bin,lib,src)
>>> > and build process as to core dependencies.
>>> >
>>> > Thank you,
>>> > Shinichiro Abe
>>> > -
>>> > 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: Problem with Olio Java Setup

[Franklin, Matthew B.]

Hi Kim,

Glad to see you are reaching out for help, but this list isn't the right place 
for this question.  Please direct this question to the Olio user list 
(olio-u...@incubator.apache.org).  

general@ is used for cross-project incubator discussions.  The vast majority of 
us on general don't have enough working knowledge of Olio to offer much help.   

-Matt

>-Original Message-
>From: Kim Rohner [mailto:rohner@googlemail.com]
>Sent: Tuesday, April 17, 2012 10:11 AM
>To: general@incubator.apache.org
>Subject: Problem with Olio Java Setup
>
>Hi all,
>
>i'm currently installing olio using the olio_java_setup:
>https://svn.apache.org/repos/asf/incubator/olio/docs/java_setup.html
>
>I installed within the setup JDK 1.7, ANT 1.8.3, FABAN 1.0.1 and
>Glassfish v3.
>I finished all previous steps of the setup and i am stuck in step 7 of
>Building the Web Application.
>When i enter the "ant" command in the terminal the Build fails with the
>following output:
>
>
>kim@ubuntu:~/olio/webapp/java/trunk/ws/apps/webapp$ ant
>Buildfile: /home/kim/olio/webapp/java/trunk/ws/apps/webapp/build.xml
>
>default-ear:
>
>init:
>
>-pre-compile:
>
>bpp-actual-compilation:
>  [echo] Compiling webapp
> [javac]
>/home/kim/olio/webapp/java/trunk/ws/bp-project/command-line-ant-
>tasks.xml:96:
>warning: 'includeantruntime' was not set, defaulting to
>build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 9 source files to
>/home/kim/olio/webapp/java/trunk/ws/apps/webapp/build/classes
>
>BUILD FAILED
>/home/kim/olio/webapp/java/trunk/ws/bp-project/command-line-ant-
>tasks.xml:96:
>/home/kim/olio/webapp/java/trunk/ws/apps/webapp/${javaee.lib.dir} does
>not exist.
>
>
>Can somebody please tell me where my mistake is and how i can fix it?
>
>Kind regards,
>Kim

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

RE: Adding Syncope IPMC member in the incubator group

[Franklin, Matthew B.]

>-Original Message-
>From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On
>Behalf Of Simone Tripodi
>Sent: Wednesday, April 18, 2012 8:31 AM
>To: general@incubator.apache.org
>Subject: Adding Syncope IPMC member in the incubator group
>
>Good morning all! :)
>
>new guys of Apache Syncope are experiencing issues on deploying
>SNAPSHOT artifacts because looks like they are not in the incubator
>group, have a look at INFRA-4675 issue[1].
>
>What is the procedure to request to join?

You need to create a ticket for INFRA to manually grant the committers the 
correct Role [1][2]

[1]: https://issues.apache.org/jira/browse/INFRA-2939
[2]: https://issues.apache.org/jira/browse/INFRA-3718

>
>Many thanks in advance, all the best!
>-Simo
>
>[1] https://issues.apache.org/jira/browse/INFRA-4675
>
>http://people.apache.org/~simonetripodi/
>http://simonetripodi.livejournal.com/
>http://twitter.com/simonetripodi
>http://www.99soft.org/
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org

RE: Adding Syncope IPMC member in the incubator group

[Franklin, Matthew B.]

>-Original Message-
>From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On
>Behalf Of Simone Tripodi
>Sent: Wednesday, April 18, 2012 8:47 AM
>To: general@incubator.apache.org
>Subject: Re: Adding Syncope IPMC member in the incubator group
>
>Thanks a lot Matthew, much more than appreciated!

No problem.  This really should be in the incubator documentation somewhere.  I 
will try to find time this week to get it added.

-Matt

>
>Have a nice day, all the best,
>-Simo
>
>http://people.apache.org/~simonetripodi/
>http://simonetripodi.livejournal.com/
>http://twitter.com/simonetripodi
>http://www.99soft.org/
>
>
>
>On Wed, Apr 18, 2012 at 2:42 PM, Franklin, Matthew B.
> wrote:
>>>-Original Message-
>>>From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On
>>>Behalf Of Simone Tripodi
>>>Sent: Wednesday, April 18, 2012 8:31 AM
>>>To: general@incubator.apache.org
>>>Subject: Adding Syncope IPMC member in the incubator group
>>>
>>>Good morning all! :)
>>>
>>>new guys of Apache Syncope are experiencing issues on deploying
>>>SNAPSHOT artifacts because looks like they are not in the incubator
>>>group, have a look at INFRA-4675 issue[1].
>>>
>>>What is the procedure to request to join?
>>
>> You need to create a ticket for INFRA to manually grant the committers the
>correct Role [1][2]
>>
>> [1]: https://issues.apache.org/jira/browse/INFRA-2939
>> [2]: https://issues.apache.org/jira/browse/INFRA-3718
>>
>>>
>>>Many thanks in advance, all the best!
>>>-Simo
>>>
>>>[1] https://issues.apache.org/jira/browse/INFRA-4675
>>>
>>>http://people.apache.org/~simonetripodi/
>>>http://simonetripodi.livejournal.com/
>>>http://twitter.com/simonetripodi
>>>http://www.99soft.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: including external code under apache 2.0

[Franklin, Matthew B.]

>-Original Message-
>From: itamar.synhers...@gmail.com [mailto:itamar.synhers...@gmail.com]
>On Behalf Of Itamar Syn-Hershko
>Sent: Saturday, April 28, 2012 5:16 PM
>To: lucene-net-...@lucene.apache.org
>Cc: general@incubator.apache.org
>Subject: Re: including external code under apache 2.0
>
>That mail from  Stephan got lost in my inbox, so I never followed up on
>that. I guess now would be a good chance to tie up all loose ends.
>
>How do I "do the ICLA"?

http://www.apache.org/licenses/#clas

>
>On Sat, Apr 28, 2012 at 1:11 AM, Troy Howard 
>wrote:
>
>> My understanding is that we can include the code as long as we have a
>> ICLA from Itamar. This was discussed at length in January for another
>> contribution that the same contributor wanted to donate. Stephan
>> (Bodewig, our Incubation mentor) laid out what needed to be done
>> really clearly in that context.
>>
>> Here's the link to the final message on that thread where Stephan
>> recaps the relevant points:
>>
>> http://s.apache.org/HZa
>>
>> I don't know if Itamar ever followed up after that and filed a ICLA.
>> If he did, we're good and just need to commit the code.. Otherwise,
>> we'll need him to do the ICLA first.
>>
>> Thanks,
>> Troy
>>
>> On Fri, Apr 27, 2012 at 2:30 PM, Prescott Nasser
>
>> wrote:
>> >
>> >
>> >
>> >
>> > Hey all, We've had a community member port a library for Lucene.Net that
>> we'd like to include in our contrib packages. The package is under the
>> apache 2.0 license, so we think we are in the clear to include the code
>> into our contrib package - but we weren't sure and just wanted to double
>> check. The contrib project is located here:
>> https://github.com/synhershko/Spatial4n Thanks for your
>guidance~Prescott
>>
>>

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