5 ms·
fantastic feedback, thank you so much for all your input AlexITC!! regarding the potential issues you noted: 1. developers get assigned by the maintainers/core
by irf1 4y ago
fantastic feedback, thank you so much for all your input AlexITC!! regarding the potential issues you noted:
1. developers get assigned by the maintainers/core-team so there is no duplication of effort, there are never multiple developers working on the same bounty. if there's no progress from the assignee, maintainers / other developers would check in and the issue would get reassigned, there is self-regulation. that being said, standardizing this process through a 'locking mechanism' is an interesting idea, we will think it through - thanks!
2. the sliding-scale fee model you are suggesting is an interesting idea, we'll think it through! if companies try bounties, are satisfied and would like to commit to a bounties budget, at the moment we offer the option to pre-pay fees at a discount. there's definitely room for experimentation here, thanks for your note!
3. great point, at the moment you'd evaluate people by looking at their github profiles and whether they've contributed to your project before (or other projects in your ecosystem). there's definitely room to improve that 'selection' process for maintainers. once again great point!
- AlexITC 4y ago> 1. developers get assigned by the maintainers/core-team so there is no duplication of effort, there are never multiple developers working on the same bounty I have read the website docs again and I can't find any reference to this or how the process work. As a company, I would hope to see more docs related to the business before trying it out, the docs assume that you are already integrating the bounties, there are even API docs (which are fine) but no clear definitions on dispute handling (these cases will occur sooner or later). > 1. As a developer, I have had customers paying me to contribute improvements to open source projects they depend on, this case is very tricky because there is no guarantee that the upstream project will accept the change. So far, my understanding is that this case is not supported, is there any plan for it? it is the most common I have been hired for. Thanks.
- irf1 4y agowe will update our docs accordingly about the assignment flow, thank you for noting this AlexITC! regarding your last point, yeah this use case is very tricky, indeed there is no guarantee that the upstream project will accept the change. in fact, that project would need to have the algora app installed to begin with. that being said, we understand there is a pain point here, so we will note this down and seek additional feedback. we won't hesitate to reach out if/once there is a development here :) thanks so much once again for all your feedback!