* Title slide Debian Contributors A revolution in Debian project headwear fashion Aug 16, 2013 Enrico Zini (enrico@debian.org) DebConf 13, Vaumarcus, Switzerland * Slide 1 Debian Developers Debian Maintainers Alioth committers Bug reporters Wiki contributors Translators Mailing list contributors Sponsored uploaders Package reviewers Language reviewers Conference organizers Events people Press people System administrators Services developers [...] * Slide 2 \o/ \o/ \o/ \o/ \o/ \o/ \o/ *** Debian Contributors *** \o/ \o/ \o/ \o/ \o/ \o/ \o/ (the doocratic headwear) * Slide 3 The status of Debian Contributor There is no process or approval: when you contribute to Debian you are a Debian Contributor When you are a Debian Contributor, you can: *** Have your name on a list! *** * Slide 4 Also: - You can choose not to have your name on the list - You can see a summary of all your contributions - You get acknowledged for your work - You get thanked for your work - You get reputation for your work It is unacceptable that we still fail to do even that, for so many parts of Debian. _______________________________________ / Isn't this the awesomest presentation \ \ tool? / --------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || * Slide 5: gathering data Each team that takes care of its own data mining: Debian is too diverse to expect otherwise. Teams that currently have no motivation to acknowledge contributions, finally get a reason to do so. Our full range of diverse contributions finally has a chance to become visible! * Slide 6: Missing In Action Contributors are listed with the month of the last contribution we know of. People who have not contributed after year N, are listed in a "Contributors until year N" list. The list manages itself in case of inactivity! Debian Developers are not automatically Debian Contributors * Slide 7: design choices: perfection We make a good effort to thank people, but we don't need to go out of our way to do so. If a person isn't credited and can get credited by contributing some more, that is fine. If a person has done lots of contributions already, then we should find a way to credit them. We do not need to be perfect. Keep this in mind during Q&A :) * Slide 8: lossy Coarse time granularity: a month will do. Only begin and end are stored for each type of contribution: gaps of inactivity are ignored. It is ok if new contributions take a day or two to show up in the list. It is ok if one does not show up in the list after just one bug report, if that means we don't get spammers on the list. * Slide 9: team requirements Submitting data must be as simple as it can be. Teams that can track history of contributions are good. Teams that only track current membership, are also good. * Slide 10: privacy Opt in: ideally, after some contributions are detected you should get an email telling you how to be on the list. Do not publish email addresses by default. Allow people to manage what is credited to them. Hide some types of contributions only. Hide from the list altogether. Merge and manage all Debian identities: emails, fingerprints, logins, wikinames, ... But DAM would still like to see everything, as it makes accepting non-uploaders so much easier! * Slide 11 And now, a presentation of what we have made at Debconf so far.