On Fri, 27 Jun 2025 at 13:42, Niall Pemberton <niall.pember...@gmail.com> wrote: > > On Fri, 27 Jun 2025 at 12:52, sebb <seb...@gmail.com> wrote: > > > On Fri, 27 Jun 2025 at 12:39, Niall Pemberton <niall.pember...@gmail.com> > > wrote: > > > > > > On Fri, 27 Jun 2025 at 12:02, Niall Pemberton <niall.pember...@gmail.com > > > > > > wrote: > > > > > > > On Fri, 27 Jun 2025 at 11:02, Arnout Engelen <enge...@apache.org> > > wrote: > > > > > > > >> Hi, > > > >> > > > >> To make it clearer that 'Dormant' components are not actively > > maintained, > > > >> I > > > >> think it would be good if we marked GitHub repo's for those as > > 'Archived'. > > > >> AFAICS those are: > > > >> > > > >> https://github.com/apache/commons-chain > > > >> https://github.com/apache/commons-functor > > > >> https://github.com/apache/commons-ognl > > > >> https://github.com/apache/commons-proxy > > > >> > > > >> I've filed https://issues.apache.org/jira/browse/INFRA-26952 > > > > > > > > > > > > I'm +0 on this - seems pretty clear from the README files in GitHUb > > that > > > > these components are no longer maintained. > > > > > > > > If this is going to be done though, then we need to fix any issues > > before > > > > they're archived. I just corrected a couple of issues for Chain, but > > > > theres probably a few other things todo: > > > > - remove obsolete references to Twitter & IRC > > > > - remove the "Contributing" & "Donations" sections, since it won't be > > > > possible to create PRs etc once the repos are archived > > > > > > > > > > One more thought - we won’t be able to make changes to fix issues or > > > changes to the L&F of these components websites once they’re archived. > > > > The websites are not served from GH, rather from SVN, e.g. > > > > https://svn-master.apache.org/repos/infra/websites/production/commons/content/dormant/commons-ognl/ > > > > That can be populated from anywhere, so it would be possible to clone > > the source locally and rebuild the site in order to make site fixes. > > > No, this would be a mistake to allow this.
That's a policy decision; my comment was about technical possibility. > Zero visibility to the PMC of > the changes and a nightmare to ensure subsequent changes don’t overwrite a > previous “invisible” fix. The source could be cloned as a private repo and used to fix the website. This would provide visibility to the PMC. > Or indeed just fix any issues directly in SVN (as has been done > > sometimes to quickly fix broken links) > > > Not a viable long term maintenance solution as it would remove the ability > to “generate” the site from source. Indeed, that was not intended as a long-term solution. Note that regeneration of old sites can be problematic because of software updates... > For me it’s implicit that archiving these repos means that the component > websites will no longer be maintained. > > Niall > > Sebb > > > Niall > > > > > > > > > > > > > > > > Niall > > > > > > > > > > > > > > > >> > > > >> > > > >> > > > >> Kind regards, > > > >> > > > >> -- > > > >> Arnout Engelen > > > >> ASF Security Response > > > >> Apache Pekko PMC member, ASF Member > > > >> NixOS Committer > > > >> Independent Open Source consultant > > > >> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
