Deep Integration With Bountysource

[indolering]

Bountysource offers deep integration for GitHub, allowing supporters to encourage development financially.

Final Term is a project with a lot of excited onlookers, it would be great to see the developers getting paid for their work.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[p-e-w]

You seem to be talking about http://blog.bountysource.com/post/48954271533/improved-github-integration-automatically-update, which is indeed pretty cool.

As I have stated before, I myself have currently no intention of accepting money in any form for my work on Final Term, but if bounties were attached to certain open issues and someone else wants to try for them, they of course have my blessing. I shall look into Bountysource and integrate it if appropriate.

It is important, however, that people who work on bountied issues (or indeed any other major issues) maintain communication because some major architectural changes are coming up. In particular, I plan to replace TerminalView with a new component, so it makes no sense to implement e.g. Copy & Paste on top of the existing one.

[p-e-w]

I have set up Bountysource for Final Term.

Final Term now has an official Bountysource project at https://www.bountysource.com/trackers/281825-final-term. I have made a start by pledging $50 towards a fix for #296, the last issue that prevents split and tabbed panes from working as intended.

To re-clarify my policy on financial contributions to the Final Term project:

1. I greatly encourage bounties for open issues! 👍 👍 👍 Bountysource bounties are now an official and welcome way to help Final Term as they can encourage third-party contributions.
2. Everyone is invited to claim a bounty by fixing the issue in question. However, if you are considering a fix for a complex issue requiring deep changes such as Support output selection and copy & paste [$65] #7, please contact me first so we can make sure that your ideas are in alignment with the upcoming architectural changes.
3. I myself might fix bountied issues occasionally but will not claim the bounty in that case. I see bounties as a way to attract new contributors, rather than filling my purse in exchange for work I was going to do anyway. So if you put a bounty on an issue I fix eventually, not only will you get your fix, but your money back also 😸. Placing bounties will have no effect on the rate of my own contributions to the project.
4. The Final Term project does NOT accept donations at this time! All bounties must go towards concrete issues. This is not a fundraiser.

Well, then, spread the word 🔈 and get those bounties going 💰!

As a reminder, there are already 2 active bounties at this point:

• for Mac OS X port [$20] #92 (Mac OS X port)
• for Segfaults, GTK errors and hangs with NestingContainer [$70 awarded] #296 (Segfaults, GTK errors and hangs with NestingContainer)

[mdrmike]

I would like to see the details related to bounties added to the finalterm homepage. Both the policy and the HOWTO add/contribute to a bounty would be helpful.

Had I not run accross this issue today due to the copy & paste issue, I would not have realized you went to the trouble to set this up -- months ago. I think it would help the project if it were more obvious. Some people are limited by time, skillset, etc -- bountiysource provides them an alternative method of giving back. Also, I commend you on the thoughtful comment explaining your posiiton -- and I think it's clear you're hoping to find more contributors to help.

However, as a side note @p-e-w, I'd also suggest you modify the wording (of the third item, above) that allows for the possibility you may change your position on collecting bounties in the future. Whether or not you ever derive income from this project is separate from the project remaining open source; in which case it remains true to the values under which it was released.

[mdrmike]

hmm, should I have just made the edits to the README and suggestion as a pull request?