Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Open source sustainment and the future of Gitea

blog.gitea.io

Post reply on HN
Print view View original

51–60 of 187 posts

Re: Open source sustainment and the future of Gitea

#51

Post by bruce511 »

guywhocodes wrote: post #11

Lost me at: > An enhanced enterprise version Good thing it's towards the end, guess it's time for the next fork of gogs then.

I'm going to assume you are not an enterprise - forgive me if I'm wrong.

Enterprises have very different needs to individual developers and small shops. So there are always features which apply to enterprises but not to small companies. Consider for example Active Directory integration.

Equally purchasing in an enterprise is different to small companies. If you work for a small company you can basically go to a decision maker, make a case, and if accepted then money glows within the day.

Enterprise businesses don't work like that. They basically can't just "donate money". There are a million layers to work through, and there have to be tangible reasons for spending the money - it can't be things like "good karma" etc.

So for OSS projects that are used by (especially non-tech) enterprise customers, it makes sense to be an entity, and sell a product, that enterprises can buy.

The inhibiter for an enterprise is not a lack of money on their side, its a lack of process on the OSS side which matches up to the process they have to fulfill.

Re: Open source sustainment and the future of Gitea

#53

Post by tpxl »

drej wrote: post #45

For me the main deterrent from Gitea has been their approach to UI design. The shameless inspiration (if you can call it that) they took from Github is pretty startling, the two interfaces look pretty much identical (well, Github has recently redesigned its repo page, but many can remember the old design). Sure, get inspired, make something similar here or there, but this is an outright copy of the whole product desi…

I just compared Gitea and Gitlab side-by-side and they're very, very similar. So either there's also copying between GitHub and Gitlab, or the design of git lends itself to a very specific interface.

Re: Open source sustainment and the future of Gitea

#54

Post by Dave3of5 »

hrbf wrote: post #37

Gitea is a great piece of software. In fact, when starting out with self hosting, I found it to be a very capable solution with a small footprint. Over time I realized: I don’t need to be able to merge pull requests and do code reviews in a web interface. Nowadays I’m invested in a plain Git/SSH setup with cgit as a web frontend and email patches. It never breaks, is as secure as your server is and does everything yo…

How do you setup a plain git server is there a step by step anywhere I could follow ?

Re: Open source sustainment and the future of Gitea

#55

Post by johannes1234321 »

Semaphor wrote: post #43
trevyn wrote: post #39

Earlier quoted context omitted.

To be fair, they don't exactly make it low-friction to become a member: > Membership fees are debited by means of SEPA direct debit. Please email to contact@codeberg.org for other transfer methods.

FWIW, in Germany, that is an extremely convenient way of paying.

Not only convenient, but also cheap. Often free, certainly less fees than PayPal etc.

Re: Open source sustainment and the future of Gitea

#56

Post by hrbf »

Dave3of5 wrote: post #54
hrbf wrote: post #37

Gitea is a great piece of software. In fact, when starting out with self hosting, I found it to be a very capable solution with a small footprint. Over time I realized: I don’t need to be able to merge pull requests and do code reviews in a web interface. Nowadays I’m invested in a plain Git/SSH setup with cgit as a web frontend and email patches. It never breaks, is as secure as your server is and does everything yo…

How do you setup a plain git server is there a step by step anywhere I could follow ?

Funny you should ask. I had actually written this up back then – for a FreeBSD install because it’s what I use.

https://herrbischoff.com/2021/10/how-to-install-cgit-with-gi...

I’ve also tripped over something regarding “master” and “main” branches that’s easily fixed:

https://herrbischoff.com/2022/05/cgit-missing-idle-column-on...

If you want it even simpler, just run

    mkdir repo.git && cd repo.git
    git init —bare
in a folder on a server you have SSH access to and clone it on your local machine like

    git clone user@server:/path/to/repo.git

Re: Open source sustainment and the future of Gitea

#57

Post by alias_neo »

andreareina wrote: post #27
eitland wrote: post #6

Earlier quoted context omitted.

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.

If you look at the sponsors at the bottom of the page linked, the first name is a blockchain company/organisation, which in my mind lends credibility to the fears that they really do mean blockchain and aren't just jumping on the buzz-phrase bandwagon.

Re: Open source sustainment and the future of Gitea

#58

Post by KronisLV »

tpxl wrote: post #53
drej wrote: post #45

For me the main deterrent from Gitea has been their approach to UI design. The shameless inspiration (if you can call it that) they took from Github is pretty startling, the two interfaces look pretty much identical (well, Github has recently redesigned its repo page, but many can remember the old design). Sure, get inspired, make something similar here or there, but this is an outright copy of the whole product desi…

I just compared Gitea and Gitlab side-by-side and they're very, very similar. So either there's also copying between GitHub and Gitlab, or the design of git lends itself to a very specific interface.

> So either there's also copying between GitHub and Gitlab

Isn't it likely that there's just a certain kind of interface and functionality that both works and people have also gotten used to it over time?

It might make a lot of sense to copy it to at least some degree, instead of reinventing the wheel: if you look at MS Office and something like LibreOffice, you'll notice that both of the spreadsheet apps are rather similar (and you can even enable a ribbon interface in LibreOffice, if you want).

I think the same more or less applies to every piece of software, from how phone OSes look, to how desktop environments look and work, as well as why the majority of websites out there look a bit samey.

Re: Open source sustainment and the future of Gitea

#59

Post by alias_neo »

bruce511 wrote: post #51
guywhocodes wrote: post #11

Lost me at: > An enhanced enterprise version Good thing it's towards the end, guess it's time for the next fork of gogs then.

I'm going to assume you are not an enterprise - forgive me if I'm wrong. Enterprises have very different needs to individual developers and small shops. So there are always features which apply to enterprises but not to small companies. Consider for example Active Directory integration. Equally purchasing in an enterprise is different to small companies. If you work for a small company you can basically go to a decis…

The issue, in my mind, if I was making a similar comment, is that projects seem draw the line in the wrong place for where "Enterprise" begins.

I suspect this person's fears may be similar. The issue isn't that they'll offer enterprise, the issue is that they'll carve up the non-enterprise version as a differentiator.

Inevitably, and I've seen this before, the non-enterprise version loses all steam because time and effort have to be focused on the enterprise customers, and feature parity can't be maintained because those differentiators have to show value in the enterprise offering.

Those OSS users who built the community and contributed to your product for years end up having been beta testers, unceremoniously ushered out to find an alternative.

Elastic for example made the mistake of making "secure" (by default) an "Enterprise" feature of Elastic Stack, then Amazon came along and ate their lunch.

For me, I've seen this enough not to worry; if they go "south" in this respect, there are alternatives; and failing that, there's the minimalist approach of plain git.

Re: Open source sustainment and the future of Gitea

#60

Post by IshKebab »

slbtty wrote: post #9
simonw wrote: 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.

There is absolutely nothing that stops anyone from forking the project.

There's nothing literally stopping someone click "fork" on GitHub. There are tons of things that make it difficult for people to create a successful forked version that people use and contribute to.

Though in this case I guess they could just use Gogs anyway.

Post reply on HN