<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Good work! I think this change could
bring some more developers to xfce. Allowing pull-requests makes
participation much more simple.<br>
<br>
... looking forward to possibly migrate bz --> gittea as well
some day .. hate it that I cannot fix my own typos in comments ;)<br>
<br>
Cheers,<br>
Alex<br>
<br>
On 08.10.2017 00:36, Simon Steinbeiss wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAApLaz3oNFju=vtSEKd0Ue6cfeXFF-L5Ry+m92rX7QPJqbKe-Q@mail.gmail.com">
<div dir="ltr"><font color="#212121">PS: Oh, and here's the link
to the wiki page summarizing some of our thoughts: <a
href="https://wiki.xfce.org/infra/nextgen"
moz-do-not-send="true">https://wiki.xfce.org/infra/nextgen</a></font>
<div><font color="#212121">and the current POC / staging
instance that I forgot in my previous email: </font><a
href="https://gitea.xfce.alteroot.org/xfce"
moz-do-not-send="true">https://gitea.xfce.alteroot.org/xfce</a><br>
<br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sun, Oct 8, 2017 at 12:21 AM Simon
Steinbeiss <<a href="mailto:simon@xfce.org"
moz-do-not-send="true">simon@xfce.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi everyone,
<div><br>
</div>
<div>there have been discussions around our current
infrastructure - be it hardware or software - and
following Gnome's discussions around moving from
cgit/gitolite+bugzilla to something that feels a
little less dated and provides more integrations (they
are ogling at Gitlab) we have also had several
discussions of our own.</div>
<div><br>
</div>
<div>We have started writing up requirements for the new
infrastructure (again, both hardware and software) and
have started looking into candidates more concretely.</div>
<div>For the software one hard requirement is
self-hosting, a few more are features we would like to
either get or not lose over the status quo. Of the
candidates we took into closer consideration (Gitlab
and Gitea) we have been leaning towards Gitea. In
short, Gitea is a very Github-like (some say it's a
clone), lightweight piece of software that provides a
Git server (with collaboration features like
pull-requests), a very simple issue tracker (like the
one of Github) and a very simple internal wiki. The
latter two components can either be disabled or
redirected at external services.</div>
<div><br>
</div>
<div>In order not to get stuck in endless discussions
(which could be dragged out by the fact that people
have lives and can't always participate in the
discussions) I would like to propose that we try to
move ahead with a switch to Gitea.</div>
<div>I know that feels a little dramatic and I'm hoping
to also spark some discussion here, but it's not as
brutal as it may sound.</div>
<div><br>
</div>
<div>The current proposal for phase 1 would be the
following:</div>
<div>1) Replace cgit/gitolite with Gitea (for browsing
and administering Git repos)</div>
<div>2) Keep Bugzilla and Dokuwiki for their purposes
(you can see the integration in the instance Skunnyk
set up)</div>
<div><br>
</div>
<div>The migration and setup of the Xfce repositories
can be automated quite nicely (Skunnyk has already
done that) so that part is not a real blocker.</div>
<div>What we have to figure out to some extent is</div>
<div> * how to manage permissions (there are
organisations, teams and per repository permissions as
different layers for which we will need a concept)</div>
<div> * how to best migrate/set up the hooks (both for
the Github mirror and the bugzilla comments)</div>
<div> * to what extent to allow everyone to register and
create forks (what private repos are in cgit atm) in
order to submit pull requests</div>
<div><br>
</div>
<div>For the future Gitea still provides the following
points (imo):</div>
<div> * issue tracking (migrating away from Bugzilla)</div>
<div> * release management (potentially replacing <a
href="http://archive.xfce.org" target="_blank"
moz-do-not-send="true">archive.xfce.org</a> by
uploading signed tarballs to Gitea)</div>
<div> * continuous integration integration (yeah, double
the integration!)</div>
<div> * considering whether we ever want to use the
internal wiki for anything</div>
<div><br>
</div>
<div>So far we haven't really found anything where Gitea
lacks over cgit/gitolite feature-wise. (Even the
hyperlinks on Bugzilla issues work.) However this does
not mean that we will potentially find any drawbacks
of this situation. The good news is that switching
back is not very painful, as far as we can tell. As
only Git management moves to Gitea that's the only
part that would have to be switched back.</div>
<div><br>
</div>
<div>Finally I would argue that it would be beneficial
to try this out for real (instead of toying with a
staging instance over a longer period of time) because
we already have limited resources, so toying with
stuff is usually something people don't have too much
time for anyhow. While I can easily push to both cgit
and Gitea, this doesn't mean I'll be familiar with the
features or way of working of either (as I'm in both
cases only using the Git command-line locally as my
main interaction).</div>
<div><br>
</div>
<div>So anyway, that's the proposal in full. I know it
was/is a lot, but thanks for reading and even more so
for commenting and a healthy discussion.</div>
<div><br>
</div>
<div>Cheers</div>
</div>
<div dir="ltr">
<div>Simon</div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Xfce4-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xfce4-dev@xfce.org">Xfce4-dev@xfce.org</a>
<a class="moz-txt-link-freetext" href="https://mail.xfce.org/mailman/listinfo/xfce4-dev">https://mail.xfce.org/mailman/listinfo/xfce4-dev</a></pre>
</blockquote>
<p><br>
</p>
</body>
</html>