On Thu, Apr 02, 2015 at 01:33:55PM -0700, W. Trevor King wrote:
> 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 …

So it's a bit more work this way, but “copied from bc” is enough to
find the source.  Looking through swcarpentry/bc for stuff touching
files like 'badge*png' turns up:

* Initial creation (maybe copied from swcarpentry/boot-camps?) in
  d5d75d1 (Initializing template for Software Carpentry bootcamp home
  pages, 2013-07-14).
* Edits in 96ef9a4 (Updated badges, 2013-08-18, #14 [1]).
* Removal in bf9e6c1 (Only two bootcamps ever included instructor
  bios…, 2013-12-02, #189 [2]).

Preston includes the SVG source in #14, so that's probably enough
source for you to create a new badge along the same style.  He also
changes some comments in the SVGs from “Created with Inkscape” to
“Generator: Adobe Illustrator…”, which hints at the process ;).

Cheers,
Trevor

[1]: https://github.com/swcarpentry/bc/pull/14
[2]: https://github.com/swcarpentry/bc/pull/189

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org

Reply via email to