mydigitalself

In just a few weeks, most of which was familiarising myself with Bubble, I was able to build a pretty polished responsive web app.

If you're interested in what you can build with Bubble, check it out - I'd love to get feedback.

And if you're so inclined, I'm on Product Hunt today too.

https://www.producthunt.com/posts/troupe

What's wrong with the current mentions plugin and what's preventing you from writing a new one or improving the existing one with a PR?

I wouldn’t imagine that to be intentional, possibly upstream infrastructure is blocking somewhere.

Thanks, glad you've noticed the improvements. We've still got more to do, but it's been an important part of every release for a while now.

Hi, sorry you haven't noticed any improvements. We've been chipping away at performance for the last 6 months and have made some pretty noticeable improvements in various areas of the application.

For example, the average response time of an issue page has come down from 2.5s to 750ms over the last 6 months.

We still have a lot to do, but we're getting there.

We've been working quite a bit of our NFS storage topology and have recently introduced some remediation to prevent outages based on NFS availability. Previously an NFS failure would have pretty wide-reaching implications, now it's a lot more isolated.

We're also working on an entirely new storage architecture for scaling and are slowly rolling this out. You can see more here: https://gitlab.com/gitlab-org/gitaly

We've been spending a lot of effort making GitLab.com more performant over the course of this year. We still have some ways to go, but every release includes performance enhancements based on performance data from GitLab.com.

We no longer see GitLab.com as a mechanism to stress test GitLab and we're certainly pushing hard to improve performance and availability.

Yip, GitLab has subgroups that allow you to organise projects like that, although it's not available for /user namespace, so you can create

groupa/subgroup/repo groupa/subgroup/subgroup/subgroup/etc/repo

https://docs.gitlab.com/ce/user/group/subgroups/

This feature is available for free on GitLab.com and is available for free in self-hosted GitLab CE

Hi there, those features are all available for free for public projects, it's only for private projects where we limit some functionality.

Thank you for the kind words, we've been working hard on improving the UI (have you tried the latest update in https://gitlab.com/profile/preferences#new-navigation) and have tried to make our free offering as valuable as possible as well as treating our existing free customers respectfully.

As Gitter was originally built as closed source with a team of people working exclusively on Gitter, this has never really been a problem for us.

This is very much v1 of the setup/instructions and would be delighted to improve them with any MRs or contributions. We'll certainly improve them ourselves over time as we get more people in less controlled environments adopting the project.

We've edited the description of the project now that has a simple explanation and a link to Gitter. Thanks for the feedback, keep it coming!

Gitter has had an IRC bridge since pretty much day 1. This allows you to connect to Gitter via any IRC client.

https://irc.gitter.im

We're actually completely overhauling the GitLab's UI https://gitlab.com/gitlab-org/gitlab-ce/issues/32794

Great question.

We're trying to achieve two things with open sourcing Gitter.

Firstly, we see Gitter as more of a community than a product. That we have nearly 1,000,000 developers coming together on the platform to talk about code and open source software where public rooms far, far outweigh private rooms, is testament to that. So we're not trying to compete with MatterMost.

What we're trying to facilitate is to allow the community and users of GitLab to contribute to the experience of the community. We've always had a very small team at Gitter and the surface area of the product is massive. This way the community can help us make it a better place by improving the product.

We also have some communities who are interested in running their own public instance entirely. Sure they could use other products, but Gitter is built community and public first and suits a lot of different needs that other products don't necessarily facilitate out of the box.

We started Gitter before React was A Thing and Marionette had a lot of the functionality we needed. We even hacked it to do server-side pre-rending and live collection binding. Topics was an experiment in how we could look to move towards react and evaluate blending technologies.

Not having started out as an open source project, this was always a major consideration.

Once we've finished fully open sourcing everything, we should look to write up our experience around the conversation, in particular, the tools we used.

Send a Merge Request ;)

Great point. We "soft launched" this yesterday so are still working on the documentation and hadn't made any official announcement yet until we've ironed out in any kinks.

Looks like HN announced it for us...

Hi there. This is something we are actively working on as part of overhauling the entire UI hierarchy.

You can follow the main issue here: https://gitlab.com/gitlab-org/gitlab-ce/issues/32794

Feel free to let us know your thoughts. This will start making it's way into the application in 9.4 (July) and will be activated through a feature toggle so people can experiment with the new UI, give us feedback and we'll iterate and improve it before we switch it over.

Hi there, thanks for the feedback.

Our UX team has grown considerably recently and this is a big area of focus for us.

In addition to small UX improvements all over the product, we are also doing a massive overhaul to the overall navigation of GitLab starting in 9.4. This work will continue behind a feature toggle for a couple of releases. You can see the work here (https://gitlab.com/gitlab-org/gitlab-ce/issues/32794) and, as always we'd love to hear your thoughts on it, free to ping me directly in that issue on @mydigitalself to discuss.

Great suggestion, I've created an issue for it: https://gitlab.com/gitlab-org/gitlab-ce/issues/31393

That's live now, thanks for your help.

https://about.gitlab.com/gitlab-com/

Sorry to hear about your issues with GitHost - feel free to share any ticket IDs and we can look into it further on our side.

We've been doing a huge amount of work on performance and availability over the last number of releases [1] and are continuing to make big advancements in our infrastructure [2] to host millions of projects on GitLab.com. Expect this to be a lot better now and in the future, especially as this marks a big step in GitLab.com's maturity.

[1] https://gitlab.com/groups/gitlab-org/issues?label_name%5B%5D... [2] https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...

GitLab as a company has had paying customers for a long time. If you take a look at our web site (https://about.gitlab.com/) you can see some amazing companies who license GitLab EE including IBM, NASA, Nasdaq, Sony and Uber to name just a few.

GitLab.com has become increasingly popular over time and we want to continue to not only provide a great self-hosted product, but also an amazing hosted (SaaS) solution.

We're currently only doing annual billing, we may look into monthly billing in the future.

The billing application is a separate app and effectively oAuths with GitLab - you should just be able to click on the login button and if you are already authenticated, grant permission to the billing app.

Interestingly, we've found little to no correlation between the number of users in a group and CI usage. Moving forward, the plans are going to be much more feature-centric than just CI minutes, hence the per user per month pricing model.

Btw, I can tell you exactly what the "Preventing Sleep" is all about. I'm 100% positive there's a bug in Chrome's WebRTC stack that causes that to happen.

Fire up Chrome, doesn't happen. Go on a Hangout, yip "Preventing Sleep".

No not the main project settings page. Settings -> Repository and it's right at the bottom, so no more scrolling than you are used to.

> non-open-source version, which we cannot use...

is it a function of cost, or otherwise?