This was extracted (@ 2024-11-20 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 Velocity is the creation and maintenance of software related to A Java Templating Engine ## Project Status: Current project status: Ongoing, low activity Issues for the board: none. ## Membership Data: Apache Velocity was founded 2006-10-24 (18 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Velocity Master POM 7 was released on 2024-07-31. velocity-engine-2.3 was released on 2021-02-27. velocity-tools-3.1 was released on 2021-02-27. ## Community Health: Michael has not withdrawn nor stated intention to any of us that he intends to do so. We are proceeding at our usual "fits and starts" pace toward a new release. We also have a new potential contributor in Eduard Drenth. Yes, there is risk if Michael were to withdraw, but as you saw with the roll call, Geir is still lurking and would likely help maintain the project if something were to happen to one of the rest of us. I also consider the somewhat cranky argument over handling the javax->jakarta business very positive as the "vocal" users in that discussion are just the type to potentially get involved if needed. They wouldn't argue if they didn't care, right? :)
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Project Status: Current project status: Ongoing, low activity Issues for the board: None ## Membership Data: Apache Velocity was founded 2006-10-24 (18 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Released a new version of our master POM in February. Work on a new Engine and Tools release have been slowed by discussion on versioning patterns, but they are still expected to proceed. ## Community Health: Emails are still answered, though with delay at times. There is low developer activity and much stability, but maintenance continues. There is no expectation of notable/ongoing issues in responding to mailing list questions.
@Christofer: pursue a roll call for Velocity PMC
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Project Status: Current project status: Active, fresh releases imminent Issues for the board: PMC Chair (me) was negligent due to temporary family issues. ## Membership Data: Apache Velocity was founded 2006-10-24 (17 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Feb 6 - released new Velocity Master POM New releases for both Velocity Tools and Velocity Engine are under active work. ## Community Health: Stable, with few active committers. Big short-term jump in activity as Michael Osipov is preparing new releases, mostly tech debt focused, as the project is in maintenance mode.
No report was submitted.
No report was submitted.
No report was submitted.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Project Status: Current project status: Dormant Issues for the board: There are no board level issues at this time. ## Membership Data: Apache Velocity was founded 2006-10-24 (17 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: There is still some slow motion toward a new Tools release, as well as a PR to deal with the javax/jakarta fiasco. ## Community Health: A very quiet quarter, even for Velocity. The PMC members needed are still around and available, but very little action is happening.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache Velocity was founded 2006-10-24 (17 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Recently voted (03-25-2023) to release a new master POM file in anticipation of a few upcoming releases. ## Community Health: Most work is being handled by two PMC members. Others are tracking conversations but dormant, as usual.
No report was submitted.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (16 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: - velocity-engine-2.3 was released on 2021-02-27. - velocity-tools-3.1 was released on 2021-02-27. - velocity-engine-2.2 was released on 2020-02-02. ## Community Health: There was more activity than in recent quarters, including new issues, but there has been no substantial work, with only one PR and one commit.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (16 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: No new features, community activity, or releases in the last quarter. Recent releases: velocity-engine-2.3 was released on 2021-02-27. velocity-tools-3.1 was released on 2021-02-27. velocity-engine-2.2 was released on 2020-02-02. ## Community Health: Quiet most of the quarter with a current flurry of small issues being discussed and resolved.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (16 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Last releases: velocity-engine-2.3 was released on 2021-02-27. velocity-tools-3.1 was released on 2021-02-27. velocity-engine-2.2 was released on 2020-02-02. ## Community Health: Quiet, activity on a few Jira issues, no coding was done in this quarter. Most developers seem satisfied with it as is.
No report was submitted.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (16 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Velocity Engine 2.3 release available 2021-03-08 Velocity Tools 3.1 released available 2021-03-08 ## Community Health: The project remains, as one PMC member put it, "hyper stable", with the devs largely focused on other projects, but still rallying (eventually) when work needs to get done.
No report was submitted.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (15 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: The last quarter was quiet, as seems typical for us this time of year. Only a little activity on one PR and a few user questions. ## Community Health: We were slow to respond to one user question, but otherwise the community seems like its usual sedate, largely dormant self.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (15 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: One of the developers has been doing some work on Tools. There's a contributor PR for Engine under consideration, a few other Engine fixes have been accepted. Another contributor created a Prettier formatter. ## Community Health: Things are slow, and we have a limited number of active committers, but it's enough to keep things moving and respond to contributors and issues (albeit slowly).
No report was submitted.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (15 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Minimal activity. A few bug reports and discussion. One PR was dealt with. ## Community Health: Stable, present, and inert. The most discussed item was for an older Velocity version, which pretty well demonstrates the contentment of most users to remain on older versions.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (15 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Velocity Engine 2.3 was released on Feb 27. Velocity Tools 3.1 was released on Feb 27. Minimal activity since that time. ## Community Health: The project is highly stable with no notable problems. The ongoing mild problem is low interest in additional investment of energy from existing developers or entice new developers to get involved.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (14 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Velocity Engine 2.3 release available 2021-03-08 Velocity Tools 3.1 released available 2021-03-08 These releases each resolve a recent CVE reports for those projects. Details have been published: https://velocity.apache.org/news.html#CVE-2020-13936 https://velocity.apache.org/news.html#CVE-2020-13959 ## Community Health: The project remains, as one PMC member put it, "hyper stable", with the devs largely focused on other projects, but still rallying (eventually) when work needs to get done. Issues do eventually get addressed. The community is small, the active community is smaller, but it is functioning. The board called for a roll call due to our developer's schedules not being satisfactory in regards to the CVE. Three PMC members responded (with various levels of irritation). The PMC member who did most to implement the fixes ignored the roll call thread. When it came time to get the releases out, the PMC showed up to test and approve with 5 binding +1 for the Engine release and 6 binding +1 for the Tools release. I'd call that the actual, meaningful "roll call".
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: The project needs new releases of Engine and Tools to make some key fixes available, but none of the PMC have spearheaded a release vote yet. ## Membership Data: Apache Velocity was founded 2006-10-24 (14 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: More work than usual has been done, including on docs and infrastructure. Both Engine and Tools are due for release. ## Community Health: Increasing contributions via Github PRs have been happening. Still need more experienced PMC devs to make more time to get releases out.
@Craig: explain security issue relevance and board communications
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (14 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Most of the action has been in Velocity Tools with an important bugfix that was much discussed. The fix is in, but we need some action to get a release out soon. Light work on Engine, with another important bugfix and a new branch to adopt and integrate some orphaned Spring integration code waiting for integration into the master branch and, of course, a release. ## Community Health: Slow responses to PRs in Github. Bugfix releases need to happen for both Tools and Engine, but there's little motion there.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: No board level issues at this time. ## Membership Data: Apache Velocity was founded 2006-10-24 (14 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Will has been dealing with a security issue for users that allow 3rd party templates that will mean a new bugfix release shortly. ## Community Health: Quiet but steady, as usual.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (14 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - Thomas Mortagne was added as committer on 2020-03-09 ## Project Activity: Most activity was addition of Thomas as a committer and getting Velocity git repositories set up on gitbox.apache.org. Things were otherwise very quiet this quarter. ## Community Health: The community continues to be rather quiet but active and progressing nonetheless.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (13+ years ago) There are currently 14 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Michael Osipov on 2017-01-30. ## Project Activity: Velocity Engine 2.2 was released on 2020-02-02. This release has improvements to logging, custom parsing support, and a big effort toward improved backward compatibility with 1.x versions. ## Community Health: The active community is small but very capable. Coding continues to be handled by a single PMC member, with others contributing to votes and discussion. The dormant PMC members did a great job coming out of dormancy to vet and support the 2.2 Engine release. Stability continues to be both intentional and appropriate, but the more active PMC members are planning to reach out to a few very active contributors, hoping to talk them into taking committer and, eventually, PMC roles.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (13 years ago) There are currently 14 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Michael Osipov on 2017-01-30. ## Project Activity: VelocityTools has seen some light improvements. Our Maven build infrastructure has gotten a few patches. Velocity Engine 2.2rc1 is out with some nice log, custom parser, and backwards-compatibility improvements. It has received two PMC votes for GA release. It is waiting on a third. ## Community Health: We are getting community input and contributions, but development is still largely handled by a single PMC member. Dormant PMC members also outnumber active ones. As the project is extremely stable by intent, the minimal committer activity is appropriate, but it should not take this long to get more PMC response on a release candidate quality.
## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Velocity was founded 2006-10-24 (13 years ago) There are currently 14 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Michael Osipov on 2017-01-30. ## Project Activity: Several of the devs have been working on custom parser support to allow configurable grammars. There have also been some contributions for dependency security notices and the Maven build. ## Community Health: Better than usual. Multiple contributors. One dev is still leading the bulk of the work, but others are involved in feedback and oversight.
## Description:
- Java-based template engine
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Moderate. One developer actively adding features, fixing bugs, and
proposing a possible major new sub-project and/or feature for
VelocityTools.
## Health report:
- Project is maintained and pushing forward, but the dev community is
minimal.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- velocity-engine-2.1 was released on Sat Mar 30 2019
## Mailing list activity:
- Mostly actual work by Claude and discussion thereof.
- dev@velocity.apache.org:
- 119 subscribers (down -1 in the last 3 months):
- 106 emails sent to list (24 in previous quarter)
- general@velocity.apache.org:
- 72 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (2 in previous quarter)
- user@velocity.apache.org:
- 278 subscribers (down -6 in the last 3 months):
- 6 emails sent to list (2 in previous quarter)
## JIRA activity:
- 10 JIRA tickets created in the last 3 months
- 16 JIRA tickets closed/resolved in the last 3 months
## Description:
- Java-based template engine
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Low. No work, just the necessary user support.
## Health report:
- Holidays are always a quiet period for us, but the small team is still
functioning and responsive.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- Last release was velocity-tools-3.0 on Wed Oct 10 2018
## Mailing list activity:
- Things were very quiet through the holidays. Mostly just a bit of user
support and bug reports
- dev@velocity.apache.org:
- 120 subscribers (down -1 in the last 3 months):
- 24 emails sent to list (203 in previous quarter)
- general@velocity.apache.org:
- 72 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (2 in previous quarter)
- user@velocity.apache.org:
- 284 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Moderate. Activity mostly centering on the Tools 3.0 release.
## Health report:
- Project has pulled together several major releases in last 4 months. Active
team is small, could be more responsive to contributors, but things are
getting done.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- Velocity Master POM 3 was released on 2018-10-25
- Velocity Tools 3.0 was released on 2018-10-01
- Velocity Engine 2.0 was released on 2018-08-06
## Mailing list activity:
- Lots of work on the Tools 3 release, some discussion on backward
compatibility for Engine 2.0 regardless of major version bump. Not much
else.
- dev@velocity.apache.org:
- 120 subscribers (up 0 in the last 3 months):
- 204 emails sent to list (116 in previous quarter)
- general@velocity.apache.org:
- 72 subscribers (down -1 in the last 3 months):
- 2 emails sent to list (4 in previous quarter)
- user@velocity.apache.org:
- 284 subscribers (down -3 in the last 3 months):
- 3 emails sent to list (5 in previous quarter)
## JIRA activity:
- 12 JIRA tickets created in the last 3 months
- 38 JIRA tickets closed/resolved in the last 3 months
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Moderate. Discussion on upcoming Tools release and various security risks
from dependencies.
## Health report:
- Project is stable and quiet. Maintenance issues and user questions are all
handled promptly, developers are talking, but no work happened.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- None this period.
- Last release was Engine 2.0 GA, Aug 6, 2017.
## Mailing list activity:
- Lists are fairly quiet. Most users either don't have questions or find
answers on Stack Overflow.
- Developers discussing Tools 3 and dependency issues.
- dev@velocity.apache.org:
- 120 subscribers (down -3 in the last 3 months):
- 117 emails sent to list (14 in previous quarter)
- general@velocity.apache.org:
- 73 subscribers (up 0 in the last 3 months):
- 4 emails sent to list (4 in previous quarter)
- user@velocity.apache.org:
- 288 subscribers (down -1 in the last 3 months):
- 5 emails sent to list (7 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 31 JIRA tickets closed/resolved in the last 3 months
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Minimal. Some light dev discussion on Tools project configuration for
upcoming major release.
## Health report:
- Project is stable and quiet. Maintenance issues and user questions are all
handled promptly, developers are talking, but no work happened.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- None this period.
- Last release was Engine 2.0 GA, Aug 6, 2017.
## Mailing list activity:
- Lists are fairly quiet. Most users either don't have questions or find
answers on Stack Overflow.
- Developers still talk, but barely.
- dev@velocity.apache.org:
- 123 subscribers (down -2 in the last 3 months):
- 13 emails sent to list (64 in previous quarter)
- general@velocity.apache.org:
- 73 subscribers (down -7 in the last 3 months):
- 4 emails sent to list (0 in previous quarter)
- user@velocity.apache.org:
- 289 subscribers (down -5 in the last 3 months):
- 7 emails sent to list (20 in previous quarter)
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- A few site updates, some user questions, and fair bit of JIRA cleanup.
## Health report:
- Project is stable and quiet. Maintenance issues and user questions are all
handled promptly, but there's no development work to speak of.
## PMC changes:
- Currently 9 PMC members.
- Michael Osipov was added to the PMC on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- None this period.
## Mailing list activity:
- Mostly issue clean up by Michael
- dev@velocity.apache.org:
- 125 subscribers (up 0 in the last 3 months):
- 78 emails sent to list (17 in previous quarter)
- general@velocity.apache.org:
- 80 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (1 in previous quarter)
- user@velocity.apache.org:
- 294 subscribers (down -4 in the last 3 months):
- 28 emails sent to list (16 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 12 JIRA tickets closed/resolved in the last 3 months
## Description: - Java-based template engine ## Issues: - No issues requiring board attention at this time. ## Activity: - Light activity, mostly centered around changes to the Velocity Tools project ## Health report: - Project is fine. Light work on Tools project. Pretty quiet since the release of Engine 2. ## PMC changes: - Currently 9 PMC members. - Michael Osipov was added to the PMC on Thu Jul 27 2017 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was Michael Osipov at Mon Jan 30 2017 ## Releases: - None this period. ## Mailing list activity: - Very light traffic, mostly about bugs in Tools. - dev@velocity.apache.org: - 125 subscribers (up 0 in the last 3 months): - 17 emails sent to list (71 in previous quarter) - general@velocity.apache.org: - 80 subscribers (down -3 in the last 3 months): - 1 emails sent to list (3 in previous quarter) - user@velocity.apache.org: - 299 subscribers (down -8 in the last 3 months): - 16 emails sent to list (2 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months
## Description: - Java-based template engine ## Issues: - No issues requiring board attention at this time. ## Activity: - Light activity, mostly centered around new PMC member, new Engine 2.0 release, and a few minor bugs. ## Health report: - Project is healthy. New major version of core product, latest committer has moved up to PMC. ## PMC changes: - Currently 9 PMC members. - Michael Osipov was added to the PMC on Thu Jul 27 2017 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was Michael Osipov at Mon Jan 30 2017 ## Releases: - Engine 2.0 was released as GA on Aug 6 2017 ## Mailing list activity: - Light traffic regarding PMC membership, Engine 2.0 release, and minor bugs. - dev@velocity.apache.org: - 125 subscribers (up 0 in the last 3 months): - 67 emails sent to list (47 in previous quarter) - general@velocity.apache.org: - 85 subscribers (up 1 in the last 3 months): - 0 emails sent to list (1 in previous quarter) - user@velocity.apache.org: - 306 subscribers (up 4 in the last 3 months): - 0 emails sent to list (9 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months
## Description: - Java-based template engine ## Issues: - No issues requiring board attention at this time. ## Activity: - Light activity, mostly finishing touches on Engine 2.0 release ## Health report: - Engine 2.0 release candidate quality vote in progress. Expected to be approved as GA shortly. - A Tools 3.0 release is still planned, but work is on hold until at least Engine 2.0 goes GA. ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was Michael Osipov at Mon Jan 30 2017 ## Releases: - None in this quarter (2.0 will just miss) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months
## Description: - Java-based template engine ## Issues: - No issues requiring board attention at this time. ## Activity: - Very busy, mostly one developer, with others testing and discussing changes. Still aiming at Engine 2.0 release soon; there have been many release candidates already. ## Health report: - Engine 2.0 release candidates are coming steadily, release should be soon. - A Tools 3.0 release is still planned, but Engine 2.0 has priority currently. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015 ## Committer base changes: - Currently 14 committers. - Michael Osipov was added as a committer on Mon Jan 30 2017 ## Releases: - none in this quarter ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months
## Description: - Java-based template engine ## Issues: - No issues requiring board attention at this time. ## Activity: - Very busy, thanks to one developer, with others testing and discussing changes. Prep and final debugging for Engine 2.0 release. Much work happening on Tools 3.0 also. ## Health report: - Engine 2.0 test builds are coming steadily, release should be soon. - Work is also in progress toward a Tools 3.0 release. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Mike Kienenberger at Mon Jun 01 2015 ## Releases: - velocity-master POM 2 ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 30 JIRA tickets closed/resolved in the last 3 months
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Very busy, thanks to one developer mostly. Many old patches applied. Much new work toward a 2.0 release.
## Health report:
- Moved much closer to a 2.0 release, thanks to hard work of one PMC member. Others chimed in on questions, everyone eager to see a 2.0 release happen.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015
## Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Mike Kienenberger at Mon Jun 01 2015
## Releases:
- No releases in the last quarter. Last release of consequence was Nov 2010.
## Mailing list activity:
- This shows the big bump in dev activity. Pretty sure those unsubscribing
weren't interested in being on an active list.
- dev@velocity.apache.org:
- 124 subscribers (down -2 in the last 3 months):
- 151 emails sent to list (6 in previous quarter)
- general@velocity.apache.org:
- 85 subscribers (down -4 in the last 3 months):
- 9 emails sent to list (0 in previous quarter)
- user@velocity.apache.org:
- 307 subscribers (down -1 in the last 3 months):
- 1 emails sent to list (1 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 44 JIRA tickets closed/resolved in the last 3 months
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Light developer activity. Light mailing list traffic. Moderate JIRA traffic.
## Health report:
- Velocity is of minimal priority to the developers at this time.
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015
## Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Maurice (Mike) L. Kienenberger at Mon Jun 01
2015
## Releases:
- No releases in the last quarter
## Mailing list activity:
- dev@velocity.apache.org:
- 126 subscribers (down -1 in the last 3 months):
- 28 emails sent to list (28 in previous quarter)
- general@velocity.apache.org:
- 89 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
- user@velocity.apache.org:
- 308 subscribers (down -1 in the last 3 months):
- 1 emails sent to list (10 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months
## Description:
- Java-based template engine
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- No commits. Very light mailing list and JIRA traffic.
## Health report:
- Velocity is of minimal priority to the developers at this time.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015
## Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Maurice (Mike) L. Kienenberger at Mon Jun 01
2015
## Releases:
- No releases in the last quarter.
## Mailing list activity:
- dev@velocity.apache.org:
- 126 subscribers (up 0 in the last 3 months):
- 28 emails sent to list (30 in previous quarter)
- general@velocity.apache.org:
- 88 subscribers (down -6 in the last 3 months):
- 2 emails sent to list (0 in previous quarter)
- user@velocity.apache.org:
- 309 subscribers (down -1 in the last 3 months):
- 10 emails sent to list (5 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
Description: Java-based template engine
Issues: No issues requiring board attention at this time.
Activity: No developer activity. Very light mailing list and JIRA traffic.
Health report: The early summer surge of activity has faded to the background.
Developers are busy with other projects.
PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015
Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Maurice (Mike) L. Kienenberger at Mon Jun 01
2015
Releases:
- No releases in the last quarter.
Mailing list activity:
- dev@velocity.apache.org:
- 126 subscribers (up 1 in the last 3 months):
- 34 emails sent to list (162 in previous quarter)
- user@velocity.apache.org:
- 310 subscribers (down -4 in the last 3 months):
- 10 emails sent to list (2 in previous quarter)
JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Velocity committee [Nathan Bubna]
## Description:
Java-based template engine
## Activity:
We had a bump in activity this last quarter, leading to a new committer and a
committer joining the PMC. More talk than work, but still good to see
progress toward a next version. Things have died down again this last month
or so.
## Health report:
Better than before, but things are still fairly sedentary.
## Issues:
Nope, no issues for the board.
## LDAP committee group/Committership changes:
- Currently 13 committers and 9 LDAP committee group members.
- Sergiu Dumitriu was added to the LDAP committee group on Mon Jun 01 2015
- Maurice (Mike) L. Kienenberger was added as a committer on Mon Jun 01 2015
## Releases:
- No releases in the last quarter.
## Mailing list activity:
- dev@velocity.apache.org:
- 125 subscribers (down -2 in the last 3 months):
- 169 emails sent to list (7 in previous quarter), lots of fun.
- user@velocity.apache.org:
- 314 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (41 in previous quarter)
- general@velocity.apache.org:
- 94 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- This list has long been pointless.
## JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 12 JIRA tickets closed/resolved in the last 3 months
## Description:
Java-based template engine
## Activity:
- Work is progressing on a 1.8 version and resurrecting the artifact and site
builds.
## Issues:
- There are no issues requiring board attention at this time.
## PMC/Committership changes:
- Currently 13 committers and 9 PMC members in the project.
- Sergiu Dumitriu was added to the PMC on Mon Jun 01 2015
- Maurice (Mike) L. Kienenberger was added as a committer on Mon Jun 01 2015
## Releases:
- No releases
## Mailing list activity:
- dev@velocity.apache.org:
- 127 subscribers (down -5 in the last 3 months):
- 136 emails sent to list (7 in previous quarter)
- user@velocity.apache.org:
- 314 subscribers (down -5 in the last 3 months):
- 9 emails sent to list (42 in previous quarter)
- general@velocity.apache.org:
- 93 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
## JIRA activity:
- 9 JIRA tickets created in the last 3 months
- 8 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
Apache Velocity is a java template engine and related projects. RELEASES * Last release was master POM, May 2012 * Last noteworthy release was Engine in 2010 CURRENT ACTIVITY * One committer has been moderately active this month doing cleanup COMMUNITY * Last committer added April 28, 2013 * Mailing list has been quiet community-wise.
Apache Velocity is a java template engine and related projects. RELEASES * Last release was master POM, May 2012 * Last noteworthy release was Engine in 2010 CURRENT ACTIVITY * No commits or releases. COMMUNITY * Last committer added April 28, 2013 * Mailing list activity was higher than usual, responses were quick. * Most questions on StackOverflow seem to concern Velocity integrations, not Velocity itself. * Frederick Brier contacted us about contributing major 2.0-type revisions he's done. We advised him, but neither CLA nor code has materialized.
@Rich: Ping them to make sure they've got enough people active.
Apache Velocity is a java template engine and related projects. RELEASES * Last release was master POM, May 2012 * Last noteworthy release was Engine in 2010 CURRENT ACTIVITY * No commits or releases. COMMUNITY * Last committer added April 28, 2013 * Mailing list activity was higher than usual, responses were quick. * Few questions on Stack Overflow. * Action should be taken to confirm all active leaders are PMC members, not merely committers.
Apache Velocity is a java template engine and related projects. RELEASES * Last release was master POM, May 2012 * Last noteworthy release was Engine in 2010 CURRENT ACTIVITY * There were two commits this quarter (a bugfix and a doc fix). COMMUNITY * Last committer added April 28, 2013 * Activity is inconsistent on the user list but steady on Stack Overflow.
Apache Velocity is a java template engine and related projects. RELEASES * Last release was master POM, May 2012 * Last noteworthy release was Engine in 2010 CURRENT ACTIVITY * There were no commits or contributions this quarter. COMMUNITY * Last committer added April 28, 2013 * Activity is inconsistent on the user list but steady on Stack Overflow.
No report was submitted.
AI: Chris to pursue a report for Velocity
Apache Velocity is a java template engine and related projects. RELEASES * Last release was master POM, May 2012 * Last noteworthy release was Engine in 2010 CURRENT ACTIVITY * Dev effort was zero this quarter. * Only contribution was report of broken website links. COMMUNITY * Last committer added April 28, 2013 * Activity is low on the user list but steady on Stack Overflow. * Velocity appears to be more oft used as a component of larger products than directly used by app developers.
Apache Velocity is a java template engine and related projects. RELEASES * None CURRENT ACTIVITY * None COMMUNITY * No changes. * Activity remains low on the user list and slightly higher on Stack Overflow.
not approved
DESCRIPTION Apache Velocity is a java template engine and related projects. RELEASES * None CURRENT ACTIVITY * Minimal COMMUNITY * We have welcomed Sergiu Dumitriu as a committer. * Activity remains low on all lists and slightly higher on Stack Overflow.
DESCRIPTION Apache Velocity is a java template engine and related projects. RELEASES * None CURRENT ACTIVITY * Minimal COMMUNITY * The composition of the committers and PMC members has not changed since the last report. * Activity remains low on all lists, though Stack Overflow regularly has Velocity questions, of which the intelligent ones and a few less-so ones are answered in reasonable time. * Apache Velocity remains in a more-or-less dormant period. The rise of client-side development has undercut one of the major sources of users and thus developers. While Velocity remains quite useful for generating text on the server, overall demand seems unlikely to rise.
DESCRIPTION Apache Velocity is a java template engine and related projects. RELEASES * None CURRENT ACTIVITY * Minimal COMMUNITY * The composition of the committers and PMC members has not changed since the last report. * Activity remains low on all lists, though Stack Overflow regularly has Velocity questions, of which the intelligent ones and a few less-so ones are answered in reasonable time. * Apache Velocity remains in a more-or-less dormant period, not its first in the last 12 years though. ISSUES * There are no issues requiring board attention at this time.
DESCRIPTION Apache Velocity is a java template engine and related projects. RELEASES * None CURRENT ACTIVITY * GSoC 2012 student Dishara Wijewardana successfully completed her project. Her mentor, Claude Brisson, did a great job of guiding and overseeing the project integrating Velocity with the JSR-223 scripting interface. Her branch still needs integration with the trunk. * A few issues have been fixed in the VelocityTools project * The Velosurf project (by PMC member Claude Brisson) has been added to the sandbox. COMMUNITY * The composition of the committers and PMC members has not changed since the last report. * Activity remains low on all lists, though Stack Overflow regularly has Velocity questions, of which the intelligent ones and a few less-so ones are answered in reasonable time. * Apache Velocity remains in a more-or-less dormant period, not its first in the last 12 years though. ISSUES * There are no issues requiring board attention at this time.
No report was submitted.
AI: Greg to pursue a report for Velocity
Apache Velocity is a general-purpose template engine with several supporting projects. Status * Moderate development activity on Engine, including some key patches. * Moderate activity on mailing lists. Community * GSoC project underway, student is up for committer status Releases * Apache Velocity Master 1 (our parent Maven POM) release is imminent, but not completed.
Apache Velocity is a general-purpose template engine with several supporting projects. Status * Light development from patch contributions and one committer. Moderate activity on mailing lists, all questions answered promptly. Community * No changes. Releases * None
Status * Development discussion, but no commits. Moderate activity on mailing lists, all questions answered promptly. Community * No changes. Releases * None
Apache Velocity is a java template engine and various derivative and supporting projects. There are no board level issues at this time. Infrastructure ------------------- There are no infrastructure issues at this time. Development ------------------ There have been no releases during this period. ==== VelocityTools project ==== Fixed a number of issues in trunk and 2.0.x branch. There is some interest in doing a 2.0.1 release in the near future. Community ---------------- There have been no new commiter or PMC members added during this period. User list traffic has been relatively low for this period, excepting some dev@ stuff that happened there.
Status * Development discussion, but no commits. Low activity on mailing lists. Community * No changes. Releases * None
=== Status === Flurry of activity before the holidays, quiet since then. The Velocity project currently has no board-level issues at this time. === Community changes === Nathan Bubna has assumed Chair duties. === Velocity Engine project === Velocity Engine 1.7 final release was announced on Nov. 30. The Engine 2.x branch is now the main development trunk.
WHEREAS, the Board of Directors heretofore appointed Henning
Schmiedehausen to the office of Vice President, Apache
Velocity, and
WHEREAS, the Board of Directors is in receipt of the
resignation of Henning Schmiedehausen from the office of Vice
President, Apache Velocity, and
WHEREAS, the Project Management Committee of the Apache
Velocity project has chosen by vote to recommend Nathan Bubna
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Henning Schmiedehausen is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache Velocity, and
BE IT FURTHER RESOLVED, that Nathan Bubna be and hereby is
appointed to the office of Vice President, Apache Velocity, 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.
Approved by unanimous roll call vote.
== November 2010 Board Report == === Status === Another quiet quarter in Velocity land. The Velocity project currently has no board-level issues at this time. === Community changes === Antonio Petrelli was voted onto the Velocity PMC. The Velocity PMC has voted to change the chair from Henning Schmiedehausen to Nathan Bubna. === General Project news === Some fixes to the Velocity site build enable building the site off-line and outside the Velocity zone. === Velocity Engine project === Reorganization and bug-fixing of the engine code continues. We expect to release the last version of the 1.x code base soon and then switch to 2.x
This has been a quiet period for the Apache Velocity project since the last board report. Anthony Petrelli has reorganized the Velocity Engine code base and build system to be based on Maven. Traffic on the user lists seems slower than typical, with a new inquiry every couple of days. Responses remain fairly quick, with 3 or 4 committers actively monitoring the lists and responding to questions. No new PMC members were voted in since the last board report. There are no issues requiring board attention.
[Received late, from Will Glass-Husain on behalf of vacationing chair.] This has been a quiet quarter for the Apache Velocity project. Anthony Petrelli has reorganized the Velocity Engine code base and build system to be based on Maven. Traffic on the user lists seems slower than typical, with a new inquiry every couple of days. Responses remain fairly quick, with 3 or 4 committers actively monitoring the lists and responding to questions. No new PMC members were voted in since the last board report. There are no issues requiring board attention.
The report was received too late.
June 2010 Board Report Status We really need someone to step up and do some site/build work. It has been a hindrance for some time. Community changes No new PMC members were voted in since the last board report. Antonio Petrelli (apetrelli) was voted in as a Velocity committer on June 2nd. Velocity Engine project Released versions 1.6.4 (should be last in 1.6 branch) and 1.7-beta1. Actual development is slow/quiet; one active committer and one active-voted-in-but-no-karma-yet-committer. Getting good bug reports and active user list. 2.0 development has taken a back seat to 1.6/1.7 but is not forgotten. Velocity Tools project Released version 2.0 finally!! Current development of Tools is slow/quiet; 1.5 active committers and one active-voted-in-but-no-karma-yet-committer. Getting good bug reports and light user list activity. Sandbox directory has been requested by contributor to revamp Maven build; the PMC agreed, but this must be done by the chair who has not done it. Velocity Anakia project There were no changes in the Anakia code base. No Anakia development happened in the last month. Several users have popped up with problems and questions recently, but no one in the developer community has been able/willing to help. Velocity Texen project There were no changes in the Texen code base. No Texen development happened in the last month. Users are out there, but don't show their faces around here, at least not in a very long time. Velocity DVSL project There were no changes in the DVSL code base. No DVSL development happened in the last month. No bug reports or list activity in a very, very long time. Velocity Docbook project There were no changes in the Docbook code base. No Docbook development happened in the last month. No bug reports or list activity in a long time.
Shane to follow up.
Justin to pursue a report for Velocity (and has already sent a reminder)
Feb 2010 Board Report ===================== Status ------ Velocity continues to be quiet and steady. Traffic on the dev list continues to be light (and is mostly reflecting bug tracker activity). User list traffic also is light but steady. The Velocity project currently has no board-level issues at this time. Community changes ----------------- Velocity did not add or remove any new committers or PMC members since the last board report. Velocity Engine project ----------------------- Velocity Engine 1.6.3 was released on Dec. 16th, 2009. Light activity on the bug tracker, new bugs are addressed and closed, the overall rate of bug reports is pretty low (Velocity is, after all, pretty mature software). 9 Bugs were opened after Dec 1st., 18 were resolved or closed in various states (mostly fixed). Velocity Tools project ---------------------- The tools project had no releases since the last board report. Discussion about a 2.0 release has been started but not yet concluded. Other Velocity Sub projects --------------------------- There was no activity in the other velocity sub-projects.
Status ====== Velocity still continues its quiet, steady flow. Activity picked up a little in October with some messages on the dev list. The user lists continues to be very self-helping with questions getting answered by members of the user and dev communities. Velocity changed its chair from Will Glass-Husain to Henning Schmiedehausen. The Velocity project currently has no board-level issues at this time. There were no new committers or PMC members voted in since the last board meeting. No beta or final releases were made since the last board report.
WHEREAS, the Board of Directors heretofore appointed Will Glass-Husain to the office of Vice President, Apache Velocity, and WHEREAS, the Board of Directors is in receipt of the resignation of Will Glass-Husain from the office of Vice President, Apache Velocity, and WHEREAS, the Project Management Committee of the Apache Velocity project has chosen by vote to recommend Henning Schmiedehausen as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Will Glass-Husain is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Velocity, and BE IT FURTHER RESOLVED, that Henning Schmiedehausen be and hereby is appointed to the office of Vice President, Apache Velocity, 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 7G, Change the Apache Velocity Project Chair, was approved by Unanimous Vote of the directors present.
This very short Board report for October 2009 is submitted, with apologies, following missed reports for August and September 2009. We presume our regular reporting schedule will resume with the November 2009 reports. Activity in the Velocity project has been quiet in the past few months. There have been a handful of commits and no new releases since the last report in May. Mailing lists are low traffic but still active with about a message a day. All questions are promptly replied to by one of the active committers or others in the community. The Velocity project currently has no board-level issues at this time.
No report filed.
No report provided. Roy noted that this was the second month in a row without a report.
No report provided.
The Apache Velocity project continues it's slow but steady development effort in what was a fairly typical quarter for this mature project. Community - We continue to have a small core of active committers and several frequent contributors - User list traffic remains steady with 1-2 messages per day, all answered quickly. Velocity Engine - In March 2009 we released Apache Velocity 1.6.2, a bug fix release addressing several regression issues with Velocity 1.6. - A new svn trunk for version 2.0 has been opened up. While full scope is yet to be determined, the initial intent is to offer incremental improvements without the ball-and-chain of perfect backwards compatibility Velocity Tools - The Velocity Tools sub-project is in the midst of a vote for a 2.0-beta4 release. We anticipate a full 2.0 release in the coming quarter. The Velocity project currently has no board-level issues at this time.
The Apache Velocity project continues to have renewed momentum for what is essentially mature product. The increased dev-list traffic reported last quarter continues, and we're now up to three engaged committers and several other regular contributors. User list traffic remains steady with 1-2 messages per day, all answered quickly. In December 2008 we released Velocity 1.6. This release added incremental features, syntax improvements, and extensive performance improvements. We followed up shortly thereafter with a bug fix release Velocity 1.6.1 in January 2009. Velocity Tools released version 2.0-beta3 in December 2008. We anticipate a full 2.0 release in the coming quarter. We have added one new committer, who has taken a very active role in testing, fixing bugs and moving us towards our next release. The Velocity project currently has no board-level issues at this time.
Velocity has taken a step up in activity this past quarter with two new beta releases for the Velocity Engine that point to a full version release within the next quarter. While these efforts are largely driven by a single committer, it's encouraging to see discussion, JIRA comments, and contributions coming from a variety of non-committer developers. Other committers contribute discussion, testing, and votes on an occasional basis. As a sign of the increased activity, the message traffic on the dev list is about double what it has been for recent quarters. (and better yet -- all from productive discussion). User list traffic remains the same, with 1-2 messages per day. Questions continue to get answered quickly by both project committers and other community members. There has been a small amount of activity on the Velocity Tools project. This remains at a late beta stage, with an anticipated upcoming release. The Velocity project currently has no board-level issues at this time. There have been no changes to the Velocity Committers or PMC.
Velocity remains a mature product, with development occurring in fits and starts. At the moment we have one committer driving the majority of the development activity, though there are three others who participate on JIRA and the lists regularly and contribute occasional code. Traffic on the user list remains constant with 2-3 messages a day. Questions continue to get answered quickly by both project committers and other community members. On an encouraging note, in the last month we've had a community member contribute a substantial set of patches to improve performance of page rendering. (Particularly with pages involving macros). His tests showed that our current trunk had a significant performance decrease over the current version; with his series of patches performance is boosted and now exceeds the last version. There's been a flurry of activity as he and our committers have discussed these and other improvements. We'll likely roll up all these changes into a new release in the next quarter The Velocity Tools project had a release of Velocity Tools 2.0 Beta 2 on July 11. We anticipate a final release in the next quarter. The Velocity project currently has no board-level issues at this time. There have been no changes to the Velocity Committers or PMC
May 2008 Board Report Velocity remains a mature product. Development activity this past quarter was mild and focused on preparation of the Velocity Tools 2.0 codebase towards an upcoming release. User mailing list traffic remains at 1-2 messages a day with responses generally answered quickly. The Velocity project currently has no board-level issues at this time. Community Changes --- Since the last board report, Chris Schultz has been added as a new committer. Crypto Status --- As requested, the PMC chair has reviewed the ASF notes on cryptography export notification. Since Velocity has no crypto code, and no links or dependencies on such code, these requirements do not apply to our project.
Velocity remains a mature product. At the moment, development is primarily focused on the tools project. User mailing list traffic remains at 1-2 messages a day with responses generally answered quickly. Nathan Bubna oversaw our involvement in Google's GHOP program in November/December 2007. We had several students make useful contributions to our documentation and logos. Many thanks to the participants and to Google. The Velocity project currently has no board-level issues at this time. ECCN REVIEW As requested, the PMC chair has reviewed the ASF notes on export notification. Since Velocity has no crypto code, and no links or dependencies on such code, these requirements do not apply to our project. COMMUNITY CHANGES We have a new committer, but have not formally announced it as his CLA has not yet been received. No new PMC members were voted in since the last board report. VELOCITY ENGINE Minor activity fixing some bugs. There are several patches received by users in the last couple of weeks that need review. No beta or final releases were made since the last board report. VELOCITY TOOLS Velocity tools has released 2.0-beta1. We hope to release 2.0 by May. VELOCITY TEXEN Texen has been refactored to separate out ant task from main code. The code is ready for a point release in the not too distant future. Texen currently has an unresolved Gump issue. VELOCITY DVSL, VELOCITY ANAKIA, VELOCITY DOCBOOK No activity this past quarter.
Approved by General Consent.
STATUS Velocity remains a mature product with spurts of developer activity. Developers and power users remain present on the mailing lists. The user list averages 1-2 questions a day from new users, of which almost all are answered immediately. We've been struggling a little with Gump issues in the past month. Commons Lang subtly changed the spec for an API call ( https://issues.apache.org/jira/browse/LANG-363 ) which caused one of the unit tests in Velocity to fail. The lack of debuggability of the gump run led to some very inelegant print statements scattered throughout the unit test until the specific failure was isolated. Very old-style coding. (change a line, wait a day for gump, change a line, wait a day). We still have a Texen gump failure, though hoping to get that straightened out soon. The Velocity project currently has no board-level issues at this time. COMMUNITY CHANGES No new committers were voted in since the last board report. No new PMC members were voted in since the last board report. VELOCITY ENGINE There's been some minor activity improving various syntax issues (i.e. adding variable arguments) and fixing user-reported bugs. No beta or final releases were made since the last board report. VELOCITY TOOLS Velocity Tools is currently the most active project, with development focused on the new 2.0 branch. This is in alpha and moving towards beta. We had a brief discussion on the dev lists whether to continue supporting the 1.x branch (currently on version 1.3), or urge users to adopt 2.0 when it is released. The consensus was to release a 1.3.1 version with minor updates and fixes, then retire that branch. (Seemed the practical direction given the straight-forward upgrade path from 1.3 to 2 and the interests of our small developer community). We hope to release both 2.0-beta1 and 1.3.1 by January. VELOCITY DOCBOOK We committed our first user-submitted patch (DBF-1). Otherwise this product remains stable. It appears to be primarily used internally though there are occasional queries and comments about it on the user list. VELOCITY ANAKIA No development activity this past quarter. VELOCITY DVSL No development activity this past quarter. VELOCITY TEXEN There was a small amount of activity fixing bugs and adding user- submitted patches from JIRA. If enough patches and updates get submitted we will release a version 1.1 by the next quarter. Texen currently has an unresolved Gump issue (see above).
Approved by General Consent.
STATUS The Velocity project has had a quiet summer, with activity centered around Google Summer of Code, Velocity Tools, and Velocity DVSL. The Velocity project has no board-level issues at this time. COMMUNITY CHANGES No new committers were voted in since the last board report. No new PMC members were voted in since the last board report. VELOCITY ENGINE PROJECT Work continues towards a Velocity 1.6 release. A Google Summer of Code student, Supun Kamburugamuva, successfully completed a series of enhancements to the macro processing features of Velocity, which were immediately committed into the development trunk. We are grateful to Google for supporting this program, Ross and Jukka for administering the Apache organizational efforts and Supun for doing such quality work. No beta or final releases were made since the last board report. VELOCITY TOOLS PROJECT The Velocity Tools team released version 2-alpha1 on July 2. Things are going well and we anticipate a new alpha release soon. There have been some significant bugs fixed since 1.3, and the team plans to release a 1.3.1 or 1.4 version, though this has been delayed due to efforts on the 2.x branch. VELOCITY DVSL PROJECT DVSL version 1.0 was released on August 14. DVSL (Declarative Velocity Style Language) is a tool modeled after XSLT and is intended for general XML transformations using the Velocity Template Language as the templating language for the transformations. Before releasing DVSL 1.0, the DVSL team fixed an incompatibility between DVSL 0.x and Velocity 1.5 and completed some minor clean up and refactoring. It is not a drop in replacement of DVSL 0.45 since the main package has changed from org.apache.tools.dvsl to org.apache.dvsl. This is the first binary release of DVSL though the code base has been around for some time, VELOCITY DOCBOOK PROJECT There were no changes in the DocBook code base. No DocBook development happened in the last quarter.
Approved by General Consent.
WHEREAS, the Board of Directors heretofore appointed Henning Schmiedehausen to the office of Vice President, Apache Velocity, and WHEREAS, the Board of Directors is in receipt of the resignation of Henning Schmiedehausen from the office of Vice President, Apache Velocity, and WHEREAS, the Project Management Committee of the Apache Velocity project has chosen by vote to recommend Will Glass-Husain as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Henning Schmiedehausen is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Velocity, and BE IT FURTHER RESOLVED, that Will Glass-Husain be and hereby is appointed to the office of Vice President, Apache Velocity, 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 6E, Change the Apache Velocity Project Chair, was approved by Unanimous Vote.
General information =================== The Apache Velocity project had an exciting first quarter of 2007 with the long anticipated release of the Velocity engine. We have no board-level issues at this time. Our various releases since the beginning of 2007 sent a clear message out to the Java world that the Velocity project was never dormant and is picking up speed. The number of messages on the develpment and user lists reflect this nicely. The Velocity Engine 1.5 release was covered in depth on various Java related web sites (e.g. theserverside.com). The Velocity project tried to organize a formal press release for the Velocity engine release and even postponed the official release date to get possible better coverage. Will Glass-Husain worked as our liaison with the PRC. Unfortunately, this press release did not work out. While we tried to work in a timely manner (we started six weeks before the actual release date collecting quotes from Velocity users for the release and circulated drafts to the PRC), Will reported that the PRC did not respond at times and seemed to be dormant and he had to ping the chair directly. Various objections came up only hours before the intended release date even though we tried to give ample time for the PRC to review drafts. In the end, the Velocity PMC decided to withdraw the press release draft. The experience working with the PRC was interesting, though not entirely good. We hope that the PRC and other PMCs can learn from our experience and we streamline the review/feedback process for the next time. The Velocity project created three new sub projects in Q1: - Velocity Anakia, formerly a part of the Velocity Engine - Velocity Texen, formerly a part of the Velocity Engine - Velocity DocBook Framework, intended to generate high-quality documentation suitable for on-line viewing and printing The Velocity project has discussed to sponsor the incubation of the Click Framework, which is based on Velocity. The Click community has already reached consensus that they want to be incubated to become an Apache project; discussion is still open whether this will be a sub-project of Velocity or a TLP in its own right. We expect to see a formal incubation proposal in Q2. Community changes ================= Claude Brisson was voted to become a member of the Velocity PMC on April, 3rd. He accepted his nomination. No new committers were added to the Velocity project in Q1. Google Summer of Code ===================== The Velocity community is proud that a proposal to the Google Summer of Code 2007 was accepted: Supun Madhushanka Kamburugamuva will work to improve the Velocity Macro capabilities (see: http://code.google.com/soc/asf/appinfo.html?csaid=75DF2BC1378C84A5 ), Will Glass-Husain, Velocity PMC member will mentor him. Velocity Engine project ======================= The Velocity Engine team released Apache Velocity 1.5 on March 13th. Work on Velocity 1.x continues at the usual pace. Velocity Tools project ====================== Velocity Tools currently works towards a 2.0 release. No release have been made in Q1. Velocity DVSL project ===================== Since the inception of the Velocity TLP, the DVSL code base was not changed and there seems to be no interest in it from users and developers. We will discuss mothballing it in Q2. Velocity Anakia =============== Anakia is an old/new tool that used to be part of the Velocity engine. It was spun out of the engine after the 1.5 release to allow different release cycles. Velocity Anakia 1.0, which is just a repackaged version, was released on April 28th. Velocity Texen =============== Texen is an old/new tool that used to be part of the Velocity engine. It was spun out of the engine after the 1.5 release to allow different release cycles. Velocity Texen 1.0, which is just a repackaged version, was released on April 28th. Velocity DocBook Framework ========================== The DocBook Framework is intended to help everyone that wants to write documentation in an industry-wide accepted format that is suitable for printing and on-line viewing. For the time being (and because it is used to generate the Velocity documentation), this stays as part of the Velocity project. If it fits better into another TLP in the future, it is expected to leave Velocity). Velocity DocBook Framework 1.0 was released on April 9th.
The board discussed the PR-related issues mentioned in the report. Jim indicated that the timeline mention in the report was not quite correct, since the 1st draft differed from the 2nd quite a bit, so it was "unfair" to suggest that the approval process was as long as implied. Jim was to follow up with Henning.
Approved by General Consent.
General Information (As our esteemed chair Henning Schmiedehausen is on vacation this month, this quarter's report is being prepared by Will Glass-Husain). The Velocity project is inches away from the eagerly anticipated release of Velocity 1.5, the first major release of our engine in almost three years. December and January saw a flurry of activity in cleaning up last minute bugs, updating documentation, and preparing the release. We have had passionate recent discussion on the dev and private list about release procedure. In part, this is due to the anticipated visibility of the Velocity 1.5 release and in part due to the relatively young nature of the Velocity TLP / PMC as we establish correct release practice. For recent beta / rc releases we have had a "vote-then-build" process in which a PMC member announces they are ready to release, a vote is held, then the release is shipped. In mid-January such a vote was announced for Velocity 1.5. Midway through the vote one of the PMC members expressed concern that there were no binaries to examine. A consensus opinion urged a switch to a "build-then-vote" procedure and the current vote was tabled. A few days later, a second vote was held to release Velocity 1.5 with +1's from almost all parties except for a last-minute -1 (from a different PMC member). The concerns driving the -1 vote were not serious (minor documentation / site issues), but the -1 voter felt strongly that these issues should be addressed before release. (Being a release vote, the -1 was not binding but our release manager agreed to table the release in light of the concerns). A frustrating aspect of this process was that these issues could not be directly fixed, but needed to wait for the vote to conclude, then a rebuild of the distro then a new vote. The departure of our chair (who had been driving the release) on a month-long vacation has temporarily paused this process. Will Glass-Husain has offered to push the release through to conclusion in the meantime but personal committments have led to a several week delay. In related news, we have prepared a press release for distribution regarding the Velocity 1.5. Due to the wide-spread use of this library in the Java community we anticipate getting plenty of attention when the release occurs. The release was shared with the PRC committee list (which was somewhat unresponsive) but suggestions for improvements were received from several members. The Velocity project has no board-level issues at this time. Community Changes No new committers were voted in since the last board report. No new PMC members were voted in since the last board report. Velocity Engine project As noted above, the entire Velocity community is eagerly awaiting the upcoming release of Velocity 1.5. We fully expect this release to conclude as previously predicted during Q1. Velocity Tools project Velocity Tools 1.3 was released on February 8. Work on the next 1.x version has already begun. Velocity DVSL project There were no changes in the DVSL code base. No DVSL development happened in the last month.
There was a discussion regarding the 'vote-then-build' vs. the 'build-then-vote' meme. It was agreed that, in all cases, what must be voted on (and approved) is the actual release tarball/jar-file/whatever. No software can be released without the actual released entity being voted on and approved. Jim to remind PMCs of the groundrule Release Guidelines.
Approved by General Consent.
General information ------------------- We have moved out of the Jakarta umbrella and cut almost all ties. The TLP now has an official web site at velocity.apache.org with sub-websites for all projects. The Velocity project currently has no board-level issues at this time. No new committers were voted in since the last board report. No new PMC members were voted in since the last board report. A short discussion on the PMC list revealed that a number of "emeritus committers" fell off the boat when we moved out of Jakarta. These are now recognized in an "Emeriti" section on the web site. The PMC discussed about re-granting committer status if any of these emeritus committers decides to ask about it. Velocity Engine project ----------------------- Development towards the next major release, 1.5 continues. A CfV date has been proposed (21st January). No beta or final releases were made since the last board report. Velocity Tools project ---------------------- VelocityTools 1.3-beta1 has been voted and released on December 21st. A new test framework and minor tool enhancements have been checked in since. It doesn't appear likely that we'll need another beta. The hope is for an RC by end of January and a final in early February. Velocity DVSL ------------- There were no changes in the DVSL code base. No DVSL development happened in the last month.
Approved by General Consent.
General information ------------------- The Velocity project is busy moving out of the Jakarta umbrella and into top-level status. Since the last report we have successfully moved the SVN repository with the help of infrastructure and also set up a commits mailing list. For the TLP itself we are in process of setting up a web site which then links all the project web sites together. This should be done till the end of December. The Velocity project currently has no board-level issues at this time. New Committers / PMC members ---------------------------- Claude Brisson <claude@renegat.net> was voted in as a committer to the Velocity Tools project (and in turn to the Velocity project as a whole) on Dec, 1st. His CLA has been sent in and recorded. No new PMC members were voted in since the last board report. Velocity Engine project ----------------------- The Velocity engine project voted and released 1.5-beta2 on November 24th. According to the discussion on the infrastructure mailing list, we moved this beta release together with all other voted beta releases (currently only 1.5 beta1) into the mirrored distribution tree at www.apache.org/dist/velocity/ The engine project fully expects to keep its early Q1 '07 release date. Velocity Tools project ---------------------- Velocity Tools is gearing up towards the 1.3 release. No beta or final releases were made since the last board report. Velocity DVSL ------------- There were no changes in the DVSL code base. No DVSL development happened in the last month.
Approved by General Consent.
6. Special Orders
Velocity Top Level move ----------------------- The Velocity project is excited about its move out from the Jakarta umbrella and onto top-level status. The board decided to establish the Apache Velocity project on Oct 25th and appointed Henning Schmiedehausen (henning@apache.org) as Vice President, Velocity and chair of the Velocity PMC. Ever since then, we have started to migrate our web site, mailing lists and repositories out of the Jakarta umbrella. With help from the infrastructure team, we currently have moved all mailing lists onto velocity.apache.org, created the private@ and general@ lists and started migrating the web site (we already have velocity.apache.org but it is currently redirecting to the jakarta site). We hope to finish the migration until the end of November. General information ------------------- Some talk with the Click project (click.sf.net), which is a framework centered around Velocity, has taken place to bring Click through the incubator into the Velocity project. There has been enthusiasm on the Click side and from us, but we have not taken any steps yet, because we wanted to let the dust from the top level move settle first. Velocity Engine project ----------------------- The 'velocity' project has been renamed the 'Velocity Engine project' a while ago. What is commonly known as "Velocity" is actually the templating engine. The Velocity Engine team is pushing heavily towards the 1.5 release. We have released one beta and will be releasing our second (and hopefully last) beta this week (we already voted on it). We expect an RC until the end of November and plan for a final release very early Q1 2007 (both Will and Henning attended Sally's PR talk @ ApacheCon US and we tried to understand the value of good release timing). We also plan sort of a "mini PR campaign" similar to the press releases issued at AC US. We will get in contact with the PRC once the RC is out. The code base itself has seen a steady progression; we were able to triage and sort all of the issue reports in JIRA and prioritize them nicely. The number of open issues is steadily going down so we expect the 1.5 release to be the best Velocity release ever. There has been work on a docbook based Documentation (User Guide, Developers Guide), which in turn has spawned a docbook framework which might usable outside Velocity as a general purpose documentation framework. Velocity Tools project ---------------------- Velocity Tools is working through a short backlog of patch contributions and bugs hoping to get a 1.3 version released before Velocity Engine 1.5 goes final. It's also the plan to test VelocityStruts 1.3 against Struts 1.3 for compatibility. Velocity Tools 1.3 is likely to be the last major release in the 1.x line, as the development team already started planning for version 2. Velocity DVSL ------------- There were no changes on the DVSL code base in the last few months. DVSL currently has no active developers, but we do apply the odd patch. All issue reports against DVSL were triaged and checked but there are no immediate plans to do a DVSL release unless one of the contributors steps up or strong desire for a release is shown on the user list.
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 Velocity template engine,
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Velocity Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Velocity Project be and hereby is
responsible for the creation and maintenance of software
related to the Velocity template engine; and be it further
RESOLVED, that the office of "Vice President, Velocity" 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
Apache Velocity Project, and to have primary responsibility for
management of the projects within the scope of responsibility
of the Apache Velocity Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Velocity Project:
* Will Glass-Husain (wglass@apache.org)
* Geir Magnusson Jr. (geirm@apache.org)
* Daniel L. Rall (dlr@apache.org)
* Henning Schmiedehausen (henning@apache.org)
* Nathan Bubna (nbubna@apache.org)
* Marin A. Jnsson (marino@apache.org)
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Henning
Schmiedehausen be appointed to the office of Vice President,
Velocity, 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 Apache Velocity Project be and
hereby is tasked with the creation of a set of bylaws intended
to encourage open development and increased participation in
the Velocity Project; and be it further
RESOLVED, that the initial Apache Velocity Project be and
hereby is tasked with the migration and rationalization of the
Apache Jakarta Velocity, Velocity Tools and DVSL subprojects;
and be it further
RESOLVED, that all responsibility pertaining to the Jakarta
Velocity, Velocity Tools, and DVSL subprojects and encumbered
upon the Apache Jakarta Project are hereafter discharged.
Special Order 6A, Establishing the Apache Velocity Project, was
approved by Unanimous Vote.