Hi,

The JBoss Community Team are proud to announce an upgrade of the Project Documentation Editor's "Content approval" feature based on users' requests:

http://docs.jboss.org/author

We've introduced configurable email notifications for defined users and email addresses when content is awaiting approval. We've also introduced "Thank you" email notifications to the original contributor of the content once it's approved:

https://issues.jboss.org/browse/ORG-1213

Another enhancement is the possibility to configure users who can approve content (in addition to Space Administrators who approved the content in previous versions), and to configure "Trusted Contributors". Content contributed by these users needn't be approved:

https://issues.jboss.org/browse/ORG-1379

The new version includes some patches for minor bugs too.

Basic help on how to enable and use the "Content approval" feature for your documentation space is available here:

https://docs.jboss.org/author/display/AUTHGUIDE/How+to+use+the+Content+Approval+feature

Enjoy!

Hi,

The JBoss Community Team are proud to announce the rollout of SSO for jboss.org.

Applications/domains involved in the SSO login are:

• community.jboss.org (SBS)
• issues.jboss.org (JIRA)
• docs.jboss.org/author (Confluence)
• source.jboss.org (FishEye/Crucible)

Clicking on any login link (including the one at www.jboss.org) takes you to the new SSO login page. From here you're automatically logged into all of the above applications when you visit them without need to login again.  An SSO session created using the "Remember Me" feature from the SSO login page is valid for 10 days for security reasons. After 10 days you'll be forced to login again.

In addition to your full name being displayed in the headers for the subdomains listed above you'll also see it in the header at http://www.jboss.org (this is done using JavaScript since it's not possible to 'login' to www.jboss,org. To edit Magnolia pages you login to http://www.jboss.org/author which is a different application.)

Logout links log you out from the individual applications and you're then given the option to perform an SSO logout from the relevant log out page. The only exception to this is the logout link on www.jboss.org which performs an SSO logout directly (again because you're not 'logging out' from www.jboss.org).

As part of this release we also updated the SBS user interface to have a new fluid design which gives the content more room to breath (no fixed width anymore).

The Website FAQ [1] and help pages [2] have been updated to include information about SSO.

If you experience problems logging in using the new SSO login page please try the 'I forgot my password' link which may help sort things out in the background (syncing passwords across systems for example). For problems in general please use the 'sso.jboss.org' component of our ORG JIRA project:

https://issues.jboss.org/browse/ORG

Thanks to all members of the JBoss Community and Eng Ops Teams involved in developing, staging and rolling out SSO to production.

[1] https://community.jboss.org/wiki/WebsiteFAQ#Single_Sign_On

[2] http://www.jboss.org/help

Enjoy!

Hi,

The JBoss Community Team are proud to announce the upgrade of the Project Documentation Editor to Confluence 3.5, which brings a lot of improvements.

http://confluence.atlassian.com/display/DOC/Confluence+3.5+Release+Notes

We've also introduced a new "Content approval" feature. This allows space admins to better control contributions from the community, review changed parts of the documentation and approve or revert changes - https://docs.jboss.org/author/display/AUTHGUIDE/How+to+use+Content+Approval+feature

Enjoy!

Hi,

Following user feedback on the Project Documentation Editor (https://docs.jboss.org/author) the JBoss Community Team are proud to announce the availability of the following enhancements:

1) DocBook export is now a one-step process in Confluence and may also be called from scripts

https://issues.jboss.org/browse/ORG-1122

https://issues.jboss.org/browse/ORG-1123

This change simplifies and speeds up the project release process and allows better automation of the process. Description how to call DocBook export from the scripts is available directly on export page in Confluence under "Tools -> JBoss DocBook Export" menu item.

2) Allow multiple versions of project documentation in Confluence

https://issues.jboss.org/browse/ORG-1127

This allows corrections to be easily made to older doc versions (following corrections it's still good practice to upload HTML, single-HTML and PDF versions from the generated DocBook XML to http://docs.jboss.org for completeness): https://docs.jboss.org/author/display/AUTHGUIDE/How+to+release+documentation

3) Improvements to the DocBook import plugin to produce better wiki syntax on imported documents

4) Simple navigation between pages for documentation

https://issues.jboss.org/browse/ORG-1096

This feature adds simple "< Previous | Front page | Next >" navigation above and under page content for simpler navigation over documentation guides.

Enjoy!

Hi,

Following today's (Thursday 2nd June) upgrades to JIRA and FishEye the JBoss Community Team are proud to announce the availability of Crucible and GreenHopper. We've also taken the opportunity to rename fisheye.jboss.org to source.jboss.org since both FishEye and Crucible are now served from that domain:

https://issues.jboss.org/browse/ORG-439 - Install Crucible

https://issues.jboss.org/browse/ORG-863 - Change fisheye.jboss.org domain to source.jboss.org

These new features are integrated with JIRA and allow project teams to perform code reviews and agile project management:

http://www.atlassian.com/software/crucible - code reviews

http://www.atlassian.com/software/greenhopper - agile project management

You can find documentation using the above links and access the features as follows:

http://issues.jboss.org - click on the Agile menu item for GreenHopper

http://source.jboss.org - click on the Projects menu item to see projects configured for Crucible and the Reviews menu item for a list of code reviews

In both cases project teams should contact the JBoss Community Team to enable the features for their projects. Crucible code reviews are intended to be used for periodic reviews of the code in addition to GitHub's code review functionality which is generally used when accepting patches.

Enjoy!

Hi,

Following user feedback after the announcement of the Project Documentation Editor (https://docs.jboss.org/author) on 28th Feb 2011 the JBoss Community Team are proud to announce the availability of two enhancements:

1) A Pages structure tool  - https://issues.jboss.org/browse/ORG-1023

This allows you to quickly create and validate the structure of Confluence pages (documentation chapters) against a given template. It's especially useful for projects that have multiple modules that need the same structure:

https://docs.jboss.org/author/display/AUTHGUIDE/How+to+manage+pages+structure

2) Defining metadata for reuse in pages - https://issues.jboss.org/browse/ORG-1038

This allows you to change the metadata (Project Name, Version Number, etc...) in one location instead of having to go through all pages, for example when performing a release:

https://docs.jboss.org/author/display/AUTHGUIDE/Metadata+for+documentation+variables

Special thanks to Max Andersen and Aslak Knutsen for these ideas.

Enjoy!

Following the announcement of the Project Documentation Editor on 28th Feb 2011, the JBoss Community Team are proud to announce the availability of a DocBook XML import tool: http://issues.jboss.org/browse/ORG-965

This allows you to import your current project documentation from DocBook XML files into the Confluence server to quickly populate your space with content: https://docs.jboss.org/author

Documentation is available at: How to import DocBook XML page

We also implemented a solution to workaround Confluence's unique page title constraint:

How to organize space content - Unique page titles

And last but not least we added a new plugin allowing you to remove a whole branch of pages in Confluence in one action.

Special thanks go to Jared Morgan and Laura Bailey for user acceptance testing.

Enjoy!