-
Notifications
You must be signed in to change notification settings - Fork 38
get any possible help by outsourcing with remaining weekly budget #984
Comments
Have you ever completed a bounty on BountySource? We've been on BS for years and have never gotten any traction from it. I don't think it's worth spending time on, personally. |
The 4 issues that have >$10 bounty are:
IMO they are all way too big to be attractive issues for bounty hunters. None of them have clear scope, and the minimum workload needed of any one seems to be weeks if not more. This can be just wishful thinking, but I think it will be different if we:
In case still no external developer is interested with those in time (1 week), let's raise the bounty, up-to the point where any of our internal collaborators feel it's worth their effort. In case that happens, I'd say we do a twyw internally with the earned bounty, among those who are involved in the issue. One reason to bring this up at this point is, if we decide to roll out npm integration and make a hit, IMO it's better to polish the whole project as much as possible, and I see quite a few issues in tracker that seem to be good candidates. Will try to list some here. |
I would like to see money put toward TWYW...but I think there is some social pressure holding people back from taking more than @whit537 does. I know that TWYW is take what you want, but do you see what I mean? Not implying that Chad wants to hold people back--I think he wants the opposite. |
@mattbk great point you raised. IMO it's one of the most critical issues in current twyw model. One thought, we use group intelligence instead of personnal intelligence to help this issue:
|
And: |
Actually, I think he's the last anyway if TWYW is still operating under "kids eat first," where the newest members of the |
Seems we don't have an issue discussing about twyw procedure internally. Maybe we need to re-ticket that part, and only focus on the BS topic here? |
I'm happy to discuss our current twyw spread. If there's a way we can use that money more productively then by all means let's find it. I'm much more interested in that convo than in trying to make bounties work. I see bounties as a failed model, and one that is more or less antithetical to Gratipay. I think we should invest our time and effort in building a strong team using twyw, and retire BountySource if anything. |
Moved TWYW to separate thread. @whit537 IMO $ amount is a reasonable scale to quantify exactly how much we want a certain issue done, no matter we use BS or not. We may put label like "$50" or "$20" to issue internally if we just want to do everything internally. Using BS (or any other similar service) is just to broaden our audience and increase level of public envolvement in our developing, which will result in more motivations for the internal collaborators even with no external interest attracted, and any additional help from the public would be just a bonus.
If it can accelarate our growing, IMO it's fine to grow together. We should be able to see the effectiveness of different models in the long run, but we need to grow first. |
Here are some potential bounty candidate issues with relatively high visibility/severity, clear scope, and hopefully little estimated workload based on my very limited knowledge of Aspen. By "little" I mean: make Team explorer pageable |
I don't think it can.
This doesn't sound right to me at all. Are you suggesting that we start adopting bounties internally? 😳 |
Shall I put some bounty on one of the low-hanging fruits to see if it'll get external interest? If so could you check which of the issues I listed is most low-hanging? That is "1-2 day for new developer with average expertise skills required for the issue with some pointers from internal developers, or hours for former developer that had experience with gratipay dev with environment setup already."
Either that or some kind of label that reflects the weight of the issue. By weight I mean benefit/cost. |
I like the idea of recruiting more collaborators, but I don't think BountySource is the place to do it. We want community members, not mercenaries. |
With currently weekly budget, we can still put ~$40 to 1 or 2 issues that are high-severity/priority but low workload (for domain experts) on crowdsourcing site like BountySource. It'll require some additional burden to get new developers on board, but IMO still worth it.
The text was updated successfully, but these errors were encountered: