6 ms·
While the seeming lack of communication from the Gitea owners (see the Gitea open letter) is a bit worrying, it does seem a bit premature to fork and potentiall
by TheBrokenRail 4y ago
While the seeming lack of communication from the Gitea owners (see the Gitea open letter) is a bit worrying, it does seem a bit premature to fork and potentially fragment the community before they've actually done anything.
- gtaylor 4y agoGitea itself was forked off of Gogs.
- josephcsible 4y agoGitea said they were going to make "An enhanced enterprise version" (i.e., a proprietary version). That's bad enough to warrant a fork in my book.
- joencott 4y agoIf only everyone follows ddevault's advice and starts each project with AGPL, that way no company can steal the code.
- TylerE 4y agoSo it’s stealing to use a license you don’t like? As an outsider, your posts throughout this thread come across as whiny, entitled m, and thoroughly self-serving.
- josephcsible 4y agoNo. Using a pushover license instead of the AGPL is like not locking your door, and using other people's free work in your own non-free product is stealing from the commons.
- deleted 4y ago[deleted]
- joencott 4y agoToday the for-profit company released a code dump for the implementation of an integrated CI/CD server. This was worked on in secret for months by multiple people with no say from the community. Gitea should work with Woodpecker for closer integration, not build one by itself. There is no incentive for the company to support alternative CI/CD
- ofrzeta 4y agoIt's the first time I hear of Woodpecker https://woodpecker-ci.org/ https://woodpecker-ci.org/ And I thought I knew the CI/CD ecosystem fairly well. Now I learned that it's a fork of Drone https://www.drone.io/ https://www.drone.io/ Oh, the irony.
- joencott 4y agoYou should try it, Codeberg uses it for their public CI/CD
- shamiln 4y agoWhy should Gitea/Forejo lock themselves into a CI product such as Woodpecker, which could, like Drone, be purchased out? Creating standards would be better, but in the lack of, a closely tied CI/CD or runner or whatever would be sufficient. Right now, even the Gitea/Gogs/Forgejo ecosystem is fragmented. The latter fork exists, but I don't see how it's different from Foregjo and I have no inclination to believe that it will be optimised for codeberg's use case beyond others, but now I do ask - if Gitea implements functionality such as CICD / run pipelines, will Forgejo keep that or strip it out of their fork, if they maintain upstream syncs? Is there even a document about what the product aims are? If they're just going to maintain Gitea sync without adding functionality, why should I even look at it, which is likely to fall out of sync with Gitea?
- ViViDboarder 4y agoSorry, why should they work with Woodpecker? I like the project, but options are generally good. For example, Why work on Woodpecker? Why not Jenkins?
- isitmadeofglass 4y agoThings being what they are, gitea is essentially the form, and this is the continuation of the existing open source model. Gitea(Tm) is trying to fragment the community by creating a company, but this fork is just about building a great open source product. If anyone at Gitea(Tm) is seriously afraid of fragmenting the community they are free to contribute to the open source product just like everyone else, but the open source community is naturally not free to engage in anything on behalf of the company.