> In cases like this (badge graphics), I'd suggest the Git history as a > useful place to store the creation routine. We currently have > messages like “Adding helper badge from 'bc' repo [3]”, but that would > be more useful if it had a message body like: > > Created with: > > $ ./bin/badge-create.py … > > Then folks don't have to remember how a repeated task works, they just > have to check the version control history and see what the last person > to do something similar has to say about how they accomplished it.
The scripts that create the badges are at https://github.com/swcarpentry/site/. Check https://github.com/swcarpentry/site/blob/master/bin/badge-create.py, https://github.com/swcarpentry/site/blob/master/bin/badge.py and https://github.com/swcarpentry/site/blob/master/bin/badgebakery.py. The lack of documentation is my fault. Sorry about that. I thought that $ ./bin/badge-create.py -h usage: badge-create.py [-h] username email {core,creator,helper,instructor,organizer} [site_dir] Create JSON blob and baked PNG for a badge positional arguments: username email {core,creator,helper,instructor,organizer} site_dir optional arguments: -h, --help show this help message and exit as OK at the time. Anyone needing help with the badges please feel free to get in touch with me directly. Cheers, Raniere
signature.asc
Description: Digital signature
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
