This was extracted (@ 2024-03-20 21:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
A wave is a hosted, live, concurrent data structure for rich communication. It
can be used like email, chat, or a document.
Wave has been incubating since 2010-12-04.
Three most important issues to address in the move towards graduation:
1. Appoint members of the PMC
2. Update release procedure
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
There were no relevant events regarding the community in this period.
How has the project developed since the last report?
Some members of community work on side projects - like UI improvements, but overall we had a low level of activity.
How would you assess the podling's maturity? Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
March 2016
When were the last committers or PPMC members elected?
March 2017
Signed-off-by:
[X](wave) John D. Ament
Comments: Reached out to get the dates fixed up. In order to graduate, we have to figure out how to get more activity.
[ ](wave) Upayavira
Comments:
IPMC/Shepherd notes:
Drew Farris (shepherd): Two mentors active. Light activity on the project in
general, some discussion towards graduation a couple months back.
A wave is a hosted, live, concurrent data structure for rich communication. It
can be used like email, chat, or a document.
Wave has been incubating since 2010-12-04.
Three most important issues to address in the move towards graduation:
1. Appoint members of the PMC
2. Update release procedure
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
There were no relevant events regarding the community in this period.
How has the project developed since the last report?
A ToDo list of tasks to reach graduation has been set, and some members are
working on it.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
March 2016
When were the last committers or PPMC members elected?
March 2017
Signed-off-by:
[x](wave) Upayavira
Comments:
Wave continues as a very small scale project. It hovers just under the
threshold of sufficient
participation for graduation, whilst is too active to argue for
retirement.
IPMC/Shepherd notes:
johndament: Considering your comments, are there additional contributors who
you think may make sense to start to invite?
upayavira: perhaps a new mentor might bring something new, but repeated
efforts to draw in new contributors have not brought the kind of interest
the project needs. It remains one active PPMC member below the minimum for
graduation. Any help warmly accepted, even if short term.
A wave is a hosted, live, concurrent data structure for rich communication. It
can be used like email, chat, or a document.
Wave has been incubating since 2010-12-04.
Three most important issues to address in the move towards graduation:
1. Growing community
2. Improving code base
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Pablo Ojanguren has accepted invitation to become committer.
Community is discussing whether it have reached
a sufficient level of stability to consider graduation.
How has the project developed since the last report?
IP clearance got from SwellRT former copyright owners.
In process to plan a release.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
March 2016
When were the last committers or PPMC members elected?
December 2016
Signed-off-by:
[x](wave) Upayavira
Comments:
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Growing community 2. Improving code base Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The community has several new/re-activated contributors and participants across different disciplines since last report. The most significant developments for our community have come about since September. After an open community conference call on Sept 28th, a joint effort between Wave and SwellRT development was initiated. SwellRT API has been tried out by some members of the community and a branch containing the SwellRT code is now in the repository. Discussions are still taking place to determine the full extent of the integration as the projects share a common goal but have side plans as well. SwellRT is a fork of Wave resolving some complexity issues of the Wave code that have prevented community growth and adoption issues. How has the project developed since the last report? Some members of Wave community have tried SwellRT API and some common tasks have been performed, such as: - Cleaned up some obsolete dependencies. - New branch created on wave repo containing a mirror of SwellRT code. - Updated major dependencies and fixed minor bugs, some taken from SwellRT. Date of last release: March 2016 When were the last committers or PMC members elected? February 2016 Signed-off-by: [ ](wave) Christian Grobmeier [x](wave) Upayavira Shepherd/Mentor notes: Upayavira: SwellRT appears to be a useful addition to Wave - it was originally a fork of Wave that has been improved/simplified. The Wave community still needs to handle IP Clearance for the SwellRT codebase.
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Growing community 2. Improving code base. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? - We have ongoing community discussion about how to bring in new developers to ensure sustainability of the project. A votation session has been scheduled (Sept 28th) to decide if Wave's fork Swellrt is brought/merged into Wave. This would bring SwellRT active developers into Wave and it could facilitate use of Wave by new developers thanks to a new API, removing GWT legacy code. How has the project developed since the last report? - Made some code improvements Date of last release: March 2016 When were the last committers or PMC members elected? February 2016 Signed-off-by: [ ](wave) Christian Grobmeier [X](wave) Upayavira Shepherd/Mentor notes: Upayavira: Once more Wave is on the brink of retirement. However, this time, an offer has been made of code from SwellRT, which is a fork of Wave itself, and a concall has been scheduled for interested parties to discuss whether it is a go-er. It is my (limited) understanding that many of the complexity issues in the Wave code that have prevented community development have been resolved in SwellRT. I will watch to see where this goes, if anywhere.
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Growing community 2. Improving code base. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? - We had a few discussions regarding technical developments. How has the project developed since the last report? - Made some code improvements - Introduced GitHub based pull requests as accepted way for change submissions. Date of last release: March 2016 When were the last committers or PMC members elected? February 2016 Signed-off-by: [ ](wave) Christian Grobmeier [x](wave) Upayavira Shepherd/Mentor notes: Upayavira: Wave is a slow moving, but functioning, project. It needs to attract additional developers to focus on attracting new developers in order to be able to exit the incubator.
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Growing community 2. Improving code base. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? - We made our first release. - Elected new committer. - Previously private fork (wiab.pro) opened the source code that includes many improvements that can be integrated back into main project. - Also, there's an active development in additional open source fork (swellrt) that potentially allows us to integrate back important features. How has the project developed since the last report? - Replaced the old ANT build system with a new Gradle one. - Fixed a few bugs - Made a few code improvements Date of last release: March 2016 When were the last committers or PMC members elected? February 2016 Signed-off-by: [x](wave) Upayavira
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Finalizing the first release 2. Growing community 3. Improving code base. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The Wave project put its first release on the Incubator PMC, however, it looks like the review takes a long time and we didn't get any communication back. How has the community developed since the last report? Not much, even though we managed to get a release and proceed with voting. How has the project developed since the last report? There some additional code developments in the process. Date of last release: NA When were the last committers or PMC members elected? July 2014 Signed-off-by: [ ](wave) Christian Grobmeier [x](wave) Upayavira Shepherd/Mentor notes: Upayavira: Firstly, I believe Christian has resigned as a mentor, leaving just myself. As noted above, having struggled for a long time to pass a vote on a release artifact, the Wave PPMC has now done this, and is waiting on the members of the Incubator PMC to step forward and review the release. Please review this release! I myself have deliberately postponed voting, as my involvement at the ASF has not involved much by way of release reviewing.
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. [x](wave) Upayavira [ ](wave) Christian Grobmeier Shepherd/Mentor notes: Marvin Humphrey (marvin): Wave's report was deliberately not signed off by its Mentors. Mentor Upayavira engaged the Wave community about the possibility of retiring. The community preferred to continue; a timeline for making an incubating release was discussed. Upayavira (upayavira): As Marvin observed, I'm doubtful that Wave has the momentum to make any significant change nor to progress towards graduation. The community will need to meet some targets - the immediate one is to make a release before the next board report is due.
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. We are still working on first release. Several votes were attempted, however, we were slowed down due to unfamiliarity with release process and last second technical issues with the code. 2. Need to grow up community. 3. Make effort to lower entrance barrier for new contributors which is pretty high due to steep learning curve. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at this time. How has the community developed since the last report? While people are in general interested in the software - we see traffic on demo servers and bug reports, but we have only limited contribution by new members. How has the project developed since the last report? We had a few votes on the release - each time issues were found and fixed. We are working on a new wiki for the project to allow new contributors a better access to the project information. Also we cleaned up the issues in Jira and categorized them in order to allow potential contributors to find a potential task easier. Date of last release: N/A When were the last committers or PMC members elected? July 2014 Signed-off-by: [X](wave) Christian Grobmeier [ ](wave) Upayavira Shepherd/Mentor notes:
A wave is a hosted, live, concurrent data structure for rich communication.
It can be used like email, chat, or a document.
Wave has been incubating since 2010-12-04.
Three most important issues to address in the move towards graduation:
1. Wave is very close to making its first release. This is the top
priority.
2. The project needs to determine what the next few technical goals are.
3. The project needs to attract more developers and users.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None at this time.
How has the community developed since the last report?
The community has been slow to develop. There are still many people
downloading and using the software, we have seen several bug reports and
questions, but there has not been much contribution by new members.
How has the project developed since the last report?
The code for the release has largely been finalized. We believe that
major legal and technical issues have been overcome. Only a few finals
steps remain. The project believes that we are finally ready to make a
release.
Date of last release:
N/A
When were the last committers or PMC members elected?
July 2014
Shepherd/Mentor notes:
Christian Grobmeier:
The mentors have missed to sign this report last time. For that reason I
am adding it again. Since last month there was some discussion on how to
prevent the project going to the attic.
Upayavira:
We have received a GSoC application, and a committer has accepted the
role of mentor. The task involves simplification of the codebase which
will make it more accessible to others, hopefully facilitating greater
involvement, as it seems the greatest impediment to Wave is the
(over)complexity of its codebase.
Signed-off-by:
[X](wave) Christian Grobmeier
[X](wave) Upayavira
A wave is a hosted, live, concurrent data structure for rich communication.
It can be used like email, chat, or a document.
Wave has been incubating since 2010-12-04.
Three most important issues to address in the move towards graduation:
1. Wave is very close to making its first release. This is the top
priority.
2. The project needs to determine what the next few technical goals are.
3. The project needs to attract more developers and users.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None at this time.
How has the community developed since the last report?
The community has been slow to develop. There are still many people
downloading and using the software, we have seen several bug reports and
questions, but there has not been much contribution by new members.
How has the project developed since the last report?
The code for the release has largely been finalized. We believe that
major legal and technical issues have been overcome. Only a few finals
steps remain. The project blieves that we are finally ready to make a
release.
Date of last release:
N/A
When were the last committers or PMC members elected?
July 2014
Signed-off-by:
[ ](wave) Christian Grobmeier
[ ](wave) Upayavira
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Making release. 2. Growing community. 3. Source fixes/improvements. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? After some spike in activity we had a slowdown. How has the project developed since the last report? Some improvements were committed like full text search with Solr and some more need to be reviewed/merged. We are working on making an updated RC and plan to hold review/voting soon. Date of last release: not yet. When were the last committers or PMC members elected? No Signed-off-by: [X](wave) Christian Grobmeier [ ](wave) Upayavira
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Make a release. 2. Grow community. 3. Develop new feature/fix bugs. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? A new committer joined us. There has been increased activity from existing members, and we have started receiving patches from a new developer. How has the project developed since the last report? Work has continued on generating our first release. We are now testing out RC6 - after RC5 failed due to a couple of missing licenses, and a bug in the MongoDB implementation. In the mean time, development work on the main branch has added profiling support, JDK 7 support, Solr as a search backend, and various bugfixes. Date of last release: No release yet. When were the last committers or PMC members elected? July 2014 - Andrew Kaplanov Signed-off-by: [X](wave) Christian Grobmeier [ ](wave) Upayavira
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Make a release 2. Expand the community 3. Decide on a future path (whether we are continuing?) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? There has been no major development. A new user reported a regression on master compared to the last release candidate, but overall the project has been very quiet this last quarter. How has the project developed since the last report? Some maintenance work has been committed from new developers, this replaced Socket.IO with Atmosphere. A few other minor fixes for different aspects (gadgets, build system) have been committed. Date of last release: N/A When were the last committers or PMC members elected? 30th June 2013. Signed-off-by: [X](wave) Christian Grobmeier [ ](wave) Upayavira
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Make a release 2. Expand the community 3. Decide on future path (application framework, or web application) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? Around the time of the last report, there was discussion on the list about shutting down the project due to a lack of activity. Since then, we have had 3 new developers submit patches adding new features to Wave, pointing out bugs, and picking up older features that stalled before completion. How has the project developed since the last report? Several major patches adding support for MongoDB, full text search, and date filtering to Wave have been submitted for review. Some of the older ideas (e.g. the email bridge robot) have been picked up by new developers. Date of last release: N/A When were the last committers or PMC members elected? The last 2 committers were elected around 30th June 2013 Signed-off-by: [X](wave) Christian Grobmeier [X](wave) Upayavira
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Make the initial release 2. Extend the community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? The community is in a relatively quiet state. There's is a certain amount of interest in the project but seems like steep learning curve along with tightly coupled client-server architecture poses obstacles for new developers to begin actively contributing. How has the project developed since the last report? Mainly worked on the next release candidate and sorting out related legal issues. Date of last release: Not yet When were the last committers or PMC members elected? The last 2 committers were elected around 30th June 2013 Signed-off-by: [X](wave) Christian Grobmeier [X](wave) Upayavira Shepherd notes: Christian Grobmeier (grobmeier): It was discussed to end graduation because lack of momentum, which led to a lot of emails. So far there are a couple of people around but to less who do actual coding work. It was discussed briefly to push development via a Kickstarter project. So far there is no outcome of the discussions.
Wave is rich, web-based, distributed, collaboration platform that allows users to interact in near real time. The wave platform includes a web-based user interface containing an rich-text. The system is extendable though widgets, robots, and editor doodads. The Wave In a Box implementation is developed in Java using a variety of web technologies such as Websockets, Javascript, GWT, and supported by an operational transform based conflict resolution algorithm. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Make the initial release 2. Extend the community 3. Decide on the future of the existing codebase Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at this time. How has the community developed since the last report? Following the busyness noted in the last report, the community has since returned to a relatively quiet state. Last month, a second public discussion (on Hangouts) was held, to extend Wave's public image. Some experiments using volunteers from the community, to test out possible changes to the OT algorithm, have been planned. How has the project developed since the last report? Following on from 0.4-RC3 being rejected at the Incubator list. Work on 0.4-RC4 has been completed (albeit fairly slowly), with a request for review for RC4 posted to the Wave-dev list only a few days ago. This addressed the remaining licensing problems, and merged in some of the trunk development that had occurred in the meantime (new translations, federation fixed). Some questions have been asked about the future of the existing codebase beyond the 0.4 release, with a rewrite looking preferred if enough development time can be secured. Date of last release: N/A. When were the last committers or PMC members elected? The last 2 committers were elected around 30th June 2013. Signed-off-by: [X](wave) Christian Grobmeier [ ](wave) Upayavira Shepherd notes: Mentor notes: Ben Laurie and Vincent Siveton have stepped down as Mentors, leaving the project with two active mentors. Currently this is not an issue. (christian)
Wave is rich, web-based, distributed, collaboration platform that allows users to interact in near real time. The wave platform includes a web-based user interface containing an rich-text. The system is extendable though widgets, robots, and editor doodads. The Wave In a Box implementation is developed in java using a variety of web technologies such as Web Sockets, Java Script, GWT, and supported by an operational transform based conflict resolution algorithm. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Finish the initial release 2. Continue increasing the community size 3. Improve documentation for new users Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at this time. How has the community developed since the last report? The last month has seen significantly increased activity on the mailing list regarding long-term visions on where the Wave project should be heading, with an influx of new people (mostly as potential users) discussing how they can help the project. At one of their suggestions, a public discussion was held to help with Wave's publicity, with the aim to bring more people to the project. How has the project developed since the last report? Much progress has been made towards an initial release (named 0.4), with RC2 and RC3 having votes on the wave-dev list. RC3's vote ends on the 8th June and is looking likely to be submitted for a vote on the general incubator list within the next few days. Meanwhile development has continued on the trunk, receiving 5 review requests with the last week from 3 different people (2 new to the project). The documentation has also seen work, with 3 people have been granted wiki access to help. Date of last release: N/A Please check this [X] when you have filled in the report for Wave. Signed-off-by: Santiago Gala: [ ](wave) Upayavira: [X](wave) Andrus Adamchik: [ ](wave) Vincent Siveton: [ ](wave) Ben Laurie: [ ](wave) Shepherd notes: The report is very accurate and Wave is actually ways more active than before. All ideas of moving it to the attic/github should be delayed, as the project might have a chance to succeed, if the activity persists. From the mentors, only Upayavira is active. Not heard of any of the others the past period. (grobmeier)
A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Make a release (stalled). The licensing issues have been resolved, and build scripts have been put into the repository. Documentation (see 2) is missing, after which point we can finalize a commit suitable for release. 2. Improve documentation. This is currently scattered between the old WaveProtocol site, the mailing list, and elsewhere. It needs to be pruned (of no-longer relevant documentation), structured and put on the wiki. 3. Increase community size. We are lacking any contributors who are able to make/support large code changes at the moment. A release should help increase wider knowledge of the project, to hopefully bring in more development support. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at this time. (Though see Shepard's notes). How has the community developed since the last report? The mailing list traffic continues to consist of new people asking questions about setting-up/running a WIAB server. (Which could be resolved by #2). Other than that, mostly stagnation. How has the project developed since the last report? Some progress towards a release (licensing) has been made. Internationalization support has been added. Signed-off-by: Santiago Gala: [ ](wave) Upayavira: [ ](wave) Andrus Adamchik: [ ](wave) Vincent Siveton: [ ](wave) Ben Laurie: [ ](wave) Christian Grobmeier: [X] (Note: I am NOT a mentor, but i follow the project and due to timing issues I would like to confirm this report) Shepherd notes: grobmeier: The project is very silent with less commit activity (last commit before 5 weeks). Even when the committers are usually responsive on mailing-lists it is very clear that nobody there can spend enough time to actually drive Wave forward. The next weeks the question needs to be asked if the Incubator goals can ever be reached or if GitHub would be a better home for Wave. A new committer has been elected before a couple of months but the situation didn't change. The missing project report does unfortunately reflect the situation. From Mentor side of view, only Upayavira is actively and constructively contributing to the project. Actually the other mentors should be asked if they are still interested in mentoring Wave.
Wave is rich, web-based, distributed, collaboration platform that allows users to interact in near real time. The wave platform includes a web-based user interface containing an rich-text. The system is extendable though widgets, robots, and editor doodads. The Wave In a Box implementation is developed in java using a variety of web technologies such as Web Sockets, Java Script, GWT, and supported by an operational transform based conflict resolution algorithm. Wave has been incubating since December of 2010. * Three most important issues to address in the move towards graduation. 1. Performing an initial release (currently in progress). We have started the release process, but it has stalled. We were first dealing with the large amount of files with incorrect copyright headers. That has been largely overcome. However we are still struggling with the possible need to obfuscate third party jars with less than compatible licenses. The technical and legal implications of this still need to be addressed. 2. Updating the web site and online documentation. The web site does not have very much useful information on it. Most Information is scattered on the old google-code and waveprotocol.org sites. Prospective users and developers are constantly asking for where the documentation is. 3. Increasing developer / community contributions. While we are making progress in this area, we need more contributors. We believe that taking care of #1 and #2 will help with this. Building an active community is difficult, but very important. * Issues for the PMC / ASF Board None at this time. * How has the community developed since the last report The community has added two new committers in that last several months (Ali Lown and Vicente J. Ruiz Jurado). Additionally, we have seen an increase in the number of code reviews and mailing list traffic. * How has the project developed since the last report. Several Jira issues have been resolved and a few enhancements have been made. We are making progress towards an initial release. Signed-off-by: Upayavira IPMC comments: rgardler: the confusing note about "obfuscating binaries" in the Wave report was picked up by Benson and taken to the project and IPMC lists. It seems to be cleared up now. It was a matter of weak-copyleft build-time dependencies. It looks like the term "obfuscate" is incorrectly used in this context, but the community is now set to move forwards.
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 committer 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.
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: Full text search, Archiving/Folders, Tags. Community: The mailing lists activity is stable and judging by questions on the mailing list - WIAB is already being used by private organizations and persons. There are also several commercial/open applications based on WIAB, like co-meeting.com and kune.cc. Jira Activity: - 18 new issues opened since last report. - 11 issues resolved since last report. Commits: - 30 commits to SVN. Project development: Upgraded the search implementation to use Lucene index instead of in-memory map. Upgraded "Add Gadget popup" - now it allows to search gadgets by name/description and also to filter by categories. Added more gadgets to the Gadget Gallery - now it includes about 75 definitions of gadgets supported by Wave. Some more small improvements and bug fixes. Some more developments not yet finished but in progress: - Migration to Maven - Full text search Signed off by mentor: Upayavira Shepherd: Ross Gardler - What is missing is new committers (none voted in since entering the incubator) and a release (none made yet). However the report does not address these two items.
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. - Bug fixes. Community: The Wave project attracted significant interest recently - probably caused by Google Wave becoming read only. The activity levels on the mailing list are increasing constantly, as well as number of contributors. Project development: - Added waves import from Google Wave. - Added SSL server capabilities. - Bug fixes + improved stability. - Some improvements to UI. There are more features soon to be added to Wave in the review process. Signed off by mentor:
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. Community: There's a stable levels of community activity around development of Wave in a Box (WIAB). Also, there are a number of WIAB based projects like Kune and CollaDi with their maintainers taking active role in discussions and development. Project development: - Migrated the code to Apache SVN. - Updated to a new version of Jetty server. - Reduced the memory footprint of WIAB. - Bug fixes + small improvements.
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: * Migrate source code from code.google.com to SVN. * Building up community. Community: The community shows stable levels of activity. Project development: - The migration of the source code was delayed due to technical issues of migrating Mercurial repository from Google Code to Apache SVN without loosing history. After some discussion we decided to move the code to Apache infra by 28th September 2011 even if that would require a clean check in without history. - About 26 commits with improvements and bug fixes.
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: * Migrate source code from code.google.com to SVN. * Building up community. Community: The community shows stable levels of activity. Project development: - The migration of the source code was delayed due to technical issues of migrating Mercurial repository from Google Code to Apache SVN without loosing history. After some discussion we decided to move the code to Apache infra by 28th September 2011 even if that would require a clean check in without history. - About 26 commits with improvements and bug fixes.
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). Incubating since: Dec-2010 Most important issues are: * Migrate source code from code.google.com to SVN. * Bug fixes and scaling/enhancing stability in preparations toward 1.0 version. * Implement WIAB functionality to import waves (deltas) from Google Wave Community: The Wave in a Box community exhibits a stable even if slow growth. The mail list stays very active, new contributors emerge every month, WIAB demo servers show constant growth both in active users and topics discussed. Project development: - Issues migrated to the ASF Jira - Introduction of "shared per domain waves" - Improvement of search functionality performance. - Using Guice for servlet injection - which should facilitate using WIAB modules for 3-rd party developers. - User and admin password robot agents. - Remote logging of client errors. - Numerous important enhancements to the client side architecture. - about 40 more changes and bug fixes.
Wave 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 WIAB instances). Recent activities: * Elected a new committer, Yuri Z * Project web site infrastructure (CMS, SVN) set up and Apache web site created * SVN, Jira, and review board are set up (but nothing imported yet) * New demo instance waveinabox.net:9898 deployed * Lots of mailing list traffic in February: 191 posts from over 40 people * And lots of code: 26 patches committed, 15 bugs closed * Enabled persistent storage of waves * Basic client/server search protocol * Google Wave search UI implemented with client-side optimistic digests Most important issues are: * Migrate source code and issues from code.google.com to SVN and Jira * Finish implementation of indexing and improved client-server protocol * Implement WIAB functionality to import waves (deltas) from Google Wave
Wave lets you communicate and collaborate in real time. Wave in a Box project lets developers and enterprise users run wave servers and host waves on their own hardware. Recent activities: * Old Google Groups mailing list has been disabled * SVN Repository has been created, code not migrated yet * Jira has been created, issues not migrated yet * Confluence space has been created for project documentation * All (bar two) Wave committers got the Apache accounts * The implementation of search is well under way * First cut of persistence has been tested and reviewed Most important issues are: * Finish building website and wiki on apache.org * Migrate source and issue tracking to SVN and Jira * Finish implementation of persistence, search/indexing, improved client-server protocol
Wave a real-time communication and collaboration tool Wave entered incubation on December 12, 2010. We're currently in the process of moving to Apache infrastructure. Mailing lists and continuous build have moved, source, issues and documentation has not. On the technical side, the Wave in a Box system needs completed persistence and search/indexing implementations, import from Google Wave, and improvements to protocols and documentation thereof. Most important issues are: * Build website and wiki on apache.org * Move source and issue tracking to apache.org * Finish implementation of major outstanding items: persistence, search/indexing, protocols