-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup a Bountysource Salt campaign for funding #537
Comments
Good idea. Open Collective could be an alternative. |
I completely agree, and would be willing to donate as indicated in this issue I posted today (#538) in order to encourage continued development. While I agree the best case scenario is consistent funding and developing, and that current requested enhancements/feature requests such as file transfers (#15) and supporting synchronization of one account across multiple devices (#99) would be great improvements, they're not absolutely crucial. For example, OnionShare (https://github.com/micahflee/onionshare) is a well respected application for file transfers, and while adding this functionality to Ricochet would be great, I believe keeping the code up to date is more important. With a successful audit now complete (https://ricochet.im/files/ricochet-ncc-audit-2016-01.pdf), we know the code works and is secure. The only real issue I feel is present in the code is the out of date Tor version, which currently would require consistent developer action to keep up to date without lag (Ricochet is currently using 0.2.8.9 which was released over 6 months ago). In the short term I believe it would be best if we prepared for the worst case scenario, which would be low community donations and low continued enhancements. If Tor were to be unbundled from Ricochet as discussed here (#538), it would allow users themselves to ensure they are running secure and up to date code by keeping their own installation of Tor up to date. This short term fix would then allow us to focus on the long term goal - using Bountysource or Open Collective as discussed above to secure the long term development and success of Ricochet. |
I can create the account for us if this is all is needed, but I believe someone better associated/trusted within this community should do so. |
Also, Open Whisper Systems BitHub could be an option. Sounds like a few of us at least would want to donate to this project to keep it going. I read that @s-rah has been recently using it in her work. It would be great to keep the work going on this project. @special, any thoughts on funding the project? |
So, I Edit: Sent the Bounty Source team an email about the situation. |
Hi @gnujedi, thanks for your work on this. I don't believe I have enough standing to make a comment on ownership of the campaign, but I'm replying here to once again state my support for this project and my promise to donate. |
Okay, so I deactivated the team I had set up since there was already a "ricochet-im" team (not "ricochet") that has some bounties set up for this project, but the Salt feature of bountysource will have to wait until @special wants to set it up. I opened a pull request #554 to change the readme to include a bounty button to show the current amount of cash available to bounty hunters. This doesn't resolve this issue, as I intend lead devs to be able to be funded on a monthly basis. However, I hope it brings more people to work on the code. Edit: |
For this project to succeed in the plethora of messengers out there, funding is needed to keep developers working on this project.
Bountysource created Salt for this purpose:
Similar to Patreon, this allows pledges to FOSS developers. In today's age of surveillance, we need technologies like ricochet in order to maintain freedom. The Salt program will possibly help keep this project going.
The text was updated successfully, but these errors were encountered: