Change Details

**Type of activity:** Talk **Main topic:** Drawing in new MW developers with Hackathons, and then what == The problem == I had been running couple of Hackathons myself with University students, and the code contributions it produce duringt the Hackathon hours are just great - like there were days when we had like 5-8 patches in Gerrit in less than 8 hours. The funny thing is, right after the hackathon, people just forget about the same, and there are not any more contributions are follow up on the same. Ther are exceptional cases, but its percentage is far low than average. This is a general problem with any technical community, but Wikimedia Foundation needs to take care of this, as: # University students are prospective Google Summer of Code or Outreachy interns, so there is a chance for finding some long term developers there. # The number of Google Summer of Code selects and valid applicants are reducing as per https://www.mediawiki.org/wiki/User:MaxSem/GSoC_analysis. == Expected outcome == I would like to talk and find ideas about: * Running a Mediawiki code contribution drive/hackathon (from my experiences) * Statistics of recent hackathoins, how productive are they, in general. * What happens after the hackathon, * What kind of tracking or later annoucements should be done, etc * Should we stick on to some tracking tools or something, specially for the Hackahtons (or something like that) == Current status of the discussion == ... == Links == * ... PS: Sadly, the author @01tonythomas might not be present during the event, and if someone is interested in moving it forward, do upate in the description.

== Session title == Drawing in new MW tech volunteers with Hackathons, and then what ==Main topic== [[ https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/How_to_grow_our_technical_community | How to grow our technical community]] == Type of activity == Unconference session == Description == %%% == 1. The problem == I had been running couple of Hackathons myself with University students, and the code contributions it produce duringt the Hackathon hours are just great - like there were days when we had like 5-8 patches in Gerrit in less than 8 hours. The funny thing is, right after the hackathon, people just forget about the same, and there are not any more contributions are follow up on the same. Ther are exceptional cases, but its percentage is far low than average. This is a general problem with any technical community, but Wikimedia Foundation needs to take care of this, as: # University students are prospective Google Summer of Code or Outreachy interns, so there is a chance for finding some long term developers there. # The number of Google Summer of Code selects and valid applicants are reducing as per https://www.mediawiki.org/wiki/User:MaxSem/GSoC_analysis. == 2. Expected outcome == I would like to talk and find ideas about: * Running a Mediawiki code contribution drive/hackathon (from my experiences) * Statistics of recent hackathoins, how productive are they, in general. * What happens after the hackathon, * What kind of tracking or later annoucements should be done, etc * Should we stick on to some tracking tools or something, specially for the Hackahtons (or something like that) == 3. Current status of the discussion == ... == 4. Links == * ... == Proposed by == @01tonythomas (originally), @srishakatux and @Rfarrand (current owners) == Preferred group size == 15-20 == Any supplies that you would need to run the session == Post-its and markers == Interested attendees (sign up below) == # Add your name here

**Type of activity:** Talk== Session title == **Main topic:** Drawing in new MW developtech volunteers with Hackathons, and then what ==Main topic== [[ https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/How_to_grow_our_technical_community | How to grow our technical community]] == Type of activity == Unconference session == Description == %%% == 1. The problem == I had been running couple of Hackathons myself with University students, and the code contributions it produce duringt the Hackathon hours are just great - like there were days when we had like 5-8 patches in Gerrit in less than 8 hours. The funny thing is, right after the hackathon, people just forget about the same, and there are not any more contributions are follow up on the same. Ther are exceptional cases, but its percentage is far low than average. This is a general problem with any technical community, but Wikimedia Foundation needs to take care of this, as: # University students are prospective Google Summer of Code or Outreachy interns, so there is a chance for finding some long term developers there. # The number of Google Summer of Code selects and valid applicants are reducing as per https://www.mediawiki.org/wiki/User:MaxSem/GSoC_analysis. == 2. Expected outcome == I would like to talk and find ideas about: * Running a Mediawiki code contribution drive/hackathon (from my experiences) * Statistics of recent hackathoins, how productive are they, in general. * What happens after the hackathon, * What kind of tracking or later annoucements should be done, etc * Should we stick on to some tracking tools or something, specially for the Hackahtons (or something like that) == 3. Current status of the discussion == ... == 4. Links == * ... PS: Sadly== Proposed by == @01tonythomas (originally), the author @01tonythomas might not be present during the event, and if someone is interested in moving it forward, do upate in the description. @srishakatux and @Rfarrand (current owners) == Preferred group size == 15-20 == Any supplies that you would need to run the session == Post-its and markers == Interested attendees (sign up below) == # Add your name here