Re: November reports

2012-11-15 Thread Roman Shaposhnik
On Wed, Nov 14, 2012 at 3:56 AM, Benson Margulies  wrote:
> Droids seems to be a really easy shepherding assignment. They are on
> the watch list for low activity, they are self-aware of this, and they
> are having a conversation with the commons TLP about perhaps becoming
> a component there. I don't know if there is any contribution any of
> the rest of us could make to increasing the likelihood of a positive
> outcome of that conversation.

Ditto for Nuvem. Almost exactly word-for-word. The only difference
is that they are talking to Apache Tuscany about becoming a
sub-project there.  There doesn't seem to be much to do except to
keep an eye on that conversation.

Thanks,
Roman.

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



[ANNOUNCE] Apache Bloodhound 0.2 incubating Released

2012-11-15 Thread Joachim Dreimann
The Apache Bloodhound (Incubating) team is pleased to announce the
availability of the Apache Bloodhound 0.2-incubating release.

Apache Bloodhound is a project to provide a tool to track progress and
defects in projects, with a primary focus on software projects. Standing on
the shoulders of the well-known Trac project, it will provide issue
tracking, repository browsing and a simple wiki syntax for easy reference.
On top of this Bloodhound aims to provide intuitive support for managing
multiple software projects, an advanced user-friendly interface and simple
installation with some of the most important plugins for Trac available by
default.

This is mostly a bugfix release, however the release notes can be viewed at
the link below: [1]

The release can be downloaded from *
http://www.apache.org/dyn/closer.cgi/incubator/bloodhound/apache-bloodhound-incubating-0.2.tar.gz
*

For further information on Apache Bloodhound, please visit the project
website at 
http://incubator.apache.org/**bloodhound/

The Apache Bloodhound Team.

[1]
http://svn.apache.org/viewvc/incubator/bloodhound/branches/0.2/RELEASE_NOTES?revision=1394550&view=markup

Disclaimer:
Apache Bloodhound is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator. Incubation is required
of all newly accepted projects until a further review indicates that the
infrastructure, communications, and decision making process have stabilized
in a manner consistent with other successful ASF projects.  While incubation
status is not necessarily a reflection of the completeness or stability of
the code, it does indicate that the project has yet to be fully endorsed by
the ASF.


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

2012-11-15 Thread Joachim Dreimann
Hi all,

and with this we've got a result!

With Brane repeating his IPMC binding vote from bloodhound-dev and Greg and
Hyrum adding their voices here, the results are:

   Greg Stein (binding) +1
   Hyrum Wright (binding) +1
   Branko Čibej (binding) +1

With 3 +1s I understand that release of Apache Bloodhound 0.2 (incubating)
is approved. I will complete the process by moving the artefacts from
Bloodhound's /dist/dev area to the equivalent /dist/release area this
evening.

Thanks to all those who took part.

Cheers,
   Joe


On 15 November 2012 02:15, Greg Stein  wrote:

> I've confirmed this discrepancy is the same as what Alexander
> Broekhuis posted about, as noted in INFRA-5445.
>
> So 0.2 is all good to go!!
>
> On Wed, Nov 14, 2012 at 12:57 PM, Greg Stein  wrote:
> > Oh. Forgot one item: so the below is conditional on resolving: the
> > .md5 does not match the .tar.gz. (I did not examine the signature
> > (.asc) to see if it matches the .tar.gz)
> >
> >
> > On Wed, Nov 14, 2012 at 12:52 PM, Greg Stein  wrote:
> >> +1 to release (IPMC, binding)
> >>
> >> [ apologies for the extreme delay :-( ]
> >>
> >> On Mon, Oct 29, 2012 at 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
>
>


-- 
Joe Dreimann
UX Designer | WANdisco 
*
*
*Transform your software development department. Register for a free SVN
HealthCheck  *


[Shepherd] Amber

2012-11-15 Thread Dave Fisher
Hi -

I've added the following to the November report wiki:

I think that Amber is ready to graduate - the traffic on the ML is down but 
indicates that some might use Amber if it were a TLP. I see starts to the 
process, I think that the mentors just need to give the podling some nudges. 
Some status updates to the mentor lists and sign-offs are in order as well.

I put Amber in the "Ready to Graduate" category. If the podling doesn't move 
then it could also be put into "Low Activity" and that would not bode well for 
the future.

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



Re: [PROPOSAL] Apache Steams Project

2012-11-15 Thread Davide Palmisano
Thank you so much.

No, I'm not participating on behalf of an employer.

cheers,

Davide

On Thu, Nov 15, 2012 at 8:46 AM, Ate Douma  wrote:
> Hi Davide,
>
> You will need to create a wiki account and thereafter request write access
> here.
> For your convenience I've already added your name to the initial committers
> section of the proposal.
>
> If your are participating on behalf of a employer, please let us know so we
> can add that to the affiliation section of the proposal as well.
>
> Kind regards,
>
> Ate
>
>
> On 11/14/2012 01:41 PM, Davide Palmisano wrote:
>>
>> Thanks Matthew,
>>
>> but the page is an immutable one.
>>
>> how can I do?
>>
>> cheers,
>>
>> Davide
>>
>> On Wed, Nov 14, 2012 at 12:14 PM, Franklin, Matthew B.
>>  wrote:

 -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 

Re: [VOTE] Release JSPWiki version 2.9.0-incubating

2012-11-15 Thread Alexei Fedotov
Hello Juan,

According to your answers, I suggest the following (IMHO, not binding anyway)
1) remove licenses for files which are not included into the source
release (this actually means the source release license file should be
different from the binary release one);
2) remove the second copy for any LICENSE (the one under doc/);
3) for the binary release, make the artifact list complete, so it
would contain the reference to Mozilla licensed file and other missed
entities.

--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095


On Thu, Nov 15, 2012 at 4:11 AM, Juan Pablo Santos Rodríguez
 wrote:
> Hi Alexei,
>
> activation-1.1.jar et al are downloaded as part of the build. They're not
> included in the source because that's contrary to the Apache principles.
> That was noted in our July report (and tracked at [#1]).
>
> Regarding the LICENSE / doc/LICENSE.* files: initially, we kept each
> license in a separate file (doc/LICENSE.*), while ./LICENSE contained only
> the AL. This raised some concerns, noted on our 3rd RC vote [#2], which led
> to ./LICENSE file also having verbatim copies of all used licenses. As for
> the Mozilla license, it's in the ./LICENSE file (line 1090 onwards), we use
> custom-rhino in some of the tests, which uses that license.
>
>
> cheers,
> juan pablo
>
> p.d.: your vote being..? O:-D
>
> [#1]: 
> https://issues.apache.org/jira/browse/JSPWIKI-738
> [#2]:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201210.mbox/%3c80852492-ac42-4f8d-82ca-760eefccd...@oracle.com%3E
>
> On Wed, Nov 14, 2012 at 4:36 PM, Alexei Fedotov 
> wrote:
>
>> Great work!
>>
>> I've got the following questions concerning the ./LICENSE file for the
>> source release:
>>
>> There is a list of jar files in the ./LICENSE file of the following form:
>> activation-1.1.jar  doc/LICENSE.cddl
>>
>> What is the point of including licenses for files which are absent in
>> the source release?
>> Why license texts appear twice (both in the ./LICENSE file and ./doc/
>> folder)? That provides more place for possible errors.
>> I believe the list is good to exist in the ./LICENSE file for the
>> binary release. Why it does not mention all licenses from the source
>> release ./LICENSE file, e.g. Mozilla license?
>>
>> How to understand "Copyright (c)  " in MIT
>> license. The template style cannot appear in final version of the
>> LICENSE. Also, IMHO, copyright attribution does not belong to the
>> license (unless you use a copyrighted license).
>>
>> --
>> With best regards / с наилучшими пожеланиями,
>> Alexei Fedotov / Алексей Федотов,
>> http://dataved.ru/
>> +7 916 562 8095
>>
>>
>> On Wed, Nov 14, 2012 at 5:03 AM, Florian Holeczek 
>> wrote:
>> > Hi all,
>> >
>> > I'd like to start a vote on an incubator release for Apache JSPWiki,
>> version
>> > 2.9.0-incubating.
>> >
>> > Apache JSPWiki (incubating) is a leading open source WikiWiki engine,
>> > feature-rich and built around standard J2EE components (Java, servlets,
>> > JSP).
>> >
>> >
>> > A vote was held on the developer mailing list [1] and passed with 9 "+1"s
>> > [2], two of them from our mentors.
>> >
>> >
>> > This release candidate fixes the following issues:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732&version=12319521
>> >
>> > The tag to be voted upon:
>> >
>> https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating
>> >
>> > Source and binary files:
>> > http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/
>> >
>> > Checksums:
>> >
>> > JSPWiki-2.9.0-incubating-src.zip
>> > MD5:287e75857b03b41dca769211591c6144
>> > SHA1:   74b24e526177b7ddf5394b4b96b67bb9081628a4
>> > SHA512:
>> >
>> 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a
>> >
>> > JSPWiki-2.9.0-incubating-bin.zip
>> > MD5:7e774dc46c112ca895aad60fb607dc60
>> > SHA1:   e529eb02d13f4061534d85dd0e78d67c5dfe29a5
>> > SHA512:
>> >
>> 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd1328ef083fb4a4fe9f3867e9ec7c7e4a640b845a2e2ee4
>> >
>> > JSPWiki's KEYS file containing PGP keys we use to sign the release:
>> > http://www.apache.org/dist/incubator/jspwiki/KEYS
>> >
>> > For convenience, this directory includes a binary distribution and a RAT
>> > report on the cited tag.
>> > You can manually generate the RAT report from a clean source by running
>> the
>> > "rat-report" Ant target.
>> >
>> >
>> > Please vote:
>> >
>> > [ ] +1  approve, release Apache JSPWiki 2.9.0-incubating
>> > [ ] +0  no opinion
>> > [ ] -1  disapprove (and giving a reason)
>> >
>> >
>> > The vote will be open for at least 72 hours.
>> >
>> > Best regards
>> >  Florian Holeczek
>

Re: [PROPOSAL] Apache Steams Project

2012-11-15 Thread Ate Douma

Hi Davide,

You will need to create a wiki account and thereafter request write access here.
For your convenience I've already added your name to the initial committers 
section of the proposal.


If your are participating on behalf of a employer, please let us know so we can 
add that to the affiliation section of the proposal as well.


Kind regards,

Ate

On 11/14/2012 01:41 PM, Davide Palmisano wrote:

Thanks Matthew,

but the page is an immutable one.

how can I do?

cheers,

Davide

On Wed, Nov 14, 2012 at 12:14 PM, Franklin, Matthew B.
 wrote:

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