This was extracted (@ 2024-04-17 22:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
Report was filed, but display is awaiting the approval of the Board minutes.
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Project Status: Current project status: ongoing. Issues for the board: none. ## Membership Data: Apache Tapestry was founded 2006-02-14 (18 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Volker Lamp on 2022-04-14. ## Project Activity: It was a quiet quarter, with lower activity than usual and no releases done. There was some interesting discussions about the team plans for the Tapestry's future, specially about support to the latest Java version and Jakarta EE. We also discussed one person to invite to the PMC, who unfortunately declined for the time being, and another for committer. ## Community Health: As mentioned in the previous section, it was a quarter with lower-than-usual activity overall, although we still had a few positive or neutral stats: 6 issues opened in JIRA, past quarter (-14% change) 4 issues closed in JIRA, past quarter (33% increase) 8 commits in the past quarter (-20% change) 4 code contributors in the past quarter (no change) 2 PRs opened on GitHub, past quarter (no change)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Project Status: Current project status: ongoing. Issues for the board: none. ## Membership Data: Apache Tapestry was founded 2006-02-14 (18 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Volker Lamp on 2022-04-14. ## Project Activity: We've released Tapestry 5.8.3 on 2023-07-16, with a new feature, an option for using multiple classloaders, aimed at users with large projects. We've been discussing the roadmap for the project, including how to adopt latest Java and Servlet API versions without leaving users on old, but currently supported, versions of them behind. ## Community Health: Even though we had a minor release very early in the latest quarter, the project had lower activity than in the previous one.
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache Tapestry was founded 2006-02-14 (17 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Volker Lamp on 2022-04-14. ## Project Activity: We have a release vote underway for a new release, 5.8.3, with 21 tickets, including bugs and enhancements, which is the highest for a long time. We're also working on some stuff for future releases, like improving our Gradle build and supporting Jakarta EE. ## Community Health: Very active quarter, specially when compared to the previous ones: dev@tapestry.apache.org had a 85% increase in traffic in the past quarter (37 emails compared to 20) users@tapestry.apache.org had a 92% increase in traffic in the past quarter (25 emails compared to 13) 19 issues closed in JIRA, past quarter (850% increase) 76commits in the past quarter (280% increase) 6 code contributors in the past quarter (50% increase) 5 PRs closed on GitHub, pastquarter (66% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (17 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Volker Lamp on 2022-04-14. ## Project Activity: This past quarter had its activity focused on developer productivity, specifically improvements to live class reloading and reducing the number of invalidated cached page instances. Getting it done requires getting a lot of moving parts implemented correctly, so it's complex work that should help developers on large projects. It's taking us longer than expected, we admit. ## Community Health: While the commit number was down, the community participation was up: dev@tapestry.apache.org had a 100% increase in traffic in the past quarter (16 emails compared to 8) users@tapestry.apache.org had a 116% increase in traffic in the past quarter (13 emails compared to 6) 7 issues opened in JIRA, past quarter (16% increase) 2 issues closed in JIRA, past quarter (100% increase) 15 commits in the past quarter (-48% change) 3 code contributors in the past quarter (50% increase) 3 PRs opened on GitHub, past quarter (300% increase) 3 PRs closed on GitHub, past quarter (50% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (17 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Volker Lamp on 2022-04-14. ## Project Activity: We've been working on better cache invalidation when not in production mode, something that should improve developer productivity, at least for larger projects. We've also had a couple bugfixes. We should definitely have a new release next quarter. ## Community Health: We had an increase in activity this quarter compared to the previous one: dev@tapestry.apache.org had a 120% increase in traffic in the past quarter (55 emails compared to 25) 6 issues opened in JIRA, past quarter (100% increase) 29 commits in the past quarter (625% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (17 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Volker Lamp on 2022-04-14. ## Project Activity: The project released version 5.8.2 in June 19th. Since then, project activity has been slow. It's a mature project, so sometimes we get these periods. We have plans for at least one new feature in the next quarter, plus a couple improvements to existing ones. ## Community Health: dev@tapestry.apache.org had a 120% increase in traffic in the past quarter (55 emails compared to 25) 3 issues opened in JIRA, past quarter (-82% change) 2 issues closed in JIRA, past quarter (-92% change) 4 commits in the past quarter (-92% change)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (16 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - Volker Lamp was added as committer on 2022-04-14 ## Project Activity: We had 2 Tapestry releases, both including bugfixes and new features (full Tapestry-IoC support for Java versions up to 17 and CORS support). We also added a new committer, Volker, who didn't waste any time getting his contributions into code and documentation. Our last release had the most different committers in a long time. ## Community Health: We've had the busiest quarter in the last few years: - 25 issues closed in JIRA, past quarter (38% increase) - dev@tapestry.apache.org had a 120% increase in traffic in the past quarter (55 emails compared to 25) - 5 code contributors in the past quarter (66% increase) 5 PRs closed on GitHub, past quarter (500% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (16 years ago) There are currently 28 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Ben Weidig on 2020-12-30. ## Project Activity: 2 releases were done in this quarter. 5.8.0, a major version, introducing REST support and async request, support. 5.8.1 introduces support for all Java features introduced between Java 9 and 17 in Tapestry-IoC,plus some other minor fixes and enhancements. We've just had a successful vote for adding a new committer, Volker Lamp, who already submitted his ICLA. It was a busier, more active quarter than average, as the community health stats below show. ## Community Health: dev@tapestry.apache.org had a 120% increase in traffic in the past quarter (55 emails compared to 25) 21 issues opened in JIRA, past quarter (950% increase) 17 issues closed in JIRA, past quarter (240% increase) 53 commits in the past quarter (47% increase) 8 PRs opened on GitHub, past quarter (300% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (16 years ago) There are currently 28 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Ben Weidig was added to the PMC on 2021-12-02 - No new committers. Last addition was Ben Weidig on 2020-12-30. ## Project Activity: Activity was mostly about 2 new features, one of them major, REST support, and support for asynchronous handling of requests. A new major release with them should be done before the next report. ## Community Health: While the user mailing list traffic was exactly the same as the last quarter, the dev one had a sharp increase in traffic. We also had a spike in commits and pull requests. In addition, we added a new member to our PMC. dev@tapestry.apache.org had a 120% increase in traffic in the past quarter (55 emails compared to 25) 34 commits in the past quarter (100% increase) 3 code contributors in the past quarter (50% increase) 2 PRs opened on GitHub, past quarter (100% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (16 years ago) There are currently 28 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - No new committers. Last addition was Ben Weidig on 2020-12-30. ## Project Activity: The team has been mostly working on small issues and features, plus creating a couple new features, specially proper REST support. I expect a new major release during the next quarter. ## Community Health: Since there were no issues this quarter, the community metrics were down: dev@tapestry.apache.org had a 43% decrease in traffic in the past quarter (28 emails compared to 49) 11 issues opened in JIRA, past quarter (-8% change) 6 issues closed in JIRA, past quarter (-40% change) 11 commits in the past quarter (-31% change)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (15 years ago) There are currently 28 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - No new committers. Last addition was Ben Weidig on 2020-12-30. ## Project Activity: We had an unusual number of releases this quarter due to security vulnerabilities, but we also had a few enhancements and other bugs done too. We also had more non-committer contributions than we usually do, which is always welcome and may result in inviting a new committer in the future. ## Community Health: Our hightlights: users@tapestry.apache.org had a 29% increase in traffic in the past quarter (48 emails compared to 37) 3 code contributors in the past quarter (50% increase)
@Bertrand: follow up with PMC about the private list discrepancies
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: No issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (15 years ago) There are currently 28 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - No new committers. Last addition was Ben Weidig on 2020-12-30. ## Project Activity: This quarter we finally managed to release Tapestry 5.7.0, a new major release, with the highlight being much more friendly to Java 9+ modules. Besides that, we also had 4 minor releases. 2 security vulnerabilities were fixed and a fixed version released within a few weeks of disclosure.. ## Community Health: We had a spike in mailing list traffic, mostly related to the new major version release. dev@tapestry.apache.org had a 0% decrease in traffic in the past quarter (112 emails compared to 112) users@tapestry.apache.org had a 400% increase in traffic in the past quarter (50 emails compared to 10)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: A couple months ago I tried to remove the Tapestry private mailing list subscribers which aren't in the PMC using the tool at https://whimsy.apache.org/committers/moderationhelper.cgi and now I noticed it hasn't worked. I tried again today. ## Membership Data: Apache Tapestry was founded 2006-02-14 (15 years ago) There are currently 28 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - Ben Weidig was added as committer on 2020-12-30 ## Project Activity: We've had a quarter with more commit and ticket activity than average due to our new upcoming major version, 5.7.0, which we expect be released at most next month. We've added a new committer to our team last December. ## Community Health: dev@tapestry.apache.org had a 26% increase in traffic in the past quarter (120 emails compared to 95) users@tapestry.apache.org had a 75% decrease in traffic in the past quarter (13 emails compared to 51) 14 issues opened in JIRA, past quarter (7% increase) 15 issues closed in JIRA, past quarter (114% increase) 78 commits in the past quarter (32% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (15 years ago) There are currently 27 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 9:4. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - No new committers. Last addition was Balázs Palcsó on 2019-01-17. ## Project Activity: Since the last report, we had Tapestry 5.6.0 and 5.6.1 released. After a long time, we received a code contribution and it's already merged to master. We've also been working on having proper Java 9+ modules support, requiring lots of refactoring. We expect to have 5.7.0 released with it in November. ## Community Health: After some quarters without much action, we had a better, more active one, and I hope we keep it that way in the upcoming ones. dev@tapestry.apache.org had a 253% increase in traffic in the past quarter (99 emails compared to 28) users@tapestry.apache.org had a 59% increase in traffic in the past quarter (51 emails compared to 32) 12 issues opened in JIRA, past quarter (50% increase) 8 issues closed in JIRA, past quarter (60% increase) 52 commits in the past quarter (173% increase) 2 code contributors in the past quarter (no change) 1 PR opened on GitHub, past quarter (100% increase)
## Description:
The mission of Tapestry is the creation and maintenance of software related to
Component-based Java Web Application Framework
## Issues:
There are no issues requiring board attention. Answering jm's question ("May
it be time to clean up your roster a little?") Is this just about the private
list or the committer and PMC member roster too? If this the former, yes, we
can definitely do that. If the latter, than we
(or at least I) need to research the right of doing it. I don't think Tapestry
ever did that. Roll call? Indeed, we have a number of non-active people still
in the committer and membership rosters.
## Membership Data:
Apache Tapestry was founded 2006-02-14 (14 years ago)
There are currently 27 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Dmitry Gusev on 2019-09-02.
- No new committers. Last addition was Balázs Palcsó on 2019-01-17.
## Project Activity:
No new releases, but we've working towards a new major release, 5.6.0,
very soon. One security vulnerability was reported to our team,
but it's already fixed in source and it's going to be released in 5.6.0.
## Community Health:
In the one hand, the users mailing list traffic was pretty low this quarter.
Interestingly, we had more traffic in the dev list, mostly in preparation for
the 5.6.0 release, than in the users one. Tapestry is a mature project with no
major new features or changes in the last years, so I'd say a decrease in mail
traffic is expected.
dev@tapestry.apache.org had a 0% decrease in traffic in the past quarter (50
emails compared to 50) users@tapestry.apache.org had a 90% decrease in traffic
in the past quarter (6 emails compared to 59) 8 issues opened in JIRA, past
quarter (60% increase) 5 issues closed in JIRA, past quarter (25% increase) 19
commits in the past quarter (-5% decrease) 1 code contributor in the past
quarter (-50% decrease)
No report was submitted.
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Questions from the last report * da: What was it that prevented you from releasing Tapestry 5.5, was it simply lack of developer cycles? Or is there some other headwind? Yes, lack of developer cycles. * druggeri: Thank you for sharing statistics, but can you please elaborate on what the statistics mean in terms of community health? Stats were stagnated when comparing to its previous report. On the other hand, this report has better stats than its previous report. ## Issues: There are no issues requiring board attention ## Membership Data: Apache Tapestry was founded 2006-02-14 (14 years ago) There are currently 27 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 9:4. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - No new committers. Last addition was Balázs Palcsó on 2019-01-17. ## Project Activity: The team released Tapestry 5.5.0 on 2020-03-20. We're also discussing a roadmap for the upcoming releases, specially when and how to deal with the latest developments in the Java languages. ## Community Health: The new major release has caused a raise in overall community participation: dev@tapestry.apache.org had a 322% increase in traffic in the past quarter (38emails compared to 9) users@tapestry.apache.org had a 130% increase in traffic in the past quarter (60 emails compared to 26) 4 issues opened in JIRA, past quarter (100% increase) 1 issue closed in JIRA, past quarter (100% increase) 7 commits in the past quarter (250% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (14 years ago) There are currently 27 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 9:4. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - No new committers. Last addition was Balázs Palcsó on 2019-01-17. ## Project Activity: This was a pretty slow quarter for the project. Unfortunately, we weren't able to release Tapestry 5.5 in the last quarter as we planned, but we definitely are going to do that in this month or in the next. We expect a little increase in community activity after the release. ## Community Health: dev@tapestry.apache.org had a 87% decrease in traffic in the past quarter (11 emails compared to 82) 3 issues opened in JIRA, past quarter (-50% decrease) 0 issues closed in JIRA, past quarter (-100% decrease) 1 commit in the past quarter (-92% decrease) 1 code contributor in the past quarter (-66% decrease) 1 PR opened on GitHub, past quarter (-66% decrease) 0 PRs closed on GitHub, past quarter (-100% decrease)
No report was submitted.
@Shane: pursue a report for Tapestry
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (14 years ago) There are currently 27 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 9:4. Community changes, past quarter: - Dmitry Gusev was added to the PMC on 2019-09-02 - No new committers. Last addition was Balázs Palcsó on 2019-01-17. ## Project Activity: A new beta, 5.5.5-beta-3 was released in September 15th. We've been preparing for the new major release, 5.5.0, and waiting for user feedback, specially the CSS changes (being able to use Twitter Bootstrap 3 out of the box, Bootstrap 4 out of the box, or no Bootstrap at all. ## Community Health: dev@tapestry.apache.org had a 1283% increase in traffic in the past quarter (83 emails compared to 6) users@tapestry.apache.org had a 46% decrease in traffic in the past quarter (43 emails compared to 79) 6 issues opened in JIRA, past quarter (200% increase) 4 issues closed in JIRA, past quarter (400% increase) 14 commits in the past quarter (180% increase) 3 code contributors in the past quarter (50% increase) 3 PRs opened on GitHub, past quarter (300% increase)
No report was submitted.
@Daniel: pursue a report for Tapestry
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: As Shane Curcuru correctly noted, the Tapestry team was very slow in responding and fixing the 3 vulnerabilities we got last year and we apologize for that. Fixes for two of them were released in Tapestry 5.4.4, published in December 18th, 2018. The other issue was fixed in 5.4.5, released in September 7th, 2019. We promise to do better next time. ## Membership Data: Apache Tapestry was founded 2006-02-14 (14 years ago) There are currently 27 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 9:4. Community changes, past quarter: - Dmitry Gusev was added to the PMC on 2019-09-02 - No new committers. Last addition was Balázs Palcsó on 2019-01-17. ## Project Activity: Tapestry 5.4.5 was released September 7th, 2019, and we're working towards the next major release, 5.5.0. ## Community Health: The Tapestry community has been shrinking over time for two main reasons: * It was a niche project among other Java web frameworks since its beginning. * The web development world has been steadily moving logic from server to client. In other words, more logic is being coded in JavaScript to run in the browser and less in the server, which is usually reduced to a set of REST endpoints. This way, Java web frameworks, or similar frameworks in any language, are losing users. Commits have been sparse in the latest couple of years due to mainly three factors: * We don't have any committer which is paid to work full-time or even part-time on Tapestry as other projects do. We're all working on Tapestry on our free time, with the exception of a few cases of a company commissioning us to work on some small enhancements. * The project reached a maturity level so it doesn't really have many features to be added. * The codebase is very flexible, so many interesting things can and are done outside of the Tapestry project. Our PMC has decided, a long time ago, to not include more subprojects so it could focus on the Tapestry core. There's a number of open source projects built on Tapestry, some integrating it with other libraries and frameworks, and some provide components. We may have a small community, but it's passionate. We voted a new PMC member this month. There's one committer we may invite to the PMC. Stats: * dev@tapestry.apache.org had a 284% increase in traffic in the past quarter (50 emails compared to 13) * users@tapestry.apache.org had a 76% increase in traffic in the past quarter (88 emails compared to 50) * 3 issues opened in JIRA, past quarter (200% increase) * 1 issue closed in JIRA, past quarter (-50% decrease) * 10 commits in the past quarter (42% increase) * 3 code contributors in the past quarter (50% increase) 1 PR opened on GitHub, past quarter (100% increase)
## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attenttion. ## Membership Data: Apache Tapestry was founded 2006-02-14 (14 years ago) There are currently 27 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Kalle Korhonen on 2019-01-16. - No new committers. Last addition was Balázs Palcsó on 2019-01-17. ## Project Activity: Some work being done on the upcoming Tapestry 5.5.0 release. We expect it to be released this year. ## Community Health: Community size and participation was a little lower in the last quarter. This should improve when the next version is released.
@Shane: pursue a more detailed report
No report was submitted.
@Joan: pursue a report for Tapestry
## Description: - A component-oriented framework for creating highly scalable web applications in Java. ## Issues: - There are no issues requiring board attention at this time ## Activity: - We've been preparing the 5.5.0 major release this last quarter. A number of snapshots and one beta version were released. ## Health report: - The project activity remains low but not zero. On the other hand, we got one addition to the PMC and one to the committers list. ## PMC changes: - Currently 11 PMC members. - Kalle Korhonen was added to the PMC on Wed Jan 16 2019 ## Committer base changes: - Currently 27 committers. - Balázs Palcsó was added as a committer on Thu Jan 17 2019 ## Releases: - Last release was 5.4.3 on Sun Apr 23 2017 ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months
## Description: - Description goes here ## Issues: - There are no issues requiring board attention at this time ## Activity: - Tapestry 5.4.4 was released in December 18th, the first release for a long time. - Tapestry 5.5.0-beta-1 was released in December 19th, preparing for the new major release. ## Health report: - We have a new commiter and a new PMC member votes. More people are contributing with discussions and patches. We're having now a period with more activity than we were having. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bob Harner on Thu Apr 06 2017 ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months - Last committer addition was Dmitry Gusev at Fri May 26 2017 ## Releases: - Last release was 5.4.4 on December 18 2017 ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
## Description:
- Apache Tapestry is a Java component-based web framework that features high
productivity, great code reuse, robust deployment, and terrific performance.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- It was a pretty slow quarter in terms of activity.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Bob Harner on Thu Apr 06 2017
## Committer base changes:
- Currently 26 committers.
- No new committers added in the last 3 months
- Last committer addition was Dmitry Gusev at Fri May 26 2017
## Releases:
- Last release was 5.4.3 on Sun Apr 23 2017
## Mailing list activity:
- users@tapestry.apache.org:
- 743 subscribers (down -5 in the last 3 months):
- 100 emails sent to list (112 in previous quarter)
- dev@tapestry.apache.org:
- 243 subscribers (down -1 in the last 3 months):
- 7 emails sent to list (21 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Tapestry is a Java component-based web framework that features high
productivity, great code reuse, robust deployment, and terrific performance.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- It was another pretty slow quarter in terms of activity.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Bob Harner on Thu Apr 06 2017
## Committer base changes:
- Currently 26 committers.
- No new committers added in the last 3 months
- Last committer addition was Dmitry Gusev at Fri May 26 2017
## Releases:
- Last release was 5.4.3 on Sun Apr 23 2017
## Mailing list activity:
- users@tapestry.apache.org:
- 744 subscribers (down -5 in the last 3 months):
- 133 emails sent to list (75 in previous quarter)
- dev@tapestry.apache.org:
- 243 subscribers (down -1 in the last 3 months):
- 7 emails sent to list (21 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
@Mark: pursue a report (again) for Tapestry
No report was submitted.
@Mark: pursue a report for Tapestry
## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Activity: - It was a pretty slow quarter in terms of activity. Mailing list had an increase in volume. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bob Harner on Thu Apr 06 2017 ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months - Last committer addition was Dmitry Gusev at Fri May 26 2017 - No new committers to be invited in sight. ## Releases: - Last release was 5.4.3 on Sun Apr 23 2017 ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 7 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - It was a pretty slow quarter in terms of activity. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bob Harner on Thu Apr 06 2017 ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months - Last committer addition was Dmitry Gusev at Fri May 26 2017 ## Releases: - Last release was 5.4.3 on Sun Apr 23 2017 ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - It was a pretty slow quarter in terms of activity. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bob Harner on Thu Apr 06 2017 ## Committer base changes: - Currently 26 committers. - Dmitry Gusev was added as a committer on Fri May 26 2017 ## Releases: - 5.4.3 was released on Sun Apr 23 2017 ## Mailing list activity: - users@tapestry.apache.org: - 772 subscribers (up 4 in the last 3 months): - 106 emails sent to list (71 in previous quarter) - dev@tapestry.apache.org: - 251 subscribers (down -2 in the last 3 months): - 58 emails sent to list (78 in previous quarter) ## JIRA activity: - 10 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We've just elected one new PMC member and one new committer. - We've just released a new maintenance version, 5.4.2, with fixes and a new feature, and we're working towards a new major version, 5.5. ## PMC changes: - Currently 11 PMC members. - Bob Harner was added to the PMC on Thu Apr 06 2017 ## Committer base changes: - Currently 25 committers. - Last committer addition was Jochen Kemnade at Fri Apr 25 2014 - Dmitry Gusev has just been voted as a new committer, but he's still in the process of filing the CLA and creating his Apache id. ## Releases: - 5.4.2 was released on Wed Apr 12 2017 ## JIRA activity: - 7 JIRA tickets created in the last 3 months - 9 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Activity on the user mailing list is slow, and unfortunately getting slower. - Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the 5.4 release. ## Branding requirement progress: - We'll try to add the 'tm' to the Apache Tapestry logo ourselves in the near future. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jochen Kemnade on Thu Mar 19 2015 ## Committer base changes: - Currently 25 committers. - No new committers added in the last 3 months - Last committer addition was Jochen Kemnade at Fri Apr 25 2014 ## Releases: - Last release was 5.4.1 on Sat Mar 19 2016 ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Activity on the user mailing list is slow, and unfortunately getting slower. - Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the 5.4 release. ## Branding requirement progress: - License and Security links added. - We'll try to add the 'tm' to the Apache Tapestry logo ourselves in the near future. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jochen Kemnade on Thu Mar 19 2015 ## Committer base changes: - Currently 25 committers. - No new committers added in the last 3 months - Last committer addition was Jochen Kemnade at Fri Apr 25 2014 ## Releases: - Last release was 5.4.1 on Sat Mar 19 2016 ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 41 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Activity on the user mailing list is slow. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the 5.4 release, with the occasional question about earlier versions. There are also occasional announcements concerning third-party libraries developed entirely outside the Tapestry team. - We just had an announcement of a new, free book on Tapestry, written by Barry Books. - Plans are underway to determine what changes will be introduced into Tapestry 5.5, which already has some coding going on. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jochen Kemnade on Thu Mar 19 2015 ## Committer base changes: - Currently 25 committers. - No new committers added in the last 3 months - Last committer addition was Jochen Kemnade at Fri Apr 25 2014 ## Branding requirement progress: - License and Security links are missing, but should be added very soon. - TM missing from logo: we'll try to get help from the designer who created the current logo. If we don't get it in a reasonable amount of time, we'll try to add the 'tm' ourselves. ## Releases: - Last release was 5.4.1 on Sat Mar 19 2016 ## JIRA activity: - 14 JIRA tickets created in the last 3 months - 10 JIRA tickets closed/resolved in the last 3 months
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? Thiago H. de Paula Figueiredo replaces Howard Lewis Ship as the project's PMC chair. When did the project last make any releases? Tapestry 5.4.1 was released on 16 Mar 2016. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is slow, but improving when compared to last quarter. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the 5.4 release, with the occasional question about earlier versions. There are also occasional announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. Plans are underway to determine what changes will be introduced into Tapestry 5.5. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 25 Apr 2014, and subsequently been voted into the PMC (2 Mar 2015). Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo Legal issues or questions: None. Infrastructure issues or strategic needs: None.
WHEREAS, the Board of Directors heretofore appointed Howard M. Lewis Ship (hlship) to the office of Vice President, Apache Tapestry, and WHEREAS, the Board of Directors is in receipt of the resignation of Howard M. Lewis Ship from the office of Vice President, Apache Tapestry, and WHEREAS, the Project Management Committee of the Apache Tapestry project has chosen by vote to recommend Thiago H. de Paula Figueiredo (thiagohp) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Howard M. Lewis Ship is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Tapestry, and BE IT FURTHER RESOLVED, that Thiago H. de Paula Figueiredo be and hereby is appointed to the office of Vice President, Apache Tapestry, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7F, Change the Apache Tapestry Project Chair, was approved by Unanimous Vote of the directors present.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? We have begun to discuss the process of a change in project lead, as Howard Lewis Ship's involvement in the project has markedly decreased over the last year or more. When did the project last make any releases? Tapestry 5.4.0 was released on 21 Dec 2015. This was a long, long, time in the making. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is slow. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the 5.4 release. There are also occasional announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. Plans are underway to determine what changes will be introduced into Tapestry 5.5. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 25 Apr 2014, and subsequently been voted into the PMC (2 Mar 2015). Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo Legal issues or questions: None. Infrastructure issues or strategic needs: None.
No report was submitted.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? We have begun to discuss the process of a change in project lead, as Howard Lewis Ship's involvement in the project has markedly decreased over the last year or more. When did the project last make any releases? The latest stable version of Tapestry (5.3.8) has been released 20 Nov 2014. We have made available the a series of beta builds of the upcoming 5.4 release, (most recently, 5.4-beta-35, on 23 Aug 2015), following successful votes. Although a consensus has been reached to pursue a release candidate, the effort is currently stalled. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is slow. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. There are also occasional announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 25 Apr 2014, and subsequently been voted into the PMC (2 Mar 2015). Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo Legal issues or questions: None. Infrastructure issues or strategic needs: None.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We have made available the a series of beta builds of the upcoming 5.4 release, (most recently, 5.4-beta-26, on 19 Jan 2015), following successful votes. A release candidate vote has completed, and a first release candidate will be made available in the next few days. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is slow. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. There are also frequent announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 25 Apr 2014, and subsequently been voted into the PMC (2 Mar 2015). PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: None.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We have made available the a series of beta builds of the upcoming 5.4 release, (most recently, 5.4-beta-26, on 19 Jan 2015), following successful votes. A release candidate vote was run and failed; a new RC vote is currently in progress. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is fair. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. There are also frequent announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 25 Apr 2014, and subsequently been voted into the PMC (2 Mar 2015). PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: None.
@David please submit a new report next month with some changed content
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We have made available the a series of beta builds of the upcoming 5.4 release, (most recently, 5.4-beta-26, on 19 Jan 2015), following successful votes. A release candidate is expected in the coming quarter. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is fair. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. There are also frequent announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 25 Apr 2014, and subsequently been voted into the PMC (2 Mar 2015). PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: None.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We have made available the a series of beta builds of the upcoming 5.4 release, (most recently, 5.4-beta-26, on 9 Jan 2015), following successful votes. A release candidate is expected in the coming quarter. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is fair. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. There are also frequent announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 25 Apr 2014, and subsequently been voted into the PMC (2 Mar 2015). PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: None.
No report was submitted.
No report was submitted.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We have made available the a series of beta builds of the upcoming 5.4 release, (most recently, 5.4-beta-22, on 2014-10-10), following successful votes. A release candidate is expected in the coming quarter. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is high. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. There are also frequent announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 2014-04-25. The last PMC addition has been Massimo Lusetti on 2012-08-27. PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: None.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We have made available the a series of beta builds of the upcoming 5.4 release, (most recently, 5.4-beta-6, on 2014-05-29), following successful votes. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is high. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. There are also frequent announcements concerning third-party libraries developed entirely outside the Tapestry team. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Jochen Kenmade has been voted in as a committer on 2014-04-25. The last PMC addition has been Massimo Lusetti on 2012-08-27. PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time with Howard Lewis Ship being the driving force behind Tapestry's development and various other committers working on areas of their interest. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: None.
@Chris: strike sentence re: driving force
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We have made available the first beta build of the upcoming 5.4 release, 5.4-beta-3, on 2014-03-03, following a successful vote. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is high. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. At this point we are primarily looking at fixing bugs (from our large backlog) and documenting the significant new features. When were the last committers or PMC members elected? Lance Semmens has been voted in as a committer on 2013-07-07. The last PMC addition has been Massimo Lusetti on 2012-08-27. PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time with Howard Lewis Ship being the driving force behind Tapestry's development and various other committers working on areas of their interest. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: * We have been unable to run builds on the Jenkins CI server for some time. We have been waiting for Uli to investigate.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Any issues for the Board? There are no Board-level issues at this time. When did the project last make any releases? The latest stable version of Tapestry (5.3.7) has been released 2013-04-29. We made available numerous preview builds of the upcoming 5.4 release, the latest (5.4-beta-2) on 2013-12-23. Describe the overall activity in the project over the past quarter. Activity on the user mailing list is high. Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the upcoming 5.4 release. Activity on the dev mailing list is medium. The focus of development currently lies on the upcoming Tapestry 5.4 which will bring major improvements in JavaScript support and other new features. We have run a successful vote to switch development of Tapestry 5.4 to beta, which entails an emphasis on fixing bugs over adding new features. An initial beta release is forthcoming. PMC member Thiago H. de Paula Figueiredo ran a successful campaign on IndieGoGo to fund a month of dedicated Tapestry 5.4 development. These changes are underway. Interest recent work from outside of Apache includes an integration with Atomsphere (a websocket implementation) and a refresh of the Tapestry Jumpstart tutorial site to align with Tapestry 5.4. When were the last committers or PMC members elected? Lance Semmens has been voted in as a committer on 2013-07-07. The last PMC addition has been Massimo Lusetti on 2012-08-27. PMC and committer diversity PMC and committer diversity is good. To our knowledge no two committers share the same employer. Levels of contribution vary over time with Howard Lewis Ship being the driving force behind Tapestry's development and various other committers working on areas of their interest. Project branding or naming issues, either in the project or externally. No known issues. Branding requirements progress: * "Project Website Basics: homepage is project.apache.org" - completed * "Project Naming And Descriptions: use proper Apache forms, describe product, etc." - completed * "Website Navigation Links: navbar links included, link to www.apache.org included" - License and Security links are missing * "Trademark Attributions: attribution for all ASF marks included in footers, etc." - completed * "Logos and Graphics: include TM, use consistent product logo on your site" - TM missing from logo * "Project Metadata: DOAP file checked in and up to date" - completed Legal issues or questions: None. Infrastructure issues or strategic needs: None.
Apache Tapestry is a Java component-based web framework that features high
productivity, great code reuse, robust deployment, and terrific performance.
Any issues for the Board?
There are no Board-level issues at this time.
When did the project last make any releases?
The latest stable version of Tapestry (5.3.7) has been released 2013-04-29.
We made available numerous preview builds of the upcoming 5.4 release, the
latest (5.4-alpha-24) on 2013-11-04.
Describe the overall activity in the project over the past quarter.
Activity on the user mailing list is high. Questions are answered with
participation of not only the core contributors but also by the community
at large. Discussion focuses especially around new features of the upcoming
5.4 release.
Activity on the dev mailing list is medium.
The focus of development currently lies on the upcoming Tapestry 5.4 which
will bring major improvements in JavaScript support and other new features.
When were the last committers or PMC members elected?
Lance Semmens has been voted in as a committer on 2013-07-07.
The last PMC addition has been Massimo Lusetti on 2012-08-27.
PMC and committer diversity
PMC and committer diversity is good. To our knowledge no two committers share
the same employer. Levels of contribution vary over time with Howard Lewis
Ship being the driving force behind Tapestry's development and various other
committers working on areas of their interest.
Project branding or naming issues, either in the project or externally.
No known issues.
Branding requirements progress:
* "Project Website Basics: homepage is project.apache.org" - completed
* "Project Naming And Descriptions: use proper Apache forms, describe product,
etc." - completed
* "Website Navigation Links: navbar links included, link to www.apache.org
included" - License and Security links are missing
* "Trademark Attributions: attribution for all ASF marks included in footers,
etc." - completed
* "Logos and Graphics: include TM, use consistent product logo on your site" -
TM missing from logo
* "Project Metadata: DOAP file checked in and up to date" - completed
Legal issues or questions:
None.
Infrastructure issues or strategic needs:
None.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Progress continues on the 5.4 release, which is still in alpha. There have been several further preview releases.
AI: Roy pursue a better report for next month
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. We've very recently voted in a new committer, Lance Semmens. He's currently getting his CLA processed. We've added comment notifications to the public website, and are getting a small stream of updates and other useful postings there. We've updated our build process to address a JavaDoc-related vulnerability, and regenerated the current set of JavaDoc files. Progress continues on the 5.4 release, which is still in alpha. There have been several further preview releases.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. The website has been migrated to svnpubsub; users have noticed an improvement in access speed. There has been great progress with Tapestry 5.4, and a further alpha preview release has been made available. We are currently planning a 5.3.7 bug fix release. There have been a number of notable third-party libraries for Tapestry announced recently. However, mailing list traffic is a bit lower than in prior quarters.
Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. Mailing list activity remains constant at about 1000 messages per month. After a long delay, Tapestry is now again building correctly on the Jenkins CI server. Great progress has been made on Tapestry 5.4, which is primarily concerned with significant improvements to Tapestry's client-side JavaScript. Two early alpha preview releases have been made available. We are currently in the process of migrating the website to svnpubsub.
Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and great performance. We've elected Massimo Lusetti to the Tapestry PMC. Work continues in the master branch on a significant re-engineering of Tapestry's client-side JavaScript support. We've released three bug fixes releases (5.3.4 through 5.3.6); this has been significantly easier to manage since the move from Subversion to Git. We've received an security vulnerability report from the MATTA organization. After a bit of a false start, we've had ongoing discussions with them. Primarily, there is a need for for HMAC (hash-based message authentication) when Tapestry stores serialized Java objects on the client. This has been addressed as part of the 5.3.6 release. Further security work will continue later, with support for detecting cross-site scripting attacks. We've been having some challenges getting Tapestry to build correctly on the Jenkins continuous integration server. Mailing list traffic continues in the 900 - 1000 messages per month range.
Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and great performance. We've had a bug fix release on the 5.3 branch that addressed some broken functionality and enhanced performance, especially under very heavy load. A further bug fix release is currently being voted on. Tapestry switched to Git as its source code repository, and that has greatly enhanced our ability to backport fixes from the master development branch to the 5.3 branch. This is a great service for our user community. In the master branch (which will be 5.4), work is well underway on significant improvements to Tapestry's JavaScript support on both the client and the server. There have been some interesting releases of late from the community: * Portlet support * jQuery integration * Twitter Bootstrap integration * cometd integration * Highcharts integration (client-side JavaScript charting) * ... and several more. Mailing list traffic seems to be in the summer doldrums, but still running around 1000 messages per month. We are considering options for documentation, given that the Confluence Wiki approach we currently use is being end-of-lifed.
(Tapestry)
Tapestry is a Java-based component web framework. This quarter saw the release of Apache Tapestry 5.3.2, which removes some limitations on Java component classes, and improves integration with the Spring framework. A small amount of work has continued on Tapestry 5.4, with most new features and fixes back-ported to the Tapestry 5.3.3 branch, which is nearing a release. Beyond Apache, there have been new releases of useful third party libraries, including jQuery integration, Twitter Bootstrap integration, Less/CoffeeScript integration, and more. Several of these third party libraries presage functionality that is expected to be the default in Tapestry 5.4. We're continuing to see mailing list traffic of 1000 - 1200 messages per month.
Tapestry is a component-based Java web framework that combines high performance, extensibility, conciseness, and excellent developer productivity. It has been a busy quarter for Tapestry; we've released Tapestry 5.3, a significant upgrade to Tapestry functionality and performance, just under a year after the 5.2 release. We have followed up with a 5.3.1 bug fix release, with at least one more bug fix release planned. The Tapestry 5.3.1 vote and release was executed by Massimo Lusetti which is notable as nearly all other recent releases where executed by Howard Lewis Ship. Some initial work on Tapestry 5.4 is already underway. Mailing list activity remains steady, with approximately 1400-1500 messages/month on the mailing lists. Widely used third party libraries (developed outside of Apache) such as chenille-kit and Tynamo have released new versions compatible with 5.3.1. Igor Drobiasko is continuing to work on his self-published book on Tapestry. Ulrich Stark is investigating a conversion of the Tapestry project site from Confluence to Apache CMS.
Tapestry is a Java component web framework. This has been busy quarter; we've voted in a new committer, Taha Hafeez. In addition, we've generated a long series of Tapestry 5.3 beta previews on the Apache Nexus. These have, in turn, spurred great feedback from the community, and allowed a number of critical performance and threading bugs to be identified and fixed. We are on target to make a release candidate available shortly, with the goal of voting up a final Tapestry 5.3 release soon after. Tapestry's last major release was 5.2.5 (December 2010), with a bug fix release, 5.2.6, in June 2011.
Tapestry is a Java language, component-based, web framework. This was a busy quarter for Tapestry; we've completed a switch from Maven to Gradle as the project's build tool. On the community side, we've elected three new committers: Francois Facon, Bob Harner, and Massimo Lusetti. The plastic bytecode library, developed by Howard Lewis Ship on GitHub, was imported as a new Tapestry module, and enhanced. Ultimately, this will break the current Tapestry dependency on JBoss Javassist. We've released a bug fix for Tapestry 5.2: version 5.2.6 addresses some critical Internet Explorer 9 incompatibilities. We've also voted to update (and document) our version naming system and release process. We now make previews available more frequently. Bob Harner and others have continued to improve the web site, including changes to older documentation that improved search results for new documentation.
Tapestry is a Java language, component-based web framework. Tapestry 5.2 We've released a maintenance release, 5.2.5, with minor fixes, including a change that makes Tapestry applications easier to debug. Tapestry 5.3 Still in alpha; with partial conversion from a Maven build to a Gradle build, the addition of a JPA integration library, numerous small changes, and the first steps in removing the dependency on Javassist (instead, using a wrapper around the ASM bytecode framework). Community We've elected two new committers: Kalle Korhonen and Francois Facon. We are matching mentors to GSOC (Google Summer Of Code) interns; we have three proposals.
Tapestry is a component-oriented web framework for Java. Branding requirements implementation progress: - Project Website Basics: homepage is project.apache.org [OK] - Project Naming And Descriptions: use proper Apache forms, describe product, etc. [OK] - Website Navigation Links: navbar links included, link to www.apache.org included, License and Security links are missing [PARTIAL] - Trademark Attributions: attribution for all ASF marks included in footers, etc. [OK] - Logos and Graphics: include TM, use consistent product logo on your site: TM missing [PARTIAL] - Project Metadata: DOAP file checked in and up to date It's still referencing Tapestry 4, need to update that. [PARTIAL] We've had a series of beta releases for Tapestry: 5.2.2, 5.2.3 (which was voted down due to a problem), and 5.2.4. 5.2.4 was voted up as a GA release on December 16th; the first GA release is almost 18 months. A live demo of Tapestry is now available at http://tapestry.zones.apache.org:8180/tapestry5-hotel-booking/signin We have deployed the new and improved web site, which is authored in Confluence and exported as a static web site. This includes a brand new and improved logo. In addition, we've had much community work (by non-committers, but with CLAs, and therefore access to Confluence) organizing and rewriting the documentation.
Work on Tapestry 5.2 has accelerated, with a goal of a GA release in Q4. The first alpha release, 5.2.0, was released in August, and the first beta release, 5.2.1, in October. In addition, we've voted in another committer, Josh Canfield. Quite a bit of effort has been expended moving documentation from individual Tapestry modules (in Maven's documentation format APT) and onto the Tapestry Confluence wiki. Howard Lewis Ship presented _Apache Tapestry: State of the Union_ as a birds-of-a-feather session at JavaOne in September. Mailing list activity has been steady, running at 1100 - 1500 messages per month.
Tapestry had a very busy quarter, with new PMC members voted in (Igor Drobiazko and Ulrich Stärk) as well as new committers (Robin Komiwes and Christophe Cordenier). In addition, we ran an vote to retire inactive PMC members. We had an unsuccessful vote to codify the Tapestry bylaws; another attempt is expected in the coming report period. We are preparing a new set of documentation whose content will be kept in the Confluence Wiki, addressing Tapestry's greatest weakness as a project. The goal is to create more accessible documentation, that is more up-to date and useful. Further, the Wiki will be accessible to anyone who has provided a CLA, leading to much more community involvement in the documentation. Part of this effort includes a new and very modern logo for the project. Our Google Summer of Code intern has been making progress on his projects. Finally, we expect to release an alpha of Tapestry 5.2 in the near future, with the goal of a short beta and a final release before JavaOne.
Tapestry 5.2 continues to progress at a good rate, but is still alpha. Howard has been tackling some significant infrastructure issues inside Tapestry that will eventually break the dependence on the JBoss Javassist module. Discussion has continued about how to reorganize the documentation to better address the concerns of new users. Several groups outside Apache are now regularly producing extensions to Tapestry. Thiago and Ulrich have spearheaded a Google Summer of Code internship; they will be mentoring a student who will be adding several Ajax-powered components to Tapestry's standard library. Andreas has switched Tapestry over to Apache's Hudson server for continuous integration, and the Apache Nexus server to stage release artifacts. The old server, tapestry.formos.com, is no longer referenced in the Tapestry 5.2 POMs. We expect to add additional committers over the next quarter, and will likely have a beta release of Tapestry 5.2.
This has been a good quarter for Tapestry involvement: several critical bug fixes were backported from the Tapestry 5.2 code base to Tapestry 5.0 (as release 5.0.19) and to Tapestry 5.1 (as release 5.1.0.7, still pending). Andreas Andreou has spearheaded the release process, as well as the use of Apache's Nexus server (to stage releases) and Hudson server (for continuous integration builds). We are investigating how to get xfvb (X virtual frame buffer) and FireFox installed on the Hudson server (a requirement for running the Tapestry 5 test suite). Work on Tapestry 5.2 has been accelerating, with over 80 bug fixes already in place, and with a newly-added module to support JSR-303 (Bean Validation). Traffic on the mailing list has been good, currently running about 74 messages a day. We've voted in a new committer, Ulrich Stark. In addition, we've expanded the PMC, voting in Thiago H. de Paula Figueiredo. We expect to continue expanding the size of the community in the near future.
Tapestry development was very relaxed over the summer. There's been a bit of bug fixing for the 5.2 release. Mailing list activity has been steady. A community-based effort to improve the organization of our online documentation is in progress. We are in the process of expanding our PMC, adding active committers. We are in the midst of a discussion on the mechanics of moving the Tapestry code base to a Git repository.
Justin will get with infrastructure to ensure that the git/svn issues have been resolved. The goal is to discourage projects from using git as their primary repository.
The Tapestry Project released Tapestry 5.1 on May 6. Tapestry 5.1 is a new stable release for the Tapestry 5 code base; this was a significant upgrade of Tapestry 5 in terms of functionality and performance. This was also a chance to demonstrate Tapestry's new commitment to backwards compatibility, with most users seeing a very easy upgrade from 5.0 to 5.1. Bug fixing has started for a forthcoming 5.2 release with some effort underway to ensure that Tapestry 5 can be deployed inside Google Application Engine. We are also considering a dot release for 5.1 to make it compatible for Google Application Engine. The newest committers, Thiago and Robert, are also the most active (after Howard). In addition, a new initiative to fill the documentation gap for Tapestry is underway. This has long been identified as the primary limitation of Tapestry: there is no good, comprehensive tutorial and cookbook for new users (free or otherwise), just detailed reference documentation. Howard is committed to working on documentation before switching gears to 5.2 coding. Tapestry 3 and Tapestry 4 are unofficially dead; there is limited support available on the mailing lists, but none of the committers have bandwidth for maintaining or evolving the code.
Brett noted the existence of Cascade which has an overlap of one committer with this project, but nobody saw that as an issue.
Tapestry 3, Tapestry 4 No activity. Tapestry 5 Work on 5.1 is finishing up; we've voted up several alpha releases and are voting on release 5.1.0.3 currently, which should be the beta. 5.1.0.4 is expected to be the GA release. The 5.1 release mostly adds features related to performance including a number of optimizations of internal code, and the use of GZIP compression in responses. The IoC container gains a number of new features that make it easier to customize Tapestry's behavior. Many users are upgrading from 5.0.18 to the 5.1 alphas and experiencing only minor issues, if any. Tapestry Community Robert Zeigler and Thiago H. de Paula Figueiredo have been voted on as Tapestry committers. Robert was already a Cayenne committer, Thiago is new to Apache. Both have contributed some significant code to Tapestry 5.1, largely in the area of customization of Tapestry URLs. Activity on the mailing lists appears steady. Howard Lewis Ship created a Tapestry Refcard for dzone.com. Activity on Tapestry360 (tapestry.formos.com) is increasing; this is an external site that provides project hosting for projects that can't live at Apache due to licensing or other concerns.
Betrand points out that http://tapestry.formos.com/ does not seem to include the "not endorsed by ASF" disclaimer.
Jim takes the action item to follow up on the lack of disclaimer and to inform PRC.
Tapestry 4.1 No work has been done on Tapestry 4. There is a backlog of issues in JIRA but nobody has stepped forward to work on them. Tapestry 5 A series of release candidates were voted up. 5.0.16 and 5.0.17 had minor issues that were corrected for 5.0.18, which was subsequently voted as the final release for 5.0. A set of performance improvements for Tapestry 5.0 are in the 5.0 branch; if released this will be 5.0.19. However, the same changes are available in 5.1. Tapestry 5.1 A significant number of new features have been added to Tapestry 5.1. We are hoping to have a 5.1 final release available in just a few months. We think it is important to the perceived stability of Tapestry that a release that builds on 5.0 but stays fully compatible be made available. An effort is underway to rewrite the standard Tapestry 5 documentation as an extended tutorial. Tapestry Community New committers added to the project over the last year have continued to contribute very lightly. The vast bulk of the code continues to be developed by Howard Lewis Ship. With no committers "stepping up to the bat", there has been no progress on expanding the membership of the PMC. That being said, the rest of the community is lively, with many users mentoring each other in the user list, a steady flow of issues (some with patches), and a respectable number of messages (79 messages / day, across the three mailing lists, according to MarkMail.org). In addition, to support the community, an external Tapestry development hub named "Tapestry 360" (tapestry.formos.com) is being set up by Formos (Howard Lewis Ship's employer). This will allow a centralized location for open source Tapestry development that can not take place at Apache due to, for example, licensing restrictions.
Some concerns about endorsing non-ASF resources in board minutes. No action taken.
Henning has been following this, and Jim will begin monitoring this. No actions on the concerns at this time, but could be in the future.
Tapestry 4: A maintenance release, 4.1.6, was created to address several highly-voted bugs, and add an JavaScript abstraction layer Tapestry 5: Two beta releases, 5.0.15 and 5.0.15, have been created. The next release, 5.0.16, is expected to be the release candidate.
Bertrand to follow up with Howard to make sure that an adequate report is made.
Tapestry PMC The Tapestry PMC has voted in a new committer, Igor Drobiazko. Tapestry 3 Jesse Kuhnert has been performing maintenance work on this release, adding performance improvements. Tapestry 4.1 Andreas Andreou has updated the tapestry-archetype to use the latest tapestry 4 versions and has included several enhancements suggested by the community. Together with Marcus Schulte they've fixed some minor bugs and a new 4.1.6 release should be expected soon. Tapestry 5 Two releases have occurred: 5.0.11 and 5.0.13 (5.0.12 was voted down due to a significant bug). Some minor work still remains before 5.0.14, which will likely be the release candidate.
Tapestry PMC The Tapestry PMC has voted in three new committers: Daniel Jue, Ted Steen and Kevin Menard. Tapestry 5 Voted on preview release 5.0.8, which was retracted due to the presence of a blocker bug, identified by Andreas Andreou. The system works! Reviewed the export notification policy (http://www.apache.org/dev/crypto.html) and found nothing in the Tapestry code base that would be in violation. Released Tapestry 5.0.9, 5.0.10 and 5.0.11. We are progressing towards API stability and a release candidate. Resolved an licensing conflict due to the use of a LGPL JavaScript Calendar; replaced the library with an ASL licensed equivalent.
Organization The Tapestry PMC has expanded, voting committers Andreas Andreou and Marcus Schulte up to PMC status. The PMC is actively discussing members of the community who may be extended an invitation to become committers. Tapestry 4.1 Work has been started which should allow any JavaScript library to serve as the "core" library used on the client by Tapestry. This would be accomplished via a set of configurable plugins and common base set of JavaScript library functions which can be mixed in with specific implementations tailored to the desired JavaScript library. Other than the new JavaScript library support the majority of work being done is bug fixing in Tapestry and OGNL. Tapestry 5 Two preview releases of Tapestry 5: 5.0.6 and 5.0.7 have been released, with work on 5.0.8 continuing at a brisk pace. The latest releases fill in some gaps in the functionality and have started to introduce Ajax features. Community support is still strong, with an active mailing list, several off-Apache component libraries under development, and lots of bugs being filed and fixed. Some questions about the licensing of certain JavaScript libraries bundled within Tapestry has been raised, which may require some clarification, and possibly, a switch in libraries.
Jim to take Tapestry branding issue to the PRC
Approved by General Consent.
Organization The Tapestry PMC has voted in another new member, Dan Adams, who expects to concentrate on Tapestry 5 development. Howard Lewis Ship finally figured out how to properly administer messages to the Tapestry private mailing list, which has really streamlined the process of adding new users. Tapestry 4.1 Tapestry 4.1 has continued to stabilize and evolve, with new 4.1.3 release now available. The upcoming 4.1.4 release should continue to provide more bug fixes / performance improvements / new components and JavaScript based widgets. It is expected that Tapestry 4 development will continue for some time but mostly be concentrated around minor improvements and bug fixes - until more of the core T4 developers have had time to transition over to Tapestry 5. The Tapestry 5 Ajax features being finalized will accelerate this process. OGNL The OGNL release cycle has now more or less started to mirror the Tapestry 4 release cycle, so the same sorts of things have been happening there as in Tapestry 4. Tons of bug fixes / performance improvements and the addition of java 5 support (besides one varargs bug) have also silently made their way in to the last 2.7.1 release of OGNL. It was suggested on the Struts dev list a while back that it might be nice to have OGNL moved in to the ASF to make it easier for more project developers to participate. It was suggested that the decision would have to be made by the controllers of OpenSymphony (who currently store the source), but the idea has merit. Not sure what - if any - other interest there is in moving OGNL into the ASF, so it looks like that concept is dead in the water unless someone else more motivated speaks up. JavaScript Several changes on the way JavaScript is used by Tapestry have been made. These allow users to integrate their preferred JavaScript/Ajax library in place of the one provided (Dojo Toolkit). Tapestry 5 Tapestry 5 progress is still a bit slow, but has picked up just in the last couple of weeks, and is expected to return to a reasonably brisk pace shortly. However, the road map has been extended out as the Ajax features are still missing (partly from debate over which Ajax framework to embrace). New Snapshot build / documentation process Nightly builds (via a Maven snapshot repository) and documentation (at http://tapestry.formos.com/nightly/tapestry5) are now available for Tapestry 5. The goal here is to publish snapshot versions of both software and documentation, so as to keep the main Apache site consistent with the latest stable releases -- this was getting to be a problem, with documentation on the main web site "ahead" of the latest non-snapshot releases. It is expected that Tapestry 4 will also eventually use this resource as well.
Approved by General Consent.
Organization The Tapestry PMC has voted in several new committers to the project: Dan Gredler, Marcus Schulte and Ben Dotte. Of course, Ben Dotte is unable to contribute since his CLA has not been recorded, despite repeated snail-mail and FAX copies being sent. This has dragged on for nearly two months. This is completely unacceptable and has fueled discussions about pulling out of Apache. Tapestry 4.1 Jesse has pulled together the optimized OGNL, and following a vote, release 4.1.2 has been unleashed. Tapestry 5 Progress has slowed slightly on Tapestry 5, but new features continue to be added. A vote to release a new preview, Tapestry 5.0.5, ran succesfully. Ajax features for T5 are just around the corner.
The board discussed ways in which to make it more obvious how to get in contact with the secretary when issues like this arise. No action was taken at this time.
Approved by General Consent.
Tapestry development is continuing in the 4.1 and 5 branches. Organization: The board has alerted the Tapestry PMC of irregularities in the voting and release of the early Tapestry 4 and Tapestry 5 releases. The clarifications has been embraced, with a mix of procedural and technical changes (such that we may "vote on the binaries"). We should see the first such proper vote coming soon, for Tapestry 5.0.4. The Tapestry PMC is also looking to extend the size of the Tapestry committer community. Several active users meet the qualifications and a vote is expected soon. Tapestry 4.1: Development of the 4.1.X series continues with feature improvements, bug fixes and the elimination of "quirks". In addition, Jesse Kuhnert has taken a leadership role in the development of the OGNL library on which Tapestry depends, and has been implementing an OGNL-to-bytecode compiler that will result in about a 30x improvement of performance of OGNL expressions (which account for at least 50% of the time spent processing a Tapestry request). It is expected that new OGNL library, release 2.7, will be nailed down within a few more weeks. The OGNL changes will be useful well outside the domain of Tapestry; Jesse has been in active communication with Patric Lightbody on furthering OGNL, potentially for use with WebWork, Struts 2 and elsewhere. Tapestry 5: Tapestry 5 continue to steam forward, adding new features and documentation. A bit of effort has been expended over the last few weeks to simplify the IoC container, adapting ideas from Google's Guice. Other simplifications are targetting to streamline integration with Spring, an important feature for the majority of users. User contributed patches have simplified and improved deployment of Tapestry application into a number of application servers (ironing out tricky class loading issues that are application-server specific). Beyond Apache, outside users are already creating reusable Tapestry 5 component libraries, a very encouraging development.
Clarification of "OGNL" was provided: It is the OpenSymphony project, and Struts 2 (aka WebWork) depends on it rather heavily.
Approved by General Consent.
Tapestry 4.1 Tapestry 4.1 integrates Ajax support directly into Tapestry. It bundles the Dojo toolkit libraries and adds many features to integrate the two. We've seen the gradual maturation of some of the new Ajax features, as well as general bug fixes and other improvements to the Tapestry 4 code base. The use of Maven 2 in has resulted in a much improved overall development process, and improved developer interaction with the Tapestry community. * Snapshot releases - Tapestry 4.1 / 4.1.1 / 4.1.2 have all been continually released into the Apache snapshot repositories throughout the development cycle for each release, resulting in much better user feedback as well as improved community happiness as bug fixes and improvements don't have to wait for the next official release. * Documentation Management - There has been big improvements in the quality and quantity of Tapestry documentation. In addition, marketing and support of Tapestry has also been improved increasing the prominence of related links on the Tapestry project home page. Tapestry 5 Tapestry 5 continues to steam along, many of the main features are in place, including basic form support and input validation. Performance continues to be excellent. Kent Tong is building a test framework for unit testing individual pages/components, aiming to make Tapestry 5 one of the most test-friendly web frameworks. Many core functions are already working. Miscellaneous Progress * Community Projects - There has been a lot of good activity involving outside project development. Some of the more exciting projects are Tapestry IDE support projects for NetBeans and for IntelliJ. A couple of different approaches to Hibernate integration have become available. A brand new Tapestry book, Tapestry 101, covers Tapestry 4 in detail. * Improved "Look" - The main Tapestry web sites and demo projects have all been reworked to project a more polished and professional look and feel.
Approved by General Consent.
Tapestry is now well established as a top-level domain, with two distinct sub-sections for Tapestry 4 and Tapestry 5. Tapestry 4.1 progress continues, headed by Jesse Kuhnert and Andreas Andreou. The 4.1.1 release is nearly ready. A lot of stabilization and refinement of the new Ajax-oriented APIs has been completed. Snapshot builds of the release have been published to the private Maven repository on a constant basis to early users. The remaining action items include additional Dojo widget components, as well as documentation and bug fixing. Tapestry 5 progress has also been great. Tapestry 5 is shaping up to be a compelling and highly productive platform for web application development. A minority of the user community is upset at the lack of backwards compatibility to Tapestry 4, the majority are very excited by the new features.
There was some discussion regarding the statement regarding the Tapestry 5 development and the effect on the "minority" and "majority". The concern was that these terms could be very subjective. Henri noted that it would be easy to see that the people upset at the T3->T4 migration pains would be sensitive to the proposed reinvention again for T5. After discussion the board determined that this is really a technical decision, although we need to ensure that the developer and user community are not being ignored.
Approved by General Consent
Progress on Tapestry 4.1 (mostly by Jesse Kuhnert) continues, including a converstion to a Maven 2 build. Kent Tong has finally regained commit access to the repository. Howard Lewis Ship has been working on the all-new Tapestry 5 code base.
See above comments
Approved by General Consent
6. Special Orders
Most of the TLP move work has been completed to move Tapestry out of Jakarta and on to the new subdomain http://tapestry.apache.org. Tapestry 4 and 5 now both use Maven2 to build/deploy web site updates. Tapestry 4.1 progress has continued to pick up pace. Snapshot builds are beginning to be released into the Maven2 snapshot repo. Plans are also being formed to extend and improve the current set of documentation for the 4.X branch in order to help fill in any missing gaps. Maven2 has been incredibly helpful in this regard. New sub-project structure: The top level http://tapestry.apache.org site now works in a similar way to that of http://tomcat.apache.org, in that each series of Tapestry releases has their own core web sites/documentation sets to go along with them. The sub-project sites are currently made up of 3.X/4.0/4.1/5. The tapestry4.1 site should be the new home of any new documentation efforts for the 4.1 series. New testing structure: With the conversion of Maven2 it has also been decided that Tapestry should now start using TestNG for unit testing as it hosts a very impressive set of features that go beyond those provided via JUnit. To better facilitate a clear path for Tapestry users to test their own Tapestry applications it is also planned that a new tapestry-testing subproject will be created to document and host all of the testing infrastructure that has thus far not been visible to Tapestry end users. The 4.1 series will also be using the Dojo toolkit's JavaScript based testing infrastructure to test core functionality provided, when possible. This comes in the form of a new library developed by Jesse Kuhnert that bundles up the Mozilla Rhino runtime plus JUM/jsunit in order to write test cases in JavaScript outside the confines of the Dojo build system.
The board was curious if Howard was the only one working on v5 and questions if there was any community involvement there? Henri noted that all of the code commits to date are from Howard, and that there is a little conversation on the mailing list but not very much: 12 or so changes to a couple of wiki pages.
Approved by General Consent
Most of the TLP move work has been completed to move Tapestry out of Jakarta and on to the new subdomain http://tapestry.apache.org. Tapestry 4 and 5 now both use Maven2 to build/deploy web site updates. Tapestry 4.1 progress has continued to pick up pace. Snapshot builds are beginning to be released into the Maven2 snapshot repo. Plans are also being formed to extend and improve the current set of documentation for the 4.X branch in order to help fill in any missing gaps. Maven2 has been incredibly helpful in this regard. New sub-project structure: The top level http://tapestry.apache.org site now works in a similar way to that of http://tomcat.apache.org, in that each series of Tapestry releases has their own core web sites/documentation sets to go along with them. The sub-project sites are currently made up of 3.X/4.0/4.1/5. The tapestry4.1 site should be the new home of any new documentation efforts for the 4.1 series. New testing structure: With the conversion of Maven2 it has also been decided that Tapestry should now start using TestNG for unit testing as it hosts a very impressive set of features that go beyond those provided via JUnit. To better facilitate a clear path for Tapestry users to test their own Tapestry applications it is also planned that a new tapestry-testing subproject will be created to document and host all of the testing infrastructure that has thus far not been visible to Tapestry end users. The 4.1 series will also be using the Dojo toolkit's JavaScript based testing infrastructure to test core functionality provided, when possible. This comes in the form of a new library developed by Jesse Kuhnert that bundles up the Mozilla Rhino runtime plus JUM/jsunit in order to write test cases in JavaScript outside the confines of the Dojo build system.
Tabled due to time constraints.
New committers Brian, Andreas and Jesse continue to attack the bug list and missing documentation. Another round of bug fixes for the Tapestry 3 and Tapestry 4 branches are (or near) ready for release. Kent Tong has finally gotten Subversion access. Committers now have proper access via SVN. A new Tapestry logo has been created and will debut on the revised project web page, once that is available. Howard Lewis Ship has been working on the Tapestry 5 code base. Tapestry 4.1 development progress coming along smoothly, featuring improved integration with the Dojo JavaScript toolkit. Expecting to be ready for an alpha release by end of May. Infrastructure has set up a blank tapestry.apache.org web site, ready to be populated, as well as setting up the new Tapestry mailing lists. Still to be done: moving the wiki to the new domain. Tapestry is due to receive the Duke's Choice award from Sun at JavaOne on May 16 2006. Howard Lewis Ship will be onhand to accept the award on behalf of the Tapestry project.
Approved by General Consent.
Tapestry has been in a state of transition away from a Jakarta sub-project and to an Apache top level project. Two new PMC members / committers have been added: Andreas Andreou and Brian K. Wallace. Andreas has been active in the external Tacos project (Ajax components for Tapestry). He and Brian have been actively mentoring and supplying patches for months. Bug fix releases of Tapestry 3 (release 3.0.4) and Tapestry 4 (release 4.0.1) have been released. These efforts have been spearheaded by Jesse Kuhnert and Brian K. Wallace. We've succesfully moved the SVN repository out from under the Jakarta project. Howard Lewis Ship has taken over responsibility for granting SVN access karma to Tapestry team members. We're beginning to formulate rules and procedures for breaking the Tapestry project into individual sub-projects. We are facing a large amount of work to convert from an Ant-based build to a Maven2-based build, primarily in terms of documentation (reams of which are currently in Forrest XML format). We are working on a new logo for Tapestry and expect to debut the new http://tapestry.apache.org/ web site when it is ready. Our remaining transfer tasks concern other bits of infrastructure to move out from under Jakarta: the Tapestry wiki, and the Tapestry mailing lists.
Approved by General Consent.
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to the implementation of the Tapestry Web Application Framework, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Tapestry PMC", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Tapestry PMC be and hereby is responsible for the creation and maintenance of software related to creation and maintenance of open-source software and documentation related to the Tapestry Web Application Framework based on software licensed to the Foundation; and be it further RESOLVED, that the office of "Vice President, Tapestry" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Tapestry PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Tapestry PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Tapestry PMC: * Howard M. Lewis Ship (hlship@apache.org) * Geoffrey Longman (glongman@gmail.com) * Kent Tong (freemant2000 at yahoo dot com) * David Solis (dsolis@gmail.com) * Jesse Kuhnert (jkuhnert@gmail.com) * Paul Ferraro (pferraro@apache.org) * Richard Lewis-Shell (rlewisshell@gmail.com) * Mind Bridge (mindbridgeweb@yahoo.com) * Tsvetelin Saykov (tsvetelin.saykov@gmail.com) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Howard Lewis Ship be appointed to the office of Vice President, Tapestry, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Tapestry PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Tapestry Project; and be it further RESOLVED, that the initial Tapestry PMC be and hereby is tasked with the migration and rationalization of the Apache Jakarta PMC Tapestry subproject; and be it further RESOLVED, that all responsibility pertaining to the Jakarta Tapestry sub-project and encumbered upon the Apache Jakarta PMC are hereafter discharged. Resolution 6A, Establish the Apache Tapestry Project, was approved by Unanimous Vote.