Build it: Difference between revisions

← Older edit

Build it (view source)

Revision as of 00:32, 2 February 2012

840 bytes added , 12 years ago

m

Protected "Build it": Excessive spammers ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Anonymous user

imported>Paulproteus

Revision as of 16:20, 31 March 2011 (view source) imported>Paulproteus (Created page with ''''Rationale''': We have a theory: lots of users of free desktop software want to get involved in customizing or contributing to the project's development, but they haven't gotte…')		Latest revision as of 00:32, 2 February 2012 (view source) imported>Paulproteus m (Protected "Build it": Excessive spammers ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite)))
(57 intermediate revisions by 34 users not shown)
Line 1: __NOTOC__ === Overview === '''Rationale''': We have a theory: lots of users of free desktop software want to get involved in customizing or contributing to the project's development, but they haven't gotten to the first step of getting the program to compile. '''The event''': The first week of April, we want to see five projects email their mailing lists saying, "Experienced people will be on the IRC channel at a particular time, waiting to help you compile the app." The second week, we want to see new contributors feel included and invited. '''The ask''': Are you a member of the development team for a free software desktop app, and do you want more prospective contributors to join in? We need to find four more projects. We need you to [mailto:starling@openhatch.org email us] and pick a day and time that works for you to be in your project's IRC chat room and helping people in your community. Line 7 ⟶ 11: '''The goal''': We want to see a dozen people, over the course of the week, go from confused wannabe contributor to someone who feels comfortable following discussion on their chosen projects' development lists. === ~~How~~Why toyou ~~get~~should ~~involved~~do it for your project === It sends a ''strong signal'' to prospective developers that you ''truly want them to join you''. We need '''advocates''' to run this event within their project. If you're a free software contributor and know how to compiled a program you work on, then it can be you.▼ === How to apply on behalf of your project === ▲~~We need '''advocates''' to run this event within their project.~~ If you're a free software contributor and know how to ~~compiled~~compile a program you work on, ~~then~~we itwant ~~can~~you beto run this ~~you~~event within your project. Email us: ~~<div style="text-align: center; font-size: 300%">Email~~* starling@openhatch.org ~~to apply</div>~~ * Answer these questions, with ''one sentence or less'' each: Your project's name What you like about this outreach event ** How you heard about the "Build it" week Remember that '''space is limited''', and we'll get back to you to let you know if there are still slots available. ~~=== The schedule ===~~ We're particularly looking for projects with plenty of users, which means a healthy pool of people to draw from. ~~Projects signed up right now:~~ === The ~~GIMP~~schedule === Dates and times: Fri, Apr 15, 0300 UTC: GIMP, with Akkana Peck (akk) * Monday, Apr 4 ** Blog post: http://shallowsky.com/blog/gimp/gimp-buildit.html * Tue, Apr 5 ** Mailing list post: None yet, I think (?) * Wed, Apr 6 * Fri, Apr 15, 1300 UTC: Vidalia, with Tomás (chiiph) * Thu, Apr 7 ** Blog post: https://blog.torproject.org/blog/vidalia-get-involved * Fri, Apr 8 ** Mailing list post: None yet, I think (?) === More explanation === Line 42 ⟶ 55: === Blog posts === * http://shallowsky.com/blog/gimp/gimp-buildit.html * Danny said he could write up a blog post about this.