Re: [gentoo-dev] Marking bugs for bugday?
On 2010.03.01 21:17, Ioannis Aslanidis wrote: > Hello, > [snip] > Bug Day, followed by an announcement the week before and a reminder > the day before. This needs to happen in publicly visible places (and > has happened in some of them as far as I recall): forums, gentoo- > user, > gentoo-dev, gentoo-announce, gentoo-dev-announce, the newsletter > (dead?) and the website. Having people related to the Bug Day project > posting to their blogs can help a lot in this case as well. [snip > Regards. > > [snip] > > > -- > Ioannis Aslanidis > http://www.deathwing00.org > 0x47F370A0 > I used to do the announces, sometimes under the psudonym of Welps PA. I can chip in again and with some of the organisation and the announces. Its definately worth saving bugday - it brings devs and users closer together. sping was looking at "two days in plain Python" - do we need a developer to do that or could that be one of the bugs for bugday ? I realise that gentoo.org will host it, so we need to validate it but that should be much less time than writing the code. -- Regards, Roy Bamford (Neddyseagoon) an member of gentoo-ops forum-mods trustees pgpSzOs2UpSyL.pgp Description: PGP signature
Re: [gentoo-dev] Marking bugs for bugday?
I propose a value that you can set at runtime. We do this at work with the gflags package (already in the tree) or a config file. -A On Tue, Mar 2, 2010 at 1:05 PM, Sebastian Pipping wrote: > On 03/02/10 21:47, Alec Warner wrote: >> I would recommend not hardcoding 10 seconds; but otherwise caching is good ;) > > What do you propose? > > > > Sebastian > >
Re: [gentoo-dev] Marking bugs for bugday?
On 03/02/10 21:47, Alec Warner wrote: > I would recommend not hardcoding 10 seconds; but otherwise caching is good ;) What do you propose? Sebastian
Re: [gentoo-dev] Marking bugs for bugday?
When am I getting control over that? Can infra help me? On Tue, Mar 2, 2010 at 8:36 PM, Sebastian Pipping wrote: > On 03/01/10 22:17, Ioannis Aslanidis wrote: >> getting control of bugday.gentoo.org and be able to upload our own >> content would be great. > > The current page is said to generate one XML request per bug listed on > the page for each request. From my experience trying to remove bugs > from that page yesterday(?) (through clicking on "remove" buttons) I > have the impression that it's true: Du to page reload times the site in > it's current form is unusable in the very sense of the word. > > Ideas I have on a rather simple rewrite: > > - Split the bugday website into two pages: > - Page "Open bugs" showing > - open bugday-keyworded bugs (with date of the latest bugday) > in randomized order > - Page "Closed bugs" showing > - closed bugday-keyworded bugs (with date of the latest bugday) > in some sorted order > - a ranking with closed bugs per participant > (as that may not be the assignee such information could > maybe be encoding into the status whiteboard, somewhere > we can query it from easily if whiteboard fits for that) > > - Do one search request to bugzilla internally, only. > Should be possible as we're now asking bugzilla for the list > of bugs instead of asking for details on a list we pass in. > > - Simple caching of bugzilla requests for 10 seconds or so. > Should not hurt the bugday experience much and reduce load > further. > > I could imagine that an ugly prototype with rough-edges of that could > take two days in plain Python. At the moment I cannot say when and if I > have these two days, but maybe someone else with time is fire and flame > for it by now? > > > > Sebastian > > -- Ioannis Aslanidis http://www.deathwing00.org 0x47F370A0
Re: [gentoo-dev] Marking bugs for bugday?
On Tue, Mar 2, 2010 at 11:36 AM, Sebastian Pipping wrote: > On 03/01/10 22:17, Ioannis Aslanidis wrote: >> getting control of bugday.gentoo.org and be able to upload our own >> content would be great. > > The current page is said to generate one XML request per bug listed on > the page for each request. From my experience trying to remove bugs > from that page yesterday(?) (through clicking on "remove" buttons) I > have the impression that it's true: Du to page reload times the site in > it's current form is unusable in the very sense of the word. > > Ideas I have on a rather simple rewrite: > > - Split the bugday website into two pages: > - Page "Open bugs" showing > - open bugday-keyworded bugs (with date of the latest bugday) > in randomized order > - Page "Closed bugs" showing > - closed bugday-keyworded bugs (with date of the latest bugday) > in some sorted order > - a ranking with closed bugs per participant > (as that may not be the assignee such information could > maybe be encoding into the status whiteboard, somewhere > we can query it from easily if whiteboard fits for that) > > - Do one search request to bugzilla internally, only. > Should be possible as we're now asking bugzilla for the list > of bugs instead of asking for details on a list we pass in. > > - Simple caching of bugzilla requests for 10 seconds or so. > Should not hurt the bugday experience much and reduce load > further. I would recommend not hardcoding 10 seconds; but otherwise caching is good ;) > > I could imagine that an ugly prototype with rough-edges of that could > take two days in plain Python. At the moment I cannot say when and if I > have these two days, but maybe someone else with time is fire and flame > for it by now? > > > > Sebastian > >
Re: [gentoo-dev] Marking bugs for bugday?
On 03/01/10 22:17, Ioannis Aslanidis wrote: > getting control of bugday.gentoo.org and be able to upload our own > content would be great. The current page is said to generate one XML request per bug listed on the page for each request. From my experience trying to remove bugs from that page yesterday(?) (through clicking on "remove" buttons) I have the impression that it's true: Du to page reload times the site in it's current form is unusable in the very sense of the word. Ideas I have on a rather simple rewrite: - Split the bugday website into two pages: - Page "Open bugs" showing - open bugday-keyworded bugs (with date of the latest bugday) in randomized order - Page "Closed bugs" showing - closed bugday-keyworded bugs (with date of the latest bugday) in some sorted order - a ranking with closed bugs per participant (as that may not be the assignee such information could maybe be encoding into the status whiteboard, somewhere we can query it from easily if whiteboard fits for that) - Do one search request to bugzilla internally, only. Should be possible as we're now asking bugzilla for the list of bugs instead of asking for details on a list we pass in. - Simple caching of bugzilla requests for 10 seconds or so. Should not hurt the bugday experience much and reduce load further. I could imagine that an ugly prototype with rough-edges of that could take two days in plain Python. At the moment I cannot say when and if I have these two days, but maybe someone else with time is fire and flame for it by now? Sebastian
Re: [gentoo-dev] Marking bugs for bugday?
That sounds great! On Tue, Mar 2, 2010 at 1:02 AM, Sebastian Pipping wrote: > > Quoting Ioannis Aslanidis : >> >> I would prefer to keep the keyword for >> Bugday Members to administer. > > I don't think that sending mails would work well. > If you want extra control/QA for bugday team members > I would propose two different keywords: one for bugday > candidates and one for confirmed bugday bugs. > > Any dev could mark bugs as candidates easily and without > delays while you could still reserve acknoledgement to you. > > > > Sebastian > > > > > -- Ioannis Aslanidis http://www.deathwing00.org 0x47F370A0
Re: [gentoo-dev] Marking bugs for bugday?
Quoting Ioannis Aslanidis : I would prefer to keep the keyword for Bugday Members to administer. I don't think that sending mails would work well. If you want extra control/QA for bugday team members I would propose two different keywords: one for bugday candidates and one for confirmed bugday bugs. Any dev could mark bugs as candidates easily and without delays while you could still reserve acknoledgement to you. Sebastian
Re: [gentoo-dev] Marking bugs for bugday?
On 01/03/2010 22:19, Ben de Groot wrote: On 1 March 2010 22:17, Ioannis Aslanidis wrote: [...] Great ideas! The teams should send the list of bugs, with each bug filling a skeleton similar to the following: * Ticket number. * Title. * Clear, easy to understand, short description of what we want to delegate to our users. * Topic of the task (as in networking, C/C++, python, ebuild, etc.). * Difficulty of the task. * Detailed step-by-step description of the task. This will not work. You need to keep things really simple for our devs. I don't see anybody but the most dedicated ones, who also happen to have a lot of time on their hands, fill out such a detailed form. I'd say let devs just nominate bugs, either by adding BugDay to the keywords field or something similar, or by passing the bugday team a list of bug numbers. Then the bugday team can sort these and see if any instructions are needed. They could always ask the involved devs/teams for more info when necessary. Cheers, You don't need to make it compulsory to fill out those fields and if just 1 out of every 10 or 20 bugs gets that filled then it is still a big leap forward. Or... Ask for a dev whose whole job is to fill out those forms. I'm sure there are plenty of non-coders out there who would be willing to do it, even a team!
Re: [gentoo-dev] Marking bugs for bugday?
Ioannis Aslanidis said: > Hello, > [... whole bunch of ideas ...] > Let me hear of what you have to say to all this. Has anyone looked at how others projects do bugdays? We shouldn't need to reinvent the wheel here and can probably get some great ideas from other distributions out there. -- Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com
Re: [gentoo-dev] Marking bugs for bugday?
I understand that the implication and the time demand of this last point may be a little excessive. If anyone still has the time to fill the skeleton in, they are still welcome to do it. Otherwise with the bug list it will be enough. I would prefer to keep the keyword for Bugday Members to administer. On Mon, Mar 1, 2010 at 11:19 PM, Ben de Groot wrote: > On 1 March 2010 22:17, Ioannis Aslanidis wrote: >> [...] > > Great ideas! > >> The teams should send the list of >> bugs, with each bug filling a skeleton similar to the following: >> >> * Ticket number. >> * Title. >> * Clear, easy to understand, short description of what we want to >> delegate to our users. >> * Topic of the task (as in networking, C/C++, python, ebuild, etc.). >> * Difficulty of the task. >> * Detailed step-by-step description of the task. > > This will not work. You need to keep things really simple for our devs. > I don't see anybody but the most dedicated ones, who also happen > to have a lot of time on their hands, fill out such a detailed form. > > I'd say let devs just nominate bugs, either by adding BugDay to > the keywords field or something similar, or by passing the bugday > team a list of bug numbers. Then the bugday team can sort these > and see if any instructions are needed. They could always ask the > involved devs/teams for more info when necessary. > > Cheers, > -- > Ben de Groot > Gentoo Linux developer (qt, media, lxde, desktop-misc) > __ > > -- Ioannis Aslanidis http://www.deathwing00.org 0x47F370A0
Re: [gentoo-dev] Marking bugs for bugday?
On 1 March 2010 22:17, Ioannis Aslanidis wrote: > [...] Great ideas! > The teams should send the list of > bugs, with each bug filling a skeleton similar to the following: > > * Ticket number. > * Title. > * Clear, easy to understand, short description of what we want to > delegate to our users. > * Topic of the task (as in networking, C/C++, python, ebuild, etc.). > * Difficulty of the task. > * Detailed step-by-step description of the task. This will not work. You need to keep things really simple for our devs. I don't see anybody but the most dedicated ones, who also happen to have a lot of time on their hands, fill out such a detailed form. I'd say let devs just nominate bugs, either by adding BugDay to the keywords field or something similar, or by passing the bugday team a list of bug numbers. Then the bugday team can sort these and see if any instructions are needed. They could always ask the involved devs/teams for more info when necessary. Cheers, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) __
Re: [gentoo-dev] Marking bugs for bugday?
Hello, After having a talk with Sebastien (aka sping), I think it is time to give a clear reply from my side to this discussion, given that I am still a member of the project and I am willing to rescue it. At this moment, the Bugday Project is starving because no one feeds it. It needs to eat bugs, so before anything let's fill up the plate with as many of them as possible. In order to do this, we need to change a few things here and there so that the bugs flow correctly towards the project. The first thing that would help us a lot is to actually have a keyword 'bugday' in our bugzilla. This will definitely help us out a lot when managing all the tickets and be able to produce some sort of report. The second thing that comes to my mind is pretty internal, but requires some external interaction. We need to work ahead of the Bug Day and be capable of having everything needed ready. Having the proper tools is very important for this task, and getting control of bugday.gentoo.org and be able to upload our own content would be great. It's a virtual apache host running in the same place as bugs.gentoo.org, as it requires access to the database (although this does not necessarily need to be like this if the database is accessible through the network). The third thing that we need is the proper audience. We need more PR. My proposal here is to start with an announcement two weeks before the Bug Day, followed by an announcement the week before and a reminder the day before. This needs to happen in publicly visible places (and has happened in some of them as far as I recall): forums, gentoo-user, gentoo-dev, gentoo-announce, gentoo-dev-announce, the newsletter (dead?) and the website. Having people related to the Bug Day project posting to their blogs can help a lot in this case as well. The fourth thing, is to actually get the proper information in the proper format. We need a compromise from each of the teams, so that they send us at least one bug every month that can be delegated to our users. Then the Bugday Project can decide whether the bug is appropriate or not for delegation, and tag it with the before-mentioned 'bugday' keyword. The teams should send the list of bugs, with each bug filling a skeleton similar to the following: * Ticket number. * Title. * Clear, easy to understand, short description of what we want to delegate to our users. * Topic of the task (as in networking, C/C++, python, ebuild, etc.). * Difficulty of the task. * Detailed step-by-step description of the task. Let me hear of what you have to say to all this. Regards. If we have this piece of information, we can organize ourselves better. On Mon, Mar 1, 2010 at 2:35 AM, Joshua Saddler wrote: > On Sun, 28 Feb 2010 21:04:04 +0100 > Sebastian Pipping wrote: > >> On 02/28/10 20:54, Markos Chandras wrote: >> > Do we still have bugdays? Who is taking care of this project and the >> > respective webpage? I think we first need to answer these questions before >> > we even consider resurrect this project >> >> welp -> away > > He's not away, he's retired. It's just taken several months to close his bug. > >> gurligebis -> no reply yet > > I thought gurli was also retired. > > -- Ioannis Aslanidis http://www.deathwing00.org 0x47F370A0
Re: [gentoo-dev] Marking bugs for bugday?
On Sun, 28 Feb 2010 21:04:04 +0100 Sebastian Pipping wrote: > On 02/28/10 20:54, Markos Chandras wrote: > > Do we still have bugdays? Who is taking care of this project and the > > respective webpage? I think we first need to answer these questions before > > we even consider resurrect this project > > welp -> away He's not away, he's retired. It's just taken several months to close his bug. > gurligebis -> no reply yet I thought gurli was also retired. signature.asc Description: PGP signature
Re: [gentoo-dev] Marking bugs for bugday?
On 02/28/10 20:54, Markos Chandras wrote: > Do we still have bugdays? Who is taking care of this project and the > respective webpage? I think we first need to answer these questions before we > even consider resurrect this project welp -> away deathwing00 -> mail contact with me gurligebis -> no reply yet
Re: [gentoo-dev] Marking bugs for bugday?
On Saturday 27 February 2010 06:18:39 Sebastian Pipping wrote: > Hello! > > > I'm surprised that there is no keyword in Gentoo's bugzilla [1] to mark > bugs for bugday. Is there a good reason why such a keyword does not > exist? Would it be hard to set up? > > Thanks, > > > > Sebastian > > > [1] https://bugs.gentoo.org/describekeywords.cgi Do we still have bugdays? Who is taking care of this project and the respective webpage? I think we first need to answer these questions before we even consider resurrect this project -- Markos Chandras (hwoarang) Gentoo Linux Developer Web: http://hwoarang.silverarrow.org signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Marking bugs for bugday?
On Sat, Feb 27, 2010 at 06:38:57PM +0100, Sebastian Pipping wrote: > bugday.gentoo.org could still be used as an entry point showing these bugs. http://bugday.gentoo.org/ would easily be made able to show bugs with a specific Bugzilla keyword only. If I recall correctly, we had to do some very naughty things back when Gentoo changed the Bugzilla system to run with a MySQL cluster as backend. Back in the early days of Bugday, the site queried the database directly, but these days it uses Bugzilla's XML API for all the requests, which is why it takes forever to load the page. We did spend one Bugday making it a bit faster though, but it's still not fast enough (yes, it was even worse before that). A rewrite with a cache would probably not be a bad idea and it would be an easy task for any user who wants to contribute with something useful :) Until then, it would probably be a good idea to clean up the ACL of http://bugday.gentoo.org/. I'm still able to log in using my ancient username and password, and I can see on the accesslist that there are multiple former developers who still has access to the site. -- Alexander Færøy pgpJngzegL7g3.pgp Description: PGP signature
Re: [gentoo-dev] Marking bugs for bugday?
On Sunday 28 February 2010 00:14:36 Mark Loeser wrote: > Ben de Groot said: > > > Its been pretty much dead. We need more developer involvement so users > > > can actually talk to them and help resolve issues. If we can't get > > > enough developers to participate then we should just stop trying to do > > > it instead of putting on such a poor showing. > > > > I would like to be involved but not in the current disorganized form. Our > > #gentoo-bugs channel topic still refers to the thoroughly outdated > > bugsday.g.o page, and I can't edit either of them. > > I can modify the channel topic for you. I should have a login for the > bugsday.g.o page somewhere, if not...I'm sure we can get one. > welp transfered #gentoo-bugs to you last time when i asked him, so you are now the owner. But every developer can change topic by /msg chanserv topic #gentoo-bugs -- Cheers Dawid Węgliński
Re: [gentoo-dev] Marking bugs for bugday?
Ben de Groot said: > > Its been pretty much dead. We need more developer involvement so users > > can actually talk to them and help resolve issues. If we can't get > > enough developers to participate then we should just stop trying to do > > it instead of putting on such a poor showing. > > I would like to be involved but not in the current disorganized form. Our > #gentoo-bugs channel topic still refers to the thoroughly outdated > bugsday.g.o page, and I can't edit either of them. I can modify the channel topic for you. I should have a login for the bugsday.g.o page somewhere, if not...I'm sure we can get one. > We need an easier interface to mark bugs to be tackled on bugday, > and I like Sebastian's proposal for that. The idea for the bugsday.g.o > page is good, but it needs to be brought up-to-date and accessible > to all devs. Low barriers to participation and all that. And even devs > who cannot take part on the day itself could participate by requesting > certain bugs or issues to be tackled. If you want to take the lead on this, come and talk to me on IRC and let me know what ideas you have. I'd love to see it take off, but I don't have the time to put towards it myself. > Also, participating devs should get permission to commit easy fixes > for packages they don't maintain (the other thread about commit > policies is relevant here). Obviously issues that are more involved > need to be passed on to the proper maintainers. This is something we'll have to be careful of and discuss what types of changes can be done. Not everything needs to be necessarily fixed in the tree though, helping users get proper patches onto bugs can be just as good and help get more useful contributions from those users in the future. Consider it an opportunity to train possible new developers. > I think if we can get a few devs and possibly some users together > to organize this in a better way, this could be useful. But if things > are to stay the way they are, then we better stop pretending. I couldn't agree more. -- Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com
Re: [gentoo-dev] Marking bugs for bugday?
On 27 February 2010 21:48, Mark Loeser wrote: > Roy Bamford said: >> The last few times I've dropped into bugday, its been very quiet, which >> suggests its in need of some tlc but maybe its just my timezone. > > Its been pretty much dead. We need more developer involvement so users > can actually talk to them and help resolve issues. If we can't get > enough developers to participate then we should just stop trying to do > it instead of putting on such a poor showing. I would like to be involved but not in the current disorganized form. Our #gentoo-bugs channel topic still refers to the thoroughly outdated bugsday.g.o page, and I can't edit either of them. We need an easier interface to mark bugs to be tackled on bugday, and I like Sebastian's proposal for that. The idea for the bugsday.g.o page is good, but it needs to be brought up-to-date and accessible to all devs. Low barriers to participation and all that. And even devs who cannot take part on the day itself could participate by requesting certain bugs or issues to be tackled. Also, participating devs should get permission to commit easy fixes for packages they don't maintain (the other thread about commit policies is relevant here). Obviously issues that are more involved need to be passed on to the proper maintainers. I think if we can get a few devs and possibly some users together to organize this in a better way, this could be useful. But if things are to stay the way they are, then we better stop pretending. Cheers, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) __
Re: [gentoo-dev] Marking bugs for bugday?
chrome://messenger/locale/messengercompose/composeMsgs.properties: Sorry, what's "tlc"? Next Saturday is a bugday date again, btw. Sebastian Tender Loving Care. Dale :-) :-)
Re: [gentoo-dev] Marking bugs for bugday?
Roy Bamford said: > The last few times I've dropped into bugday, its been very quiet, which > suggests its in need of some tlc but maybe its just my timezone. Its been pretty much dead. We need more developer involvement so users can actually talk to them and help resolve issues. If we can't get enough developers to participate then we should just stop trying to do it instead of putting on such a poor showing. -- Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com
Re: [gentoo-dev] Marking bugs for bugday?
On 02/27/10 19:14, Roy Bamford wrote: > What would be the criteria for marking a bug as bugday? I would say something along a "yes" to Could this task fit for being solved by someone who is not a Gentoo developer? It's not precise, does it need to be? > Why whould it be any better than a properly maintained > bugday.gentoo.org page, which also tried to classify bugs. As I said: with this keyword every Gentoo dev can help classifying. Lower risk on bottlenecks/delays and manpower. > The last few times I've dropped into bugday, its been very quiet, which > suggests its in need of some tlc but maybe its just my timezone. Sorry, what's "tlc"? Next Saturday is a bugday date again, btw. Sebastian
Re: [gentoo-dev] Marking bugs for bugday?
On 2010.02.27 17:38, Sebastian Pipping wrote: [snip] > what i see as an advantage of the bugzilla-keyword approach is that > any > developer can contribute: everyone (especially bug wranglers) can > mark > bugs for bugday easily from bugzilla. > > bugday.gentoo.org could still be used as an entry point showing these > bugs. > > > > sebastian > Sebastian, What would be the criteria for marking a bug as bugday? Why whould it be any better than a properly maintained bugday.gentoo.org page, which also tried to classify bugs. The last few times I've dropped into bugday, its been very quiet, which suggests its in need of some tlc but maybe its just my timezone. -- Regards, Roy Bamford (Neddyseagoon) an member of gentoo-ops forum-mods trustees pgptyplfBCzz7.pgp Description: PGP signature
Re: [gentoo-dev] Marking bugs for bugday?
On 02/27/10 16:39, Roy Bamford wrote: > That sounds good. If it were an enumerated type bugs could be graded > for bugday too. > > .e.g. > Novice > You need to have fixed a few > Intermediate > We don't have a clue. > > I'm not suggesting any grades - those are just for illustration. I had that idea too and found it not too helpful. Potential issues: - Difficulity can be very subjective - Introducing new "levels" later doesn't work well as we'd manually have to go through each bug "left" or "right" of that new level. So we'd have to get it very right the first time. Sebastian
Re: [gentoo-dev] Marking bugs for bugday?
On 02/27/10 17:22, Mark Loeser wrote: > I think the goal was to have http://bugday.gentoo.org/ fill this role whenever i visit bugday.gentoo.org it takes minutes to load. afair for the two bugdays i participated it didn't display anything helpful (to me), especially: why does it show fixed bugs, too? about half of them are fixed. section "new, requests for ebuilds, or just a version bump" doesn't have a single bug after 2006, that's how "new" it is. > instead of polluting bugzie with more keywords. would a single keyword be pollution? > I'm not really attached > to one approach over the other, but atleast this little site gives the > users one place to have to check for things and we can categorize them > easily. what i see as an advantage of the bugzilla-keyword approach is that any developer can contribute: everyone (especially bug wranglers) can mark bugs for bugday easily from bugzilla. bugday.gentoo.org could still be used as an entry point showing these bugs. sebastian
Re: [gentoo-dev] Marking bugs for bugday?
Sebastian Pipping said: > Hello! > > > I'm surprised that there is no keyword in Gentoo's bugzilla [1] to mark > bugs for bugday. Is there a good reason why such a keyword does not > exist? Would it be hard to set up? I think the goal was to have http://bugday.gentoo.org/ fill this role instead of polluting bugzie with more keywords. I'm not really attached to one approach over the other, but atleast this little site gives the users one place to have to check for things and we can categorize them easily. -- Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com
Re: [gentoo-dev] Marking bugs for bugday?
On 2010.02.27 04:18, Sebastian Pipping wrote: > Hello! > > > I'm surprised that there is no keyword in Gentoo's bugzilla [1] to > mark > bugs for bugday. Is there a good reason why such a keyword does not > exist? Would it be hard to set up? > > Thanks, > > > > Sebastian > > > [1] https://bugs.gentoo.org/describekeywords.cgi > > Sebastian, That sounds good. If it were an enumerated type bugs could be graded for bugday too. .e.g. Novice You need to have fixed a few Intermediate We don't have a clue. I'm not suggesting any grades - those are just for illustration. -- Regards, Roy Bamford (Neddyseagoon) an member of gentoo-ops forum-mods trustees pgpiYL8TSYAcY.pgp Description: PGP signature
[gentoo-dev] Marking bugs for bugday?
Hello! I'm surprised that there is no keyword in Gentoo's bugzilla [1] to mark bugs for bugday. Is there a good reason why such a keyword does not exist? Would it be hard to set up? Thanks, Sebastian [1] https://bugs.gentoo.org/describekeywords.cgi
