The communication between the developers and the user community in the Apache Velocity project is intended to be as open and accessible as possible. This is why we prefer to have public mailing lists to which everyone can subscribe and which are archived.
For bug reporting and issue tracking, Velocity uses the JIRA bug tracker at the Apache Software Foundation. Please report bugs using the tracker, if you send them to the mailing lists, most of the times a member of the Apache Community will point you there anyway. Using the bug tracker makes sure that your bug report is recorded and processed in a timely manner.
Please be aware that sending confidential or private data to these lists is strongly discouraged and if this happens, we can not do anything to remove or erase this information from public archives.
We also strongly frown upon disclaimers attached to mails sent to these lists that declare the contents to be confidential, private or only intended for the recipient. But we understand that these disclaimers are often beyond your control. However, by sending mail to a Velocity mailing list, the intended recipient is the general public.
|general¶||Send a message||Archive||Subscribe||Unsubscribe||Keep up-to-date with the Velocity project as a whole.|
|user¶||Send a message||Archive||Subscribe||Unsubscribe||General discussion for developers wanting to use one of the Apache Velocity projects in their own code.|
|dev¶||Send a message||Archive||Subscribe||Unsubscribe||Watch the Velocity development process. Participate in Velocity development yourself.|
|commits¶||Send a message||Archive||Subscribe||Unsubscribe||Monitor the changes to the Velocity Source Code repository.|
|general||This list is used for general, Velocity project related, discussion and announcements. This list is not for specific questions on how to do something using Velocity but for questions about Velocity. Usually very low volume.|
|user||This mailing list is intended for questions around using the Apache Velocity projects in your own code, about writing templates in the Velocity Templating Language and most everything else related to using Velocity. If you are a developer and want to use Velocity, subscribe here. This list has a moderate volume.|
|dev||Found a bug, have a patch, want to improve Velocity? Subscribe to this mailing list, this is where all the developers hang out. Please do not ask questions on how to use Velocity in your own code unless it is related to a problem with Velocity itself. This list has low to moderate volume.|
|commits||This list reflects all the commit messages to the Velocity Subversion source code repository.|
These are the issue trackers for the various Velocity sub projects:
|Engine||JIRA||(depends on the bug itself)|
|Tools||JIRA||(depends on the bug itself)|
Contacting the Apache Velocity PMC¶
The Apache Velocity Project Management Committee (PMC) provides oversight to the project and is legally responsible for all software releases. It reports to the Board of the Apache Software Foundation quarterly. The reports are archived and public.
The Apache Velocity PMC can be reached at firstname.lastname@example.org.