FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 02-27-2010, 10:14 PM
Mark Loeser
 
Default Marking bugs for bugday?

Ben de Groot <yngwin@gentoo.org> 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
 
Old 02-27-2010, 11:22 PM
Ryan Hill
 
Default Marking bugs for bugday?

On Sat, 27 Feb 2010 05:18:39 +0100
Sebastian Pipping <sping@gentoo.org> wrote:

> 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 would use it. I honestly didn't know we still did bugdays. :/


--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
 
Old 02-28-2010, 08:36 AM
Dawid Węgliński
 
Default Marking bugs for bugday?

On Sunday 28 February 2010 00:14:36 Mark Loeser wrote:
> Ben de Groot <yngwin@gentoo.org> 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
 
Old 02-28-2010, 12:15 PM
Alexander Fry
 
Default 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 Fry
 
Old 02-28-2010, 06:54 PM
Markos Chandras
 
Default 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
 
Old 02-28-2010, 07:04 PM
Sebastian Pipping
 
Default 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
 
Old 03-01-2010, 12:35 AM
Joshua Saddler
 
Default Marking bugs for bugday?

On Sun, 28 Feb 2010 21:04:04 +0100
Sebastian Pipping <sping@gentoo.org> 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.
 
Old 03-01-2010, 08:17 PM
Ioannis Aslanidis
 
Default 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 <nightmorph@gentoo.org> wrote:
> On Sun, 28 Feb 2010 21:04:04 +0100
> Sebastian Pipping <sping@gentoo.org> 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
<deathwing00[at]gentoo.org> 0x47F370A0
 
Old 03-01-2010, 09:19 PM
Ben de Groot
 
Default Marking bugs for bugday?

On 1 March 2010 22:17, Ioannis Aslanidis <aslanidis@gmail.com> 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)
__________________________________________________ ____
 
Old 03-01-2010, 09:26 PM
Ioannis Aslanidis
 
Default 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 <yngwin@gentoo.org> wrote:
> On 1 March 2010 22:17, Ioannis Aslanidis <aslanidis@gmail.com> 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
<deathwing00[at]gentoo.org> 0x47F370A0
 

Thread Tools




All times are GMT. The time now is 12:05 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org