Re: Sunsetting backports.wiki.kernel.org

>=20
> There are two ways forward:
>=20
> 1. You can clone that git repository and host it on github. This would al=
low
>    for a quick readthedocs.org integration and allow you to edit the file=
s
>    directly via the github interface. This is a very wiki-like workflow a=
nd
>    would allow you to grant access to the repository to anyone with a git=
hub
>    account, plus accept pull requests with modifications. Once you have
>    readthedocs.org integration working, we can configure it to be under t=
he
>    docs.kernel.org domain, which will allow you to remove the ads from th=
e
>    site.
>=20
> 2. Continue to host it in the current location and accept edits via patch=
es
>    sent to this mailing list.
>=20
> Please let me know how you would like to proceed. If I don't hear back fr=
om
> anyone in the next few days, I will configure the backports.docs.kernel.o=
rg
> with the current converted contents and redirect backports.wiki.kernel.or=
g
> there.

Maybe for now it'd make sense to move the repo into the backports/ group
on kernel.org? Or are you trying keep everything together in
docs/docsko/?

It probably doesn't matter anyway, I'm just not sure how permissions
would work if it's in docs/docsko/, I guess you can still give the
backport group access? Who actually does have access to the repo now?

Honestly, I have very little opinion on this - even the few changes that
backports is still seeing we're not taking much care of the wiki these
days. Maybe Hauke has any further thoughts.

johahnnes