Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Haxx will stop hosting most Rockbox services after 2020

Re: Haxx will stop hosting most Rockbox services after 2020

From: Baptiste BARON via rockbox-dev <rockbox-dev_at_cool.haxx.se>
Date: Sun, 15 Mar 2020 11:13:36 +0100

Le 13/03/2020 ā 09:31, Daniel Stenberg via rockbox-dev a écrit :
> On Sat, 8 Feb 2020, Daniel Stenberg via rockbox-dev wrote:
>
> Hello,
>
> This is just a gentle reminder that there has now been over a month
> since we made everyone aware of the coming service
> shutdown/transition. Since then, scorche has also advertised that he
> too shuts down the Rockbox related services he runs, at the same time.
>
> I will again urge interested people to start this transition ASAP.
> There will be no deadline extension.
>
>> As mentioned in the subject, the Haxx team (me, Björn, Linus and
>> Kjell) will stop hosting most Rockbox related services on January 1st
>> 2021. It should give everyone plenty of time to find new places and
>> alternatives for everything that needs to survive.
>
>>  https://github.com/Rockbox/rockbox/wiki/Transition
>

Hello, people.

The https://github.com/Rockbox/rockbox/wiki/Transition page gives an
insight of what is needed in terms of resources.

I'd like to bring my advice, point after point.

First of all, I pronounce myself in favor of GitHub for "code hosting",
and self-hosting for "content delivery". What I mean is that we can
still have code backups in the cloud, which is much more secure than
code that may disappear if the main provider stops hosting the services
altogether (which might happen with Rockbox now...)

* Git : I see that the last commits were made on git.rockbox.org, and
that the github mirror is still a mirror. We might switch ASAP and
consider the active version to be the GitHub one, and the passive one to
be the git.rockbox.org one.

* Themes and Translate : Can someone mirror them to a GitHub repo,
separate from the main Rockbox one (like
github.com/Rockbox/rockbox-themes and
github.com/Rockbox/rockbox-translate) ? We might have a look at the code
and modernize it later, but the main thing is to at least have a version
mirrored in the cloud ASAP.

*Forums : Same as above, dump the database and mirror the forums on a
third GitHub branch (github.com/Rockbox/rockbox-forums). We might ensure
a transition with an update later on.

* Gerrit : Is it easy to setup once the main repo is GitHub ? What is
used for the CI ? Can the CIs be migrated as well ? May we see the code
somewhere ?

* Flyspray : Development for Flyspray has resumed some time ago, most
up-to-date version is 1-0rc9, per the website. They also have a GitHub
repo as well. Can we see the code for the current FlySpray used for
Rockbox, so we can test migrations ?

* Daily builds : Host the scripts on GitHub as well ?

* Wiki : Is it hard-coded or based on an existing framework like
DoKuWiki or MediaWiki ?

As for the self-hosting, I am no dev, but I am a sysadmin. There is a
French provider with cheap, but powerful servers, and an unlimited
bandwidth. Given what is indicated in the "Resource Overview" heading,
they might suffice to host all of your services.

Here is a link : https://www.soyoustart.com/us/essential-servers/

Those are dedicated servers and not VPS, it seems, which is much more
convenient. And, on the top of that we have unlimited bandwidth. (Data
consumption is generally not charged in France, except for 4G data).

Thank you all for your advice.

Regards,
Baptiste B.
Received on 2020-03-15


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa