Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add "checkpoints" feature for issues. #97
A lot of issues are complex, requiring a lot of smaller steps to get to the end result. FS should model that in the following way:
Any issue can enable a "checkpoints" feature by adding other issues to a list of checkpoints. This represents a step-by-step overview of the steps necessary to achieve the final goal. These checkpoints, as separate issues, can be sponsored individually.
What makes this cool is that the first issue page, the one for the big issue at the top of the heirarchy, displays the completion status of all the checkpoints, and for its bounty, displays a total of its own funding plus that of all its checkpoints. So if I sponsor "Fix automatic font retrieval" for $20, and that issue is listed as a checkpoint for both "Interface upgrade" and "Get rid of all WTFPL-licensed code", the total sponsorship for all three will go up by $20 (though it is the same $20).
Optional feature for discussion
Splitting up a big issue's bounty among its component steps. So if the big issue has its own bounty of $300, not counting checkpoints, then that $300 is split up between the component issues equally, or proportional according to their own sponsorship. This would be a complex undertaking though, and probably not too good an idea for that reason alone.
Sharing my 2 cents, I think an issue in FS should be a "project" in the
Even if it has multiple steps, or multiple tasks, or multiple references on
On Tuesday, December 11, 2012, Jarl Arntzen wrote:
Henrique Bastos http://henriquebastos.net
Curso Welcome to the Django http://welcometothedjango.com.br
Thanks @henriquebastos. I think this type of issue (I mean an issue like Add other samplers that properly reduce (downsample) and warp images) should really be modeled differently from original issues.
I agree the name "issue" might even not be right for it.
I like the name issue for FS, all my comments are related to the FS
For me it seems a false premise to say that 1 issue means 1 payment. Like
The semantic is tied to the project's culture.
I don't like the name "project" either (that's why I used quotes ;)).
How about "upgrade" or "enhancement"?
I just recently got word of freedomsponsors, and saw this issue as something to perhaps get my feet wet into the code base. I like the idea of having an umbrella term that encapsulates multiple issues. This not only makes it easier on the back end, but also gives the chance for multiple developers to work together towards a larger goal by sharing the bounty by working on many issues on the way to that goal.
I'll poke around the code, think of some mockups, and go from there in the next while..