[arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)

[Pierre Schmitz]

Hi all. I feel bad about this. I was not transparent at all about my
plans and got lost in a pile of projects which are only slowly
progressing. I started improving dbscripts to make it easier to work
with; which led to creating a Docker base image to be able to test the
latter. Most of my free time then went into a huge refactoring of
archlinux.de to finally extract and improve on the pkgstats backend.
Now I am drowning in hundreds of arch related emails and "things I
should do".

I would welcome help on dbscripts a lot. I had a look at those git
attempts in the past but in the end they were not easily mergable.
Maybe a few suggestions:
* Let's use github for Pull Requests
* Make sure PRs are small enough to be reviewable in let's say within an hour
* New code needs to be tested (Travis build needs to pass)
* Code Coverage should be as close to 100% as possible and useful

If we prefer a complete rewrite (e.g. when moving from Bash to e.g.
Go) where small pull requests are not possible and we need to start
from scratch, I would still strongly recommend my suggestions above;
esp. those about testing.

Greetings,

Pierre

On Mon, Jan 29, 2018 at 7:29 PM, Gaetan Bisson via arch-dev-public
<arch-dev-public at archlinux.org> wrote:
> [2018-01-29 16:51:54 +0100] Florian Pritz via arch-dev-public:
>> Eli offered to take the lead on getting that done and also later
>> migrating us to git instead of svn. If there are no objections I'll help
>> where necessary and give him access to the dbscripts and devtools repos
>> in two weeks.
>
> That sounds great!
>
> --
> Gaetan