The API bounty - deliverables

Then there is the splitting of the bounty. David from Bountysource replied to me (sorry been busy with work so this has been pending on me…) and he gave two options:

  1. manually split the bounty between multiple developers, so long as a) the issue is closed and backers are happy b) all developers involved publicly agree to the split details (eg $100 to X, $250 to Y, etc)

  2. If you create multiple, smaller tasks that collectively accomplish the “API Needed” goal, I could help you move bounties off this issue and onto those.

I’d say 1) is easier and more flexible, 2) will be more work.

I personally have never done a REST API with Rails, so I’m a bit hesitant to start putting percentages. I’d maybe start with the two main categories, split those, maybe even 50% if no one has better guesses, and then split down if needed in the wiki spec.

@jhass @dennisschubert @steffenvanbergerem do you guys (with more Rails experience) have some ideas on the weight we could give to particular areas suggested here in the deliverables? 50/50 between the main groups ok?