[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4585) Community documentation updates and improvements.
Matthieu Chase Heimer (JIRA)
jira-events at lists.jboss.org
Mon Mar 8 00:17:58 EST 2010
[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12518608#action_12518608 ]
Matthieu Chase Heimer commented on JBSEAM-4585:
Don't break in up into a lot of sub-forums, beginners never post in the correct sub-forum. Too much time is wasted moderating. Standing tags for message might be nice to help categorize the posts.
Seam is too central to the current site and documentation. I (and other beginners) want CDI information and now that JSR299 and JSR330 are in EE 6 there is a need for a central hub for people using standards based DI. Currently I have to go to a seam website and look at weld information, that isn't natural for someone trying to find CDI information.
Given that you guys wrote and will be maintaining the CDI spec, why isn't there a:
* CDI forum
* CDI jira
* CDI documentation
I understand that most of the Weld reference doc is actually about CDI but I think some effort should be put into separating out the CDI and Weld information. People using CanDI, OpenWebBeans, and Weld should have a central hub. Preferably something not buried underneath seam, remember seam is just the add-on now.
The Weld dev mailing list isn't on the forum because??? (Maybe the average person likes reading a forum, blog, and mailing list to try and keep track of the issues and developments of an open source project) Convert the Weld user forum into a CDI forum and promote the Web Dev mailing list to a forum that is for all things Weld specific.
The CDI spec needs a JIRA project or some other issue tracking method. Any Weld issue that is opened that ends up being spec related is closed with a polite pointer to contact the CDI expert group. This means emailing someone. First of all the email is hard to find (for the group, not Gavin) and second, email is a poor issue tracking tool. It's like the black hole of issue tracking.
I agree with breaking the seam stuff into version (especially because I only care about the seam 3 stuff)
> Community documentation updates and improvements.
> Key: JBSEAM-4585
> URL: https://jira.jboss.org/jira/browse/JBSEAM-4585
> Project: Seam
> Issue Type: Task
> Components: Documentation Issues
> Affects Versions: The future
> Reporter: Lincoln Baxter III
> Priority: Optional
> Fix For: The future
> As part of an initiative to improve the experience for new and existing developers, community members getting involved with Seam and Weld, I am documenting a set of improvements to be made to the current state user-facing http://seamframework.org and related documentation.
> This task serves as a running list of inconsistencies, improvement areas, and erroneous information provided on SWFK.org (and related.)
> * http://seamframework.org/Community/GettingStartedDevelopingTheSeamFramework -- page still references version 2.0 of Seam for new development, which is now a lie
> * http://seamframework.org/Download/SeamDownloads#H-SeamSVNRepository contains repo URLs that are now broken for SCM checkout.
> * Too hard to find JIRA links -- added JIRA links to sidenav -- Lincoln Baxter
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues