Call for contributors for Miro 3.5

Note: This is an old post in a blog with a lot of posts over a long span of time. The world has changed, technologies have changed, and I've changed. It's likely this is out of date, the code doesn't work, the ideas haven't aged well, or the ideas were terrible to begin with. Let me know if you think this is something that needs updating.

For many contributions, there's "paperwork" that sticks around allowing me to programmatically figure out who has helped out. For example, the author field in git checkins, reporters/commenters in bugzilla, ...

For other things (translations, testing, ...), I don't have a good way to programmatically figure out who's helped out, who's participated, who's worked with me and other contributors to Miro's development to make Miro as awesome as we can make it.

Going forward, I'll continue to work on making sure that we're doing a good job of crediting everyone who worked on a release because other projects do it and we should be doing it to.

For this release, I want to make sure we credit everyone. If you've contributed to Miro development, let me know because I want to include you in the CREDITS file and other places. Either leave a comment or send me an email.

If you read this entry (and the previous one, please dent it, tweet it, and mention it wherever you can so that we can credit as close to everyone we can as possible. Thank you!

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.