Hey guys,
A few days ago, we were looking at the metrics for open issues on our
bug tracker. The summary is, there are a lot 
Many of these are
probably old, but many will still be valid, and many require certain
configurations to test the issue.
So, we thought we'd try and organise a community bug hunt, and either
close or reproduce & update as many bugs as we can in one go. To do
this we need to start thinking about a few things, so I'm opening it
up to you guys to have your say (with my own thoughts as well):
-
How long should the event be?
A lot of us work in different timezones, so 4 hours? 12 hours? a
whole 24 hours (probably too much :P)?
-
When shall we organise it for?
I'm thinking about a month from now…
-
How shall we divide up the work?
I think we'll want to use IRC as the primary communication channel,
but we could start a Google+ hangout too, just for fun and chat
We'll probably need some kind of real-time page where people can say
which bugs they're checking out, and a tag to give to bugs which have
already been tested. That way we don't duplicate effort.
Anything else?
Your input is appreciated - let's make this awesome 
Cheers,
Greg
If we have enough community members spread about, 24 hours may not be a bad
thing - we'd just need to do it in "shifts" - ie. ohad & the gang for X
hours during their day would supervise, someone like bgupta (if he's
willing) could handle US East Coast hours, some of us on the US west coast
could do the same, etc - this would give us an opportunity for the global
foreman community to contribute, while still letting you guys get some
rest
That said, I'm open to criticism on this front. Regardless, I think a
hackathon/bug-smash event is a fantastic idea.
-torrancew
···
On Thu, Oct 25, 2012 at 06:02:42PM +0100, Greg Sutcliffe wrote:
> Hey guys,
>
> A few days ago, we were looking at the metrics for open issues on our
> bug tracker. The summary is, there are a lot ;) Many of these are
> probably old, but many will still be valid, and many require certain
> configurations to test the issue.
>
> So, we thought we'd try and organise a community bug hunt, and either
> close or reproduce & update as many bugs as we can in one go. To do
> this we need to start thinking about a few things, so I'm opening it
> up to you guys to have your say (with my own thoughts as well):
>
> 1) How long should the event be?
> A lot of us work in different timezones, so 4 hours? 12 hours? a
> whole 24 hours (probably too much :P)?
>
> 2) When shall we organise it for?
> I'm thinking about a month from now...
>
> 3) How shall we divide up the work?
> I think we'll want to use IRC as the primary communication channel,
> but we could start a Google+ hangout too, just for fun and chat
> We'll probably need some kind of real-time page where people can say
> which bugs they're checking out, and a tag to give to bugs which have
> already been tested. That way we don't duplicate effort.
>
> Anything else?
>
> Your input is appreciated - let's make this awesome :)
>
> Cheers,
> Greg
>
I can cover EST through PST since I'm usually online pretty late.
Big +1 from me about setting up a document to track what different
people are working on. I also think we should pre-populate it with bugs
and associated difficulty so newbies can dive in quickly even if they
haven't looked at the code base before.
What are you thinking about for dates?
Thanks for putting this together! Looking forward to knocking out lots
of bugs
-S
···
On 10/25/2012 01:15 PM, Tray Torrance wrote:
> If we have enough community members spread about, 24 hours may not be a bad
> thing - we'd just need to do it in "shifts" - ie. ohad & the gang for X
> hours during their day would supervise, someone like bgupta (if he's
> willing) could handle US East Coast hours, some of us on the US west coast
> could do the same, etc - this would give us an opportunity for the global
> foreman community to contribute, while still letting you guys get some
> rest ;)
>
> That said, I'm open to criticism on this front. Regardless, I think a
> hackathon/bug-smash event is a fantastic idea.
>
> -torrancew
>
> On Thu, Oct 25, 2012 at 06:02:42PM +0100, Greg Sutcliffe wrote:
>> Hey guys,
>>
>> A few days ago, we were looking at the metrics for open issues on our
>> bug tracker. The summary is, there are a lot ;) Many of these are
>> probably old, but many will still be valid, and many require certain
>> configurations to test the issue.
>>
>> So, we thought we'd try and organise a community bug hunt, and either
>> close or reproduce & update as many bugs as we can in one go. To do
>> this we need to start thinking about a few things, so I'm opening it
>> up to you guys to have your say (with my own thoughts as well):
>>
>> 1) How long should the event be?
>> A lot of us work in different timezones, so 4 hours? 12 hours? a
>> whole 24 hours (probably too much :P)?
>>
>> 2) When shall we organise it for?
>> I'm thinking about a month from now...
>>
>> 3) How shall we divide up the work?
>> I think we'll want to use IRC as the primary communication channel,
>> but we could start a Google+ hangout too, just for fun and chat
>> We'll probably need some kind of real-time page where people can say
>> which bugs they're checking out, and a tag to give to bugs which have
>> already been tested. That way we don't duplicate effort.
>>
>> Anything else?
>>
>> Your input is appreciated - let's make this awesome :)
>>
>> Cheers,
>> Greg
>>
Random thought sorry if stupid: Assign the bugs in Redmine. Create a
version for this game day and target them for it?
···
On 25 Oct 2012 19:02, "Greg Sutcliffe" wrote:
Hey guys,
A few days ago, we were looking at the metrics for open issues on our
bug tracker. The summary is, there are a lot Many of these are
probably old, but many will still be valid, and many require certain
configurations to test the issue.
So, we thought we’d try and organise a community bug hunt, and either
close or reproduce & update as many bugs as we can in one go. To do
this we need to start thinking about a few things, so I’m opening it
up to you guys to have your say (with my own thoughts as well):
-
How long should the event be?
A lot of us work in different timezones, so 4 hours? 12 hours? a
whole 24 hours (probably too much :P)?
-
When shall we organise it for?
I’m thinking about a month from now…
-
How shall we divide up the work?
I think we’ll want to use IRC as the primary communication channel,
but we could start a Google+ hangout too, just for fun and chat
We’ll probably need some kind of real-time page where people can say
which bugs they’re checking out, and a tag to give to bugs which have
already been tested. That way we don’t duplicate effort.
Anything else?
Your input is appreciated - let’s make this awesome
Cheers,
Greg
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
That sounds good, especially because then we can move all the fixes
from the bug fix version to 1.1.
-S
···
On Thu 25 Oct 2012 03:18:52 PM EDT, Mikael Fridh wrote:
> Random thought sorry if stupid: Assign the bugs in Redmine. Create a
> version for this game day and target them for it?
>
> On 25 Oct 2012 19:02, "Greg Sutcliffe" > wrote:
>
> Hey guys,
>
> A few days ago, we were looking at the metrics for open issues on our
> bug tracker. The summary is, there are a lot ;) Many of these are
> probably old, but many will still be valid, and many require certain
> configurations to test the issue.
>
> So, we thought we'd try and organise a community bug hunt, and either
> close or reproduce & update as many bugs as we can in one go. To do
> this we need to start thinking about a few things, so I'm opening it
> up to you guys to have your say (with my own thoughts as well):
>
> 1) How long should the event be?
> A lot of us work in different timezones, so 4 hours? 12 hours? a
> whole 24 hours (probably too much :P)?
>
> 2) When shall we organise it for?
> I'm thinking about a month from now...
>
> 3) How shall we divide up the work?
> I think we'll want to use IRC as the primary communication channel,
> but we could start a Google+ hangout too, just for fun and chat
> We'll probably need some kind of real-time page where people can say
> which bugs they're checking out, and a tag to give to bugs which have
> already been tested. That way we don't duplicate effort.
>
> Anything else?
>
> Your input is appreciated - let's make this awesome :)
>
> Cheers,
> Greg
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To post to this group, send email to
> foreman-users@googlegroups.com
> .
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
> Random thought sorry if stupid: Assign the bugs in Redmine. Create a version
> for this game day and target them for it?
+1 on that.
> If we have enough community members spread about, 24 hours may not be a bad
> thing - we'd just need to do it in "shifts" - ie. ohad & the gang for X
The Asia timezones may be difficult to cover - might be an early start
for Ohad Still, I agree with your thinking, that's why I put 24
hours down as possible.
···
On 25 October 2012 20:18, Mikael Fridh wrote:
On 25 October 2012 18:15, Tray Torrance wrote:
On 25 October 2012 18:50, Sam Kottler skottler@redhat.com wrote:
What are you thinking about for dates?
My guess would be around the end of November - I know Thanksgiving is
around then, but it seems like about the right timeframe.
Can we regionalize this? Anybody else in Portland want to meet up for this event and work side by side?
Thanks,
Corey Osman
corey@logicminds.biz
Green IT and Data Center Automation Specialist
···
On Oct 26, 2012, at 3:12 AM, Greg Sutcliffe wrote:
On 25 October 2012 20:18, Mikael Fridh frimik@gmail.com wrote:
Random thought sorry if stupid: Assign the bugs in Redmine. Create a version
for this game day and target them for it?
+1 on that.
On 25 October 2012 18:15, Tray Torrance foreman_bugs@warrentorrance.com wrote:
If we have enough community members spread about, 24 hours may not be a bad
thing - we’d just need to do it in “shifts” - ie. ohad & the gang for X
The Asia timezones may be difficult to cover - might be an early start
for Ohad Still, I agree with your thinking, that’s why I put 24
hours down as possible.
On 25 October 2012 18:50, Sam Kottler skottler@redhat.com wrote:
What are you thinking about for dates?
My guess would be around the end of November - I know Thanksgiving is
around then, but it seems like about the right timeframe.
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.
Not sure what you mean by regionalize - meetups sound cool though I
think we'll still want to use the #theforeman channel as big part of
the communication.
I think the big question we need to resolve is when. Do people prefer
weekdays or weekends? Once we've resolved that we can start proposing
some dates.
Greg
···
On 26 October 2012 19:25, Corey Osman wrote:
> Can we regionalize this? Anybody else in Portland want to meet up for this
> event and work side by side?
This is a very good idea.
Maybe before this event we could look at our own ( bugs / features
request that are
open and maybe not still valid. (I have some of my own …)
Would love to participate to that event !
Romain
···
On 10/26/2012 08:25 PM, Corey Osman wrote:
> Can we regionalize this? Anybody else in Portland want to meet up for
> this event and work side by side?
>
>
> Thanks,
>
> Corey Osman
> corey@logicminds.biz
>
> Green IT and Data Center Automation Specialist
>
>
>
>
>
>
> On Oct 26, 2012, at 3:12 AM, Greg Sutcliffe > wrote:
>
>> On 25 October 2012 20:18, Mikael Fridh > > wrote:
>>> Random thought sorry if stupid: Assign the bugs in Redmine. Create a
>>> version
>>> for this game day and target them for it?
>>
>> +1 on that.
>>
>> On 25 October 2012 18:15, Tray Torrance >> > > wrote:
>>> If we have enough community members spread about, 24 hours may not
>>> be a bad
>>> thing - we'd just need to do it in "shifts" - ie. ohad & the gang for X
>>
>> The Asia timezones may be difficult to cover - might be an early start
>> for Ohad ;) Still, I agree with your thinking, that's why I put 24
>> hours down as possible.
>>
>> On 25 October 2012 18:50, Sam Kottler > > wrote:
>>> What are you thinking about for dates?
>>
>> My guess would be around the end of November - I know Thanksgiving is
>> around then, but it seems like about the right timeframe.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
What do people think about November 15? I know it's earlier than had
originally been talked about, but the end of November tends to be bad
in the US because of Thanksgiving; tons of people travel during that
time.
···
On Tue 30 Oct 2012 09:32:06 AM EDT, Greg Sutcliffe wrote:
> On 26 October 2012 19:25, Corey Osman wrote:
>> Can we regionalize this? Anybody else in Portland want to meet up for this
>> event and work side by side?
>
> Not sure what you mean by regionalize - meetups sound cool though :) I
> think we'll still want to use the #theforeman channel as big part of
> the communication.
>
> I think the big question we need to resolve is when. Do people prefer
> weekdays or weekends? Once we've resolved that we can start proposing
> some dates.
>
> Greg
I'm free then, but is that enough time to get the word around and to
do some prep cleanup?
Greg
···
On 30 October 2012 13:35, Sam Kottler wrote:
> What do people think about November 15? I know it's earlier than had
> originally been talked about, but the end of November tends to be bad in the
> US because of Thanksgiving; tons of people travel during that time.
The 15th works for me, but the weekend after US Thanksgiving doesn't - I
have an all-day, on-site maintenance that Saturday, and will be behind some
servers for a few hours
-torrancew
···
On Tue, Oct 30, 2012 at 02:31:31PM +0000, Greg Sutcliffe wrote:
> On 30 October 2012 13:35, Sam Kottler wrote:
> > What do people think about November 15? I know it's earlier than had
> > originally been talked about, but the end of November tends to be bad in the
> > US because of Thanksgiving; tons of people travel during that time.
>
> I'm free then, but is that enough time to get the word around and to
> do some prep cleanup?
>
> Greg
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.
>
My vote is for a weekend day. However, please don't let my vote be a
deciding factor, as I might still be able to participate in the
evening. If we do a weekend, we might be able to have some NYC folks
over to my place if it helps with coordination.
-Brian
···
On Tue, Oct 30, 2012 at 10:31 AM, Greg Sutcliffe wrote:
> On 30 October 2012 13:35, Sam Kottler wrote:
>> What do people think about November 15? I know it's earlier than had
>> originally been talked about, but the end of November tends to be bad in the
>> US because of Thanksgiving; tons of people travel during that time.
>
> I'm free then, but is that enough time to get the word around and to
> do some prep cleanup?
>
> Greg
Ok, it's been a week with no further input, so lets make a decision.
We propose an all day bug squashing even on the 15th November (1 week
today). We'll do a bug-scrub before Thursday, and tag all the bugs that
need looking at with #bugday. We'll have at least one or two co-ordinators
on IRC, so you have to do is show up on IRC, pick an unassigned bug from
the #bugday list, and tell us that you're going to reproduce it/fix
it/whatever with it. Then assign the bug to yourself, and you can go from
there. Once done, update the bug with the status and pick another one.
At least some of the foreman team should be around from around 7am GMT to
midnight GMT. That gives us 17 hours of bug squashing awesomeness. And we
might even help you guys too
Side notes:
If you don't already have one, create an account on http://theforeman.org.
We'll be online during the bug event, of course, so we can help if there
are any Redmine issues.
IRC (#theforeman) will be the main communication channel, but I'm certainly
planning to hangout on Google+ too. See you there
I should personally be about from ~10am GMT to ~7pm GMT, but I may well be
online well into the evening.
