Why 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?
shamiln|3 years ago
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?