gmane.comp.apache.incubator.general

JIRA and communities

Benson Margulies — 2012-05-25T15:37:54

On Fri, May 25, 2012 at 12:53 AM, Steve Loughran
<steve.loughran< at >gmail.com> wrote:

I don't claim that JIRA helps, but I also don't accept the proposition
that JIRA hurts.

I think that we should focus on the community, not the tools. The
JIRA-oriented projects I follow have JIRA set to send all new issues,
and all new comments, to the dev list. So all community members, and,
in particular, all PMC members with a duty to supervise, see all the
traffic.

Meanwhile, some projects, with or without JIRA, just creep along
making small, incremental, changes and bugfixes. There's no grand
strategy or vision, and, as a result, not much to talk about most of
the time. Bugs and requests come in and people deal with them -- or
not.

So, I won't claim that your disfunction scenario is impossible or
never observed at the ASF. I will point out that bugzilla could be
used just as effectively to create the same problem.

As a mentor, what I care about is what happens when a new person shows
up. Does the dev list manage to welcome and encourage that person? Or
does that person find a mysterious, opaque situation in which there
seems to be a secret code that has to be broken to get a contribution
accepted?

If welcome and encouragement amounts to 'go find a JIRA and get busy,'
that does not bother me, so long it leads to the happy result of
applied patches and eventual karma.

[ANNOUNCE] Apache Wink 1.2.0-incubating release

Luciano Resende — 2012-05-23T16:36:40

The Apache Wink team is pleased to announce the release of Apache Wink
1.2.0-incubating.

Apache Wink is a simple yet solid framework for building RESTful Web
services. It is comprised of a Server module and a Client module for
developing and consuming RESTful Web services.

The Wink Server module is a complete implementation of the JAX-RS v1.1
specification. On top of this implementation, the Wink Server module
provides a set of additional features that were designed to facilitate
the development of RESTful Web services.

The Wink Client module is a Java based framework that provides
functionality for communicating with RESTful Web services. The
framework is built on top of the JDK HttpURLConnection and adds
essential features that facilitate the development of such client
applications.

For full details about the release and to download the distributions
please go to:

http://incubator.apache.org/wink/downloads.html

Apache Wink welcomes your help. Any contribution, including code,
testing, contributions to the documentation, or bug reporting is
always appreciated. For more information on how to get involved in
Apache Wink visit the website at:

http://incubator.apache.org/wink/

Thank you for your interest in Apache Wink!

The Apache Wink Team.

June reports in two weeks

Jukka Zitting — 2012-05-23T23:28:18

Hi all,

There's plenty of time still before the June reports [1] start flowing
in. As an early remainder to podlings starting to draft their reports,
here's how the IPMC saw your status as of the previous quarterly
report in March [2]:

  IP clearance: Openmeetings
  No release: Bloodhound, Cordova, OpenOffice
  Low activity: Kalumet, Kato
  Low diversity: Bigtop, Etch, Isis, HCatalog, S4, Wave
  Ready to graduate: Flume

Has the situation in your podling changed over the last three months?
If not, what's your plan for improving the situation? Is there
anything for which you'd appreciate more help?

I'm especially worried about Kato as it seems like the project has
more or less died even though the JSR 326 / Oracle trouble got finally
sorted out. Is it time to retire the project or can we hope for a
revival?

I also wanted to start preparing for this reporting round in good time
by assigning shepherds [3] already now. Using a fuzzy algorithm based
on the available volunteers, their stated preferences, and the
podlings they're already mentoring, I came up with the following
initial assignments that I've also recorded on the wiki page:

  Benson Margulies - CloudStack, HCatalog, Kato
  Dave Fisher      - Bloodhound, Flume
  Matt Franklin    - Bigtop, Flex, Openmeetings
  Matt Hogstrom    - Cordova, OpenOffice.org
  Jukka Zitting    - Etch, Isis, S4
  Mohammad Nour    - Kalumet
  Ross Gardler     - Wave

Feel free to shuffle these around or ask for someone else to fill in
if you're expecting to be too busy for the extra reviews in early
June. Other IPMC members and interested observers, please jump in and
volunteer as extra shepherds if you'd like to help this effort.

As discussed earlier, shepherds are not there to replace existing
mentors. If everything is going well with a project, the shepherd can
simply acknowledge a report and move on. If there are any relevant
questions that the report doesn't answer, the shepherd may ask the
podling and its mentors for more details. And finally if something
seems wrong, the shepherd should raise a flag for the mentors and the
rest of the IPMC to focus on. Most importantly, we need to be talking
*with* the podlings, not just *about* them, so especially any
constructive and encouraging feedback to them will be highly useful.

[1] http://wiki.apache.org/incubator/June2012
[2] http://wiki.apache.org/incubator/March2012
[3] http://wiki.apache.org/incubator/IncubatorShepherds

BR,

Jukka Zitting

[VOTE] Accept Crunch into the Apache Incubator

Josh Wills — 2012-05-23T18:45:49

I would like to call a vote for accepting "Apache Crunch" for
incubation in the Apache Incubator. The full proposal is available
below. We ask the Incubator PMC to sponsor it, with phunt as
Champion, and phunt, tomwhite, and acmurthy volunteering to be
Mentors.

Please cast your vote:

[ ] +1, bring Crunch into Incubator
[ ] +0, I don't care either way,
[ ] -1, do not bring Crunch into Incubator, because...

This vote will be open for 72 hours and only votes from the Incubator
PMC are binding.

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

Proposal text from the wiki:
----------------------------------------------------------------------------------------------------------------------
= Crunch - Easy, Efficient MapReduce Pipelines in Java and Scala =

== Abstract ==

Crunch is a Java library for writing, testing, and running pipelines
of !MapReduce jobs on Apache Hadoop.

== Proposal ==

Crunch is a Java library for writing, testing, and running pipelines
of !MapReduce jobs on Apache Hadoop. Its main goal is to provide a
high-level API for writing and testing complex !MapReduce jobs that
require multiple processing stages. It has a simple, flexible, and
extensible data model that makes it ideal for processing data that
does not naturally fit into a relational structure, such as time
series and serialized object formats like JSON and Avro. It supports
running pipelines either as a series of !MapReduce jobs on an Apache
Hadoop cluster or in memory on a single machine for fast testing and
debugging.

== Background ==

Crunch was initially developed by Cloudera to simplify the process of
creating sequences of dependent !MapReduce jobs, especially jobs that
processed non-relational data like time series. Its design was based
on a paper Google published about a Java library they developed called
!FlumeJava that was created in order to solve a similar class of
problems. Crunch was open-sourced by Cloudera on !GitHub as an Apache
2.0 licensed project in October 2011. During this time Crunch has been
formally released twice, as versions 0.1.0 (October 2010) and 0.2.0
(February 2012), with an incremental update to version 0.2.1 (March
2012) . These releases are also distributed by Cloudera as source and
binaries from Cloudera's Maven repository.

== Rationale ==

Most of the interesting analytical and data processing tasks that are
run on an Apache Hadoop cluster require a series of !MapReduce jobs to
be executed in sequence. Developers who are creating these pipelines
today need to manually assign the sequence of tasks to perform in a
dependent chain of !MapReduce jobs, even though there are a number of
well-known patterns for fusing dependent computations together into a
single !MapReduce stage and for performing common types of joins and
aggregations. This results in !MapReduce pipelines that are more
difficult to test, maintain, and extend to support new functionality.

Furthermore, the type of data that is being stored and processed using
Apache Hadoop is evolving. Although Hadoop was originally used for
storing large volumes of structured text in the form of webpages and
log files, it is now common for Hadoop to store complex, structured
data formats such as JSON, Apache Avro, and Apache Thrift. These
formats allow developers to work with serialized objects in
programming languages like Java, C++, and Python, and allow for new
types of analysis to be performed on complex data types. Hadoop has
also been adopted by the scientific research community, who are using
Hadoop to process time series data, structured binary files in the
HDF5 format, and large medical and satellite images.

Crunch addresses these challenges by providing a lightweight and
extensible Java API for defining the stages of a data processing
pipeline, which can then be run on an Apache Hadoop cluster as a
sequence of dependent !MapReduce jobs, or in-memory on a single
machine to facilitate fast testing and debugging. Crunch relies on a
small set of primitive abstractions that represent immutable,
distributed collections of objects. Developers define functions that
are applied to those objects in order to generate new immutable,
distributed collections of objects. Crunch also provides a library of
common !MapReduce patterns for performing efficient joins and
aggregation operations over these distributed collections that
developers may integrate into their own pipelines. Crunch also
provides native support for processing structured binary data formats
like JSON, Apache Avro, and Apache Thrift, and is designed to be
extensible to support working with any kind of data format that Java
supports in its native form.

== Initial Goals ==

Crunch is currently in its first major release with a considerable
number of enhancement requests, tasks, and issues recorded towards its
future development. The initial goal of this project will be to
continue to build community in the spirit of the "Apache Way", and to
address the highly requested features and bug-fixes towards the next
dot release.

Some goals include:
* To stand up a sustaining Apache-based community around the Crunch codebase.
* Improved documentation of Java libraries and best practices.
* Support the ability to "fuse" logically independent pipeline stages
that aggregate the same data in different ways into a single
!MapReduce job.
* Performance, usability, and robustness improvements.
* Improving diagnostic reporting and debugging for individual !MapReduce jobs.
* Providing a centralized place for contributed extensions and
domain-specific applications.

= Current Status =

== Meritocracy ==

Crunch was initially developed by Josh Wills in September 2011 at
Cloudera. Developers external to Cloudera provided feedback, suggested
features and fixes and implemented extensions of Crunch. Cloudera's
engineering team has since maintained the project with Josh Wills, Tom
White, and Brock Noland dedicated towards its improvement.
Contributors to Crunch include developers from multiple organizations,
including businesses and universities.

== Community ==

Crunch is currently used by a number of organizations all over the
world. Crunch has an active and growing user and developer community
with active participation in
[[https://groups.google.com/a/cloudera.org/group/crunch-users/topics|user]]
and [[https://groups.google.com/a/cloudera.org/group/crunch-dev/topics|developer]]
mailing lists.

Since open sourcing the project, there have been eight individuals
from five organizations who have contributed code.

== Core Developers ==

The core developers for Crunch are:
* Brock Noland: Wrote many of the test cases, user documentation, and
contributed several bug fixes.
* Josh Wills: Josh wrote much of the original Crunch code.
* Gabriel Reid: Gabriel significantly improved Crunch's handling of
Avro data and has contributed several bug fixes for the core planner.
* Tom White: Tom added several libraries for common !MapReduce
pipeline operations, including the sort library and a library of set
operations.
* Christian Tzolov: Christian has contributed several bug fixes for
the Avro serialization module and the unit testing framework.
* Robert Chu: Robert did the left/right/outer join implementations
for Crunch and fixed several bugs in the runtime configuration logic.

Several of the core developers of Crunch have contributed towards
Hadoop or related Apache projects and are familiar with Apache
principles and philosophy for community driven software development.

== Alignment ==

Crunch complements several current Apache projects. It complements
Hadoop !MapReduce by providing a higher-level API for developing
complex data processing pipelines that require a sequence of
!MapReduce jobs to perform. Crunch also supports Apache HBase in order
to simplify the process of writing !MapReduce jobs that execute over
HBase tables. Crunch makes extensive use of the Apache Avro data
format as an internal data representation process that makes
!MapReduce jobs execute quickly and efficiently.

= Known Risks =

== Orphaned Products ==

Crunch is already deployed in production at multiple companies and
they are actively participating in creating new features. Crunch is
getting traction with developers and thus the risks of it being
orphaned are minimal.

== Inexperience with Open Source ==

All code developed for Crunch has been open sourced by Cloudera under
Apache 2.0 license. All committers to Crunch are intimately familiar
with the Apache model for open-source development and are experienced
with working with new contributors.

== Homogeneous Developers ==

The initial set of committers is from a reduced set of organizations.
However, we expect that once approved for incubation, the project will
attract new contributors from diverse organizations and will thus grow
organically. The submission of patches from developers from several
different organizations is a strong indication that Crunch will be
widely adopted.

== Reliance on Salaried Developers ==

It is expected that Crunch will be developed on salaried and volunteer
time, although all of the initial developers will work on it mainly on
salaried time.

== Relationships with Other Apache Products ==

Crunch depends upon other Apache Projects: Apache Hadoop, Apache
HBase, Apache Log4J, Apache Thrift, Apache Avro, and multiple Apache
Commons components. Its build depends upon Apache Maven.

Crunch's functionality has some indirect or direct overlap with the
functionality of Apache Pig and Apache Hive but has several
significant differences in terms of their user community and the types
of data they are designed to work with. Both Hive and Pig are
high-level languages that are designed to allow non-programmers to
quickly create and run !MapReduce jobs. Crunch is a Java library whose
primary community is Java developers who are creating scalable data
pipelines and !MapReduce-based applications. Additionally, Hive and
Pig both employ a relational, tuple-oriented data model on top of
HDFS, which introduces overhead and limits expressive power for
developers who are working with serialized objects and non-relational
data types. Crunch uses a lower-level data model that gives developers
the freedom to work with data in a format that is optimized for the
problem they are trying to solve.

== An Excessive Fascination with the Apache Brand ==

We would like Crunch to become an Apache project to further foster a
healthy community of contributors and consumers around the project.
Since Crunch directly interacts with many Apache Hadoop-related
projects and solves an important problem of many Hadoop users,
residing in the Apache Software Foundation will increase interaction
with the larger community.

= Documentation =

* Crunch wiki at GitHub: https://github.com/cloudera/crunch/wiki
* Crunch jira at Cloudera: https://issues.cloudera.org/browse/crunch
* Crunch javadoc at GitHub: http://cloudera.github.com/crunch/apidocs/

= Initial Source =

* https://github.com/cloudera/crunch/tree/

== Source and Intellectual Property Submission Plan ==

* The initial source is already licensed under the Apache License,
Version 2.0. https://github.com/cloudera/crunch/blob/master/LICENSE.txt

== External Dependencies ==

The required external dependencies are all Apache License or
compatible licenses. Following components with non-Apache licenses are
enumerated:

* com.google.protobuf : New BSD
* org.hamcrest: New BSD
* org.slf4j: MIT-like License

Non-Apache build tools that are used by Crunch are as follows:

* Cobertura: GNU GPLv2

Note that Cobertura is optional and is only used for calculating unit
test coverage.

== Cryptography ==

Crunch uses standard APIs and tools for SSH and SSL communication
where necessary.

= Required Resources =

== Mailing lists ==

* crunch-private (with moderated subscriptions)
* crunch-dev
* crunch-commits
* crunch-user

== Github Repositories ==

http://github.com/apache/crunch
git://git.apache.org/crunch.git

== Issue Tracking ==

JIRA Crunch (CRUNCH)

== Other Resources ==

The existing code already has unit and integration tests so we would
like a Jenkins instance to run them whenever a new patch is submitted.
This can be added after project creation.

= Initial Committers =

* Brock Noland (brock at cloudera dot com)
* Josh Wills (jwills at cloudera dot com)
* Gabriel Reid (gabriel dot reid at gmail dot com)
* Tom White (tom at cloudera dot com)
* Christian Tzolov (christian dot tzolov at gmail dot com)
* Robert Chu (robert at wibidata dot com)
* Vinod Kumar Vavilapalli (vinodkv at hortonworks dot com)

= Affiliations =

* Brock Noland, Cloudera
* Josh Wills, Cloudera
* Gabriel Reid, !TomTom
* Tom White, Cloudera
* Christian Tzolov, !TomTom
* Robert Chu, !WibiData
* Vinod Kumar Vavilapalli, Hortonworks

= Sponsors =

== Champion ==

* Patrick Hunt

== Nominated Mentors ==

* Tom White
* Patrick Hunt
* Arun Murthy

== Sponsoring Entity ==

* Apache Incubator PMC

[VOTE] Release ManifoldCF 0.5.1, RC1

Shinichiro Abe — 2012-05-23T00:37:00

Hi,

Please vote on whether or not to release ManifoldCF 0.5.1, RC1.
This RC has passed our podling vote[1] and awaits your inspection.

You can download the release candidate from
http://people.apache.org/~shinichiro/apache-manifoldcf-0.5.1-RC1/
and there is also a tag in svn under 
https://svn.apache.org/repos/asf/incubator/lcf/tags

Thank you in advance.

[1]
http://mail-archives.apache.org/mod_mbox/incubator-connectors-dev/201205.mbox/%3C19D6EF99-AC0E-4030-B0E9-235F347C42C1%40gmail.com%3E

Shinichiro Abe

karma for new oozie committers

Alan Gates — 2012-05-22T20:03:47

All,

The Oozie podling has added two new committers, harsh and virag.  None of the mentors are VPs and thus none of us can grant them karma on Oozie's SVN.  Would someone with the ability to do this be kind enough to do so?  Thanks.

You can see the vote threads at:

https://mail-search.apache.org/pmc/private-arch/incubator-oozie-private/201205.mbox/%3cCACDdcgf6Vak4Moey5fNCoXnW4g6DV5ArZAA=70NR556q9nfwyQ< at >mail.gmail.com%3e

and 

https://mail-search.apache.org/pmc/private-arch/incubator-oozie-private/201205.mbox/%3cCACDdcgev+3nXJ3Y9vnhtpQ4ozn=pH146RvQTxiWmg-8W=Gq1_w< at >mail.gmail.com%3e

Alan.

[VOTE] Release Apache Wookie 0.10.0-incubating (General Incubation List)

Scott Wilson — 2012-05-21T15:13:05

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

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

Vote thread:
http://markmail.org/message/2p4veen6n22w7hnb

Result:
http://markmail.org/message/d2jzbrdgic3od5uj

Svn source tag:
https://svn.apache.org/repos/asf/incubator/wookie/tags/0.10.0-incubating/

Release notes:
https://svn.apache.org/repos/asf/incubator/wookie/tags/0.10.0-incubating/RELEASE_NOTES

Release artifacts:
http://people.apache.org/builds/incubator/wookie/0.10.0-incubating/

Maven artifacts
https://repository.apache.org/content/repositories/orgapachewookie-094/

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

Lazy consensus, vote open for 72 hours.

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

PhotArk down to one mentor

Jukka Zitting — 2012-05-20T20:39:25

Hi,

I just talked to Martin Cooper who was listed as a PhotArk mentor
together with Luciano Resende. Martin actually resigned from the IPMC
and his mentor duties already in 2010, which puts PhotArk down to just
a single mentor.

Even though Luciano has been doing a good job, I think having more
IPMC members around to help PhotArk would be useful, especially given
that much of the community action is happening as a part of the GSoC
program.

Any volunteers? For an update on what PhotArk is about nowadays, see
Luciano's post from a few months ago [1].

[1] http://markmail.org/message/7ptsuyilhzcqeyum

BR,

Jukka Zitting

Policy for new committers to podlings

Benson Margulies — 2012-05-18T18:03:39

I'm embarrassed to report that I'm feeling a bit foggy on the new
committer policy, and a quick tour with google failed to find it on a
web page. We're long on pages about initial podling setup, and not so
long on others.

So, if a podling has held a vote for a new contributor, what exactly
happens next? And what web page should I have read this on, and if it
is actually missing, I'll go put it someplace.

[DISCUSS] Crunch to join the Apache Incubator

Josh Wills — 2012-05-16T00:23:28

Hi all,

I would like to propose Crunch, a library for writing MapReduce
pipelines in Java and Scala, as an Apache Incubator project. The
proposal is here:

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

We would gladly welcome additional volunteers to act as mentors on the
project, so if this sounds like your cup of tea, please feel free to
sign up or let us know.

Thanks!
Josh

[ANNOUNCE] HCatalog 0.4.0 released

Alan Gates — 2012-05-17T23:36:30

The HCatalog team is happy to announce the release of HCatalog 0.4.0

Apache HCatalog provides a table management service for Hadoop.  More details about HCatalog can be found at http://incubator.apache.org/hcatalog


The highlights of this release are:

- Full support for reading from and writing to Hive.
- Support for deeply nested maps, arrays, and structs.
- Switch from StorageDrivers to SerDes.  HCatalog no longer supports its own StorageDriver classes for data (de)serialization.  Instead it uses Hive's SerDe classes.
- Addition of JSonSerDe to support reading and writing JSON data.
- The HCatalog binary distribution no longer includes Apache Hive.  We now require that Hive first be installed.
- The HCatalog source distribution no longer includes Apache Hive source.  It now pulls the required jars via maven. 

The details of the release can be found at http://incubator.apache.org/hcatalog/releases.html

Alan.

wiki karma

Josh Wills — 2012-05-17T17:14:29

Hi,

I'd like to have edit permissions for my account (JoshWills) on the
incubator proposal wiki.

Thanks!
Josh

[DISCUSS] Crunch joining the Apache Incubator

Josh Wills — 2012-05-17T03:14:04

Hi all,

I would like to propose Crunch, a library for writing MapReduce
pipelines in Java and Scala, as an Apache Incubator project. The
proposal is here:

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

We would gladly welcome additional volunteers to act as mentors on the
project, so if this sounds like your cup of tea, please feel free to
sign up or let us know.

Thanks!
Josh

Update IP clearance page

Alexander Broekhuis — 2012-05-16T08:08:55

Hi all,

I've added a IP Clearance to SVN and updated the index.xml, how do I get it
to show up on the actual site [1]?

As far as I can tell I've followed the template and filled in everything
needed for this.

Thanks!

[1]: http://incubator.apache.org/ip-clearance/

Sorry to hear about HISE

Jack Put — 2012-05-15T07:53:29

Dear Reader,

 

I am sorry to read about the retirement of HISE as a project.

 

The question now to subject matter experts, what to do now?

 

Is Apache ODE a good alternative? (Comparing Apples and Oranges perhaps).

 

The software we create depends greatly on the use of (Zend) PHP, and we are
in need of a component (service) to take care of (human) task handling.

 

While we seek to improve automation (system to system) tasks in the future,
the human part is important in a few months from now.

 

Love to hear about any suggestions towards this.

 

Kind regards,

Ing. Jack Put MBA

Unit Manager

[VOTE] Let the retired Zeta Components project keep their name

Christian Grobmeier — 2012-05-14T12:30:32

Hello,

Zeta Components has been retired and the committers want to go to
github with the project. They have requested to keep their name and
reached out for trademarks if this is possible. Shane explained he
would agree in this case if:

A) the IPMC confirms the podling is retired
B) the retirement guide has been fulfilled
C) the community clearly note on their homepage that they are not
longer associated with the ASF

We have a successful vote for A).
B) has been completed by me (pending some closing tasks from Infra)

Assuming C) will be done by the community this vote is now to allow
them to use their old name Zeta Components.

Please note, no release has happened so far.

Please choose:

[] +1, allow them to use Zeta Components as name
[] -1, don't, because

This vote is open for 72h.

Cheers
Christian

Zeta Components retirement

Christian Grobmeier — 2012-05-14T09:20:47

Hello all,

I just completed the retirement process. Some stuff is left for infra:
https://issues.apache.org/jira/browse/INFRA-4791

The Zeta Devs will come up here for a vote in a pretty short time.
Trademarks (Shane) has said, once the retirement is complete (and if
all devs agree to it) the guys can held some kind of a vote here to
keep their name.

Cheers
Christian

[VOTE] Release Apache HCatalog 0.4.0-incubating

Alan Gates — 2012-05-11T23:33:25

Hi,

Please vote for releasing Apache HCatalog 0.4.0-incubating.

rc6 for this release has passed a PPMC vote and is now advancing to an IPMC vote.

The PPMC vote thread is at http://mail-archives.apache.org/mod_mbox/incubator-hcatalog-dev/201205.mbox/%3C47EA6ABF-9675-4988-9BE3-5783CD121146%40hortonworks.com%3E

The release is available at: http://people.apache.org/~gates/hcatalog-0.4.0-incubating-candidate-6/

The keys used to sign this release are available in svn at: http://svn.apache.org/repos/asf/incubator/hcatalog/trunk/KEYS

The release tag is: http://svn.apache.org/repos/asf/incubator/hcatalog/tags/release-0.4.0-rc6/

This vote will be open for at least 72 hours.

Here's my +1.

Alan.

[VOTE] Apache Syncope 1.0.0-RC1-incubating / 2nd attempt

Francesco Chicchiriccò — 2012-05-11T15:29:45

I've created a 1.0.0-RC1-incubating release, with the following 
artifacts up for a vote:

SVN source tag ( r1335495):
https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.0-RC1-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-055/

Source release (checksums and signatures are available at the same 
location):
https://repository.apache.org/content/repositories/orgapachesyncope-055/org/apache/syncope/syncope-root/1.0.0-RC1-incubating/syncope-root-1.0.0-RC1-incubating-source.tar.gz
https://repository.apache.org/content/repositories/orgapachesyncope-055/org/apache/syncope/syncope-root/1.0.0-RC1-incubating/syncope-root-1.0.0-RC1-incubating-source.zip

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/incubator/syncope/KEYS

This has been voted through on the syncope-dev< at >incubator.apache.org 
mailing list [1],
and now requires a vote on general< at >incubator.apache.org

Votes already cast (on syncope-dev):

+1 (binding)
* Francescp Chicchiriccò
* Massimiliano Perrone
* Fabio Martelli
* Simone Tripodi
* Colm O hEigeartaigh (IPMC member)


Vote will be open for 72 hours.

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

Best regards.

[1] 
http://syncope-dev.1063484.n5.nabble.com/VOTE-Apache-Syncope-1-0-0-RC1-incubating-5th-attempt-tt5694411.html

DeltaSpike status (Was: [Incubator Wiki] Update of "May2012" by struberg)

Jukka Zitting — 2012-05-10T10:03:27

Hi,

Thanks for the report, DeltaSpike!

On Tue, Apr 24, 2012 at 8:54 PM, Apache Wiki <wikidiffs< at >apache.org> wrote:

Nice list of progress! Keep it up and you'll be graduating in no time.


Note that documentation, while it certainly helps, is not a graduation issue.

About community building, what's your current status in terms of
community activity and diversity?

BR,

Jukka Zitting

VCL status (Was: [Incubator Wiki] Update of "May2012" by aaronpeeler)

Jukka Zitting — 2012-05-10T09:34:56

Hi,

Thanks for the report, VCL! Sounds like you're doing fine.

On Tue, May 1, 2012 at 3:11 PM, Apache Wiki <wikidiffs< at >apache.org> wrote:

Sounds great, good luck with the release.

I notice that your previous release was over a year ago, which
probably explains why this release is so big. Cutting releases more
frequently is a good way to make them more manageable, and doing so
also helps drive adoption as your reaction time to user needs (bug
fixes, improvements, etc.) becomes better.


Based on a quick look around I couldn't spot any obvious graduation
issues, so +1 to moving ahead unless the community or your mentors
feel otherwise.

BR,

Jukka Zitting