Re: Sunsetting backports.wiki.kernel.org
Johannes Berg <[email protected]> Fri, 11 Oct 2024 16:28:43 +0200
| Newsgroups | org.kernel.vger.backports |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 2024-10-11 at 10:15 -0400, Konstantin Ryabitsev wrote: > On Fri, Oct 11, 2024 at 02:01:41PM GMT, Johannes Berg wrote: > > > Please let me know how you would like to proceed. If I don't hear bac= k from > > > anyone in the next few days, I will configure the backports.docs.kern= el.org > > > with the current converted contents and redirect backports.wiki.kerne= l.org > > > there. > >=20 > > Maybe for now it'd make sense to move the repo into the backports/ grou= p > > on kernel.org? Or are you trying keep everything together in > > docs/docsko/? >=20 > Yes, it has to stay under docs/docsko for the triggers to work properly. OK, right. > > 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? >=20 > I've granted access to that repository to the @backports group, so you sh= ould > now be able to push changes there. Thanks. > > Honestly, I have very little opinion on this - even the few changes tha= t > > backports is still seeing we're not taking much care of the wiki these > > days. Maybe Hauke has any further thoughts. >=20 > I'm perfectly happy to keep the source where it is. The only downside com= pared > to hosting it on readthedocs.io is that propagating changes takes much lo= nger > (10-15 minutes). Let's just leave it then. Not that it was hard to do this all with github for the wireless one, but I feel at this point, unless some community re-forms here, it's mostly left as a historical artifact. johannes