What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2017-02-27 | Appointed Cédric Damioli | the board, by resolution |
| 2012-11-21 | Appointed Thorsten Scherler | the board, by resolution |
| 2011-08-17 | Appointed Simone Tripodi | the board, by resolution |
| 2008-05-21 | Appointed Vadim Gritsenko | the board, by resolution |
| 2006-05-24 | Appointed Reinhard Pötz | the board, by resolution |
| 2004-06-23 | Appointed Sylvain Wallez | the board, by resolution |
| 2003-05-21 | Appointed Steven Noels | the board, by resolution |
| 2003-01-22 | Appointed Stefano Mazzocchi | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2025-01-15 | Terminate the Apache Cocoon Project | special order | approved |
| 2003-01-22 | Creation of the Apache Cocoon Project | special order | no outcome recorded |
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Project Status: Current project status: Considering moving to the Attic Issues for the board: none. ## Membership Data: Apache Cocoon was founded 2003-01-22 (22 years ago) There are currently 80 committers and 34 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Christofer Dutz on 2024-01-30. - No new committers. Last addition was Christofer Dutz on 2023-05-10. ## Project Activity: No recent activity, the Attic vote has passed, we now have to process due tasks. ## Community Health: Now that the Attic vote has passes, the heartbeat is obviously very low. As reminded last quarter, we have to officially inform the users list of the termination of the project
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Project Status: Current project status: Considering moving to the Attic Issues for the board: none. ## Membership Data: Apache Cocoon was founded 2003-01-22 (22 years ago) There are currently 80 committers and 34 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Christofer Dutz on 2024-01-30. - No new committers. Last addition was Christofer Dutz on 2023-05-10. ## Project Activity: Almots no activity past quarter. Ongoing renewed discussions about Attic. ## Community Health: Despite the project is dormant, there's still people around to answer every thread. Nevertheless this is not sufficient to maintain a software project.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache Cocoon was founded 2003-01-22 (21 years ago) There are currently 80 committers and 34 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Christofer Dutz on 2024-01-30. - No new committers. Last addition was Christofer Dutz on 2023-05-10. ## Project Activity: Very quiet this quarter. It seems that the Git migration will actually take place in the following days. There's also a new interest for experimenting the Cocoon principles in the industrial area. ## Community Health: The current PMC chair has expressed its will to step down. We now have a candidate so we will begin the vote.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Project Status: Current project status: Dormant/At risk Issues for the board: Issues for the board: none. ## Membership Data: Apache Cocoon was founded 2003-01-22 (21 years ago) There are currently 80 committers and 34 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Christofer Dutz was added to the PMC on 2024-01-30 - Torsten Curdt was added to the PMC on 2024-01-30 - No new committers. Last addition was Christofer Dutz on 2023-05-10. ## Project Activity: Statistically, the project seems to be in good shape, with 2 new PMC members, a new release less than 3 months ago, and the declared will to move on with a Git migration ## Community Health: It's still hard to have active PMC members. The current chair has expressed its will to step down a month ago, but so far there's no volunteer to replace him.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Project Status: Current project status: At risk / Considering moving to the Attic Issues for the board: Issues for the board: none. ## Membership Data: Apache Cocoon was founded 2003-01-22 (21 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers. Last addition was Christofer Dutz on 2023-05-10. ## Project Activity: Thanks to Christofer, a 2.3.0 release is on its way, but currently lacks 3 PMC members to review and vote. ## Community Health: The general consensus was to finally release the 2.3.0 and then consider moving to the Attic. The release vote did not receive 3 +1 votes yet A message has been posted to dev@ to explain the current status. We hope to be able to positively end the current release cycle and then probably properly submit the Attic vote.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Project Status: Current project status: Dormant. Issues for the board: none. ## Membership Data: Apache Cocoon was founded 2003-01-22 (21 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers. Last addition was Christofer Dutz on 2023-05-10. ## Project Activity: We've recently committed some pending changes. We hope to be able to release anytime soon. ## Community Health: We hope to be able to finalize the current 2.2.x release cycle, and then certainly reopen the discussion about going to the Attic or not.
No report was submitted.
No report was submitted.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (20 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - Christofer Dutz was added as committer on 2023-05-10 ## Project Activity: Thanks to Christofer's help, we hope to be able to release anytime soon. This would end the current security fix cycle begun 6 months ago. ## Community Health: Right after the release, if we manage to do it, we will certainly have to decide if and when properly end the good old Cocoon project and get it to the Attic.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (20 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: There are three security issues concerning the 2.2 branch. We managed to fix them and then wanted to make a release, 9 years after 2.2.0. But the release process is too old, too complex, relying on obsolete or unexisting tools, so at the time of this board report, we didn't manage to complete the process. ## Community Health: Due to our inability to even complete a release process of one of our two main branches, some PMC members initiated a poll to measure the PMC ability to maintain the project. The result is that, even probably complying with the 3-committers threshold, there are not enough active PMC members to maintain both branches. We have to discuss further about the next steps.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (20 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: Very slow activiy this quarter. We'll certainly have to release a new Cocoon 2.2 version in the following weeks, which has not been done since more than 8 years ! ## Community Health: A very recent thread on private list show that there's still PMC members around able to handle quickly any urgent matter.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (20 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: 2.1.13 was released on 2020-07-29 2.1.12 was released on 2013-03-14 ## Community Health: The project is mainly in maintenance mode. Low but not null traffic during summer.
No report was submitted.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (19 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: 2.1.13 was released on 2020-07-29 2.1.12 was released on 2013-03-14 ## Community Health: The project is in maintenance mode. As usual, low but not null activity on both user and dev lists.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (19 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: 2.1.13 was released on 2020-07-29 2.1.12 was released on 2013-03-14 ## Community Health: There was a XXE security hole reported in January that the PMC decided to actually not consider as an issue. The reporter has yet to be answered.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (19 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: Still low activity, no commits, but some discussions on lists. ## Community Health: Interestingly, there was a thread on users list mentioning a possible future release of the 2.2 branch
No report was submitted.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (19 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: Still low activity, no new commits or issues last quarter. ## Community Health: Interestingly, despite very low dev activity, there was a few threads on the users list with quick answers from commiters.
No report was submitted.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (18 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: 2.1.13 was released on 2020-07-29. Since then, only really low activity. ## Community Health: Even if the project is in maintenance mode with low activity on both dev and users lists, we still see active users on the project.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (18 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: Since the release this summer, almost no activity on the projet, which is back on maintenance track. ## Community Health: Very low traffic this quarter, no bug fix nor commits. To be monitored in the future.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (18 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: Since the release this summer, not much activity on the projet. It's back on its maintenance track. We've also completed the handling of a XXE vulnerability discovered by a 3rd party. ## Community Health: After a renewed interest due to the ongoing release process last quarter, the list traffic has obviously strongly decreased.
No report was submitted.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (18 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: 7 years after last release, we finally managed to release Cocoon 2.1.13 with about 20 fixes. ## Community Health: The recent 2.1.13 release process has brought a renewed activity on mailing lists.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (17 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: The project is mainly in maintenance mode. The most recent release is 2.1.12 on 2013-03-14 ## Community Health: There was almost no visible activity in the last quarter, but there's still active PMC members around here. Writing this board report has actually be the opportunity to start a thread on the PMC list about the opportunity to continue the project or move to the Attic, and if so, to start a new release process, 7 years after the previous one.
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (17 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: I don't really understand why the report last month was flagged as 'minimal' and 'last-minute report'. The report was approved by the PMC and IMHO there was nothing more to say. Project's activity is obviously low, but answers are given quickly when required. The most recent release is 2.1.12 on 2013-03-14 The project is mainly in maintenance mode. ## Community Health: Still very few activity on the project. Still active PMC members around here. There was some activity on users list showing that the branch 2.2 is still in use, while all activity was previously mainly on branch 2.1
## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (17 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: The most recent release is 2.1.12 on 2013-03-14 The project is mainly in maintenance mode. ## Community Health: Still very few activity on the project. Still active PMC members around here. There was some activity on users list showing that the branch 2.2 is still in use, while all activity was previously mainly on branch 2.1
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: Still very few activity on the project. Still active PMC members around here. Question on dev list showed that there is still someone to answer (quickly). An email to users@infra.a.o about our git mirror remains unanswered. The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report. A little activity on both users and dev mailing-lists, even if still at a low level. The project is mainly in maintenance mode. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: Still very few activity on the project. Last report was followed by the board questioning us being somewhat dormant. As usual, this question is actually fair regarding the activity, and as usual, many PMC members (8 IIRC) answered they're still there. The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report. A little activity on both users and dev mailing-lists, even if still at a low level. The project is mainly in maintenance mode. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: There are no issues requiring board attention at this time ## Activity: Last quarter report and board's heads up from the previous one gave us the opportunity to work on a few issues. All pending activity seems now to have been resolved. Following recent discussions on private list, we now have to decide what to do with our several branches. The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report, but more than previous quarters. A little activity on both users and dev mailing-lists, even if still at a low level. The project is mainly in maintenance mode. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: Thanks Brett for the heads up last month. I (Cédric) have indeed several times thought about making a release, but never found enough time. It happens that I recently found a bug that I want to be fixed, so this will push me to move forward ! The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report. A little activity on both users and dev mailing-lists, even if still at a low level. The project is mainly in maintenance mode. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report. A little more activity on both users and dev mailing-lists, even if still at a low level. The project is mainly in maintenance mode. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report. A little activity on both users and dev mailing-lists, in any case more than the previous quarter. The project is mainly in maintenance mode. Last board feedback asked if there are at least 3 active PMC members. Following discussion shows that the answer is positive. Last board report, back in May, was the opportunity to gather metrics about Cocoon usage. It appears from maven statistics that we still have 60k downloads per month. A PMC member also pointed to INFRA-15406 which may provide a way to have download statistics for non-Maven artifacts. We still have to figure out how to use them. I also proposed to cut a 2.1.x release, but haven't yet found the time to do it. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report. A little activity on both users and dev mailing-lists, in any case more than the previous quarter. The project is mainly in maintenance mode. Last board feedback was the occasion to have a small discussion between PMC members on the opportunity/interest to move to the Attic. It seems that the time has not yet come, but it's true that the activity keeps being low. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: The most recent release is 2.1.12 on 2013-03-14 No JIRA issues opened nor resolved since last report. There's only a little activity on both users and dev mailing-lists (a question was asked on the users list and answered by a committer). The project is mainly in maintenance mode. There have been some quite interesting changes since last release, at least for 2.1 branch, which would deserve a release. We issued the same statement last quarter but noone launched the process yet. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: The most recent release is 2.1.12 on 2013-03-14 2 JIRA issues opened and resolved since last report. There's only a little activity on both users and dev mailing-lists (a dozen messages during the period). The project is mainly in maintenance mode. There have been some quite interesting changes since last release, at least for 2.1 branch, which would deserve a release. We issued the same statement last quarter but noone launched the process yet. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened since last report There's only a little activity on both users and dev mailing-lists. There was a final point given to an old security report (rejected as a security issue by the PMC). There have been some quite interesting changes since last release, at least for 2.1 branch, which would deserve a release. The last board feedback recommanded us to plan a release. This is definitely something we should think about, for each of our 3 branches, 2.1.x, 2.2.x and 3.x ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: Following the step down of Thorsten, the PMC voted for nominating Cédric Damioli as PMC chair. ## Activity: The same activity report than the last quarter apply here: The most recent release is 2.1.12 on 2013-03-14 No JIRA issues opened nor resolved since last report No commits since last report There's only a little activity on both users and dev mailing-lists. There have been some quite interesting changes since last release, at least for 2.1 branch, which would deserve a release. In the last board report, there was concerns about the low activity and the community health. The project is actually in a very quiet state, in that there's almost no development activity, only bug fixes, but the project itself is very stable and mature and still used, according to a recent PMC discussion. The discussion about the future of the project periodically reappears, and it seems that up to now, the community is still fine with the current status. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: Following the step down of Thorsten, the PMC voted for nominating Cédric Damioli as PMC chair. ## Activity: The most recent release is 2.1.12 on 2013-03-14 No JIRA issues opened nor resolved since last report No commits since last report There's only a little activity on both users and dev mailing-lists. There have been some quite interesting changes since last release, at least for 2.1 branch, which would deserve a release. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
## Description: Web development framework: separation of concerns, component-based. ## Issues: We are currently in the process of choosing a new PMC chair. The community will also be asked if it's time for the project to go to the Attic. ## Activity: The most recent release is 2.1.12 on 2013-03-14 2 JIRA issues opened since 2016-10-01 3 JIRA issues resolved since 2016-10-01 11 commits since 2016-10-01 There's only a little activity on both users and dev mailing-lists. There have been some quite interesting changes since last release, at least for 2.1 branch, which would deserve a release. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06
No report was submitted. @Mark: pursue a report for Cocoon
No report was submitted.
Web development framework: separation of concerns, component-based. Issues needing board attention: None. Changes in the PMC membership: None. Most recent addition: 2012-07-06 New committers: None. Most recent addition: 2012-07-06 General status: The most recent release is 2.1.12 on 2013-03-14 Since then there have been some changes, but it will need someone to initiate the release process. There has not been anyone with sustained activity to be considered as a potential new committer/PMC member. However there are some people on the dev list that resurface occasionally, so they could be encouraged. There are also some regulars on the users list that could be encouraged. There was some activity on the users mail list. Two major topics, which did have users helping each other, and one PMC member assisting. There was only a little activity on the dev mail list. About ten PMC members were present during the quarter. This confirms that there are sufficient people hanging around for us to potentially be able to make a decision or encourage new contributors. However it is a little worrying that no-one responded to this draft report. The Cocoon chair has been absent and not attending his duties in a timely manner since the beginning of the year. I take the consequences and will step down to leave room for someone that can attend the project as it should be. Progress of the project: A committer added some features to 2.1 regarding XMLResourceBundles and i18n.
No report was submitted.
Web development framework: separation of concerns, component-based. Issues needing board attention: None. Changes in the PMC membership: None. Most recent addition: 2012-07-06 New committers: None. Most recent addition: 2012-07-06 General status: The most recent release is 2.1.12 on 2013-03-14 Since then there have been some changes, but it will need someone to initiate the release process. There has not been anyone with sustained activity to be considered as a potential new committer/PMC member. However there are some people on the dev list that resurface occasionally, so they could be encouraged. There are also some regulars on the users list that could be encouraged. There was some activity on the users mail list. Two major topics, which did have users helping each other, and one PMC member assisting. A user notified about a look-alike Cocoon logo. We followed up on the private mail list. There was only a little activity on the dev mail list. About ten PMC members were present during the quarter. This confirms that there are sufficient people hanging around for us to potentially be able to make a decision or encourage new contributors. However it is a little worrying that no-one responded to this draft report. The Cocoon chair seems to be not available for this report. Progress of the project: A committer added some features to 2.1 regarding XMLResourceBundles and i18n.
## Description: Web development framework: separation of concerns, component-based. ## Issues: none ## Activity: Last release was 2.1.12 on Thu Mar 14 2013 and last PMC addition was on Fri Jul 06 2012. The reactions on our last draft board report on the private list have shown that we are still fully running. The ticket INFRA-10458 for a "Replacement VM for cocoon.zones.apache.org" is resolved, thank you infrastructure. There had been a couple of question on the user list which different user and committers attended. ## PMC changes: - Currently 32 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Javier Puerto on Fri Jul 06 2012 ## Committer base changes: - Currently 80 committers. - No new changes to the committer base since last report. ## Releases: - Last release was 2.1.12 on Thu Mar 14 2013 ## Mailing list activity: - users@cocoon.apache.org: - 388 subscribers (down -3 in the last 3 months): - 20 emails sent to list (1 in previous quarter) - dev@cocoon.apache.org: - 235 subscribers (down -1 in the last 3 months): - 3 emails sent to list (51 in previous quarter) - cvs@cocoon.apache.org: - 70 subscribers (up 1 in the last 3 months): - 1 emails sent to list (23 in previous quarter) - docs@cocoon.apache.org: - 82 subscribers (down -6 in the last 3 months): - 2 emails sent to list (0 in previous quarter)
## Description:
Web development framework: separation of concerns, component-based.
## Issues:
none
## Activity:
Last release was 2.1.12 on Thu Mar 14 2013 and last PMC addition was on
Fri Jul 06 2012.
The reactions on our last draft board report on the private list have
shown that we are still fully running as a project and therefore I did
not started a discussion whether to move to the attic or not.
Most recently there is some effort to update cocoon 2.2 with Java 8 and
Spring Framework 4.2, some pmc member and as well some devs are getting
involved in the discussion. Further we have setup a jenkins job to build
the 2.2 branch.
Further Francesco Chicchiriccò has opened a ticket INFRA-10458 for a
"Replacement VM for cocoon.zones.apache.org". He asked on our list if
for more people wish to have access but got no response.
Project status:
* 3+ people have indicated presence, so has sufficient oversight.
## PMC changes:
NONE
- Currently 32 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was on Fri Jul 06 2012
## Committer base changes:
NONE
- Currently 80 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 2.1.12 on Thu Mar 14 2013
## Mailing list activity:
- users@cocoon.apache.org:
- 391 subscribers (down -3 in the last 3 months):
- 1 emails sent to list (2 in previous quarter)
- dev@cocoon.apache.org:
- 236 subscribers (down -1 in the last 3 months):
- 51 emails sent to list (10 in previous quarter)
- docs@cocoon.apache.org:
- 88 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- cvs@cocoon.apache.org:
- 69 subscribers (up 0 in the last 3 months):
- 23 emails sent to list (2 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
## Description:
Web development framework: separation of concerns, component-based.
## Activity:
As you can see from the statics there had been close to nothing in
activities. Francesco deleted old releases and there were a question
that had not been a single reply. However the draft of this report
got 5 positive pmc votes meaning we are still fully functional as project.
## Health report:
- the project is suffering a decline of interest from the common public
since xml is nothing sexy anymore. There is further basically no
interest of doing a release and no communication on the mailing lists. I
will raise the discussion on the cocoon PMC whether we should move to
the attic.
## Issues:
- there are no issues requiring board attention at this time
## LDAP committee group/Committership changes:
- Currently 80 committers and 32 LDAP committee group members.
- No new changes to the LDAP committee group or committership since last
report.
## Releases:
- Last release was 2.1.12 on Thu Mar 14 2013
## Mailing list activity:
- users@cocoon.apache.org:
- 393 subscribers (down -1 in the last 3 months):
- 2 emails sent to list (7 in previous quarter)
- dev@cocoon.apache.org:
- 237 subscribers (up 0 in the last 3 months):
- 6 emails sent to list (6 in previous quarter)
- docs@cocoon.apache.org:
- 88 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- cvs@cocoon.apache.org:
- 69 subscribers (up 0 in the last 3 months):
- 25 emails sent to list (2 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Issues needing board attention: ------------------------------ None. Community ---------- Traffic on users and devs list had been very light this last quarter. Some users asked about different issues in the different versions of cocoon but no real discussion raised. * Last committer: Cédric Damioli and Robby Pelssers - 2011/12/18 * Changes in the PMC membership: None. - Last modified: 2012/10/21 (change of PMC chair) Releases --------- 2.1 has been released on 2013/03/20. Development ----------- None Security issues reported ------------------------ None. Progress of the project ----------------------- none. We still need to release a new version of cocoon 3 and cocoon 2.2 but no committer is stepping up to do so.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Issues needing board attention: nothing Changes in the PMC membership: None. Last modified: 2012/10/21 (change of PMC chair) Community Traffic on users and devs list had been a bit better then the last quarter. Some users asked about different hosting solution. Various devs attended the questions and provided solutions. Further Carlos a user and Francesco worked on the support for java8 and still maintaining support for 1.4. Releases 2.1 has been released on 2013/03/20. Development None Security issues reported: None. Progress of the project: We need to release a new version of cocoon 3 and cocoon 2.2 but still no committer has stepped up yet to do so.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based
around the concept of pipelines and sitemaps and it is very similar to Cocoon
2.2 in many respects but is slimmed down and designed to be easily used with
Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal
of becoming the best available platform for RESTful webservices and web
applications.
Issues needing board attention: nothing
Changes in the PMC membership:
None.
Last modified: 2012/10/21 (change of PMC chair)
Community
Traffic on users and devs list had been lighter then the last quarter. Some
users asked about different issues in the different versions of cocoon.
Various devs attended the questions and provided solutions.
We had again problems with a jira spammer "ROY Assink" which open/comment/...
on issues with spam messages, different PMC member removed the comment and
reverted the doing.
Releases
2.1.10 has been released on 2013/03/20.
Development
None
Security issues reported:
None.
Progress of the project:
We need to release a new version of cocoon 3 and cocoon 2.2 but still no
committer has stepped up yet to do so.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Issues needing board attention: None Changes in the PMC membership: None. Last modified: 2012/10/21 (change of PMC chair) Community Traffic on users and devs list had been lighter then the last quarter. Some users asked about different issues in the different versions of cocoon. Various devs attended the questions and provided solutions. We had again problems with a jira spammer "ROY Assink" which open/comment/... on issues with spam messages, different PMC member removed the comment and reverted the doing. r.assink.ra@gmail.com is the mail and he now has opened another account https://mail-search.apache.org/members/private-arch/cocoon-private/201406.mbox /%3C53AA6DB8.7010003@apache.org%3E we consulted infra whether there is possibility to get his e-mail address permanently disabled but that is not possible so we need to block the user every time new. Releases 2.1 has been released on 2013/03/20.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2012/10/21 (change of PMC chair) Community Traffic on users and devs list had been busier then the last quarter. Some users asked about different issues in the different versions of cocoon. Various devs attended the questions and provided solutions. We had problems with a jira spammer "ROY Assink" which open/comment/... on issues with spam messages, different PMC member removed the comment and reverted the doing. Releases 2.1 has been released on 2013/03/20. Development None Security issues reported: None. Progress of the project: We need to release a new version of cocoon 3 and cocoon 2.2 but still no committer has stepped up yet to do so.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2012/10/21 (change of PMC chair) Community Traffic on users and devs list continues be light. Some users asked about different issues in the different versions of cocoon. Various devs attended the questions and provided solutions. David Crossley pointed out that I was not subscribed to the board mailing which I fixed. Further I updated irs-disclosures.txt to my best knowledge however Simone had not been in this doc so I used a approx. date. Releases 2.1 has been released on 2013/03/20. Development None Security issues reported: None. Progress of the project: We need to release a new version of cocoon 3 and cocoon 2.2 but still no committer has stepped up yet to do so.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2012/10/21 (change of PMC chair) Community Traffic on users and devs list continues be light. Some users asked about the different versions of cocoon. Various devs attended the questions and provided solutions. Releases 2.1 has been released on 2013/03/20. Development None Security issues reported: None. Progress of the project: We need to release a new version of cocoon 3 and cocoon 2.2 but no committer has stepped up yet to do so.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful web services and web applications. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2012/10/21 (change of PMC chair) Community Traffic on users and devs list continues be light but steady, people got a bit more active after the release to give feedback. Further some user started to adopt the latest addition of the examples. Various devs attended the questions and provided solutions. Releases Maintenance release 2.1.12 has been released on 2013/03/20. Development Bugfixing on C3 and adding of some new features. In c3 there have been a new set of components around TIKA (user asked to migrate it to 2.1 but no work has started yet. Further some new samples where added to the rest-optional-sample block to show how to send eMails with c3. Security issues reported: None. Progress of the project: We need to release a new version of cocoon 3 but no committer has stepped up yet to do so.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2012/10/21 (change of PMC chair) Community Traffic on users and devs list continues be light but steady, people got a bit more active around the release to give feedback. Various devs attended the questions and provided solutions. Releases 2.1 has been released on 2013/03/20 after 6 posivite PMC votes. Special thanks to Cédric for his first cocoon release. 2.2 and 3 are waiting for some blocking bugs to be closed to be released. Development Bugfixing on C3 and release on the 2.1 branch. Various tickets and patches had been applied to the code base, Security issues reported: None. Progress of the project: One Forrest PMC member did assist to do testing prior to our 2.1.12 release inside Forrest.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Community Traffic on users lists continues be light but steady, people continue be interested on C2 and newer C3. Especially c3 new developments from Mansour Al Akeel, a user that had been quite active the last quarter, has spoused some discussions and bug fixes. Various devs attended the questions and provided solutions. Simone has resigned from the position of PMC chair, and Cocoon PMC voted for Thorsten to fill this role. Releases No releases during the last quarter but the community is working to do a release for all version, where the 2.2 version did get less attention then 2.1 and 3.0. The whole release effort is driven by Francesco Chicchiriccò and the 2.1 release is supported by David and Cédric. Hopefully we can release all versions within the next quarter. Development Bugfixing on C3 and release preparation on the 2.1 branch. Various tickets and patches had been applied to the code base, especially one blocking issue on the c3 branch could be closed which opened the door towards a stable c3 release.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful web services and web applications. Community Traffic on users lists continues be light, people continue be interested on C2 and newer C3, few impatient users requested C3 release date - again. Cocoon Hackaton took place at ApacheCon EU for 3.0-beta version <http://wiki.apache.org/apachecon/HackathonEU12> Thorsten Scherler and Javier Puerto, both PMC members, gave a talk "Rapid mobile development with Apache Cocoon3, Apache Cordova and Jenkins CI" at ApacheCon EU <http://www.apachecon.eu/schedule/presentation/184/> Simone Tripodi, PMC member, gave a talk "Refurbished wheels still round" at ApacheCon EU showing Cocoon3 Pipelines APIs <http://www.apachecon.eu/schedule/presentation/90/> Releases No releases during the last quarter Development Still bugfixing on C2, light traffic on C3.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Community Traffic on users lists continues be light, people continue be interested on C2 and newer C3, few impatient users requested C3 release date. The PMC still cannot schedule the C3 release date because nobody has enough cycles ATM to dedicate on reviewing all the work done on Cocoon and there is the need of APIs modification, which could be a huge work. Javier Puerto has been invited as Committer and the PMC, he accepted to join The PMC chair was re-elected by the community, which wasn't strictly necessary but he wanted to know if other people were interested in being the PMC chair Releases Following subcomponents have been released: * Apache Cocoon parent 9 * Apache Cocoon Block Deployment 1.2.1 * Apache Cocoon Serializers Charsets 1.0.2 * Apache Cocoon Integration Test Framework 1.0.0 * Apache Cocoon Configuration API 1.0.4 * Apache Cocoon Reloading ClassLoader - Spring reloader 1.0.2 * Apache Cocoon Reloading ClassLoader - Webapp Wrapper 1.0.2 * Apache Cocoon XML Utilities 2.0.4 * Apache Cocoon Maven Plugin 1.0.2 * Apache Cocoon Spring Configurator 2.2.1 * Apache Cocoon JNet 1.2.2 * Apache Cocoon Servlet Service Implementation 1.3.1 Development A lot of bugfixing on C2, light traffic on C3. All old sites sources have been migrated to the Apache Maven formats. Trademark The PMC found, outside the ASF, projects which names contain Cocoon so project owners were put in touch with the trademarks@ office which successfully and friendly addressed all the issues. You can find these projects on: * http://cocoon.codeplex.com/ * https://github.com/nathanvda/cocoon * https://github.com/project8/Cocoon * https://github.com/poymode/cocoon * https://github.com/Nerian/formtastic-cocoon CoCoons community (an OpenFOAM fork) contacted the PMC about potential trademarks issue, the Trademarks office managed them.
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Community Traffic on users lists continues be light, people continue be interested on both C2 and newer C3. A Cocoon3 article is going to be published in the German magazine 'JavaMagazin' redacted by the ASF Member Christian Grobmeier (grobmeier), which contains an interview to the Cocoon chair. Releases/Development Registered regular traffic on commits list, most of the effort has been moved on housekeeping: * Cocoon sites are now managed via SvnPubSub; * old Cocoon Documentation has been imported from old Daisy to sources managed via SvnPubSub; * Jail has been restored with demo for Cocoon2.X and Cocoon3, available on http://cocoon.zones.apache.org/ Branding checklist: Project Website Basics - done Website Navigation Links - done Trademark Attributions - done Logos and Graphics - done Project Metadata - need to be checked Read PMC Branding Responsibilities - done
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Community Traffic on users lists continues be light, people continue be interested on both C2 and newer C3. New Committers have been voted and accepted in the PMC, Cédric Damioli (cdamioli) and Robby Pelssers (robbypelssers). The Chair has been interviewed on FeatherCast.org, the interview has not been published yet. Releases/Development After Apache Cocoon 3.0.0-alpha-3 release (reported on Aug 11), development of Cocoon 3.0 continues towards 3.0.0-beta-1 release, with an experimental branch to finalize APIs. The PMC voted the JDK6 as minimum requirement to run C3 There has been healthy activity on older (2.x) branches. Traffic on dev continues on discussing about future of Cocoon, and how to restore the old Daisy Cocoon Documentation. Branding checklist: Project Website Basics - done on C3 site Website Navigation Links - done on C3 site Trademark Attributions - done on C3 site Logos and Graphics - done on C3 site Project Metadata - done on C3 Read PMC Branding Responsibilities - done
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and designed to be easily used with Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal of becoming the best available platform for RESTful webservices and web applications. Community Traffic on users lists continues be light, people complained about the C2 maintenance, since it is the foundation of some companies products. OTOH there is a renewed enthusiasm about the new Cocoon approach, people started spreading the word on Twitter an blogs about custom integrations and experimentations, we are waiting for contributions after invited them on actively participating, instead of just being users. Releases/Development After Apache Cocoon 3.0.0-alpha-3 release (reported on Aug 11), development of Cocoon 3.0 continues healthy towards 3.0.0-beta-1 release, with major activity during the last month. There has been no notable changes on older (2.x) branches. Traffic on dev continues on discussing about future of Cocoon, with new components development and evolvement of existing ones Branding checklist: Project Website Basics - not done Website Navigation Links - not done Trademark Attributions - not done Logos and Graphics - not done Project Metadata - not done Read PMC Branding Responsibilities - not done Issues for board consideration There are no issues the board should be aware of.
After a slow previous quarter, development of Cocoon 3.0 picked up a bit, and culminated with release of Apache Cocoon 3.0.0-alpha-3. There has been no notable changes on older (2.x) branches. Traffic on dev list slightly picked up due to alpha release and discussions about future of Cocoon. Traffic on users list was light. Implementation of the branding guidelines (specifically, changing page footers, and couple of other minor tweaks) seen no progress, Cocoon's website CMS has not been restored yet. I resigned from the position of PMC chair, and Cocoon PMC voted for Simone to fill this role.
Development of Cocoon 3.0 continues, closing in on the next alpha release. Cocoon 2.x branch saw couple of fixes too. Traffic on both dev and users lists remains light. We have added a new committer and PMC member, Francesco Chicchiriccò. There has been no new releases this quarter. Implementation of the branding guidelines (specifically, changing page footers, and couple of other minor tweaks) has stalled due to Cocoon's CMS being down since zones migration.
Development on Cocoon 3.0 picked up a bit, culminating with three new release artifacts. Traffic on both dev and users lists remains light. No changes to PMC and no new committers. Releases: * Cocoon JNet 1.2.0 * Cocoon Maven Plugin 1.0.0 * Cocoon Maven Site Skin 1.0.0 No work has been done yet to implement the branding guidelines.
There have been no new releases or development. Traffic on users list is steady, with mostly silence on the development list. Started the process of identifying active PMC members. By last count we have 11 active PMC member, 17 members who have not responded/decided, and following 21 PMC members became emeritus: Ard Schrijvers Arje Cahn Bertrand Delacretaz Carsten Ziegeler Christian Haul Felix Knecht Giacomo Pati Helma van der Linden Jeremy Quinn Jeroen Reijn Jorg Heymans Marc Portier Marcus Crafter Ralph Goers Ross Gardler Simone Gianni Steven Noels Timothy Larson Torsten Curdt Ugo Cei Upayavira Branding guidelines have not been implemented yet. Preliminary conclusion though is that project website is compliant with "Project Website Basics", "Project Naming And Descriptions" and "Project Metadata" sections; need to be updated to include links in "Website Navigation Links" section, and has no trademark attributions as per "Trademark Attributions" and "Logos And Graphics" sections.
No changes to projects PMC or committers. No new releases. This has been the quietest quarter during lifetime of Cocoon project, with email traffic dropping to ~130 emails to users and ~60 emails to dev lists in a quarter. Surge of maintenance activity on the Cocoon 2.1 branch which has started in the last quarter has tapered off; no plan for the maintenance release was set. Development activity on Cocoon 3 has slowed down, however interested committers stated that development will resume in the nearest future. Stefan Bodewig made progress in restoring Gump builds, with all of Cocoon 3 and some of Cocoon 2.2 building successfully. Slow down in activity spurred discussion on the PMC list on future of the project. We might start with identifying active and emeritus project members, and go from there.
There were no new committers or PMC members this quarter. No new releases. Thread on developer's list about fate of Cocoon 2.1.x branch spurred some maintenance activity, raising possibility of another maintenance release. Development continues in the trunk on the next Cocoon 3 alpha.
Community ========= * Added new committer and PMC member: Simone Tripodi Releases ======== * Apache Cocoon 3.0.0-alpha-2 * Apache Cocoon XML 2.0.2 Ongoing Work ============ Cocoon 3 is in active development.
Community ========= * No PMC changes. * No new committers. Releases ======== Two blocks for the Cocoon 2.2 were released: * Apache Cocoon Serializers Charsets 1.0.0 * Apache Cocoon Serializers Block 1.0.0 Ongoing Work ============ * With the exception of two releases for Cocoon 2.2, all of the ongoing work is happening on the Cocoon 3 branch. * GSoC student Dariusz Łuksza continues his work on the statistics module.
Report for the Apache Cocoon Project for the Jun'09 - Aug'09 quarter: Community: * Carsten Ziegeler has left the PMC. * GSoC student Dariusz Łuksza continues his work on Cocoon 3, monitoring and statistics module. * No new committers. Releases: * Cocoon Block Deployer 1.1.0 * Cocoon Spring Configurator 2.1.0 * Cocoon JNet 1.1.0 * Cocoon Servlet-Service Framework 1.2.0 Ongoing Work: * All of the ongoing work is happening on Cocoon 3 branch. Cocoon 2.1 and Cocoon 2.2 are in the maintenance mode.
Community: * Added Robin Wyles as a committer. He was voted in as committer during last quarter, but his papers and account were creating during this quarter. * Reinhard Pötz together with Steven Dolg have involved students of Vienna University of Technology to work on implementing Profiling for the Cocoon 3. * GSoC student Dariusz Łuksza is working on Cocoon 3 Monitoring. Legal: * Added a privacy page, due to our usage of Google Analytics: http://cocoon.apache.org/1508_1_1.html Releases: * No new releases. Ongoing Work: * Most of the ongoing work is happening on Cocoon 3 branch. Cocoon 2.1 and Cocoon 2.2 are in the maintenance mode.
Community: One person, Robin Wyles, has been voted in as a committer, but he did not file the paperwork. One of our PMC members is trying to reach him. There has been no PMC Changes. Releases: * Cocoon 3.0.0-alpha-1 * Cocoon XML 2.0.0 has been just voted for release Ongoing Work: Active work is going on in the Cocoon 3.0 branch. Cocoon 2.2 and 2.1 seen relatively few svn commits. Privacy policy page (required due to usage of Google Analytics) is being set up (it has been added to our CMS but is not published to live site yet).
New Committers: * David Legg PMC Changes: * Added Andreas Hartmann * Added Luca Morandini * Added Jasha Joachimsthal * Added David Legg * Added Steven Dolg No Releases. Ongoing Work: * New code in whiteboard, previously known as 'Corona', was renamed to 'Cocoon 3' and moved out of the whiteboard svn area. * Cocoon 3 sees steady stream of commits and Jira issues. Cocoon 3.0.0 alpha 1 release is expected soon. * Work is going on on the new branch which was created for Cocoon 2.1 integration with Dojo 1.1.1 release. It is expected that Cocoon 2.1.12 will be released with these changes, and they also will be merged into Cocoon 2.2 (trunk).
New Committers: * Thorsten Scherler * Luca Morandini * Steven Dolg * Jasha Joachimsthal * Andreas Hartmann PMC Changes: * Gianugo Rabellino has left the PMC * Added Thorsten Scherler Releases: * Cocoon Servlet-Service Framework Impl 1.1.0 * Cocoon Spring Configurator 2.0.0 * Cocoon JNet 1.0.0 * Cocoon Block-Deployment 1.0.0 * Cocoon Maven Plugin 1.0.0-M3 Ongoing Work: * The work in SVN whiteboard area is progressing on the 'Corona' project. Cocoon community voted to start doing alpha releases of this work under 'Cocoon 3.0' name instead of using 'Corona' codename. * Java 1.4 support has been dropped for the Cocoon trunk. Starting with next Cocoon 2.2 release, Java 1.5 (or newer) will be required. * Java 1.3 support has been dropped for the Cocoon 2.1 branch. Cocoon 2.1.12 (if it happens) will require Java 1.4 or newer.
RELEASES / ONGOING WORK - Cocoon 2.2.0 was released on 2008-05-16. - In the Cocoon whiteboard (our sandbox in SVN) there is a promising rewrite of Cocoon called Corona (working title). The Corona pipeline API doesn't have _any_ third-party dependencies and can be used easily from within any Java application. So far Corona only provides SAX XML pipeline components but alternative implementations (e.g. StAX) are welcomed. There are two additional modules "corona-sitemap" and "corona-servlet" that have the goal to make Corona usable for web applications. - Cocoon uses Excalibur JNet, a common purpose lib that allows you to dynamically register own URL handlers. Since Cocoon is currently the only project that makes use of it, we have pulled it into our repository but we are aware that there are better places for it. In particular since it might be of interest to other libraries and frameworks that have to dynamically register URL handlers too. Carsten Ziegeler, who wrote the initial version of JNet, contacted the Apache Commons community which invited us to contribute JNet to their sandbox as a new project. COMMUNITY - After almost two years I stepped down as the chair of the Apache Cocoon project. Vadim Gritsenko was elected to follow me. LEGAL [no issues]
RELEASES / ONGOING WORK - Cocoon 2.1.11 was released on 2008/01/09. - The final release of Cocoon 2.2 is expected for February/March. - The Cocoon sample web application got a new skin following the style of the new website. - There have been some experiments with completly removing all dependencies on Avalon/Excalibur and providing a Java API for pipelines in the whiteboard section of our SVN repository. COMMUNITY - nothing that requires board attention LEGAL - The Export Notification Policy reminder from the board didn't show anything to be done from the Cocoon PMC.
RELEASES / ONGOING WORK - Cocoon 2.2RC2 was released on 2007/11/03 (http://cocoon.apache.org/1421_1_1.html). - The final release is scheduled for the end of the year. - Grzegorz Kossakowski successfully finished his GSoC project "Unified expression handling and unified object model". - Cocoon 2.2RC2 is scheduled for the end of September. - There was a relaunch of the Cocoon website (design & content). COMMUNITY - emeritus PMC member: Peter Royal - The 6th Cocoon GetTogether, edition 2007, took place from 3/10/07 to 5/10/07 in Rome (http://www.cocoongt.org/). Thanks to Simone Gianni and Sourcesense it was a a great event again. LEGAL - no issues
RELEASES / ONGOING WORK - The release artifacts for Cocoon 2.2RC1 are available and the PMC voting passed. The official announcement will go along with the publishing of the new website (see http://cocoon.zones.apache.org/dev-docs/) which needs little more work though. - Cocoon 2.2RC2 is scheduled for the end of September. - Our this year GSoC student Grzegorz Kossakowski, who is also committer and PMC member, makes good progress with his ambitious project of "Unified expression handling and unified object model". - In general, over the summer months the development was steady but slow. COMMUNITY - emeritus PMC member: Niclas Hedhman - The 6th Cocoon GetTogether, edition 2007, was announced and will take place from 3/10/07 to 5/10/07 in Rome (http://www.cocoongt.org/). LEGAL - no issues
RELEASES / ONGOING WORK - Cocoon 2.2 core can be considered as "feature complete" now. - Most of the work for a relaunch of our website has been done. - Although planned there have been no releases in the last 3 months. The release of Cocoon 2.2RC1 is planned for May though. COMMUNITY - new committers and PMC members: Grzegorz Kossakowski, Jeroen Reijn, Felix Knecht - emeritus PMC members: Guido Casper, Matthew Langham - Jeroen Reijn and Andrew Savory, both Cocoon committers, held talks about Cocoon at the ApacheCon in Amsterdam. LEGAL - no issues
RELEASES / ONGOING WORK
- We released Cocoon 2.1.10, mostly bugfixing and some great work
on using Dojo in Cocoon Forms.
- We released milestone artifacts from trunk:
o org.apache.cocoon:cocoon:2 (pom)
o org.apache.cocoon:cocoon-core-modules:2 (pom)
o org.apache.cocoon:cocoon-core:1.0.0-M2 (jar)
o org.apache.cocoon:cocoon-blocks-modules:2 (pom)
o org.apache.cocoon:cocoon-template:2 (pom)
o org.apache.cocoon:cocoon-flowscript:1 (pom)
o org.apache.cocoon:cocoon-template-impl:1.0.0-M2 (jar)
o org.apache.cocoon:cocoon-flowscript-impl:1.0.0-M1 (jar)
o org.apache.cocoon:cocoon-blocks-fw:1 (jar)
o org.apache.cocoon:cocoon-blocks-fw-impl:1.0.0-M1 (jar)
o org.apache.cocoon:cocoon-tools-modules:2 (pom)
o org.apache.cocoon:cocoon-archetypes:2 (pom)
o org.apache.cocoon:cocoon-22-archetype-block:1.0.0-M4 (jar)
o org.apache.cocoon:cocoon-22-archetype-webapp:1.0.0-M1 (jar)
For each jar artifact sources and javadocs were released too.
- After the 2.2.0-M2 release there was a lot of refactoring to split up
the core into smaller pieces.
- There is some ongoing work on a new design of our website.
- In February we plan to have another, hopefully the last, series of
milestone releases from trunk. In March we plan to get the first series
of release candidates together with the new website out of the door.
COMMUNITY
- On the one hand caused by the upcoming Cocoon 2.2 we are experiencing an
increasing interest by new developers. They get involved in discussions and
provide patches. On the other hand many long-term committers became inactive
or "only" watch the dev@c.a.o and or private@c.a.o lists. All in all our
community is renewing itself. We consider this being a healthy process and
nothing to worry about.
- new committers: no
- PMC changes: no
LEGAL
- Rhino was relicensed unter MPL. See
http://groups-beta.google.com/group/mozilla.dev.tech.js-engine/browse_thread/thread/012b1279e97d1f8a/76511e91e6263eca#dcb9a0e6ee1eaed1
https://bugzilla.mozilla.org/show_bug.cgi?id=236108
- Daisy registrations now require accepting the Apache Community Contribution
Agreement (http://www.apache.org/licenses/proposed/community.txt)
Though it's still a proposal it's better than that what we had before.
- We and the designer are aware that the contribution of a new design of our
website has to be handled by an ICLA/CCLA.
RELEASES / ONGOING WORK - There were no releases, neither from the 2.1.x branch nor from trunk. - We plan to release a second milestone release of Cocoon core 2.2 and of some blocks in November. Additionally we aim to release Cocoon 2.1.10 by the end of the year. - Finally we have a working version of Cocoon blocks in trunk. After that we consider Cocoon core in trunk being feature complete. - The work on using OSGi as fundament (aka Cocoon 3.0) is "on hold" for now. The reason is that the Spring community is working on an OSGi/Spring integration layer which will save us a lot of work (www.springframework.org/osgi). - As soon as 2.2 is released, we will only apply bug fixes and minor enhancements to the 2.1.x branch. This means that there will be no hard rule to keep it in sync with trunk anymore. - There is a new documentation system in place. It is based around the Daisy CMS, a Maven 2 plugin that pulls out the content and SVN. Although we use the CMS, we will still add our generated docs to SVN before we publish them. (see http://cocoon.zones.apache.org/daisy/cdocs/1201.html) - There are plans to come up with a new, flashy design for cocoon.apache.org. COMMUNITY - From October, 2nd to October, 4th the 5th annual Cocoon GetTogether took place, this year in Amsterdam. Thanks to Arje Cahn and his team at Hippo, it was a success again. There were 91 attendees from 13 different countries (http://www.cocoongt.org/chairs-big.png) and 13 interesting talks (http://wiki.apache.org/cocoon/GT2006Notes). - new committers: Lars Trieloff - new PMC members: Andreas Hochsteger, Ard Schrijvers, Helma van der Linden, Lars Trieloff LEGAL - We use the new license headers throughout our codebase. - Cameron McCormack (Batik) asked the Rhino team about relicensing Rhino under the MPL: http://groups-beta.google.com/group/mozilla.dev.tech.js-engine/browse_thread/thread/012b1279e97d1f8a/76511e91e6263eca#dcb9a0e6ee1eaed1 - Joe Schaefer made us aware that the IP Agreement at the Daisy registration (Daisy is our CMS) doesn't follow the Apache Community Contribution Agreement (http://www.apache.org/licenses/proposed/community.txt) which hasn't been adopted by the board though, but would definitly be an improvement compared to the current text.
Releases / Ongoing work ----------------------- - After a long time of work we have started to release milestone artifacts based on our trunk. After moving our build system to Maven 2 we are able to release Cocoon in smaller chunks. This has the big benefit that people can assemble what they need from Cocoon based on binary artifacts. Additionally we can start to have different release cycles for different parts of our codebase. - Having said this we plan to release our most important artifacts every 6 weeks. Our goal is to enter into a time-based release cycle instead of a feature-based. In the past we identified a feature-based release cylce as the major reason for not to release. - We plan to release Cocoon 2.1.10 soon which might be the last release of our 2.1.x branch. - Google accepted the GSoC proposal "Repeater Pagination, Google Maps and Ajax Support" of Matthias Epheser. Community --------- - We voted in 4 new committers: Andreas Hochsteger, Jason Jonston, Peter Hunsberger, Ard Schrijvers - At the time of writing this, Peter Hunsberger has accepted our invitation to become PMC member. The invitations to the others are pending. - Daniel Fagerstrom and Peter Royal have become ASF members. - Arje Cahn has started preprations for the 5th anual Cocoon GetTogether which will take place in Amsterdam from October 2nd to October 4h. Legal ----- We have started to work on changing the license headers of our source files in order to comply with the new source header policy.
Releases / Ongoing work: - Cocoon 2.1.9 was released in April. This is a maintenance release. - Work on trunk is going on, that may lead either to Cocoon 2.2 (many usability enhancements and the move from Avalon to Spring) or Cocoon 3.0 (2.2 + move to OSGi). Community: - A new committer, Simone Gianni, who also joined the PMC, - Stefano Mazzocchi left the PMC, - Reinhard Poetz has been elected as the PMC chair after I decided to resign. - The community is concerned by the slowdown in contributions and new committers and is self-questionning about what needs to be done so that we attract people again. Legal: Nothing.
Community: - Cocoon 2.1.8 was released in November, more than 6 months after the previous release. We want to have shorter release cycles and are planning to release 2.1.9 soon. - Some heavy work was done to use Maven 2 to build trunk (version 2.2). This is a really important effort, and the Maven guys were very responsive when we encountered some problems. - 1 new committer: Jean-Baptiste Quenot - PMC: Jean-Baptiste Quenot joined, Tony Collen left. Legal: - Big issue with Rhino: the recent draft licenising policy states that NPL is a prohibited licence, meaning we should remove Rhino from Cocoon distributions. This means removing a large amount of code and some very important features that make the value of Cocoon (i.e. flowscript and server-side scripting of form handling) - We have some concerns regarding the licencing terms of the JCR (aka JSR-170) API. Although Jackrabbit is ASL, the only distribution of the API we found uses a specific licence (http://www.day.com/maven/jsr170/licenses/day-spec-license.htm). The folks at Day software, leaders of this specification, clearly stated that it is meant to be available to the widest possible audience, but we need clearer licensing terms.
Community:
- No new release this quarter. Cocoon 2.1.8 should be released in the
coming days (code is ready, some doc generation issues need to be
solved). We plan to adopt a shorter release cycle from now on.
- 3 new committers: Arje Cahn, Ross Gardler and Max Pfingsthorn. The
reasons for the nomination of Arje and Max are worth mentioning: Arje
wasn't nominated for his code contributions but for his long-time
commitment to Cocoon and its community (among them the organization of
this year's GetTogether), and Max started contributing to Cocoon
during the Google Summer of Code.
- The 4th Cocoon GetTogether, yearly meeting of Cocoon users and
developers, took place in Amsterdam in October. A fruitful two-day
hackaton, and one conference day with 100 attendees. Although a
success, this is less than last year where 140 people showed up.
- A provocative post from Stefano Mazzocchi ("Is Cocoon obsolete?")
led the team to self-question about the slowdown on mailing-lists and
the future of the project. The main outcomes are that we must take
more care of our users (a lot of devs had left the users list),
simplify the Cocoon learning process, and be less shy at deprecating
old features that are no more mainstream.
Legal:
Nothing.
Misc:
The use of a user-friendly CMS on cocoon.zones.apache.org has led an
increasing number of people to contribute to the docs. What started as
an experiment is slowly turning into a production system, and we have
to solve some issues related to accountability of doc authoring (it is
stored in Daisy and not in SVN). We're also working closely with the
Forrest team to setup the publication process.
Community: - No new release in this quarter. Cocoon 2.1.8 should be released shortly though. - We have two new committers, Helma van der Linden and Jorg Heymans - Daniel Fagerstrom joined the PMC - Nicola Ken Barozzi left the PMC - we have 3 Google Summer of Code students working on Cocoon. They each have write access to a separate sandbox in the Cocoon svn repository, allowing them to work efficiently without having the full committer privileges. - cocoon.zones.apache.org has been set up and hosts live demos of Cocoon and a Cocoon-based CMS (Daisy) for the docs (see below). - a important documentation effort has started, based on a live CMS that eases the document writer's job and allows non-committers to participate in the process. Legal: The NPL issue we have with Rhino has been taken care of by Cliff Schmidt (great job BTW!) and we're now waiting for the official policy statement from the board. Misc: The next major release of Cocoon is very likely to be using OSGi, and a number of Cocoon committers are participating in the Oscar incubation, which looks like a very interesting cross-project effort.
Community: - Cocoon 2.1.7 was released in March. This is a maintainance release while development of version 2.2 is going on. - we have one new committer, Alfred Nathaniel - two committers joined the PMC, Leszek Gawron and Ralph Goers Legal: The XML graphics PMC raised our attention on Rhino which they also use, as its licence changed from MPL to NPL last october. We're wondering about potential problems of an NPL-licenced library in our svn repository, and asked legal-discuss for some advice about this, with no answer up to now. Misc: A new project is being set up at Eclipse to build an IDE for Cocoon [1], and a number of Cocoon devs have expressed their interest in participating. This will hopefully increase the user base by making Cocoon easier to use. [1] http://www.eclipse.org/proposals/eclipse-lepido/
Community: - Cocoon 2.1.6 has been released in November. This is a maintainance release. Cocoon 2.2 development is going on, and we reduced its original scope to allow for an earlier release as it already includes a number of much wanted improvements. - The Java continuation engine and Java compiler interface that had being written in Cocoon have been moved to the Jakarta commons sandbox (JavaFlow and JCI) because we felt they could be used in a number of other contexts and may attract other developpers. - there's an ongoing effort to refactor our documentation and its writing process, at the poor structuration of our docs is a major problem for newcomers. - a new french-speaking user list has been created as an answer to the fact that many Cocoon-related questions where asked on other french-speaking lists and forums. Legal: The legal issues related to the Mozilla Rhino fork supporting continuations are solved, as we now use the latest official version which has continuation support.
Community: - The 3rd Cocoon GetTogether, yearly meeting of Cocoon users and developers, whas held as is usual now in Gent (Belgium) in early october. That was again a great success with 140 people coming from 17 countries, an active hackaton and interesting presentations. - There was a relative traffic slowdown on the dev list during spring and summer, mostly because people were very busy. After the GetTogether, the activity on the dev list raised back to its usual traffic and lots of interesting discussions are happening. - We have two new committers, Ralph Goers and Leszek Gawron. - Cocoon 2.1.6, is planned to be released next week, this is a maintainance release while development continues on the 2.2 branch. - Lenya is no more a in the Cocoon TLP as it successfully exited incubation and moved to top-level. - The death of Avalon and the fact that our component manager is considered as deprecated by the Excalibur project led us to fork it. These are only 15 source files, which allow us to master the foundations on which Cocoon is built. Legal: The legal issues we had with the Rhino fork supporting continuations are about to be solved, as the Mozilla Rhino team has added continuation support in the official Rhino, and Cocoon will therefore abandon the fork in favor in the official distribution.
Community: - Cocoon version 2.1.5 released in May: it's a bugfix release with minor new features. It was re-released as 2.1.5.1 in July when we noticed that our build system was not including the license and notice files [1]. - Lenya version 1.2 released in June - no new committer on Cocoon, one new committer on Lenya - Lenya proposed as a top-level project - PMC composition change: new chair, some new members and some resignations. Infrastructure: - moved to subversion - cocoondev.org wiki moved to ASF wiki Ongoing research work : - Javaflow (implementation of continuations in Java), which triggered the creation of a group to propose a JSR [2] - the "Kernel", a container for Cocoon blocks, - "Butterfly", an experimentation to use Spring as a component container instead of Avalon Misc: - Important new live sites with VNU UK [3] moving all its sites to Cocoon (high-traffic sites which where sucessfully slashdotted) [1] http://www.apache.org/dist/cocoon/cocoon-2.1.5-removed.txt [2] http://docs.codehaus.org/display/continuation/Home [3] http://www.vnunet.com
Cocoon ------ - Steven Noels has indicated his intention to step down from PMC chair. Bertrand was nominated but indicated his lack of continous time in the next few months. Nominations are still undergoing. - Cocoon 2.1.5 was released May 25, 2004. Mostly a bugfix release (a problem with the persistency of cached object was found and corrected) and further migration of the Woody form framework to the Cocoon Forms framework. - Pier Fumagalli reported the migration of VNUnet.com (one of the most important news sites) to a cocoon-based site in 3 weeks. Given the size and load of that site, Pier is also finding (and correcting) several misbehaviors in the core parts of the component handling system. - The community sent congrats to the three new elected ASF members David, Bertrand and Gianugo and to the new ASF director Stefano. - Wiki spamming is becoming a serious problem. We are considering blocking public write access to the wiki as a result. Also, we would like to move the wiki from cocooondev.org to the ASF-hosted wiki farm and operation is undergoing. Given the popularity of ASF's websites, we wonder how the Infrastructure team plans to handle Wiki spamming on the MoinMoin installation. - On the social side, Christopher Oliver has decided to friendly quit the project due to the legal friction generated by his patches to Rhino. No flames were generated, even if this leaves us with a core piece of the cocoon architecture as a non-official fork, basically with nobody maintaining it, licensed under the MPL and hosted on a non-apache site (cocoondev.org). Talks have been started with the Mozilla folks to relicense Rhino under an ASF-redistribution-friendly license, and while there seems to be a genuine willingness from their side, the administrative burden has been shifted back to us, the energy contributed towards this effort is minimal, and we should be careful not to let this become a permanent issue. Lenya ----- The Apache Lenya project has been busy the last few months to get the 1.2 release out. The project saw an increase in mailing list traffic for both the user and developer lists; the number of sites deploying Lenya is growing. Dale Christ was voted in as a new commiter, while Thorsten Scherler became an active commiter again. A public demo site [1] turned out to be a useful resource for users to try out Lenya and for developers to quickly confirm bug reports. A Sprint [2] brought developers together for 2 days in Zurich to work on Repository Integration. The sprint was very productive and will be repeated in the future. The notion of translating the Lenya documentation came up, while a non-english mailing list proposal was rejected over fracturing concerns. The Lenya wiki is in the process of being separated from the Cocoon one. [1] http://olr.kbs.uni-hannover.de:8080/lenya/ [2] http://wiki.cocoondev.org/Wiki.jsp?page=LenyaSprintZurich20040514
Cocoon ------ - Steven Noels has indicated his intention to step down from PMC chair. Bertrand was nominated but indicated his lack of continous time in the next few months. Nominations are still undergoing. - Cocoon 2.1.5 was released May 25, 2004. Mostly a bugfix release (a problem with the persistency of cached object was found and corrected) and further migration of the Woody form framework to the Cocoon Forms framework. - Pier Fumagalli reported the migration of VNUnet.com (one of the most important news sites) to a cocoon-based site in 3 weeks. Given the size and load of that site, Pier is also finding (and correcting) several misbehaviors in the core parts of the component handling system. - The community sent congrats to the three new elected ASF members David, Bertrand and Gianugo and to the new ASF director Stefano. - Wiki spamming is becoming a serious problem. We are considering blocking public write access to the wiki as a result. Also, we would like to move the wiki from cocooondev.org to the ASF-hosted wiki farm and operation is undergoing. Given the popularity of ASF's websites, we wonder how the Infrastructure team plans to handle Wiki spamming on the MoinMoin installation. - On the social side, Christopher Oliver has decided to friendly quit the project due to the legal friction generated by his patches to Rhino. No flames were generated, even if this leaves us with a core piece of the cocoon architecture as a non-official fork, basically with nobody maintaining it, licensed under the MPL and hosted on a non-apache site (cocoondev.org). Talks have been started with the Mozilla folks to relicense Rhino under an ASF-redistribution-friendly license, and while there seems to be a genuine willingness from their side, the administrative burden has been shifted back to us, the energy contributed towards this effort is minimal, and we should be careful not to let this become a permanent issue. Lenya ----- The Apache Lenya project has been busy the last few months to get the 1.2 release out. The project saw an increase in mailing list traffic for both the user and developer lists; the number of sites deploying Lenya is growing. Dale Christ was voted in as a new commiter, while Thorsten Scherler became an active commiter again. A public demo site [1] turned out to be a useful resource for users to try out Lenya and for developers to quickly confirm bug reports. A Sprint [2] brought developers together for 2 days in Zurich to work on Repository Integration. The sprint was very productive and will be repeated in the future. The notion of translating the Lenya documentation came up, while a non-english mailing list proposal was rejected over fracturing concerns. The Lenya wiki is in the process of being separated from the Cocoon one. [1] http://olr.kbs.uni-hannover.de:8080/lenya/ [2] http://wiki.cocoondev.org/Wiki.jsp?page=LenyaSprintZurich20040514
Community project: - A reformulation of the Cocoon project mission statement has been sent to the board for approval - pending. - Guidelines are (still) under construction (but given the even-mindedness of the Cocoon community, and our debate/consensus culture they are hardly being missed). - Wiki still resides outside ASF infrastructure, there's some W-I-P happening on a JSPWiki->moinmoin translator in a silent corner. The intention is to move all core logistical tools onto supported ASF machinery. Cocoon: - The last ASL 1.1-licensed Cocoon release had been done on Friday 13th Feb 2004 (2.1.4) - upcoming releases, also of legacy branches, will be done using the new license. - FirstFridays (a monthly online bug-fixing fest) are becoming a welcome established tradition. - A lot of work has been done on the Cocoon Forms framework, and alternative frameworks will now be actively deprecated. - The Pipelines-Flow-Woody trio quietly becomes the mainstream way of using Cocoon. - The 2.2 codebase is moving on, relatively few but regular contributors. - More systematic and structured use of bugzilla helps us get a clearer picture of what's happening. - Three new committers since mid-October 2003: Unico Hommes, Timothy Larson and Daniel Fagerstrom. Lenya: - First 'outside', active committer has been attracted and voted upon (Rolf Kulemann). - W-I-P on their second ASF-based release is ongoing. - There's good efforts underway to continuously integrate between Lenya & Cocoon. - Stale publication types are being deprecated. - Legal issues with outside codebases have been eradicated. - Incubation ongoing - no specific issues to report. Legal: - The situation with the Rhino fork Cocoon depends on still needs to be tackled - Rhino's murky legal past doesn't help a lot with that, and very few committers have time and energy to tackle this. - We have been on an active pursuit of having CLAs on file for all Cocoon committers. We are aware of the fact that non-compliance could mean future lock-out. Apart from some small nits, the Apache Cocoon project is both legally and community-wise very healthy - or aiming for achieving this future healthiness - and no issues are expected in the near future.
Here's the report on Cocoon's state of affairs. We do hope this gives
the board a feeling on how we are doing.
Let's first start with a brief run-through of the previous report
(http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105344074224116&w=2)
and see how we proceed:
1), 2), 3): no further action required or taken
4) recursive Cocoon charter: still needs to be worked upon
5) use of Cocoon brand by cocoondev.org and cocooncenter.com: ditto
6) ditto - work is slowly progressing with the infrastructure team to
migrate the Cocoon wiki to ASF infrastructure, together with Steven
Noels and Gianugo Rabellino from the Cocoon team - we believe it is
fair to indicate that an ASF-operated shared and managed Java
hosting service might accelerate this, and do hope the eventual
migration of our Wiki might serve as an example to move further
along that road.
7) solved: the XMLForms effort is being actively deprecated in favor of
other form handling frameworks (JXForms and Woody).
8) transfer of HSSF (Excel) serializer from Cocoon -> POI: no further
action has been taken yet.
9) Avalon Excalibur dependencies: Cocoon committers have now commit
karma to an Avalon CVS module that hosts code in heavy use by the
Cocoon project, making sure bugs can be fixed and patches applied
in due time.
10) the Milestone release scheme has been applied successfully, and has
resulted in a 2.1 release mid August.
11) Lenya incubation is still ongoing and monitored by the Cocoon PMC.
12), 13), 14): satisfactory ongoing.
New matter:
1) The Cocoon project has released a 2.1 version mid of August, and work
is under its way to release a forthcoming 2.1.1 quickfix release.
2) Discussions are starting on the upcoming 2.2 development.
3) Most notable discussion was about the existence (and/or creation)
of several overlapping ideas and frameworks for flow and form
handling inside Cocoon, and even though the discussions were
lenghty, at the verge of being flame-infested, the main discussion
participants came to an agreement, showing off the maturity of the
Cocoon community even when starting off from a discours of extreme
technical dissonance.
4) As a result of all this, work is under its way to refactor and
augment specific form handling code (Woody) into a truly
community-owned artefact, and API changes have been allowed to make
sure specific implementations (JS Flow with Continuations) leave
room for alternatives, should the community see fit.
5) Several new committers since the previous report: Ugo Cei, Marc
Portier, Guido Casper, Reinhard Pötz, Upayavira and Joerg Heinicke.
There's a de facto policy that all committers can subscribe to the
PMC list, but formalization of this, and whether this means they
can cast a binding PMC vote still needs to be discussed. There's a
certain tendency that there should be no distinction between active
committership and PMC membership. Lenya hasn't signed up any new
committers since it went into incubation, yet.
6) The Cocoon project guidelines and revised charter are under
construction, being based on a de-formalized branch of the Jakarta
ones.
Overall, the Cocoon project is a healthy and friendly community working
along the Apache spirit, and we expect no sudden problems to emerge.
As requested, here's the report on Cocoon's state of affairs, essentially since it has become a toplevel-status project, in no particular order. I do hope it gives the board a feel on how we are going. 1) Stefano resigned as a PMC Chair, and was succeeded by Steven Noels. A separate message in this regard has been filed with the Board already. 2) This marked somehow a transition towards a better separation between technical leadership and the more administrative/political function of a PMC Chair, which was one of the reasons Stefano decided to step down. The sense of liberation afterwards was tangible and enjoyed by all. 3) Clean-up of the Cocoon PMC Memberlist. The committee-info.txt now reflects the current composition of the Cocoon PMC quite faithfully, and new committers have been polled about their willingness to join. The policy that all committers are also PMC member, if they want to, still stands ATM. New or updated PMC members since lately are: Bruno Dumon, Geoff Howard, Ivelin Ivanov, Andrew Savory and Michael Wechner, who joins in from our incubating Lenya subproject. Pier and Sam are on our list as well. 4) The issue with the recursive Cocoon charter still stands and will be addressed shortly. 5) The use of the Cocoon name in the cocoondev.org and cocooncenter.com domain names, both offering Cocoon community resources, which had been brought forward as something the PMC should endorse by Stefano while he was Chair, has not been endorsed yet. We will discuss whether this is still needed and decide/report later on. 6) Related, we still need to discuss whether content being added to the Wiki can effectively be considered similar to code contributions, where a CLA is required, and code becomes (c) ASF. TBD. 7) There are some emotions concerning the move of a form handling library outside Apache CVS, hosted now on Sourceforge under http://www.xmlform.org/ - this might result in an oversight or community problem. The Cocoon community is aware of this issue, discussion is ongoing. 8) Discussion was held to transfer some code from Cocoon -> POI. No issues to be foreseen, no action taken yet. 9) There was some discussion about components quite central to Cocoon who are managed inside Avalon Excalibur (for reuse by other projects). The general direction is that Cocoon committers will be granted commit access to the respective Avalon CVS module upon demand, or by default. No conclusion as of now. 10) We opted for a Milestone release scheme until 2.1 is considered final, to get out of the longtime stall in releasing 2.1. So far, two milestone releases has been done. Mirroring support has been activated for our website and is in active use. 11) Lenya arrived as an incubating project, and the subsequent infrastructure request have been taken care of by the Infrastructure team in a very timely fashion - kudos. Lenya itself has a fair amount of traffic on its lists - and has not required any intervention of sorts from our side. 12) We also started moving our web and internal URI naming scheme towards reflecting our toplevel status, i.e. http://cocoon.apache.org/ for our external web presence, and http://apache.org/cocoon/ for internal (namespace) URIs. 13) Our external web presence is in the process of being refactored. 14) Stable Gump runs for Cocoon are (finally) operational and helpful.
The Cocoon Project is slowly starting up.
We are in the progress of establishing the voting rules (taken from
Avalon) so that we can start the PMC.
The PMC mail list has not been setup yet. I wanted to have the voting
rules resolved in public (means cocoon-dev) before asking
instrastructure@ to setup the pmc@cocoon.apache.org mail list.
Our policy will be to reduce traffic on pmc@cocoon.apache.org to only
those discussions that *require* privacy. Everything else will be done
in public.
The first PMC action will be to resolve the 'recursive bylaws' issue.
The second PMC action will be to establish a policy for the potential
use of the Cocoon name on commercial interests or cocoon-related non-ASF
web sites.
Infrastructure-wise, we are slowly moving away from our current
xml.apache.org location into cocoon.apache.org but we want to plan ahead
the movement to reduce user damage (broken links, mail archives and
such). Mirroring is also working even if not all links in our docs has
been updated (we plan on doing that after the move)
Pier Fumagalli has been voted back as a Cocoon committer (after his
renewed intention to work on cocoon and several patches submitted) and
is helping us a lot with infrastructure issues directly, reducing the
work on infrastructure@ directly.
At the same time, we would like to work with the other new top-level
project to synchronize the process of writing such PMC-oriented docs and
such. I'm peronally keeping an eye on infrastructure@ community@ and
general@incubator for those things and cocoon and avalon are already
sharing pieces of PMC-related work.
We are also planning to start using Forrest to build our own
documentation, even if this will make it a circular dependency (cocoon
depends on forrest and forrest depends on cocoon). But this is something
the cocoon documentation team will decide with the forrest developers
(most of which are also cocoon developers).
As far as community information, the cocoon communities appear healthy,
active and friendly. The high-rate of users becoming committers and
committers coming out of emerius status indicates a sane darwinistic
environment, well matched by the fact that only individuals or
small-sized companies perform most of Cocoon development and maintance,
allowing the community to be in total control. Frinction rate and
ego-oriented problems are, as usual, close to zero and I see no signs of
problems ahead.
- o -
As a special note, I would like to mention how the introduction of the
Cocoon wiki (hosted personally by Steven Noels' web site
www.cocoondev.org) has been seen by the user community as a great tool
and has generated very high-quality and useful documentation. The cocoon
wiki was also patched to sends diffs to the cocoon-docs@xml.apache.org
mail list (the documentation team), providing ownership and oversight.
This is seen as a very useful tool by the documentation team.
This has let us to believe that our current xml-driven documentation
system must be improved to match the editing simplicity of a wiki-based
solution, but without the unstructured-text problems of wiki content.
My personal vision is that Forrest should be dealing with those issues
and Cocoon help them with the technology they need, but that a better
documentation editing infrastructure is needed in order to allow a more
general audience to help us with that task.