Haxe(Flixel) and OpenFL bounties to help glorious progress of (haxe and) flixelkind
(*Bounty repo format straight up stolen (with permission) from (Lars)[https://github.com/larsiusprime/larsBounties] who copied it from FlibitBounties I imagine as more people put bounties this copy chain will extend indefinitely.)
This is squidBounties, the repository for Squidly who's been working on Renaine for 3 years and thinks it's about damn time for some formal help and is willing to put down money to make it happen.
All available bounties are listed on the Issues tab above as open issues. Claimed bounties that are underway will be tagged as such, and completed bounties will have their issues closed.
To claim a bounty: Post in the issue, and make it clear that you wish to claim the bounty, then follow up with some basic proof of work. This can be as simple as asking some clarifying questions that indicate you have some knowledge of the problem. The bounty counts as 'claimed' as soon as you start working on the issue.
Multiple people on one bounty: If you want to work on a bounty that's already claimed, simply get in touch and we'll negotiate. The first person to claim the bounty in good faith and who is still making progress gets deferential treatment, but in the right circumstances, and with the agreement of the original claimant, I might consider splitting the bounty or some other arrangement.
To finish a bounty: If this is a HaxeFlixel bounty it must be accepted by the HaxeFlixel organization. This means it must prescribe to their coding/testing standards. Same rules apply for OpenFL if it the feature is dependent on it. For anything specifically marked as for Renaine and Renaine only (this is very uncommon) then this rule does not apply.
All of the bounties listed have the following common rules:
#1: All source code written will be released as open source to the HaxeFlixel or OpenFL communities. For private work that's properietery I'll have other terms, but for these bounties I want to do something that benefits both the needs of my game specifically but also the greater Haxe community.
#2: You are more than welcome to write your work on completed bounties as professional work experience. If you contribute to, for example, HaxeFlixel, feel free to put that contribution down on your resume or what have you. If we end up establishing a regular working relationship I am also happy to act as a professional reference for job applications. Because my financial budget for bounties is extremely limited, this is the least I can do while also not going full "For Exposure" on aspiring programmers.
#3: You are free to work on the project however you like. If you do a lot of programming on Twitch, for example, you can stream the whole process, and you can publish anything about the project you want, including technical write-ups and example projects. You can also work in whatever environment you want, as long as the final product works on the expected platforms with the expected languages/dependencies. Note, however, that the bounties are based on an expected schedule/timeline/budget and those are unlikely to change without a very detailed assessment explaining, for example, why a project will take longer than expected.
#4: Every single project listed has a direct connection to a real-world application. My projects don't live in a bubble; if I need something done it's because there's a game out there right now that needs it (usually, but not always, one of mine). If you want to work on something that involves real commercial applications, this is a good way to do so from the outside. I will do my best to list the most relevant games that apply to a specific project.
#5: All bounties exclude extra money needed for sample games. For example, if you're working on something that requires testing a game on Steam you don't have, I'm willing to add an extra bonus to cover the costs of one game on Steam/Itch/GOG to make sure you have access to real data instead of just random unit tests.
#6: You are responsible for taxable income made from these bounties. This one's pretty obvious but for those who aren't familiar, this is effectively non-employee income and you will need to pay your own taxes (depending on where you live). In the United States, for example, this is simply "Other Income" on line 21 of Form 1040. The exception to this rule is if you live in the United States and make more than $600 from my projects, at which point I will need Form W-9 sent to me so I can send you a 1099-MISC next year.
#7: If you would like to contribute to the bounty's payout, you are free to do so. For example, if you're a developer that cannot work on a project but would like to pay extra to the person that completes it, you can simply add that as a comment to the bounty. All the above rules still apply, so you may end up getting multiple 1099-MISCs if you receive bounties from multiple companies.
If you have any further questions, my e-mail address is [email protected], and you can ping me on twitter as @squuuidly or better yet, find me in the Haxe or Renaine discords as @whodunit#4111.