Hack-a-thon 2013: Difference between revisions

Revision as of 07:44, 24 January 2013

Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.

Start Date	8 April 2013
End Date	21 January 2013

What is a Moodle Hack-a-thon?

A Hack-a-thon is a period of intense community contribution to the Moodle project. Participants are rewarded for their involvement. There is a competitive aspect to the Hack-a-thon to encourage greater involvement.

Categories of work

The following categories are specifically targeted as areas of work for the Hack-a-thon.

Bugs patched

This category is for the most bugs resolved.

There are two groups in this category, each with separate prize pools.

Recognised developers (in the jira-developers Tracker group)
New developers (not in the jira-developers group)

Moodle HQ employees are excluded from competing.

Points	5 points for every bug + 1 point for every VOTE on that bug (so vote for your favourite bugs!) + 2 points for fixing on all supported branches
Reporting	Participants should add themselves and links to their issues to Hack-a-thon_2013/Bugs_resolved. Participants should provide Git branches on the issue.
Verification	Each reported fix will be reviewed by an authorised developer. Fixes may be allowed minor fixes after reviewing.
T-shirt standard	1 verified bug fix

Dud issues identified

A dud issue is one that is open, but should be closed, for one of the following reasons.

It is a duplicate of another issue in the tracker (either a pre-existing issue or an active issue reported later; the point is that we end up closing one).
It was an issue that has been fixed in current versions.
It is an issue that has become obsolete because of changes present in current versions.
It is not able to be replicated in any reasonable supported environment.

Points	3 points per identified issue (1 point for each additional duplicate after the first)
Reporting	Participants should add themselves and links to their issues to Hack-a-thon_2013/Dud_issues_closed. Participants should comment on each issue they report.
Verification	Each reported issue will be checked and closed by authorised person.
T-shirt standard	3 issues identified and verified as duds

Docs updated

Most Moodle Docs or Moodle Dev Docs pages updated

Dev docs and User docs

Points	??? 1 point for each paragraph edited ???
Reporting	Participants should add themselves and links to their updates to Hack-a-thon_2013/Docs_updated
Verification	???
T-shirt standard	???

Plugins updated

Most Contributed plugins updated

Points	???
Reporting	Participants should add themselves and links to their plugins to Hack-a-thon_2013/Plugins_updated
Verification	???
T-shirt standard	???

Prizes and recognition

Each participant who fulfils the minimum t-shirt standard will receive a limited edition Hack-a-thon t-shirt.

Cash prizes will be awarded for each category (including two prizes for bug fixing). Prizes will be awarded as follows.

First prize	AU$200
Second prize	AU$100
Third prize	AU$50

Cash prizes will be paid via Paypal.

Winners in each category will be named in a news item on moodle.org, a feature story on moodle.com and recorded here in the Docs.

The judges decision is final. We reserve the right to disqualify someone if it becomes obvious they are cheating the system (eg. by filing fake reports, setting up fake accounts, reassigning bugs from other people after they are done etc.).

@@ Line 1: / Line 1: @@
 {{Work in progress}}
+{| class="nicetable"
+|-
+! Start Date
+| 8 April 2013
+|-
+! End Date
+| 21 January 2013
+|}
 ==What is a Moodle Hack-a-thon?==
-A Hack-a-thon is a period of intense community contribution to the Moodle project. Participants are rewarded for their involvement and there is an opportunity for others in the community to sponsor such contributions. There is a competitive aspect to the Hack-a-thon to encourage greater involvement.
+A Hack-a-thon is a period of intense community contribution to the Moodle project. Participants are rewarded for their involvement. There is a competitive aspect to the Hack-a-thon to encourage greater involvement.
+==Categories of work==
+The following categories are specifically targeted as areas of work for the Hack-a-thon.
+===Bugs patched===
+This category is for the most bugs resolved.
+There are two groups in this category, each with separate prize pools.
+* Recognised developers (in the [[Tracker#Tracker_groups_and_permissions|jira-developers]] Tracker group)
+* New developers (not in the [[Tracker#Tracker_groups_and_permissions|jira-developers]] group)
+Moodle HQ employees are excluded from competing.
+{| class="nicetable"
+|-
+! Points
+| 5 points for every bug + 1 point for every VOTE on that bug (so vote for your favourite bugs!) + 2 points for fixing on all supported branches
+|-
+! Reporting
+| Participants should add themselves and links to their issues to [[Hack-a-thon_2013/Bugs_resolved]]. Participants should provide Git branches on the issue.
+|-
+! Verification
+| Each reported fix will be reviewed by an authorised developer. Fixes may be allowed minor fixes after reviewing.
+|-
+! T-shirt standard
+| 1 verified bug fix
+|}
+===Dud issues identified===
+A [http://en.wikipedia.org/wiki/Dud dud] issue is one that is open, but should be closed, for one of the following reasons.
+* It is a duplicate of another issue in the tracker (either a pre-existing issue or an active issue reported later; the point is that we end up closing one).
+* It was an issue that has been fixed in current versions.
+* It is an issue that has become obsolete because of changes present in current versions.
+* It is not able to be replicated in any reasonable supported environment.
+{| class="nicetable"
+|-
+! Points
+| 3 points per identified issue (1 point for each additional duplicate after the first)
+|-
+! Reporting
+| Participants should add themselves and links to their issues to [[Hack-a-thon_2013/Dud_issues_closed]]. Participants should comment on each issue they report.
+|-
+! Verification
+| Each reported issue will be checked and closed by authorised person.
+|-
+! T-shirt standard
+| 3 issues identified and verified as duds
+|}
-==Areas of work==
+===Docs updated===
-The following areas may be specifically targeted as areas of work for the Hack-a-thon.
-* Most bugs resolved, in two groups
-** Recognised developers (in the [[Tracker#Tracker_groups_and_permissions|jira-developers]] Tracker group), excluding Moodle HQ employees
-** New developers (not in that group)
-* Most incorrectly open issues identified (duplicates, fixed, obsolete, not replicable)
 * Most Moodle Docs or Moodle Dev Docs pages updated
+Dev docs and User docs
+{| class="nicetable"
+|-
+! Points
+| ??? 1 point for each paragraph edited ???
+|-
+! Reporting
+| Participants should add themselves and links to their updates to [[Hack-a-thon_2013/Docs_updated]]
+|-
+! Verification
+| ???
+|-
+! T-shirt standard
+| ???
+|}
+===Plugins updated===
 * Most Contributed plugins updated
-==Prizes==
+{| class="nicetable"
+|-
+! Points
+| ???
+|-
+! Reporting
+| Participants should add themselves and links to their plugins to [[Hack-a-thon_2013/Plugins_updated]]
+|-
+! Verification
+| ???
+|-
+! T-shirt standard
+| ???
+|}
+==Prizes and recognition==
+Each participant who fulfils the minimum t-shirt standard will receive a limited edition Hack-a-thon t-shirt.
+Cash prizes will be awarded for each category (including two prizes for bug fixing). Prizes will be awarded as follows.
+{| class="nicetable"
+|-
+| First prize
+| AU$200
+|-
+| Second prize
+| AU$100
+|-
+| Third prize
+| AU$50
+|}
+Cash prizes will be paid via Paypal.
-Prizes might be cash, provided we can get sponsorship. There might be physical prizes or credit to Amazon, Paypal, etc.
+Winners in each category will be named in a news item on moodle.org, a feature story on moodle.com and recorded here in the Docs.
-The judges decision is final.We reserve the right to disqualify someone if it becomes obvious they are cheating the system (eg. by filing fake reports, setting up fake accounts, reassigning bugs from other people after they are done etc.).
+The judges decision is final. We reserve the right to disqualify someone if it becomes obvious they are cheating the system (eg. by filing fake reports, setting up fake accounts, reassigning bugs from other people after they are done etc.).
-==Sponsorship==
+==See also...==
-Prior to the Hack-a-thon we might get people to contribute to the Hack-a-thon effort by raising funds that can be used as prizes.
+* [[Bugathon]] 2007

Documentation