Contribute/Bugsquad - Revision history

Dcambie: /* Bug Weeks */ hide outdated info

2013-04-02T15:23:08Z

‎Bug Weeks: hide outdated info

Freininghaus: /* Bug Weeks */ Remove end date of Dolphin BugWeeks. It was actually planned for more than one week from the very beginning.

2012-11-01T18:09:39Z

‎Bug Weeks: Remove end date of Dolphin BugWeeks. It was actually planned for more than one week from the very beginning.

Gallaecio at 18:28, 25 October 2012

2012-10-25T18:28:27Z

Gallaecio: /* Bug Days */ Hiding the NextBugDay line, at least until there a future one.

2012-10-25T18:05:17Z

‎Bug Days: Hiding the NextBugDay line, at least until there a future one.

Agateau: /* Articles */ typo--

2012-07-27T13:41:39Z

‎Articles: typo--

Agateau: /* Articles */ Add link to Extra Mile initiative

2012-07-27T13:41:23Z

‎Articles: Add link to Extra Mile initiative

DarioAndres at 14:18, 19 December 2010

2010-12-19T14:18:59Z

Lemma: /* Bug Days */

2010-10-11T16:01:02Z

‎Bug Days

Lemma: /* Bug Days */

2010-10-11T16:00:05Z

‎Bug Days

DarioAndres: /* How to help */

2010-05-22T13:42:50Z

‎How to help

@@ Line 30: / Line 30: @@
 ===Bug Weeks===
-As an alternative to Bug Days, there are also meetings that take one week. The workflow is based on the [http://forum.kde.org/viewforum.php?f=148 KDE Community Forums]. [http://forum.kde.org/viewtopic.php?f=4&t=84473 More information →]
+As an alternative to Bug Days, there are also meetings that take one week. The workflow is based on the [http://forum.kde.org/viewforum.php?f=148 KDE Community Forums]. [http://forum.kde.org/viewtopic.php?f=4&t=84473 More information →]<!--
 The following Bug Weeks are currently scheduled:
 ;[[/BugDays/Dolphin2012|Dolphin 2012]]
-:'''Date:''' Starting October 25th, 2012
+:'''Date:''' Starting October 25th, 2012-->
 ==How to help==

@@ Line 35: / Line 35: @@
 ;[[/BugDays/Dolphin2012|Dolphin 2012]]
-:'''Date:''' October 25th - 31st, 2012
+:'''Date:''' Starting October 25th, 2012
 ==How to help==

@@ Line 7: / Line 7: @@
 You do not need any programming knowledge to be in the Bugsquad, and it is a great way to give practical support to the KDE community. If you are just starting to learn programming, it is a great way to gain familiarity with the components.
-==Bug Days==
+==Bug Meetings==
-We have regular days where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla cleaning day.<!--
+We celebrate ''bug meetings'' where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla-cleaning meeting.
-{{:Contribute/Bugsquad/NextBugDay}}-->
+The results of all past bug meetings can be found [[/BugDays|here]].
-[[:Contribute/Bugsquad/OrganizingABugDay|How to organize a BugDay]].
+{{note|Meetings are nice, but don't hesitate to join us at '''#kde-bugs''' on irc.freenode.net ''at any time''. We have plenty for you to do. ;) Check the topic to see what we are currently working on. And if you are new, please read some of the [[#Articles|articles below]] to get on your feet.}}
-The results of all past bug days can be found [[/BugDays|here]].
+===Bug Days===
-===Bug Weeks===
+When these meetings are 24-hours long, we call them ''Bug Days''. They are usually organized live through IRC — '''#kde-bugs''' on ''irc.freenode.net''.<!--
-Our team has recently launched a new iniciative named "Bug Weeks", as an evolution of the traditional BugDays. All the workflow is based on the [http://forum.kde.org/ KDE Community Forums].
+The following Bug Days are currently scheduled:
-You can find more information about it at [http://forum.kde.org/viewtopic.php?f=4&t=84473 its official announcement]
+As an alternative to Bug Days, there are also meetings that take one week. The workflow is based on the [http://forum.kde.org/viewforum.php?f=148 KDE Community Forums]. [http://forum.kde.org/viewtopic.php?f=4&t=84473 More information →]
-The first bugweek was about triaging Plasma Desktop bug reports. You can find more information in the [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek Session 0 article]. (A summary article is yet to come)
+The following Bug Weeks are currently scheduled:
-{{note|We don't just do bugs on BugDays! Don't hesitate to join us at '''#kde-bugs''' on irc.freenode.net, we have plenty for you to do. ;) Check the topic to see what we are currently working on. And if you are new, please read the "how to triage bugs" page.}}
+;[[/BugDays/Dolphin2012|Dolphin 2012]]
 ==How to help==

@@ Line 9: / Line 9: @@
 ==Bug Days==
-We have regular days where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla cleaning day.
+We have regular days where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla cleaning day.<!--
-{{:Contribute/Bugsquad/NextBugDay}}
+{{:Contribute/Bugsquad/NextBugDay}}-->
-[[:Contribute/Bugsquad/OrganizingABugDay|How to organize a BugDay]]
+[[:Contribute/Bugsquad/OrganizingABugDay|How to organize a BugDay]].
 The results of all past bug days can be found [[/BugDays|here]].

@@ Line 59: / Line 59: @@
 * [[/Guide_To_BugTriaging|Dario's Guide to Bug Triaging]] - Extensive guide on how to perform bug triagers tasks
-* [[/Quick_Introduction_to_Bugzilla|Quick introduction to Bugzilla]] - This article explains the basics about the bugtracking software that KDE uses: "Bugzilla". It includes the description of a bug reports fields and the workflow of most common tasks like searching into the databse.
+* [[/Quick_Introduction_to_Bugzilla|Quick introduction to Bugzilla]] - This article explains the basics about the bugtracking software that KDE uses: "Bugzilla". It includes the description of a bug reports fields and the workflow of most common tasks like searching into the database.
 * [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle] - This article describes the possible status of a bug report and when each should be used.

← Older revision		Revision as of 13:41, 27 July 2012
Line 72:		Line 72:

	* [[User:DarioAndres/Basic_Guide_about_Crash_Reporting\|Basic guide about crash reports]] - This article is a basic/simplified version of the previous one.		* [[User:DarioAndres/Basic_Guide_about_Crash_Reporting\|Basic guide about crash reports]] - This article is a basic/simplified version of the previous one.
		+
		+	* [http://community.kde.org/Getinvolved/Extra_Mile Extra Mile] - This article presents the Extra Mile initiative, whose goal is to help KDE applications and workspaces "walk the extra mile". The Extra Mile initiative uses Bugzilla to track extra mile bugs.

	==External links==		==External links==

← Older revision		Revision as of 14:18, 19 December 2010
Line 78:		Line 78:
	*[https://mail.kde.org/mailman/listinfo/bugsquad Subscribe to our mailinglist]		*[https://mail.kde.org/mailman/listinfo/bugsquad Subscribe to our mailinglist]
	*[http://forum.kde.org/viewforum.php?f=148 BugWeeks subforum]		*[http://forum.kde.org/viewforum.php?f=148 BugWeeks subforum]
		+	*[http://gitweb.kde.org/scratch/darioandres/bugsquad.git DarioAndres BugSquad GIT repo with useful scripts (including the batch generation for events)]

← Older revision		Revision as of 16:00, 11 October 2010
Line 12:		Line 12:

	{{:Contribute/Bugsquad/NextBugDay}}		{{:Contribute/Bugsquad/NextBugDay}}
		+
		+	{{:Contribute/Bugsquad/OrganizingABugDay}}

	The results of all past bug days can be found [[/BugDays\|here]].		The results of all past bug days can be found [[/BugDays\|here]].

@@ Line 26: / Line 26: @@
 ==How to help==
 Read the [[/Guide|guide]] and join us for one of our [[#Bug_Days|bug days]] or [[#Bug_Weeks|bug weeks]]. We meet on IRC in the #kde-bugs channel on irc.freenode.org. You can easily get started by having your questions answered there, and having someone guide you as to general bug triaging philosophy. Someone in IRC will usually be able to help you. Although we do sleep sometimes!
 A summary of the BugSquad guide is provided below to give you a quick idea of how you can help: