You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this provides a very simple way to add a third party semi-dynamic element into another site. It's a technique already used by a number of github services.
In the context of feedopensource a iteration status would probably show:
number of tasks (bugs, features, etc) that are involved, incomplete, complete, etc
percentage funded (or whether it failed to be fully funded)
whether work on the iteration has started.
probably this can be implemented as a progress bar that goes through two stages - first it shows the funding building up, and then when work on that iteration begins, it shows the proportion of tasks that are complete (a task is considered complete when the issue has been closed)
If feedopensource looked at the referer header, then it would know what github issue it was a part of and display information about just that issues!
Otherwise, feedopensource would read all the issues and (or use github api) to read find the new Iteration issue, and then parse it to find out which tasks are a part of that iteration.
The project maintainer creates a bitcoin wallet ({wallet}) for that iteration, and a target amount ({target} of bitcoins that they think they'll need to start working on / complete that iteration)
Because github aleady has back links for when an issue is refered to, you'll be able to see whether an issue is part of an iteration!
The text was updated successfully, but these errors were encountered:
The status of an iteration is displayed via a png,
just like a travis ci badge.
http://about.travis-ci.org/docs/user/status-images/
this provides a very simple way to add a third party semi-dynamic element into another site. It's a technique already used by a number of github services.
In the context of feedopensource a iteration status would probably show:
probably this can be implemented as a progress bar that goes through two stages - first it shows the funding building up, and then when work on that iteration begins, it shows the proportion of tasks that are complete (a task is considered complete when the issue has been closed)
A badge would be added to the page like this:
(edit: changed url pattern)
If feedopensource looked at the referer header, then it would know what github issue it was a part of and display information about just that issues!
Otherwise, feedopensource would read all the issues and (or use github api) to read find the new Iteration issue, and then parse it to find out which tasks are a part of that iteration.
The project maintainer creates a bitcoin wallet (
{wallet}
) for that iteration, and a target amount ({target}
of bitcoins that they think they'll need to start working on / complete that iteration)Because github aleady has back links for when an issue is refered to, you'll be able to see whether an issue is part of an iteration!
The text was updated successfully, but these errors were encountered: