While I applaud the initiative of Gitlab to opensource Gitter I think the target audience for self hosting is rather small. I think alternatives like Zulip or Mattermost are probably better suited for most organizations. I am however interested to see if the community starts making the "main instance" (gitter.im) better. Interested to know what the Gitlab / Gitter guys and gals think what the target audience is.
Gitter is open source
21–30 of 176 posts
Re: Gitter is open source
#22If you go through the commit history you can see that they removed a lot of secret keys from the repo. What if the main reason why people don't want to opensource their project is because they don't know how to use their secret keys without including them in the repo ?
Andrew, co-founder of Gitter here. Removing secrets was a lot of work - more than I expected - while we open-sourced the product. I agree with your sentiment though. Handling secrets in a codebase is not something that it currently easy or standardised. As an aside, BFG Repo Cleaner really helped a lot with cleaning things up: https://rtyley.github.io/bfg-repo-cleaner/
Re: Gitter is open source
#23Re: Gitter is open source
#24Asking users to run mongo, es, neo4j, and redis is a tall order. Mattermost just needs (AFAIK) a relational database. Also, less relevant but the Gitlab UI has far too much wasted whitespace. Like 85% of the page is navigation. I like open source competitors to incumbents but maybe just copy Github here - no one is gonna say anything.
And why do I always need to scroll down to see the project README?
Re: Gitter is open source
#25As an aside, I badly miss the Github language statistics in gitlab repositories. This is one of the crucial info for any developer browsing through new repos and it is very counter-intuitive to have this info hidden from homepage.
Re: Gitter is open source
#26Asking users to run mongo, es, neo4j, and redis is a tall order. Mattermost just needs (AFAIK) a relational database. Also, less relevant but the Gitlab UI has far too much wasted whitespace. Like 85% of the page is navigation. I like open source competitors to incumbents but maybe just copy Github here - no one is gonna say anything.
> Also, less relevant but the Gitlab UI has far too much wasted whitespace. And why do I always need to scroll down to see the project README?
Solution: https://gitlab.com/gitlab-org/gitter/webapp/blob/master/READ...
Re: Gitter is open source
#27Earlier quoted context omitted.
> Also, less relevant but the Gitlab UI has far too much wasted whitespace. And why do I always need to scroll down to see the project README?
You mean exactly like with Github? Solution: https://gitlab.com/gitlab-org/gitter/webapp/blob/master/READ...
PS: yes, same problem with github
Re: Gitter is open source
#28Asking users to run mongo, es, neo4j, and redis is a tall order. Mattermost just needs (AFAIK) a relational database. Also, less relevant but the Gitlab UI has far too much wasted whitespace. Like 85% of the page is navigation. I like open source competitors to incumbents but maybe just copy Github here - no one is gonna say anything.
> Also, less relevant but the Gitlab UI has far too much wasted whitespace. And why do I always need to scroll down to see the project README?
Files (209 MB) / Commits (44,194) / ... / Readme / MIT License / Contribution guide / ...
Re: Gitter is open source
#29Asking users to run mongo, es, neo4j, and redis is a tall order. Mattermost just needs (AFAIK) a relational database. Also, less relevant but the Gitlab UI has far too much wasted whitespace. Like 85% of the page is navigation. I like open source competitors to incumbents but maybe just copy Github here - no one is gonna say anything.
> Also, less relevant but the Gitlab UI has far too much wasted whitespace. And why do I always need to scroll down to see the project README?
Re: Gitter is open source
#30Earlier quoted context omitted.
> Also, less relevant but the Gitlab UI has far too much wasted whitespace. And why do I always need to scroll down to see the project README?
Personally, I'm finding myself far more often interested in project's main files/dirs update dates that project's readme.