<div dir="ltr"><pre class="" style="font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;font-size:12px;margin-top:0px;margin-bottom:0px;width:2031px;color:rgb(51,51,51);line-height:16px"><div class="" id="file-gistfile1-txt-LC1" style>Sorry, I'm a bit late on this. I quite like when you do a blog post for the new releases, where you have a list of bugs squashed / features added. You could do a blog post every week or two with a summary of new / updated bugs, then post a link to the mailing list, twitter, etc.</div><div class="" id="file-gistfile1-txt-LC2" style> </div><div class="" id="file-gistfile1-txt-LC3" style>Regards,</div><div class="" id="file-gistfile1-txt-LC4" style> </div><div class="" id="file-gistfile1-txt-LC5" style>Alan</div></pre></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 4, 2014 at 6:46 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
you may have noticed that we are looking into a better Bug Triage<br>
process. Our intention is that interested community members can support<br>
the project in a relatively simple but very effective way.<br>
<br>
Just like helping users on the mailinglist, follow-up questions and<br>
gathering some debugging data is often needed before a new bugreport can<br>
get worked on by a developer. The gathering of details about problems<br>
and clarifying the actual problem is what Bug Triage is all about. Not<br>
all people that report a bug know what information would be useful, or<br>
state their issue not very clear. Any community member is invited to<br>
help others with the improving of bug reports.<br>
<br>
Under the umbrella of Bug Triage we will need to get notifications about<br>
new bugs that to be reviewed. With this email I would like to hear what<br>
options are most useful for community members that are interested in<br>
checking new bugs for completeness and all. The options that we<br>
currently have are:<br>
<br>
1. subscription to the <a href="mailto:bugs@gluster.org">bugs@gluster.org</a> mailinglist<br>
2. watching the <a href="mailto:bugs@gluster.org">bugs@gluster.org</a> user with your Bugzilla account<br>
3. RSS-feed with new bugs per version or component<br>
4. lurking in #gluster on Freenode IRC, pay attention to glusterbot<br>
5. .... <-- your idea<br>
<br>
Let me know by email (to the list or me directly) how you think<br>
receiving notifications about new/updated bugs is most useful. If you<br>
have any questions about the Bug Triage itself, get in touch, and I'm<br>
happy to explain more.<br>
<br>
Many thanks,<br>
Niels<br>
<br>
<br>
PS:<br>
The 1st four options above are documented in the wiki:<br>
- <a href="http://www.gluster.org/community/documentation/index.php/Bugzilla_Notifications" target="_blank">http://www.gluster.org/community/documentation/index.php/Bugzilla_Notifications</a><br>
And so are the (quite verbose) Bug Triage Guidelines:<br>
- <a href="http://www.gluster.org/community/documentation/index.php/Bug_triage" target="_blank">http://www.gluster.org/community/documentation/index.php/Bug_triage</a><br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Alan Orth<br><a href="mailto:alan.orth@gmail.com" target="_blank">alan.orth@gmail.com</a><br><a href="https://alaninkenya.org" target="_blank">https://alaninkenya.org</a><br><a href="https://mjanja.ch" target="_blank">https://mjanja.ch</a><br>"In heaven all the interesting people are missing." -Friedrich Nietzsche<div>GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0<br></div></div>
</div>