Re:Gitea – A painless self-hosted Git service
by shakna on Sunday January 22, 2017 @07:34AM
(#13454915)
gitea was initially just a fork so development could continue - with every intention of merging it back into gogs.
However, Unknwon, responded here [0], let me point out his main reason for not merging back:
> Gitea won't be merged back to Gogs, it's not about merging work is huge and hard, it's the differences of fundamental philosophy. I personally do not like to push hard to release new features, but make code neat and clean, it's not good for business, but Gogs isn't a business, making it is what I love to do.
[0] https://github.com/gogits/gogs/issues/1304#issuecomment-1246...
Re:Gitea – A painless self-hosted Git service
by indymike on Sunday January 22, 2017 @08:42AM
(#13455138)
Success in open source is simple and hard: make useful code and let others help make it even more useful (and better). Being well funded isn't a requirement, and may be a two edged sword (docker vs rethinkdb).
Is open source about contribution or just forking? At the moment it seems the the best way to open source is to be a well funded project with tons of resources and people specifically to manage the community because of intense expectations with projects declared dead even for one week of inactivity by some users.
What I am increasingly noticing with small teams or one man projects is if the project gains some popularity some 'community' folks pop up who first place an oppressive burden of expectations on the author and then try to fork the project. There is some element of misuse of the word 'community' by a small clique of people.
Why are community expectations so high, is continuous development and an ever expanding feature set the only way to develop? I think a culture of undue pressure is being created on open source authors and projects.