On Sun, Nov 09, 2014 at 11:06:32PM +0100, Johan Engelen wrote:
Hi all, I'd like to get the developer book campaign done before the holiday season this year.
The proposal is in board-docs: proposals/developer_education_book_campaign_2014.txt
For item 4, I'd like you to take care of the front-end administrivia, since SFC takes care of the actual purchases. The tasks should be:
4. The campaign proposer (or their designee) will be empowered to i) Identify the qualified contributors as per (1), ii) Contact the qualified book recipients to collect their address and choice of book from (2), iii) Prepare a finalized list of recipients with their book choices, iv) Communicate the finalized list to SFC and work with them for any discrepancies as they make the book purchases.
We had an issue last time with delivery; the book was delivered to a building on a college campus and there was apparently some confusion there with UPS. So we should ask for "any special delivery instructions" when gathering addresses.
Differences with last year are:
- *sum* of ohloh.net 12-month rankings for Inkscape *and lib2geom*
- extended book choice: Stackoverflow list of good C++ books
Book choice sounds fine.
We had a bit of a discussion on IRC about this. For simplicity, I think it'd be good if we keep this a developer education campaign, i.e. C++ books. And then have another something for the non-coders. We of course appreciate those efforts too, I just don't know how to "rank" them and what to give.
I don't know... I feel like so many people contribute to the project in so many different ways, that to limit it to just coding sort of diminishes the importance of those contributions. OTOH I do see what you mean about difficulty ranking them.
Maybe it'd help to know what the "another something" would be? T-Shirts, mugs, etc.? Maybe allocate $250 for C++ books, and $250 for the non-coders?
Something fun was proposed: add randomization to it. So, we pick 10 out of the top 25 committers. The picking is done randomly, where your win-chance is proportional to your commit count (p = your #commits / total #commits)
That's an interesting idea. I wonder how the randomization would be handled to ensure fairness?