[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-4585: ----------------------------------- I'll provide some usability feedback to help the cause... I never start with sfwk.org. The home page has content which is somewhat dynamic, and has 0 convenient links. More times than not I go to Google, search for what I want, click to the wrong page on Seam framework, navigate around a bit more and eventually get to what I want...then I realize that I need to login...and finally I am editing the page I need to edit. So painful. Plus, you go to the Downloads or Documentation page and you are forced to really concentrate hard on which link will actually take you to the documentation that you expect. I really like the idea on javaseverfaces.org (as simple as it may be) that you just have one link that takes you the most recent documentation. Then, if you really want to get a different version, you can go to the detailed page with all the links. Actually, it would be even better to have a page in between...but I'm getting too detailed. I really don't understand why we have to present both HTML and HTML single either...who the hell cares which one? Just make HTML the default and if someone wants the HTML single, then we can put a link somewhere else, less obvious, that gets them there. (If you think the default should be the other way around, then fine, just pick one). -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Timothy Whitehead commented on JBSEAM-4585: ------------------------------------------- I have always found the search funtionality to be terrible. I normally end up using google instead. I would like to see a lot more options on the search funtionality including: 1. the ability to stop it from repeating posts from the same thread. If I am looking for something eg LDAP, then I will read any threads to do with LDAP - I don't need a list of all the posts in the thread with the word LDAP in, I need a list of all the threads. 2. I want the ability to filter threads by version of seam ie if I know my problem has something to do with version 2.1 I don't want any threads about version 1.0 in my search results. 3. The ability to include Jira in the general search. I never think of searchin Jira when I have a problem, yet quite often I find a thread which mentions that the answer is in jira and gives the link. 4. Tags. You can tag a thread when you create it. I don't know if anyone keeps maintains these at all at a later date. I see you can find a list of tags when you go to Community- >/Forums- >/Seam Forums but dont see them anywhere else. If I start with the search box in the top right I am not even aware that the threads are taged. I cant use them in my searches and if I start with the tag, I cant search within them. What use are they? -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III commented on JBSEAM-4585: -------------------------------------------- Jan, what else would you like to see in order to help beginners along? I completely agree that having an effective channel for beginners to get their feet wet is something that will help everyone. Barrier to entry is the #1 barrier to use. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III updated JBSEAM-4585: --------------------------------------- Description: 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.) ==INCOMPLETE== * 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. *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. ==COMPLETED== * Too hard to find JIRA links -- added JIRA links to sidenav -- Lincoln Baxter was: 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.) ==INCOMPLETE== * 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. ==COMPLETED== * 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Jan Groth commented on JBSEAM-4585: ----------------------------------- @Matthieu I already proposed the sub-forum idea a couple of times, and pretty much got a similar answer all the time. :-( I completely disagree with the opinion that moderating a forum is a waste of time. THIS here is a JIRA ticket concerning the - undoubtfully needed - community improvements. I find that supporting the community cannot be a waste of time _by_definition_, and I find that moving topics from one sub-forum to another can hardly be too much work for a moderator - besides I gladly volounteer to help out... I spoke with friends and colleages and I am myself moderator of a German Seam forum: All I can say is that this is a much requested, natural feature of a forum. One last argument: Have a look around around and pinpoint me to a single examplary (and comparable) forum where 11.244 topics and 42.698 posts simply mix up in a huge bag. @Lincoln I took your question as an opportunity to brainstorm with colleagues. This came out: (*) "have a better knowledge base, integrate code snippets" (my personal favorite) - like the python guys do it here: http://www.djangosnippets.org/, but better search options. I find this an extremely useful instrument for all types of users, from beginners to core developers, and I do miss this option a lot in the Seam context. BTW: A tag cloud would be a very intuitive way to browse the content. (*) "(even) better documentation for the seam examples that ship with the framework" - the distribution comes with a lot of good examples. In the documentation just a few are explained in greater detail, some others are briefly mentioned, some others are not referred to at all. Having more examples (and the underlaying concepts) explained would make a great impact for a lot of developers. (*) "provide a guided tour to start with seam" - something with the character of a tour. We could make the life of beginners even more easy if we'd provided a navigation entry "guided tour" which keeps the user busy for a couple of hours. "download the framework", "set up the AS", "run the first examples", "get the key concepts", something like this. Most information is already available, it's just a matter of presenting it in a "tour concept" (*) "provide a maven archetype for seam" - just like we did with Weld :-) (*) "diversify the search functionality" - present different hits from different categories. example: search term "XYZ": show top 5 hits from forums, then top 5 from the examples, then from the knowledge base, then code snippets... (*) "ranking system for forum users" - the already existing system where users get a rating could be extended (eg: bronze - silver - gold - platinum). beginners could then easier be distinguished from expert users, and topics could easier be categorized. users would achieve a certain reputation over the time, the better the reputation is, the more weight their answers (should) have.... -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III commented on JBSEAM-4585: -------------------------------------------- It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Geoffrey De Smet commented on JBSEAM-4585: ------------------------------------------ "I really don't understand why we have to present both HTML and HTML single either" I personally always use the HTML single, and I believe that should be available directly on the docs page. Here's why: Control-f to find something about - let's say "maven" or "i18n" -, which doesn't work in the non single page HTML. Nevertheless this is a great initiative, and I think a common "mimimal" convention should be proposed and discussed, which could be followed in other projects (including Drools where I am involved). Have you thought about a hudson link? -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III commented on JBSEAM-4585: -------------------------------------------- Hi Arbi, Thanks for your comments. How does your last link relate to this issue? --Lincoln -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III updated JBSEAM-4585: --------------------------------------- Description: 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.) ==INCOMPLETE== * 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. *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. *** No good documentation about the Seam portlet bridge, which is a closely related project. Should add visible links. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ==COMPLETED== * Too hard to find JIRA links -- added JIRA links to sidenav -- Lincoln Baxter was: 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.) ==INCOMPLETE== * 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. *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ==COMPLETED== * 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III commented on JBSEAM-4585: -------------------------------------------- That's actually not a bad idea. I like a lot of the things that those guys have done. The technology makes a lot of sense. However, there's an evaluation going on, and we're trying to move Seam / Weld back to JBoss.org so that everyone can re-join the JBoss open-source community. (There are already a few dozen projects there.) The forums are a lot nicer, and the wiki pages make a lot more sense. I think it will be a good switch. Also, the forums synchronize with the mailing list if I am not mistaken :) -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III updated JBSEAM-4585: --------------------------------------- Description: 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.) ==INCOMPLETE== * 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. *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. *** No good documentation about the Seam portlet bridge, which is a closely related project. Should add visible links. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ** Need a better knowledge base, with integrated code snippets - people need use-case driven examples, sample apps aren't enough ** Should provide a guided tour to "get started with seam" - this is almost a reality, but the level of knowledge required to succeed is too high. ** Should provide a maven archetype for seam, or provide a link to one if it exists already -- this information is currently hidden or unavailable. ==COMPLETED== * Too hard to find JIRA links -- added JIRA links to sidenav -- Lincoln Baxter was: 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.) ==INCOMPLETE== * 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. *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. *** No good documentation about the Seam portlet bridge, which is a closely related project. Should add visible links. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ==COMPLETED== * 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Fabricio Lemos commented on JBSEAM-4585: ---------------------------------------- There are a bunch of cool stuff planned to be release on Jboss projects and I think it should be easier to watch the evolution of planned features. For example, I´m really interested on Seam 3 extensions for Security and Spring Integration and on Arquillian Selenium Integration. I know these thing are planned but it would be great if there were some road map which I could watch. The natural way would be to create a Jira Feature Request for every (important) thing planned, and every "what's next" section on any blog post should link to these Jira FR. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III updated JBSEAM-4585: --------------------------------------- Description: 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.) ==INCOMPLETE== * 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. *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. *** No good documentation about the Seam portlet bridge, which is a closely related project. Should add visible links. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ** Need a better knowledge base, with integrated code snippets - people need use-case driven examples, sample apps aren't enough ** Should provide a guided tour to "get started with seam" - this is almost a reality, but the level of knowledge required to succeed is too high. ** Should provide a maven archetype for seam, or provide a link to one if it exists already -- this information is currently hidden or unavailable. ** Arquillian needs better getting started docs, or a clearer link to them: http://community.jboss.org/en/arquillian - This link would do: http://docs.jboss.org/arquillian/reference/1.0.0.Alpha1/en-US/html_single..., but the link may change as versions increment. Best way to handle? ==COMPLETED== * Too hard to find JIRA links -- added JIRA links to sidenav -- Lincoln Baxter was: 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.) ==INCOMPLETE== * 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. *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. *** No good documentation about the Seam portlet bridge, which is a closely related project. Should add visible links. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ** Need a better knowledge base, with integrated code snippets - people need use-case driven examples, sample apps aren't enough ** Should provide a guided tour to "get started with seam" - this is almost a reality, but the level of knowledge required to succeed is too high. ** Should provide a maven archetype for seam, or provide a link to one if it exists already -- this information is currently hidden or unavailable. ==COMPLETED== * 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4585?page=com.atlassian.jira.pl... ] Lincoln Baxter III updated JBSEAM-4585: --------------------------------------- Description: 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.) ==INCOMPLETE== ** Need a better knowledge base, with integrated code snippets - people need use-case driven examples, sample apps aren't enough ** Should provide a guided tour to "get started with seam" - this is almost a reality, but the level of knowledge required to succeed is too high. ** Should provide a maven archetype for seam, or provide a link to one if it exists already -- this information is currently hidden or unavailable. *** No good documentation about the Seam portlet bridge, which is a closely related project. Should add visible links. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ==COMPLETED== * [Lincoln Baxter] Too hard to find JIRA links (resolved via added JIRA links to sidenav) * [Lincoln Baxter & Dan Allen] http://seamframework.org/Community/GettingStartedDevelopingTheSeamFramework -- page still references version 2.0 of Seam for new development, which is now a lie (Resolved via Seam 3 section on sfwk.org) * [Dan Allen] http://seamframework.org/Download/SeamDownloads#H-SeamSVNRepository contains repo URLs that are now broken for SCM checkout. (resolved updated links) * [Arquillian Team] Arquillian needs better getting started docs, or a clearer link to them: http://community.jboss.org/en/arquillian - This link would do: http://docs.jboss.org/arquillian/reference/1.0.0.Alpha1/en-US/html_single..., but the link may change as versions increment. Best way to handle? (resolved via http://jboss.org/arquillian) *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. was: 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.) ==INCOMPLETE== ** Need a better knowledge base, with integrated code snippets - people need use-case driven examples, sample apps aren't enough ** Should provide a guided tour to "get started with seam" - this is almost a reality, but the level of knowledge required to succeed is too high. ** Should provide a maven archetype for seam, or provide a link to one if it exists already -- this information is currently hidden or unavailable. *** No good documentation about the Seam portlet bridge, which is a closely related project. Should add visible links. ***It is currently impossible to subscribe for email notifications of new comments or changes on a thread unless you are the author. This is a major limitation of the seamframework.org software. ==COMPLETED== * [Lincoln Baxter] Too hard to find JIRA links -- added JIRA links to sidenav * [Lincoln Baxter & Dan Allen] http://seamframework.org/Community/GettingStartedDevelopingTheSeamFramework -- page still references version 2.0 of Seam for new development, which is now a lie * [Dan Allen] http://seamframework.org/Download/SeamDownloads#H-SeamSVNRepository contains repo URLs that are now broken for SCM checkout. * [Arquillian Team] Arquillian needs better getting started docs, or a clearer link to them: http://community.jboss.org/en/arquillian - This link would do: http://docs.jboss.org/arquillian/reference/1.0.0.Alpha1/en-US/html_single..., but the link may change as versions increment. Best way to handle? *** No clear place to get started using CDI/Weld/EE6 functionality - Persistence, Transactions, CDI, all need clear getting started information and tutorials. -- 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