The Incubator continues to work reasonably well, with no major issues that
would require direct board attention or assistance.
The downward trend in the number of podlings at the Incubator continues thanks
to the efforts to more actively help podlings towards graduation and to retire
old, inactive podlings. The rate of this change has leveled off a over summer,
but we still graduate or retire some 2-3 podlings while accepting only 1-2 new
podlings on average per month.
Current podlings can be roughly divided in three equal-sized groups based on
the time they've spent in the Incubator: a) less than a year, b) less than two
years, and c) more than two years. Of the podlings reporting this month only
Etch, Isis and NPanday fall into the last group, and we're happy to see at
least Etch and Isis being close to graduation in near future.
o Community
Noah Slater joined the Incubator PMC since our last report.
The following podlings are requesting graduation to an Apache TLP:
- Apache Airavata
- Apache SIS
- Apache Stanbol
The Incubator PMC recommends the board to accept the respective resolutions.
The vote to recommend graduation of the Bigtop podling is in progress.
The following proposal for a new incubating project was accepted:
- Apache Drill
A proposal for a new project called Drill was brought up for discussion.
Only one of the podlings reporting in this month is having trouble with
low levels of community activity; see the NPanday report for details.
The interesting bit here is that just a bit over a quarter ago NPanday
looked like it was just about ready to graduate.
o Releases
The following incubating releases were made since our last report:
- August 16th, 2012: Apache S4 0.5.0-incubating
- August 20th, 2012: Apache Wink 1.2.1-incubating
- August 22nd, 2012: Apache Bigtop 0.4.0-incubating
- August 23rd, 2012: Apache OpenOffice 3.4.1-incubating
- August 24th, 2012: Apache DeltaSpike 0.3-incubating
- September 4th, 2012: Apache OpenMeetings Moodle Plugin 1.4-incubating
- September 6th, 2012: Apache Syncope 1.0.1-incubating
- September 14th, 2012: Apache Bloodhound 0.1-incubating
All the four podlings categorized below as being blocked on graduation
by the lack of an Apache release have been in that state for quite a while.
Ambari and Cordova are just on the verge of their first release, and we've
asked Kalumet and Wave to put more focus on getting a release out.
o Legal / Trademarks
The question of whether Openmeetings can releasing modules for
3rd party products with proprietary or copyleft licenses (LEGAL-147)
is unresolved and currently blocks one of their releases. Clarification
from the legal team on whether such cases can indeed be treated as
platform dependencies would be welcome.
It was noted that the podling status pages do not always have up to
date information about IP clearance. We've tried to put some focus
on this issue during podling reviews.
o Infrastructure
The recent OpenOffice release caused some trouble by contacting
svn.apache.org as a part of the build.
Many of the recent new podlings have opted for Git as their version
control system, which has caused some strain as the relevant infra
processes are still being developed.
-------------------- Summary of podling reports --------------------
Still getting started at the Incubator (4 podlings)
Allura, Blur, cTAKES, Drill
These projects are still getting started, so no immediate progress
towards graduation is yet expected.
Not yet ready to graduate (7 podlings)
No release: Ambari, Cordova, Kalumet, Wave
Low activity: NPanday
Low diversity: Bloodhound, Flex
We expect the next quarterly report of projects in this category to
include a summary of their actions and progress in solving these issues.
Ready to graduate (7 podlings)
Bigtop, Etch, HCatalog, Isis, OpenMeetings, OpenOffice, S4
We expect these projects to graduate within the next quarter.
--------------------
Allura
Allura is forge software for the development of software projects, including
source control systems, issue tracking, discussion, wiki, and other software
project management tools.
Allura has been incubating since June 2012.
Three most important issues to address in the move towards graduation:
1. Move project development to ASF hardware
2. Grow the community
3. Verify distribution rights, esp. with regard to dependencies' licenses
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues at this time
How has the community developed since the last report?
We have had several introductions and discussions among developers and users
on the allura mailing list. We recieved and merged two patches from a
contributor (who isn't a committer). The Bloodhound podling is in a similar
domain as Allura, so we have had some cross-list emails.
How has the project developed since the last report?
All active committers have submitted CLAs and have accounts created. The
software grant for Allura has been submitted. On the mailing list, several
licensing questions have been discussed and resolved how to handle: external
contributions, handling of a non-essential GPL library, and handling of our
ForgeHg tool which has a dependency on the GPL'd mercurial library.
Signed-off-by: rbowen, rgardler
--------------------
Ambari
Ambari is a monitoring, administration and lifecycle management project
for Apache Hadoop clusters.
- Incubating since 30 August 2011.
- ambari-186 merged to trunk
- trunk had roughly 400 commits since last board report
- branch 0.9 has been created to do a release.
- a release vote is currently underway. We hope to be able
to release in a week or two.
- 8 new committers have been contributing steadily since April
(Vikram Dixit, Mahadev, Yusaku, Hitesh, Jitendra, Ramya, Vinod, Varun)
- 4 new Ambari PPMC members added - Mahadev, Ramya, Jitendra and Hitesh
- new branch ambari-666 created for refactoring to make the architecture
more robust and flexible for adding more features in the long run.
Issues that must be addressed before graduation are:
- Making a release
- Attracting users and developers
- Increase diversity of developers outside of Hortonworks
Signed-off-by: ddas, omalley, wave
--------------------
Bigtop
Bigtop is a project for the development of native packaging and stack
tests of the Hadoop ecosystem.
Bigtop entered incubation on June 20, 2011.
Primary issues blocking graduation:
None: the discussion thread on bigtop-dev and bigtop-user produced
a unanimous +1 vote for starting the graduation process.
Issues which Incubator PMC and/or ASF Board might need/wish to be aware of:
Bigtop is about to start the graduation vote
Community development since last report:
Stephen Chu added as a Bigtop committer
Bigtop has developed a very robust and high profile user community:
https://cwiki.apache.org/confluence/display/BIGTOP/Powered+By+Bigtop
Increased number of patches from our new community members
Project development since last report:
- released Bigtop 0.4.0-incubating
- Bigtop 0.3.0 branch is now in active maintenance mode courtesy
of Cos and Bruno
- Bigtop 0.3.1 expected shortly
- Giraph is now supported in Bigtop 0.4.0/trunk branches
- Hue is now supported in Bigtop 0.4.0/trunk branches
- Hama is now supported in Bigtop 0.3.0 branch
- used Bigtop to validate Hadoop 1.0.* RC and Hadoop 2.0.1-alpha RC releases
- used Bigtop to validate HBase 0.92.1 RC
- increased the # and scope of integration tests
Signed-off-by: tomwhite, mnour
--------------------
Bloodhound
Bloodhound is an issue tracker derivative of Trac, with the goal of making
deployment easy, and usage intuitive.
Bloodhound has been incubating since December 2011.
The top three issues that need to be addressed to move toward graduation are:
1. Improve community diversity
2. Lowering the barrier to entry and development
3. Establish a frequent release cycle
Since our last report Bloodhound has had its first release, version 0.1.0-RC1.
This was promptly followed by one external website hosting resources required
during the installation to go offline. At the time of writing this is
unresolved, although a temporary fix has been identified and suggestions for a
more permanent fix have been made.
Our project issue tracking system has now also been upgraded to this first
release of Bloodhound. Predictably the number of issues raised since has risen
significantly since as it exposed many minor shortcomings not obvious
when not used daily.
Conversations have also started on how to highlight issues that potential new
contributors would find engaging and manageable in complexity. This is mainly
to address point 2 of the issues listed above.
Signed-off-by: gstein, jukka
--------------------
Blur
(incubating since August 2012)
Apache Blur is a search platform capable of searching massive amounts
of data in a cloud computing environment.
Issues needing Board/Incubator PMC Attention:
None.
Key Activities:
- Git repo is just now in place - code cloned from Github and updated to
latest revision so the code cleanup (package naming, licensing, etc.)
can now proceed.
- JIRA is active now.
- Mailing lists created.
- Website created and in the process of CMS-ification.
- Public Blur hack sessions/meetups are being held (Mondays) at Near Infinity
with summaries posted on dev list.
Community:
- Issues are being created and worked.
- Subscriptions: users@ - 17; dev@ - 18
Signed-off-by: phunt, cutting
--------------------
Cordova
Apache Cordova is a platform for building native mobile applications using
HTML, CSS and JavaScript. The project entered incubation as Apache Callback in
October, 2011, before changing its name to Cordova.
Cordova is an active community with contributors and committers from many
different backgrounds. The first Apache release is expected to be ready
shortly, after which Cordova should be ready to graduate.
- Tizen code contribution to CordovaJS
- Tizen native code contribution to incubator-cordova-tizen
The following ppl have been nominated for committer status:
- Regis Merlino, Intel
- Christophe Guiraud, Intel
- Paul Plaquette, Intel
- Markus Leutwyler, HP
- Andrew Grieve, Google
- Michal Mocny, Google
- Braden Shepherdson, Google
Graduation concerns:
- source release issues still open for 2.1.0
(But should be closed today! Sept 5)
- official apache release artifacts remain to be verified by a mentor
Signed-off-by: rgardler, jukka, bmargulies
--------------------
cTAKES
cTAKES (clinical Text Analysis and Knowledge Extraction System) is a natural
language processing (NLP) tool for information extraction from electronic
medical record clinical free-text.
cTAKES was voted into the Incubator by the IPMC on Monday, June 11, 2012.
Three most important steps moving towards graduation
- Attract new contributors
- Make at least one cTAKES release
- Get everyone's ICLA on file and start developing code at Apache and using
the infrastructure
Anything required IPMC attention?
Developers are waiting on the SVN load to be completed by INFRA
https://issues.apache.org/jira/browse/INFRA-5079
Community:
We have had additional committers and PPMC members join and are
waiting for one corporate CLA before finalizing the addition
of three more.
We have open JIRA tickets to replace the Bugs tickets we still
had had open on SF.net.
Development:
- We plan to migrate the entire SVN repo from SourceForge to Apache SVN.
(https://issues.apache.org/jira/browse/INFRA-5079) Our goal is to create
an initial 2.6-incubating release after this is done.
- We have received ICLA's from Sunghwan Sohn, Hongfang Liu, Stephen Wu,
Troy Bleeker.
- We began using Apache's Infrastructure (SVN, Apache CMS, Jira,
Mailing Lists)
- The ctakes-dev@ discussions have been active.
Signed-off-by: mattmann
--------------------
Drill
Drill is a distributed system for interactive analysis of large-scale datasets,
inspired by Google's Dremel.
We have just started and have mailing lists and svn up. Git has been delayed
by issues in infra.
Community development is progressing well with several companies offering paid
developers and 90 subscribers to the dev list.
A hackathon in the SF bay area is scheduled. A lunchtime meetup is
scheduled for Boston. Additional meetups in New York and London are in
the planning stages. All such physical meetups will have remote access if
possible (probably not for the lunch) and all will be reported back to the
mailing list to be sure to include those in different places and time zones
can participate.
Graduation is still a distant vision since we haven't got all the basic
mechanics in place yet. The community side of things is going well and the
development of a realistic release looks like it will be moving shortly.
Signed-off-by: tdunning
--------------------
Etch
Etch is a cross-platform, language- and transport-independent framework for
building and consuming network services. The Etch toolset includes a network
service description language, a compiler, and binding libraries for a variety
of programming languages.
Status:
The implementation of the binding-cpp was completed initially. After a
short bug fixing phase we would like to create a new release that include it.
We filed a proposal for the ApacheCon Europe 2012 to present the Apache Etch
features to a wider audience.
The Etch podling voted 6/0/0 to do the graduation to become an Apache TLP.
Currently we prepare a resolution and work out a time chart. The graduation
will start while the next days.
Future Tasks:
- Bug fixing binding-cpp
- General Bug fixing
- Graduation
- Community development
Signed-off-by: rgardler, jukka
IPMC comments:
Ross Gardler: All looks good for graduation. Not the most active of
projects but it it certainly alive.
--------------------
Flex
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop.
Summary: A large community is waiting to see if committer activity will increase
and starting to think about graduating.
Date of entry to the Incubator: December 31, 2011
Top three items to resolve before graduation:
- Get better at resolving issues the Apache Way
- Get more initial committers to commit something
- Make another release with more non-Adobe involvement
Is there anything that the Incubator PMC or ASF Board specifically needs
to address?
There was discussion about letting Flex graduate with the requirement that
one or two mentors remain on the PMC.
Are there any legal, infrastructure, cross-project or personal issues that
need to be addressed? (Are there any stumbling blocks that impede the podling?)
The issue regarding the import of attachments for existing
JIRA bugs remains open (INFRA-4380). It is not critical, but it would be
nice to get this resolved soon.
The PPMC has voted to move from SVN to Git. Having Apache approve read/write
Git repositories would be helpful.
Check that the project's Incubation Status file up to date.
http://incubator.apache.org/projects/flex
What has been done (releases, milestones, etc.) since the last report?
- We released Apache Flex 4.8.0 (incubating).
- OmPrakash Muppirala and Erik de Bruin were added as a committer and
PPMC member due to their work on the installer. Peter Ent and
Gordon Smith from Adobe were also added as committers as they are
shepherding large donations from Adobe.
- Adobe completed the trademark donation.
- Adobe donated the Text Layout Framework, the rest of the Mustella
test suite and signed off on the Falcon compiler donation.
- OmPrakash Muppirala has been leading the development of a tool that
allows IDEs like Adobe Flash Builder to work better with Apache Flex
releases. Justin McLean, Stephen Downs, Roland Zwaga, Tomasz Maciag,
and Erik de Bruin have also contributed to the tool.
- We have accepted several patches from the community to address issues
with our test suite.
- After much discussion, we voted to move from SVN to Git and employ
something known as the Git Branching Model.
What are the plans and expectations for the next period?
- We hope to finalize the release of the installer.
- Adobe will submit the Falcon compiler source
- We will get the test suite stable on Mac desktops and then on Windows
and mobile configurations. This should remove the last excuse for
committers who are afraid to make changes without a validation suite
- We hope to complete the transition from SVN to Git.
Are there any recommendations for how incubation could run more smoothly
for you?
Our mentors continue to be very helpful.
Signed off by mentor: wave, bdelacretaz, bmargulies
--------------------
HCatalog
HCatalog is a table and storage management service for data created using
Apache Hadoop. HCatalog entered Apache incubator in March 2011.
What has the project accomplished since the last report?
- Released version 0.4
- Voted in one new committer
- Received patches from 19 people
In March 2012, HCatalog was identified as having low diversity. With the
addition of the new committer there are now 9 committers from 3 organizations.
Additionally, we have received patches from 19 unique people (including
committers) some of which are outside the committer organizations. We believe
the low diversity issue has either been addressed, or good progress has been
made towards addressing the issue.
What are the top 2-3 things to resolve before graduation?
- Grow the user community. There has been progress in this area with new
users asking questions on the mailing list, receiving patches from an]
increasing number of contributors, and work towards publishing pre-built
artifacts in the Apache repository. We need to continue in this positive
direction.
- Resolve a review process issue that affects our ability to develop new
features. Time between receiving patches and committing has increased to
problematic levels, often causing code rot and contributors extra work to
rebase patches against trunk.
At this time we feel confident in our ability to make progress toward
resolving these issues.
Signed-off-by: gates, wave
--------------------
Isis
Isis is an ALv2 licensed implementation of the Naked Objects pattern. It is
based on contributions of the original Naked Objects Framework along with
a number of sister projects that were developed for the book "Domain Driven
Design using Naked Objects " (pragprog 2009).
Isis was accepted into the Incubator in 2010, September 7th.
Project Development
- Work broadly completed on integrating with JDO/DataNucleus
(in favour of OpenJPA)
- Numerous Enhancements to Wicket viewer
- Internal refactoring to simplify codebase
Community Development
- Several further new correspondents on the mailing list
- Have had four individuals that have contributed patches this quarter
- this is a substantive increase from previous quarters
- maintaining a clone of the SVN codebase on github seems to have helped
- Project (which is part-funding JDO/Wicket development) continues
- expected to run until Dec 2012, with possible extension
- Publicising RestfulObjects spec (as implemented by Isis' RestfulObjects viewer)
- talk given at 1-day conf (DDD10), in Aug
- InfoQ article on Restful Objects published
- Talks on Isis and Restful Objects to be presented at J-Fall conf, in Oct.
- Talk on Isis to be presented at ApacheCon EU, in Nov.
Top 3 Issues to address in move towards graduation
- None; per previous report we want one new committer voted on prior
to graduating
- We currently have three candidates for being new committers. We just need to
do a successful vote for one of these (highly unlikely all three
votes would fail).
- We should then be in a position to vote to graduate
We don't believe that any of these issues requires Board attention.
New Releases
- None in this period
- intention is to release 0.3.1-incubating prior to next report
Signed-off-by: mnour, struberg, mfranklin
IPMC comments:
Matt Franklin (mfranklin):
Good report. Two questions/comments:
- Why not just propose the committers and see what the PPMC thinks?
Is there a reason for waiting?
- The incubator status page needs to be completed. It appears that more
has happened than the page reflects.
--------------------
Kalumet
Apache Kalumet is a complete platform to administrate data center. It covers
the operating system tasks, middleware provisioning, etc. Kalumet entered
incubation in September 2011.
Community Developement:
Most of users are waiting for a first release to jump into Kalumet.
A talk has been submitted to ApacheCon EU. This talk is an introduction to
Kalumet, a presentation of the current features and present the roadmap.
Project Development:
We fixed major bugs:
- KALUMET-42
- KALUMET-40
- KALUMET-39
- KALUMET-38
- KALUMET-23
The Kalumet activity is better now, we did 96 commits on Kalumet.
The Kalumet community is focusing on the documentation, we made good progress
around the documentation (screenshots, etc).
Before Graduation:
- The documentation is the highest priority.
- Once a first documentation is completed, we plan to cut off a couple
of Kalumet releases.
Post Graduation:
- Kalumet scripts. It's the extension of the "software" concept globally
to all Kalumet resources. It will allow users to create custom
deployment/update plan, with a set of fine-grained steps.
- Refactoring of the UI. Currently Kalumet Console uses Echo2 framework.
It's a category B license framework. We plan to refactore the console
to use a new framework.
Web Site/Communication Development:
The website will be updated with the documentation.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of:
None so far.
Signed-off-by: jbonofre, olamy, jukka
--------------------
NPanday
NPanday allows projects using the .NET framework to be built with Apache Maven.
NPanday has been incubating since August 2010.
NPanday has had a lull of activity for several months as all the committers
have had other things occupying their time.
There are still clear goals for what to do next, when someone has cycles to
pursue them: produce a release of the most recent changes, and to better
promote the project among the .NET and Maven communities.
We continue to see occasional questions from users, and occasional patch
submissions, but haven't added a new committer since 20 April 2011.
The last release was on 16 May 2011.
Since the last report, Matthias Wessendorf resigned as a mentor.
Nobody has stepped in to replace him.
The top priorities towards graduation are:
- work out a concrete plan towards graduation in the next quarter
- encourage newer contributors to do so on a continuing basis.
Signed-off-by: dennisl, mfranklin
IPMC comments:
Matt Franklin (mfranklin)
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.
--------------------
OpenMeetings
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.
OpenMeetings entered the incubation on November 12, 2011.
Project status:
- 3 New Committers entered the project:
Stephen Cottham, Alvaro, Bustos Ruiz, George Kirkham
- 2.0 Release was announced at 26.07.2012
- Legal concerns regarding plugins have been raised and resolved,
see [https://issues.apache.org/jira/browse/LEGAL-147]
- Moodle Plugin was released at 04.09.2012 others are currently voting
- GSoC students have successfully completed their projects:
Student Dmitry Zamula: [https://cwiki.apache.org/confluence/display/OPENMEETINGS/Posting+documents+on+the+whiteboard+with+POI]
Student Ankur Ankan: [https://cwiki.apache.org/confluence/display/OPENMEETINGS/Openmeetings+Plugin+for+Zimbra]
Student German Grekov: [https://cwiki.apache.org/confluence/display/OPENMEETINGS/Connection+testing+tool]
There was one extra student that worked on this project even not accepted
by Google/ASF or OCAD. He completed a plugin for ATutor LMS:
[https://cwiki.apache.org/confluence/display/OPENMEETINGS/ATutor+plug-in+installation+and+usage]
Community status:
- new committers see above
- several plugins are available and will follow up soon, some are listed
here [https://builds.apache.org/view/M-R/view/OpenMeetings/]. Plugins
should give also Non-Java guys a chance to contribute.
- Currently discussing the RoadMap for version 2.x and 3.0. Preparing
a DHTML prototype using Apache Wicket. A pure JavaScript interface might
attract more potential contributors.
- after a long period of refactoring having more releases in shorter cycles
might attract more users and potential contributors
- several developers will come to the ApacheCon in Europe to meet and discuss
Why not graduate:
- Not all code released (some plugins missing)
Signed-off-by: yegor, mnour
--------------------
OpenOffice (was OpenOffice.org)
OpenOffice entered incubation 2011-06-13
OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms. Its localizations support
have supported 110 languages worldwide.
Most Important Items To Address Toward Graduation
1. We are discussing the makeup of the future PMC. This will be a slow
process as we digest input from our Mentors. We are separating our
discussion about who should be a PMC member from what makes an ideal
PMC member. The first will remain private for now and the second will
be renewed on ooo-dev.
2. We have begun discussing the Chair.
3. Continue our review of distributed articles to ensure compliance
with ASF policy.
We are working to fulfill graduation requirements in the next quarter.
Issues for IPMC or ASF Board Awareness
No new issues at this time.
In regards to the ooo-private leak reported on our last report. The PPMC
is satisfied with the result. The Board is aware of the result as well.
If this issue needs further discussion please ask on ooo-private.
Community Development/Outreach Progress
There are now 110 committers with 72 of those on the PPMC. Relative to the
last report, that is an increase of 15 committers and a decrease of
3 committers on the PPMC (following an audit to reconcile subscribers to
the ooo-private mailing list).
We have improved to act more as a self organized project to address and
solve project related topics (e.g. forum moderation)
We are putting more effort into addressing trademark and third-party
distribution requests. Ongoing emphasis as to how to accommodate and
track these requests is becoming an important concern.
We are increasing our global reach by recruiting volunteers to help
update and maintain the large set of native language home pages
Because our product is client-centric, we have put additional focus on our
social networking accounts – Google +, Facebook – in collecting feedback
and ideas from our user base.
Project Development Progress
We released Apache OpenOffice 3.4.1 on August 23, 2012. This was primarily
a maintenance release and included:
- Official Source tarballs in English
- Six different client platform convenience install versions in 19 languages
- Software development kit packaging for 5 platforms
- Language packs for 19 languages
- Fixes for 69 bugs and an important security fix
- Over 1.4M downloads the first week.
A summary of downloads for the installs can be found at:
http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline
The build artifacts in this last source release do not strictly follow
guidelines as some fallback downloads of dependencies do access svn.a.o.
This has been fixed in trunk by eliminating the use of svn in all cases.
Testing and implementation of old update service for OpenOffice has been
accomplished. This service is for older OpenOffice clients to identify
updates and, optionally, install an update if available. Older versions
of OpenOffice (3.1 and less) are problematic when we turned these on it
created a DDOS attack on www.apache.org which we regret.
The IBM Symphony code (mentioned in the June report) was brought into svn
in mid-May. There was discussion on the ooo-dev list about how best to
use/integrate this contribution. After some discussion, the community was
most in favor of integrating Symphony aspects into the current AOO base
over a period of time, rather than the reverse.
Community support forums remain popular with users but registration seems
to have stabilized. The ooo-users list also is quite active. As Apache
OpenOffice is a client product, we continue to investigate ways to direct
users to appropriate support venues.
The developer list, ooo-dev, now has more than 440 subscribers and remains
very active.
Signed-off-by: rgardler, jukka
--------------------
S4
S4 (Simple Scalable Streaming System) is a general-purpose, distributed,
scalable, partially fault-tolerant, pluggable platform that allows
programmers to easily develop applications for processing continuous,
unbounded streams of data.
S4 entered incubation on September 26th 2011.
Primary issues blocking graduation:
- growing the community
- verifying the name of the project. See PODLINGNAMESEARCH-10
Community development since last report:
We received contributions from new contributors, including core,
communication layer, deployment framework and command set.
Project development since last report:
We had our first release as part of the incubator, on August 16th 2012:
S4 0.5.0-incubating
Apart from being a major refactoring, this release aims at lowering the
adoption bar by clarifying the API and providing a set of commands for the
development and deployment lifecycle.
We also believe this recent release should encourage adoption and
contributions.
Signed-off-by: phunt, bmargulies
--------------------
Wave
Incubating since: Dec-2010
Description: Wave is a real-time communication and collaboration tool.
Wave in a Box (WIAB) is a server that hosts and federates waves, supports
extensive APIs, and provides a rich web client. This project also includes
an implementation of the Wave Federation protocol, to enable federated
collaboration systems (such as multiple interoperable Wave In a Box instances).
Most important issues are:
- Building up community.
- Extending the features set to match the features of Google Wave.
Community:
One new committee added. Discussions (somewhat stalled) on additional
committers. The next major milestone regarding graduation is to make a
release. The current codebase is not considered mature enough for a
useful release, however, the community is discussing what is required to
make one, both to better understand the licensing status of our
codebase, and as a means to draw in additional developers and thus speed
up development.
Signed-off-by: upayavira, mfranklin
IPMC comments:
Matt Franklin (mfranklin):
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.
--------------------
