[TYPO3-dev] The future of Bug Days

[Georg Ringer]

Hi Francois,

1st of all: Thanks a lot for your work and also for this thread.

It is long time ago since I attended one of those bugdays. My reasons 
for kind of quitting are simple: There was no advantage for me fixing 
bugs on this bug day. I still fix many of those bugs but I can do it 
when I got the time for it and when I want to.

I completly agree with your impression about the routine. Having fun 
while doing routine work is very hard!

IMO first of all it is important to know what the target of those bug 
days are because there could be some different ones:
- Is it important to have some brains together and solve issues together 
=> so more of getting things done as core team
- Get some new people to fix bugs and help those => so more a community 
thing and fixing really bugs is not that important.
- How important is it to have real life meetings for that?
- ... ?

The collected ideas sound very nice, still some personal opinions:

> - companys should be mentioned, that they set their developers free for
> the bug days

It is hard for me to have on special days for special times a free time.

> - Hosted bugdays: Maybe they should be revived, was fun and a good
> motivator, yet more organisational overhead

sounds nice, but still got the problem that it is too far away for me 
and I won't travel for a half day to the other end of Germany or wherever.

> - Idea: Arrange bug days / coding nights during TYPO3 Camps

This sounds very nice and would be also good for new ones to start.

> - maybe move bugday communication to big blue button as well

yeah, IRC is also not allowed in every network

> with an open channel for the whole day and a real voice meeting after
> lunch time (makes sense when people can leave normal work a bit earlier
> on Friday and use their afternoon)

I don't like the fridays too much because it is already weekend and 
usually it is time to turn the computer off for at least some ours.

> - lower the frequency, but make it a bug-fixing period rather than a
> single day.

+1

> My idea would be to do something over an extended week-end,
> starting on Friday and ending on Sunday. This would allow more people to
> participate. We would arrange those sprints so that as many Core Team
> members as possible are available.

IMO then it is important to have some bugs already prepared which can be 
fixed. Otherwise everyone just does his own thing - with the difference 
that bigbluebutton is opend in one of the tabs.

And an own idea:
What about ask the community / companies about their Gremlins? In many 
cases we core devs don't see the issues of others and some of them will 
be really simple to solve. This would also improve the chance that:
- the one who reported the bug is online too for giving feedback, 
testing something
- maybe a sponsorship or hosting the whole thing
- remove those gremlins which annoy people since 3.6

Georg