Please add something like the attached patch to the bug-wranglers project page (see URL). I'm unfamiliar with writing docs, so please make sure the layout complies to the standards. Thank you.
Created attachment 209631 [details, diff] see comment #1
Created attachment 209660 [details, diff] another add sunrise section patch Added section to Chapter 4, here is what it looks like. http://dev.gentoo.org/~dabbott/pr/sunrise.xml#doc_chap4
Thanks for looking at that. There is a minor problem with your version. Every line in the message start with a tab, which gets copied, if you copy and paste this message. Could you please change it, such that it's possible to simply copy and paste the message?
Don't make it a new section. Then its just confusing since it should be part of the assigning bugs section.
Created attachment 209674 [details, diff] updated per suggestions How is this? http://dev.gentoo.org/~dabbott/pr/sunrise.xml#doc_chap4
Created attachment 209677 [details] add new ebuild information about project sunrise fixed spelling errors
Well, it's still not a sub item of list above. If it isn't possible to have the listing in a sub item with the proper alignment, what about putting the listing on another page and use a link?
Perhaps we also should set the "sunrise suggested" whiteboard status, as it was done before, too.
The patch looks ok to me ( on behalf of sunrise, bug-wranglers and QA ) If there are no objections I will commit the patch in 48 hours I am CC'ing Jeroen here since he is the lead of Bug-wranglers project
So the idea is that the tasks of bug wranglers are to be extended with those of the sunrise team? My impression is that bug wranglers are overburdened already. Maybe it's now time to discuss this on gentoo-dev@ rather than to come up with a highly polished patch for the project page. I'm also quite surprised that 1) other members of the bug wranglers project are not CC'd and that 2) I was CC'd at such a late stage.
(In reply to comment #10) > So the idea is that the tasks of bug wranglers are to be extended with those of > the sunrise team? My impression is that bug wranglers are overburdened already. > > Maybe it's now time to discuss this on gentoo-dev@ rather than to come up with > a highly polished patch for the project page. > > I'm also quite surprised that 1) other members of the bug wranglers project are > not CC'd and that 2) I was CC'd at such a late stage. > I just seen this bug yesterday. I wasn't aware of that before. I don't think that we want to extend the bug wranglers project but to provide a template for new ebuilds. Some of us who belong to sunrise and do bug-wrangling as well, already use this template but the rest of the people might not be aware of that
Overall I think the template looks good, but one sentence has enough clauses to be a bit hard to read. Breaking it up into a few sentences would be an improvement, especially since the reader may not be a native english-speaker. "The Project Sunrise overlay [1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay." example rewrite: "The Project Sunrise overlay [1] is a Gentoo overlay created to host user-contributed ebuilds. Any user can have ebuilds reviewed by Gentoo devs for entry into the Sunrise overlay. Users can also earn direct commit access to this overlay by demonstrating good ebuild-writing skills."
Extensions for bugzilla (like gnome's extensions/stock-answers or maemo's greasemonkey add-on) exist where such templates are just one click away. OTOH why spam the database with thousands of sunrise-suggested comments, if we might modify bugzilla to add a nice colored box to every bug if status whiteboard (sw) contains sunrise-suggested and add the template to the mails triggered by sw changes?
Created attachment 236479 [details] bgo triage js js extension example based on maemo's bug triage script
(In reply to comment #13) > Extensions for bugzilla (like gnome's extensions/stock-answers or maemo's > greasemonkey add-on) exist where such templates are just one click away. > > OTOH why spam the database with thousands of sunrise-suggested comments, if we > might modify bugzilla to add a nice colored box to every bug if status > whiteboard (sw) contains sunrise-suggested and add the template to the mails > triggered by sw changes? > I don't know the technical aspects of this implementation but I think it is a good idea. I don't quite follow your comment for the database spamming, but how are you gonna inform the users how to get involved with sunrise? You mean the e-mail that will be sent to user when we add "sunrise-suggested" ? Again, I don't know how to implement this :) Also, i think the sunrise predefined messages as comment will be useful to users who attend the bug after the 'sunrise-suggested' addition. In this case they wont receive the template message in the first place
I played with the *user.js from maemo and add some templates for testing at http://github.com/tove/bugsgentooorg_triage_help Tried with chromium, firefox (with greasemonkey) and opera. The templates need some polish before using. The problem how to keep it uptodate is not solved. Having it integraded into bugzilla (if wanted at all) would solve this. Please send comments directly to me or file a new bug.
This comment has been removed because it contained spam. -- idl0r
There is no way for bug wranglers (or indeed anyone) to properly assess what new packages should go to sunrise and what should go into the main tree or indeed into any tree and therefore, selecting bug reports to attach a generic message to is impossible. Additionally, attaching a blanket sunrise suggestion to just any m-w bug report would be equally wrong. I guess we can close this bug now?
