[Community-cvs] www/2005 participate.html, 1.9, 1.10 policies.html, 1.4, 1.5 posting_guidelines.html, 1.3, 1.4
rishimathew at helixcommunity.org rishimathew at helixcommunity.orgUpdate of /cvsroot/community/www/2005 In directory cvs:/tmp/cvs-serv30909 Modified Files: participate.html policies.html posting_guidelines.html Log Message: Including links to Bugzilla guide Index: participate.html =================================================================== RCS file: /cvsroot/community/www/2005/participate.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -d -r1.9 -r1.10 --- participate.html 27 Sep 2005 15:54:55 -0000 1.9 +++ participate.html 9 Mar 2006 22:03:02 -0000 1.10 @@ -72,9 +72,13 @@ to make the Helix DNA better for you. If you have run into something you would like to report, you can use the <a - href="https://bugs.helixcommunity.org/?group_id=33">Bugs page</a> to -report issues encountered using the Helix DNA products -<br> + href="https://bugs.helixcommunity.org/">Bugs page</a> to +report issues encountered using the Helix DNA products. You can use the +<a href="https://community.helixcommunity.org/2006/hcbugzilla">Bugzilla +page</a> to understand how the Bug Submission process works. For a +quick guide on how to file a bug, take a look at "<a + href="https://community.helixcommunity.org/2006/writingbugreport">How +to file a good bug?</a>"<br> <ul> <li> <h3 style="font-style: italic;">Be a Developer</h3> Index: posting_guidelines.html =================================================================== RCS file: /cvsroot/community/www/2005/posting_guidelines.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- posting_guidelines.html 23 Aug 2005 16:58:57 -0000 1.3 +++ posting_guidelines.html 9 Mar 2006 22:03:02 -0000 1.4 @@ -41,7 +41,22 @@ the moderation queue need to be approved by the list administrator before they will be posted which will delay receipt of your message by your intended recipients. To ensure that your mail gets approved -please follow the posting guidelines closely. +please follow the posting guidelines closely.<br> +<br> +<span style="font-weight: bold;">Private Emails Do Not Help Others</span><br> +If you mail one of the Helix Community developers +directly with a support question, you're likely to be ignored. This +doesn't +mean that we don't want to help you out, on the contrary, we very much +want to +see you succeed in using Helix. It's just that we don't like answering +the +same questions over and over again, and one-on-one support is pretty +difficult +via email. Thus we provide our general support in a public forum where +the questions and answers get archived and can be used by future Helix +Community members at their leisure. This also allows other knowledgable +Helix Community members help us out in providing support.<br> <p style="margin-bottom: 0in;"><span style="font-weight: bold;">Introductions</span><br> New members are encouraged to introduce themselves. When joining a new mailing list, please send a @@ -95,12 +110,11 @@ to the specific project</li> <li>Chose the mailing list you wish to subscribe to - It is as easy as clicking on the -subscribe link. <></></li> +subscribe link. <></li> </ul> -<>To post a message to all list members, send email to +To post a message to all list members, send email to <project name-list>@helixcommunity.org -</> <p style="margin-bottom: 0in;">Note: Most lists are moderated and you will need to wait until your subscription has been approved before your message will be posted.<br> Index: policies.html =================================================================== RCS file: /cvsroot/community/www/2005/policies.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- policies.html 7 Sep 2005 18:58:16 -0000 1.4 +++ policies.html 9 Mar 2006 22:03:02 -0000 1.5 @@ -39,7 +39,24 @@ in mailing list discussions please first review the <span style="text-decoration: underline;"></span><a href="http://community.helixcommunity.org/2005/posting_guidelines">Helix -Community posting guidelines.</a> +Community posting guidelines.</a><br> +<br> +<big><big style="font-weight: bold;">Filing Bugs<br> +</big></big><br> +Anybody -- developers, testers or end users -- should feel free to +alert the +Helix community of issues encountered with the Helix DNA, or ideas for +ways +to make the Helix DNA better for you. If you have run into something +you would +like to report, you can use the <a + href="https://bugs.helixcommunity.org/">Bugs page</a> to +report issues encountered using the Helix DNA products. You can use the +<a href="https://community.helixcommunity.org/2006/hcbugzilla">Bugzilla +page</a> to understand how the Bug Submission process works. For a +quick guide on how to file a bug, take a look at "<a + href="https://community.helixcommunity.org/2006/writingbugreport">How +to file a good bug?</a>"<br> <h2>New Projects</h2> You can create a proposal for extending the Helix platform, which, if approved, will also give you a workspace and assistance for adding in