[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Update on Status of Gitlab Migration
From: Ömer Fadıl USTA <omerusta () gmail ! com>
Date: 2020-04-13 20:54:49
Message-ID: CAATbBR3M-s2M1+t_kisvHeQ83ZCS3mw_D9nbFbChbabQq46V0Q () mail ! gmail ! com
[Download RAW message or body]
keeping it as invent also give us opportunity to change if we need to move
our systems to someother ecosystem but keeping its name same. so my 2 cents
for going with invent name
On Mon, Apr 13, 2020, 21:31 Ben Cooksley <bcooksley@kde.org> wrote:
> On Tue, Apr 14, 2020 at 3:35 AM Nate Graham <nate@kde.org> wrote:
> >
> > On 4/13/20 4:44 AM, Albert Vaca Cintora wrote:
> > > Regarding this: is the subdomain going to stay invent.kde.org once we
> > > have officially moved? I find it's a bit confusing to use that instead
> > > of gitlab.kde.org
> >
> > I agree. gitlab.kde.org would make more sense to me, mirroring
> > phabricator.kde.org.
> >
>
> There is no intention to change the name from invent.kde.org.
>
> We have a long precedent of not using the name of the software for the
> name in DNS, and Gitlab is continuing with this, for example:
> - bugs.kde.org is run by Bugzilla
> - dot.kde.org is run by Drupal
> - techbase.kde.org is run by Mediawiki
> - conf.kde.org is run by Frab
> - reimbursements.kde.org is run by travel-support-program
> - websvn.kde.org is run by ViewVC
> - build.kde.org and binary-factory.kde.org are both run by Jenkins
> - stats.kde.org is run by Matomo (formerly Piwik)
> - survey.kde.org is run by Limesurvey
>
> For essentially all of the above, calling it after the software
> running it makes no sense, and given that in some cases we have
> multiple instances would have made things more confusing
> (jenkins1.kde.org and jenkins2.kde.org anyone?)
>
> Phabricator and Reviewboard were the only ones to not follow this
> rule, and that was an error on our part.
>
> Given that there is a popular instance at Gitlab.com, referring to
> ours as "KDE Invent" is more likely to ensure newcomers are not
> confused (as they may not be aware that you can setup an instance of
> Gitlab on your own systems)
>
> Regards,
> Ben
>
[Attachment #3 (text/html)]
<div dir="auto">keeping it as invent also give us opportunity to change if we need to \
move our systems to someother ecosystem but keeping its name same. so my 2 cents for \
going with invent name</div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Mon, Apr 13, 2020, 21:31 Ben Cooksley <<a \
href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">On Tue, Apr 14, 2020 at 3:35 AM Nate Graham <<a \
href="mailto:nate@kde.org" target="_blank" rel="noreferrer">nate@kde.org</a>> \
wrote:<br> ><br>
> On 4/13/20 4:44 AM, Albert Vaca Cintora wrote:<br>
> > Regarding this: is the subdomain going to stay <a \
href="http://invent.kde.org" rel="noreferrer noreferrer" \
target="_blank">invent.kde.org</a> once we<br> > > have officially moved? I \
find it's a bit confusing to use that instead<br> > > of <a \
href="http://gitlab.kde.org" rel="noreferrer noreferrer" \
target="_blank">gitlab.kde.org</a><br> ><br>
> I agree. <a href="http://gitlab.kde.org" rel="noreferrer noreferrer" \
target="_blank">gitlab.kde.org</a> would make more sense to me, mirroring<br> > <a \
href="http://phabricator.kde.org" rel="noreferrer noreferrer" \
target="_blank">phabricator.kde.org</a>.<br> ><br>
<br>
There is no intention to change the name from <a href="http://invent.kde.org" \
rel="noreferrer noreferrer" target="_blank">invent.kde.org</a>.<br> <br>
We have a long precedent of not using the name of the software for the<br>
name in DNS, and Gitlab is continuing with this, for example:<br>
- <a href="http://bugs.kde.org" rel="noreferrer noreferrer" \
target="_blank">bugs.kde.org</a> is run by Bugzilla<br>
- <a href="http://dot.kde.org" rel="noreferrer noreferrer" \
target="_blank">dot.kde.org</a> is run by Drupal<br>
- <a href="http://techbase.kde.org" rel="noreferrer noreferrer" \
target="_blank">techbase.kde.org</a> is run by Mediawiki<br>
- <a href="http://conf.kde.org" rel="noreferrer noreferrer" \
target="_blank">conf.kde.org</a> is run by Frab<br>
- <a href="http://reimbursements.kde.org" rel="noreferrer noreferrer" \
target="_blank">reimbursements.kde.org</a> is run by \
travel-support-program<br>
- <a href="http://websvn.kde.org" rel="noreferrer noreferrer" \
target="_blank">websvn.kde.org</a> is run by ViewVC<br>
- <a href="http://build.kde.org" rel="noreferrer noreferrer" \
target="_blank">build.kde.org</a> and <a href="http://binary-factory.kde.org" \
rel="noreferrer noreferrer" target="_blank">binary-factory.kde.org</a> are both run \
by Jenkins<br>
- <a href="http://stats.kde.org" rel="noreferrer noreferrer" \
target="_blank">stats.kde.org</a> is run by Matomo (formerly \
Piwik)<br>
- <a href="http://survey.kde.org" rel="noreferrer noreferrer" \
target="_blank">survey.kde.org</a> is run by Limesurvey<br> <br>
For essentially all of the above, calling it after the software<br>
running it makes no sense, and given that in some cases we have<br>
multiple instances would have made things more confusing<br>
(<a href="http://jenkins1.kde.org" rel="noreferrer noreferrer" \
target="_blank">jenkins1.kde.org</a> and <a href="http://jenkins2.kde.org" \
rel="noreferrer noreferrer" target="_blank">jenkins2.kde.org</a> anyone?)<br> <br>
Phabricator and Reviewboard were the only ones to not follow this<br>
rule, and that was an error on our part.<br>
<br>
Given that there is a popular instance at Gitlab.com, referring to<br>
ours as "KDE Invent" is more likely to ensure newcomers are not<br>
confused (as they may not be aware that you can setup an instance of<br>
Gitlab on your own systems)<br>
<br>
Regards,<br>
Ben<br>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic