On Sat, Nov 14, 2020 at 05:53:46PM +0000, Lorenzo Miguel Tareszkiewicz Rezende wrote:
> > We have our own infrastructure that works well for us. It is, however,
> > public: anyone can access it. We'd rather not outsource our downtime to
> > another organisation.
> It's just a suggestion, gitlab offers a self hosted platform. if you go to <https://gitlab.gnome.org/> you can see an example. As a person who search through your source code and documentation I find it really confusing.
> Would it be asking a lot if you change the repository to a SelfHosted solution? if you do not have anyone to work on it i would be happy to offer my work.
Yes. We are happy with what we have, we have no plans to move to
something else. There's simply no advantage and lots of disadvantages,
from our point of view. If anything, GitLab isn't usable from NetSurf.
But there is also the resource usage, the time spent administering it,
the security vulnerabilities that need to be kept on top of, and the
fact it doesn't actually provide anything we want or need.
> I think that switching to this type of infrastructure can add a lot to things like:
> -> Divide the source code into smaller repositories to divide the work
We already do this and this is not a feature unique to GitLab/Hub.
> -> Create teams and separate everyone's work
We already do this and this is not a feature unique to GitLab/Hub.
> -> Use forks to increase the productivity of the team's work
We already do this and this is not a feature unique to GitLab/Hub.
> -> WebIDE
We don't want to do this.
> -> several free resources
What we're using already uses free resources.
> etc.
>
> More information about it here https://about.gitlab.com/blog/2018/04/20/gitlab-tiers/#gitlab-self-hosted
>
> As I don't know how you work, I don't know if it would be an advantage for you to make this exchange, but I am confident that it would be great for new contributors like me, who are easily lost by the documentation.
There are lots of projects that do not use GitLab or GitHub and are
wildly successful. For example, Linux. We like the way we currently
work.
> If you already host your sites and repositories, it would be a small change to switch to gitlab self-hosted.
It really isn't a simple change, I can say this as somebody who has set
up GitLab in the past and knows how our current infrastructure works.
> I can give you a demonstration of what it would look like if you give me permission.
>
> [https://about.gitlab.com/images/tweets/gitlab-tiers.png]<https://about.gitlab.com/blog/2018/04/20/gitlab-tiers/#gitlab-self-hosted>
> New names for GitLab self-hosted pricing tiers | GitLab<https://about.gitlab.com/blog/2018/04/20/gitlab-tiers/#gitlab-self-hosted>
> At GitLab, iteration is one of our core values. We've recently iterated on the names of our self-hosted pricing tiers, so Marcia and I got together and wrote this post to catch you up on the current options. We'll explain each tier, and share how to figure out which features your subscription gives you access to.
> about.gitlab.com
>
> [https://gitlab.gnome.org/assets/gitlab_logo-7ae504fe4f68fdebb3c2034e36621930cd36ea87924c11ff65dbcb8ed50dca58.png]<https://gitlab.gnome.org/>
> Groups · Explore<https://gitlab.gnome.org/>
> Welcome to GNOME's integrated development platform, powered by GitLab
> gitlab.gnome.org
B.
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
No comments:
Post a Comment