We use tab to indent because that's what it's meant for. No weird formatting rules, prefer concise over expanded and elaborated. We don't have a strict style guide so don't worry about it too much. Follow Tapestry coding style (not formatting!) where possible (for example don't expect null, don't check for null). Avoid unnecessary code like plague and refactor mercilessly. Do not auto-format (all lines of) existing code, do not use @author tags.
The code has been moved to Github. Similarly, we are in the process of moving CI builds from Codehaus' Bamboo to Travis-ci. Travis is far easier to set up than Bamboo. You just need to turn on the build at https://travis-ci.org/profile/tynamo and commit the .travis.yml file with contents "language: java" to tell it that this is a Java build.
Tynamo site is a combination of Confluence and Maven originated content. Maven sites should be published to public_html/constant/sites/<module name> (note that permissions for /sites was set manually by Codehaus support so don't remove it). Unity, the front-end Codehaus site renderer, renders static content under /constant/ folder the same way as regularly for Confluence content.
Announcements need to be done manually as well. Release history should use the confluence JIRA component to show resolved issues in a given release. We don't want to use the changelog plugin, especially for sending announcements mails because Github picks up and displays the tags, edit Github release notes for the particular tag to edit release notes manually. Once you've released the module, it takes around 24 hours before the released artifacts are synched to Central. Announcement should be done only after the release is available through Central. This gives us time to do final manual check-ups after the release. If any major issues are found after the release, we should simply abandon the release, leave it unannounced and push out a new release. You should always make the announcements in at least four places: on our home page (as a Confluence blog post), email@example.com, firstname.lastname@example.org and on Twitter (kaosko owns the twitter handle tynamo_org but you can use your own handle). Twitter announcements need to use the hashtag #tapestry5.
Any project, free-of-charge or not, needs to market their offerings. Tynamo.org has a strong brand recognition within the Tapestry community but is practically non-existent in the whole wider web, even just among other Java developers. We simply need more back links to Tynamo.org from a variety of content, not just from tapestry.apache.org and stackoverflow.com. Any of of the confluence pages need to mention the following keywords at least once: Apache, Tapestry 5, Java and framework, and include one or more links to http://tynamo.org.