Can I pay for this?

[coolaj86]

I like to have the security of knowing that the software I use has some sort of plan to allow me to purchase a copy so that I know I can depend on the continued development of the software and have some access to support for bugs in existing features or pay bounties for desired features.

Is there any marketplace or business planned for this?

[lunny]

There is no marketplace and business plan currently. We are trying all our best to fix bugs and security problems ASAP. For new features, we first will implement Gitea via Gitea. If some feature is slight or someone have time, it may be implemented. However you can file an issue to describe your requirements. Since we made a community according https://github.com/go-gitea/gitea/blob/master/CONTRIBUTING.md, I think we could continue the development. Maybe we will set a donate account after we know how to spend the money on Gitea.

[strk]

@coolaj86 you can surely pay anyone to get support and custom development. For development, what you pay to be developed has to pass the approval of at least 2 maintainers to be accepted. For support it's just between you and your developer of choice.

[coolaj86]

@lunny Thanks. I'd like to incentivize the development of 'Login with GitHub' and importing Issues from GitHub. I'll create an issue for those things.

@strk exactly why I'd rather work with the existing team in some way

[tboerger]

Login with github is covered by the issue for an OAuth2 consumer. I think importing from github should be a standalone tool

[thewhitetulip]

@lunny how about we start a patreon or something on bountysource?

[tboerger]

And who should receive that? We can setup bountysource to give the opportunity that people can pay individuals for getting features implemented. The gitea team itself doesn't pay anything except @lunny who got to pay the domain once a year.

[lunny]

@tboerger I think we may need a more power host so that we can publish docker every PR! 💯

[tboerger]

@tboerger I think we may need a more power host so that we can publish docker every PR! 💯

You don't want to do that for every PR. I have already talked about that with @bkcsoft, IMHO we will do that based on tags assigned to the PR. Maybe this logic will be part of the teabot that launches containers that got a specific tag assigned and it destroys the instance when the tag gets removed.

And as this will reduce the required resources a lot we can also launch that on our sponsored droplet. So more or less unrelated to this issue :P

[lunny]

OKay with that.

[coolaj86]

You guys are on to something huge here. If you can get federated accounts working (and good migrations) you could replace github. This is fast, lightweight, runs on an RPi. It's perfect.

I will be surprised if within a year or so you don't have a non-profit, b-corp, or foundation of some sort (like what npm did) with support plans. If that's something you want to do that is.

There's all this talk about decentralization, but no one actually does it - they build distributed protocols that have a central authority and store all of their decentralized code on centralized authorities and host all of their communication on centralized authorities.

You've got an opportunity to actually be the change everyone is talking about right at the center of where all the code happens. :)

[thewhitetulip]

@tboerger Well, I do not know about patreon, but bountysource would be nice, that would give the money directly to those who fixes issues, and since gitea/gogs is amazing, I feel there is a need for bountysource.

[lunny]

Currently bountysource is a good choice.

[xor-gate]

Bountysource is the way to go, people who fix get the credits. Most people do this in their "spare time".

[tboerger]

I have enabled bountysource now. So if you want to pay for something create a bounty and the community will benefit of it.

[coolaj86]

I don't see a link to bountysource on the home page or the github page. Where is it?

[tboerger]

I don't see a link to bountysource on the home page or the github page. Where is it?

It's automatically linked within the issues, but bountysource got a small open issue that it doesn't get rendered properly:

[benyanke]

Maybe we will set a donate account after we know how to spend the money on Gitea.

You'll be able to find things to spend on it, I'm sure! You should really set up something ASAP, especially given the github news.

Even if it just sits in an account for a year, I'd highly encourage you to do so

[tboerger]

We are already registered on opencollective :)

[coolaj86]

You've got to put a call to action in the README so people have an idea of what to do and what will happen as a result of what they contribute:

Like this #4117

Or better yet, add some details:

Goals:

• $750/month - we'll self host
• $1,500/month - we'll integrate one new OAuth2 provider each month
• $5,000/month - we'll have a team member dedicated full-time to the project
• $15,000/month - we'll close out 10 small, 5 medium, and 1 large issue each month

Rewards:

• $5/month - get listed as a sponsor
• $100/month - up to 3 sponsors can be listed at the top of the readme as core sponsors

Just pick some goals and run with them.

[davidak]

I suggest Liberapay. It is open source, run by a non-profit organization and funded through it's own service. Unlike Patreon, Bountysource (salt) etc it has no fees (except from payment provider). You can donate $0.01 every week if you want! You can also set goals...

[jonasfranz]

@coolaj86 If you are searching a migration tool to migrate issues to gitea, checkout "gitea-github-migrator" I wrote: https://git.jonasfranz.software/JonasFranzDEV/gitea-github-migrator