On 02/19/2016 07:01 AM, Bhagyashree Uday wrote:
Thanks for the encouragement Justin. I will write a more generalized
script so that we can use it to analyse the upcoming BrickHack hackathon
too. Do you have any more ideas/domains for which we could develop
metrics for upcoming hackathon ?
Thinking of what we're planning on doing, badges and a count of code
changed in various repositories that participants are hacking on will be
a major part of the event.
We're planning on having two badges for the event. One is already
created, the BrickHack 2016 visitor badge, and another will hopefully be
awarded to winning participants in the Open Source category.
Participants will be hacking onto open source projects of their choice,
while various Fedora projects will be presented and made available to
those willing to hack onto our own infrastructure and software. Ideally,
we can judge contributions made based on something like number of pull
requests submitted, number of lines of code changed, and maybe some
other quality qualifier, like maybe if the PR is accepted.
I also want to try to tie long-term activity by participants holding the
badge to monitor how far or how deep they go into Fedora. Did we make an
impact with the students there? How many went on to contribute to the
Project after the event? If we can begin doing this kind of strategy at
more events, it will be easier to answer questions like:
* How did we do at [X] event?
* How does it compare to prior events?
* Did we impact more people here based on the number of people who have
* How far did event-goers go into Fedora?
And so on. Hope this helps!
Justin W. Flory