Go to: typo3.com Home TYPO3 Association Home typo3.org Home Certification FLOW3 Bugtracker Forge (Development Platform) News Buzz (TYPO3 Blogs) Wiki Mailing lists TYPO3 Snippets

Search:

TYPO3 Bug Day is simply one day a month when TYPO3 core developers are dedicated to foster TYPO3 community outreach.

It's a global 24 hours event, so join whenever you want or whenever it fits for you.

Absolutely!

Each Bug Day some core developers will be present in the IRC channel, you can ask them what to do and how to help. If you have general Bug Day related questions you can ask Ingo Renner.

We usually discuss the topic of a Bug Day together with the community members that join Bug Day in the IRC channel. If time permits or if the topic for a Bug Day is clear earlier we will also announce it through news and mailinglists.

The concept of a Bug Dday isn't really new, many other Open Source projects do that, too. Ingo Renner and Benjamin Mack started the Bug Day idea within the TYPO3 community.

If you have the code foo so to speak, you can pick through bugs that have been specially selected for TYPO3 Bug Day (they have a special tag for the running Bug Day f.e. bugday-0806 for the June '08 Bug Day) and assign it to yourself on the Bug Day's wiki page. Once this is done, you claim the bug for yourself and can ask help from a developer via the bug or talk to them directly on IRC.

There are a couple things. First, if you contribute a patch that gets included in a release, you will be listed in TYPO3's ChangeLog. This means that YOUR code will be included in the next release of the project (along with proper attribution of course!). Furthermore, you get to build relations with the core developers of the project you're donating your time to. Besides you also get the feel good feeling of contributing to open-source, right :)?

The first step is to find bugs that you're interested in doing for Bug Day. These bugs are marked with the general tag bugday or a specific bugday-YYMM tag and are conveniently linked from a respective bugday page (find one on the main BugDay page). Once you have bugs you're interested in, (a) let the person who reported the bug know by commenting on it, and more importantly (if you're a developer), (b) post your name and bugs you will be doing for Bug Day on the Bug Day's page.

Once that's done, go to IRC (#typo3-bugday) on the day of Bug Day and get help from other people there.

In general every Bug Day should have a certain topic of bugs that we try to focus on. However any bug fixes are of course welcome!

There's plenty of opportunity to participate if you're not a developer! There are TYPO3 bugs out there that need help with triage (see the question below) or if you're good with artwork, there's bugs out there that need help with art!

Programming skills might help you fix particular bugs, but triaging most bugs will not require any programming knowledge. Bug triaging is a great way for people who do not know anything about programming to return something to the TYPO3 community. To get started with triaging a bug, simply go to the TYPO3 Bug Day page:

• find the current Bug Day
• check whether the description for a bug is precise, complete, and understandable
• check whether the bug and/or its description is maybe out of date
• check whether you can reproduce the bug with the latest stable and maybe also old stable versions of TYPO3
• leave a comment about your findings
• complete the description for a bug if necessary
• update a bug's information directly if you have the rights to do so

A web browser (like Firefox) and the latest stable version of TYPO3 should suffice (note that some bugs may be tied to specific TYPO3 versions, but those can be considered more advanced).

I assume as an over-worked TYPO3 core developer with little free-time, bugs tend to languish in the inbox without some coordinated effort to keep up with them. Bug Days help keep bug-fixing on the radar and provide a great lightweight opportunity for contributors to help. Also, the community is given an opportunity to get to know core developers via triage and bug fixing!

Make sure to tag bugs ("bugday" or "community task") you think are reasonable for new contributors.

Also, make sure to update the respective wiki page for the current bug day if your'e participating.

On actual bug days, please hang out on IRC (#typo3-bugday) to help contributors! If you don't want to, that's ok, it's still possible to work with contributors via bug reports.

Sure! It's possible to help new contributors and users on IRC (#typo3-bugday).

Follow the contribution workflow described in the TYPO3 wiki.