Live data from Hacker News

Open source sustainment and the future of Gitea

blog.gitea.io

21–30 of 187 posts

Re: Open source sustainment and the future of Gitea

#21

I am happy that my git host of choice has a very simple monetization/sustainability model: I pay money, they host my code. Thanks ddevault and anyone else from Sourcehut who may see this!

I mean, that's part of the model mentioned in the post above (Instance Hosting/SaaS).

Re: Open source sustainment and the future of Gitea

#22
The implication of a DAO and Crypto involvement has stirred attention in the comments. I have 2¢ on the matter. First, I don't think we've seen many examples like this in open-source communities. For that reason alone, regardless of the idea's merit, I welcome it; if it is to fail, let us see it, that we may have a case study in the future. Worst case, there is wide support for a fork, and I don't see that becoming any more unreasonable over the next decade. Secondly, just as a brain-storming idea, what if we had like the blockchain and stuff but the rewards weren't pure value (ie. contextual value, one man's treasure; titles, hats, cosmetics, merch vs purchasing power and/or influence)?

Re: Open source sustainment and the future of Gitea

#23
post #2

Looks like Blender is onboard with moving to Gitea. However: > To preserve the community aspect of Gitea we are experimenting with creating a decentralized autonomous organization where contributors would receive benefits based on their participation such as from code, documentation, translations, and perhaps even assisting individual community members with support questions. So Gitea wants to create a DAO and "recei…

I read it as, a way to provide benefits from the company to contributors, but the blog post also mentions other ways of funding the community

Re: Open source sustainment and the future of Gitea

#24

The implication of a DAO and Crypto involvement has stirred attention in the comments. I have 2¢ on the matter. First, I don't think we've seen many examples like this in open-source communities. For that reason alone, regardless of the idea's merit, I welcome it; if it is to fail, let us see it, that we may have a case study in the future. Worst case, there is wide support for a fork, and I don't see that becoming a…

I hold zero crypto, but by reading of the DAO is that it is one of the ways mentioned of trying to benefit the community or perhaps it will be used for community governance (elsewhere in the post it mentions hiring maintainers, and also creating bounties to fund development), not a way of creating some crypto coin to sell.

Re: Open source sustainment and the future of Gitea

#25
Lots of focus on the DAO mention in the post, but it looking at the concrete things in the blog post instead of some "experiment", there are direct funding models of selling hosting, support services, training and more. The DAO is likely just a way to make the governance of the community more transparent, but I think people are confusing it with creating a crypto coin.

Re: Open source sustainment and the future of Gitea

#26
post #5

I've been donating to Gitea for years (on their Open Collective [1]) but if they start with this cryptocurrency/blockchain stuff, I am out. I am trying to fund development, not invest unstable currency technology. Gitea itself started as a fork of Gogs, it wouldn't be too surprising to see it fork again if they start being creative with the brand. [1]: https://opencollective.com/gitea

I'm confused, they don't mention crypto. This blog post is simply an announcement that they started a company. The purpose seems to mainly be for providing support services and paying developers. I see absolutely nothing wrong with that.

It does mention DAO, which is crypto adjacent, however like you said the purpose listed in the post is to provide paid support services, the DAO is for governance of the community, not to shill some scam crypto coin.

Re: Open source sustainment and the future of Gitea

#27
post #6
post #3

Creating a DAO for this sounds _incredibly_ risky to me. One tiny flaw in the design of that organization and the project could be destroyed by people gaming the DAO rules for profit.

But does decentralized autonomous organization always have to imply blockchain?

If they didn't mean blockchain they could have not used a phrase that is very strongly associated with it, and instead used any number of other terms in colloquial use that match the properties of the organization they're setting up.

Re: Open source sustainment and the future of Gitea

#28

I am happy that my git host of choice has a very simple monetization/sustainability model: I pay money, they host my code. Thanks ddevault and anyone else from Sourcehut who may see this!

I mean, that's part of the model mentioned in the post above (Instance Hosting/SaaS).

The thing is, I'm very happy with that not being part of the model, but the whole model.

I don't want to deal with experimentation or complex organizations or "an enhanced enterprise version" or free tiers. I want someone to take money from myself and other customers, and use it to make a good product without shenanigans.

E: As far as I know, it is still possible to get free accounts on sr.ht - however, it is very transparent that this is not a permanent offer.

Re: Open source sustainment and the future of Gitea

#29
post #20

If the author of this blogpost is reading this and wondering why the link in the post didn't render properly: > (their move to using Gitea)[ https://code.blender.org/2022/07/gitea-diaries-part-1/ ] it's because you switched up which braces go where for a markdown link. should be [text](link)

I constantly make that mistake. I don't know why, I simply can't seem to get the muscle memory right for some reason, and I always do ()[] first.

Well, [text](href) is just a lousy syntax. Quite apart from how easy it is to forget which way round it is, the way round that it is is syntactically problematic: the parentheses are URL code points https://url.spec.whatwg.org/#url-code-points>, so URL encoding won’t percent-encode parentheses, so Markdown doesn’t actually support all valid URLs, leading to injection attacks if all you do is regular URL encoding, deliberate or accidental, and deciding where an href ends is troublesome and inconsistent, with some Markdown implementations terminating at any right parenthesis, and others trying to match parentheses as a heuristic that helps most cases. The other way round, with the href in square brackets, would have been better in this regard, as square brackets aren’t URL code points, and thus will be percent-encoded. But better still would have been to lean on angle brackets more, matching long-held custom and the other style of links Markdown already uses (just plain ). In my own lightweight markup language that I’ve been working on for a while and am now polishing up and implementing properly, I’m currently using [text ]. [text] is also quite tempting, with slightly different trade-offs.

(When I speak of the details of URL encoding and which characters get percent-encoded, these things weren’t quite so clearly-defined back in 2004 as they are now, but I believe it was all still true.)

Re: Open source sustainment and the future of Gitea

#30
The development of Robot Framework(1) was originally paid by Nokia, but then things happened and Nokia decided not to continue doing that anymore.

The main developer of Robot Framework and few companies using RF heavily understood that something had to be done, so Robot Framework Foundation(2) was formed. RF Foundation has membership fees, it arranges RF conferences etc. which allows RF Foundation to pay for the development of RF.

I think that is a really good way to fund OSS development. Those companies which benefit the most from it, pay membership fees and gets to vote on the direction of the product.

(1) https://robotframework.org/ (2) https://robotframework.org/foundation/

Post reply on HN