* bug scrub - RFC
@ 2014-01-08 23:20 Trevor Woerner
2014-01-09 10:56 ` Jack Mitchell
0 siblings, 1 reply; 6+ messages in thread
From: Trevor Woerner @ 2014-01-08 23:20 UTC (permalink / raw)
To: openembedded-core
Hi everyone,
This is a "Request For Comments" email regarding a "bug scrub" party the
OE TSC would like to hold.
background:
It has been noticed that the number of bugs in the bugzilla[1] has been
climbing; it would be nice to hold a "bug scrub" event to raise
awareness of the bugzilla and hopefully get some issues resolved.
questions:
1) Currently it has been suggested this should be a 2-day event, should
these two days be during the week or over a weekend? In either case,
which 2 days?
2) Since this is an OE event, should it focus only on OE bugs[2], or
should it be generalized for any bug?
3) Should we create a sign-up sheet (wiki) to keep track of who is
participating, and which issues are being looked at by whom?
(anything else?)
notes:
1) If you or the company for which you work uses OE/Yocto, please
consider making this a company event and having/allowing the engineers
(to) participate.
2) Even if you're not a recipe-, or a build-, or a python-wizard there
are still many things you can do to contribute. Being able to reproduce
a bug or reporting that a bug can't be reproduced can sometimes be quite
helpful (sometimes this points to a host issue or to a bug's description
not being descriptive enough). Sometimes a bug is stuck in the "needs
info" stage which maybe you can provide.
3) Can anyone think of way to help "get the word out"?
4) It would be cool to be able to provide incentives to help people get
interested and contributing to knocking some bugs around. So if anyone
(*cough* Intel) has any neat hardware (*cough* Galileo, Edison) they
could offer as an incentive (or, conversely, if there's a board you'd
like to see Yocto target) please see about making that happen.
Thanks and best regards,
Trevor
[1] https://bugzilla.yoctoproject.org
[2]
https://bugzilla.yoctoproject.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&classification=Build%20System%20%26%20Metadata&list_id=156074&product=OE-Core&query_format=advanced&resolution=---&order=bug_id%20DESC&query_based_on=
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: bug scrub - RFC
2014-01-08 23:20 bug scrub - RFC Trevor Woerner
@ 2014-01-09 10:56 ` Jack Mitchell
2014-01-09 15:07 ` Trevor Woerner
0 siblings, 1 reply; 6+ messages in thread
From: Jack Mitchell @ 2014-01-09 10:56 UTC (permalink / raw)
To: openembedded-core
On 08/01/14 23:20, Trevor Woerner wrote:
> Hi everyone,
>
> This is a "Request For Comments" email regarding a "bug scrub" party the
> OE TSC would like to hold.
>
>
> background:
> It has been noticed that the number of bugs in the bugzilla[1] has been
> climbing; it would be nice to hold a "bug scrub" event to raise
> awareness of the bugzilla and hopefully get some issues resolved.
>
>
> questions:
> 1) Currently it has been suggested this should be a 2-day event, should
> these two days be during the week or over a weekend? In either case,
> which 2 days?
>
If it's two days long then why don't you do the best of both worlds and
have a Friday/Saturday or Sunday/Monday combination?
> 2) Since this is an OE event, should it focus only on OE bugs[2], or
> should it be generalized for any bug?
I don't think we should be limiting people to what they can work on
while "participating".
>
> 3) Should we create a sign-up sheet (wiki) to keep track of who is
> participating, and which issues are being looked at by whom?
>
> (anything else?)
I think maybe a "I will be there at some point for some amount of time"
column would be good, and maybe a place to register interest for certain
bugs or areas of code that need improvement.
>
>
> notes:
> 1) If you or the company for which you work uses OE/Yocto, please
> consider making this a company event and having/allowing the engineers
> (to) participate.
>
> 2) Even if you're not a recipe-, or a build-, or a python-wizard there
> are still many things you can do to contribute. Being able to reproduce
> a bug or reporting that a bug can't be reproduced can sometimes be quite
> helpful (sometimes this points to a host issue or to a bug's description
> not being descriptive enough). Sometimes a bug is stuck in the "needs
> info" stage which maybe you can provide.
People with different environments is always useful, either bleeding
edge or "very stable". Variety is the spice of life ;)
>
> 3) Can anyone think of way to help "get the word out"?
>
> 4) It would be cool to be able to provide incentives to help people get
> interested and contributing to knocking some bugs around. So if anyone
> (*cough* Intel) has any neat hardware (*cough* Galileo, Edison) they
> could offer as an incentive (or, conversely, if there's a board you'd
> like to see Yocto target) please see about making that happen.
>
A unified effort towards a "new trendy" board would be a fun goal, but I
worry that hardware teething issues would then eat up run of the mill
bug fixing time, handouts for participation however, (bug fixed/reviewed
by/tested by) would be a great idea.
>
> Thanks and best regards,
> Trevor
>
>
>
> [1] https://bugzilla.yoctoproject.org
> [2]
> https://bugzilla.yoctoproject.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&classification=Build%20System%20%26%20Metadata&list_id=156074&product=OE-Core&query_format=advanced&resolution=---&order=bug_id%20DESC&query_based_on=
>
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bug scrub - RFC
2014-01-09 10:56 ` Jack Mitchell
@ 2014-01-09 15:07 ` Trevor Woerner
2014-01-09 15:34 ` Otavio Salvador
2014-01-10 2:47 ` Philip Balister
0 siblings, 2 replies; 6+ messages in thread
From: Trevor Woerner @ 2014-01-09 15:07 UTC (permalink / raw)
To: openembedded-core
On 01/09/14 05:56, Jack Mitchell wrote:
> On 08/01/14 23:20, Trevor Woerner wrote:
>> questions:
>> 1) Currently it has been suggested this should be a 2-day event, should
>> these two days be during the week or over a weekend? In either case,
>> which 2 days?
>>
> If it's two days long then why don't you do the best of both worlds and
> have a Friday/Saturday or Sunday/Monday combination?
I was thinking of doing it either fully during the week, or fully on a
weekend since my feeling is that most people either work with OE/Yocto
during the weekdays or on the weekend. There's nothing to say we
couldn't run this "bug scrub" during the week, then run a second "bug
scrub" 2 months from now on a weekend (or visa versa).
>> 2) Since this is an OE event, should it focus only on OE bugs[2], or
>> should it be generalized for any bug?
> I don't think we should be limiting people to what they can work on
> while "participating".
Since this is an OE TSC event I didn't want any hard feelings ;-) I also
thought that maybe it would be easier to get people interested if this
"bug scrub" was targeted at a specific project. I thought there's a
chance it might help get people interested if we said "let's have a bug
event where we target these 30 bugs" instead of saying "there are 1000's
of bugs in the bugzilla, pick one and try to do something about it".
>> 4) It would be cool to be able to provide incentives to help people get
>> interested and contributing to knocking some bugs around. So if anyone
>> (*cough* Intel) has any neat hardware (*cough* Galileo, Edison) they
>> could offer as an incentive (or, conversely, if there's a board you'd
>> like to see Yocto target) please see about making that happen.
>>
> A unified effort towards a "new trendy" board would be a fun goal, but I
> worry that hardware teething issues would then eat up run of the mill
> bug fixing time, handouts for participation however, (bug fixed/reviewed
> by/tested by) would be a great idea.
>
Sorry, yes, this is what I meant.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bug scrub - RFC
2014-01-09 15:07 ` Trevor Woerner
@ 2014-01-09 15:34 ` Otavio Salvador
2014-01-09 15:38 ` Trevor Woerner
2014-01-10 2:47 ` Philip Balister
1 sibling, 1 reply; 6+ messages in thread
From: Otavio Salvador @ 2014-01-09 15:34 UTC (permalink / raw)
To: Trevor Woerner; +Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
On Thu, Jan 9, 2014 at 1:07 PM, Trevor Woerner <trevor.woerner@linaro.org>wrote:
> On 01/09/14 05:56, Jack Mitchell wrote:
> > On 08/01/14 23:20, Trevor Woerner wrote:
> >> questions:
> >> 1) Currently it has been suggested this should be a 2-day event, should
> >> these two days be during the week or over a weekend? In either case,
> >> which 2 days?
> >>
> > If it's two days long then why don't you do the best of both worlds and
> > have a Friday/Saturday or Sunday/Monday combination?
>
> I was thinking of doing it either fully during the week, or fully on a
> weekend since my feeling is that most people either work with OE/Yocto
> during the weekdays or on the weekend. There's nothing to say we
> couldn't run this "bug scrub" during the week, then run a second "bug
> scrub" 2 months from now on a weekend (or visa versa).
Maybe mix it, Friday, Saturday, Sunday, Monday.
So we give in a single 'event' opportunity to both.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
[-- Attachment #2: Type: text/html, Size: 1799 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bug scrub - RFC
2014-01-09 15:34 ` Otavio Salvador
@ 2014-01-09 15:38 ` Trevor Woerner
0 siblings, 0 replies; 6+ messages in thread
From: Trevor Woerner @ 2014-01-09 15:38 UTC (permalink / raw)
To: openembedded-core
On 01/09/14 10:34, Otavio Salvador wrote:
>
> On Thu, Jan 9, 2014 at 1:07 PM, Trevor Woerner
> <trevor.woerner@linaro.org <mailto:trevor.woerner@linaro.org>> wrote:
>
> On 01/09/14 05:56, Jack Mitchell wrote:
> > On 08/01/14 23:20, Trevor Woerner wrote:
> >> questions:
> >> 1) Currently it has been suggested this should be a 2-day
> event, should
> >> these two days be during the week or over a weekend? In either
> case,
> >> which 2 days?
> >>
> > If it's two days long then why don't you do the best of both
> worlds and
> > have a Friday/Saturday or Sunday/Monday combination?
>
> I was thinking of doing it either fully during the week, or fully on a
> weekend since my feeling is that most people either work with OE/Yocto
> during the weekdays or on the weekend. There's nothing to say we
> couldn't run this "bug scrub" during the week, then run a second "bug
> scrub" 2 months from now on a weekend (or visa versa).
>
>
> Maybe mix it, Friday, Saturday, Sunday, Monday.
>
> So we give in a single 'event' opportunity to both.
>
Okay, I can agree to that.
How about targeting next weekend (Jan 17-18 2014). Would that be too soon?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bug scrub - RFC
2014-01-09 15:07 ` Trevor Woerner
2014-01-09 15:34 ` Otavio Salvador
@ 2014-01-10 2:47 ` Philip Balister
1 sibling, 0 replies; 6+ messages in thread
From: Philip Balister @ 2014-01-10 2:47 UTC (permalink / raw)
To: Trevor Woerner; +Cc: openembedded-core
On 01/09/2014 10:07 AM, Trevor Woerner wrote:
> On 01/09/14 05:56, Jack Mitchell wrote:
>> On 08/01/14 23:20, Trevor Woerner wrote:
>>> questions:
>>> 1) Currently it has been suggested this should be a 2-day event, should
>>> these two days be during the week or over a weekend? In either case,
>>> which 2 days?
>>>
>> If it's two days long then why don't you do the best of both worlds and
>> have a Friday/Saturday or Sunday/Monday combination?
>
> I was thinking of doing it either fully during the week, or fully on a
> weekend since my feeling is that most people either work with OE/Yocto
> during the weekdays or on the weekend. There's nothing to say we
> couldn't run this "bug scrub" during the week, then run a second "bug
> scrub" 2 months from now on a weekend (or visa versa).
I'd suggest starting with a one day thing on a weekday so we can try and
get a critical mass of people in place over a shorter period. We can
always change things around based on how this works.
>
>>> 2) Since this is an OE event, should it focus only on OE bugs[2], or
>>> should it be generalized for any bug?
>> I don't think we should be limiting people to what they can work on
>> while "participating".
>
> Since this is an OE TSC event I didn't want any hard feelings ;-) I also
> thought that maybe it would be easier to get people interested if this
> "bug scrub" was targeted at a specific project. I thought there's a
> chance it might help get people interested if we said "let's have a bug
> event where we target these 30 bugs" instead of saying "there are 1000's
> of bugs in the bugzilla, pick one and try to do something about it".
>
Can someone make a bugzilla query that lists bugs that are good
candidates for a bug scrub. Ideally, things that are easy to resolve so
we can beat the numbers down,
Philip
>>> 4) It would be cool to be able to provide incentives to help people get
>>> interested and contributing to knocking some bugs around. So if anyone
>>> (*cough* Intel) has any neat hardware (*cough* Galileo, Edison) they
>>> could offer as an incentive (or, conversely, if there's a board you'd
>>> like to see Yocto target) please see about making that happen.
>>>
>> A unified effort towards a "new trendy" board would be a fun goal, but I
>> worry that hardware teething issues would then eat up run of the mill
>> bug fixing time, handouts for participation however, (bug fixed/reviewed
>> by/tested by) would be a great idea.
>>
> Sorry, yes, this is what I meant.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-01-10 2:47 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-08 23:20 bug scrub - RFC Trevor Woerner
2014-01-09 10:56 ` Jack Mitchell
2014-01-09 15:07 ` Trevor Woerner
2014-01-09 15:34 ` Otavio Salvador
2014-01-09 15:38 ` Trevor Woerner
2014-01-10 2:47 ` Philip Balister
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox