Live data from Hacker News

Dear open-source maintainers, a letter from GitLab

about.gitlab.com

291–300 of 325 posts

Re: Dear open-source maintainers, a letter from GitLab

#291
post #9

With VideoLAN, we're not on github, but I believe we fit the 'large open source project' description. We host VLC, FFmpeg, x264 and quite a few related libraries. For VLC and all related VideoLAN projects, we're moving to our own instance of GitLab hosted on our infrastructure. And to be honest, it's quite good, but a few stuffs are ridiculously limited, to the point that some people in the community are resisting th…

Can I just take this moment to say I love VLC; it's one of the best and most reliable programs ever; it does EXACTLY what I want 100% of the time and I am always astounded to discover some neat feature that fits some odd need I have. To you and your team, thank you so much for making it so effortless to watch so many different things without having to worry about formats, codecs, subtitles, audio tracks being off, etc etc etc. Thank you so much.

Re: Dear open-source maintainers, a letter from GitLab

#292
post #289
post #212

Earlier quoted context omitted.

That makes sense and we want to make sure GitLab CE is a great solution for open source projects. If there is an EE feature that is would come up frequently in these conversations we would not hesitate to open source it.

this is probably not the right forum to express this on, but it's what's in front of me right now and it's topical, so here it goes: I have seen the feature of being able to customize the login screen come up in discussions about gitlab come up so many times, in so many places, and I usually see it met with "EE feature" or a community member saying something like "gitlab is open source just change the files on your s…

Makes sense, this was also requested by the VideoLAN people in https://news.ycombinator.com/item?id=10923688

I've made https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 to discuss.

Re: Dear open-source maintainers, a letter from GitLab

#296
post #111
post #9

With VideoLAN, we're not on github, but I believe we fit the 'large open source project' description. We host VLC, FFmpeg, x264 and quite a few related libraries. For VLC and all related VideoLAN projects, we're moving to our own instance of GitLab hosted on our infrastructure. And to be honest, it's quite good, but a few stuffs are ridiculously limited, to the point that some people in the community are resisting th…

We would love to help you to host VideoLAN on a on-premises GitLab instance. Thanks for raising the issues you did. 1. Our EE version has the function share project with other groups http://doc.gitlab.com/ee/workflow/share_projects_with_other_... If this is essential for you we'll give you a free lifetime license for GitLab EE. 2. You can add custom labels on issues and the searches can be stored in urls that you can…

Wanted to add that we'll put the custom landing page and logo in Community Edition based on the conversation in this HN post, see https://gitlab.com/gitlab-org/gitlab-ce/issues/11489

Re: Dear open-source maintainers, a letter from GitLab

#297
post #292
post #289

Earlier quoted context omitted.

this is probably not the right forum to express this on, but it's what's in front of me right now and it's topical, so here it goes: I have seen the feature of being able to customize the login screen come up in discussions about gitlab come up so many times, in so many places, and I usually see it met with "EE feature" or a community member saying something like "gitlab is open source just change the files on your s…

Makes sense, this was also requested by the VideoLAN people in https://news.ycombinator.com/item?id=10923688 I've made https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 to discuss.

Our CTO and CRO gave their approval, we'll open source the branded login page.

Re: Dear open-source maintainers, a letter from GitLab

#298
post #123
post #78

Earlier quoted context omitted.

Yet, there is still differences. Allowing only "fork" is a good and easy thing. Having a fork that delete everything and start a new projet is easy to detect and label as spam. (there will always be abuses, but it's okay as long as you can mitigate/moderate)

I'd think it's pretty easy to have a policy that says "only VLC forks or VLC-related projects". What if someone wants to pull out part of VLC into its own library?

I'll say it is legit to be hosted on gitlab.videolan.org (edit typo)

Re: Dear open-source maintainers, a letter from GitLab

#299
post #279

Earlier quoted context omitted.

I'm primarily a Ruby developer, but my current gig has me working exclusively in PHP (and worse yet, Wordpress). PHP as a language is actually pretty stellar these days. There are things about it that I dislike, but there has been a lot of recent work put in to improving the language. I'm always finding nice features. Really the place that PHP is lacking is on the tooling/ops side of the projects built on top of it.…

> A lot of what I have to work with still seems to be 15 years old. Like what?

Ops practices of WordPress hosting companies. Pantheon is one of the few exceptions to this, so props to them.

Management panels of hosting companies.

UltraDNS's website.

Salesforce.

Re: Dear open-source maintainers, a letter from GitLab

#300
post #267
post #259

Earlier quoted context omitted.

Cool, I created an issue https://gitlab.com/gitlab-com/operations/issues/43

Thanks, subscribed. When Google Code shut down, I migrated the IPvFoo[1] source code to GitHub, but it felt dirty using an IPv4-only service for that purpose; I'll probably move again to GitLab if they follow through. [1] https://github.com/pmarks-net/ipvfoo

We will, Ian is already working on it.
Post reply on HN