+1 to archiving them. Keeping them means managing them, which includes removing code contributed under a disallowed or different license.
Both of these are useful concepts for the project; archiving allows us to bring them back later if someone is available to manage them. James Dailey On Thu, Jul 2, 2026 at 10:42 PM Aman Mittal <[email protected]> wrote: > Hi, Adam > > It seems one of the repo > > > https://github.com/apache/fineract-open-banking-app/?tab=MPL-2.0-1-ov-file > > Does not conform to Apache licence norms. I think it's better to archive > this and add a Legal Warning that these are POCs. If any PMC member wishes > to maintain it, that is a different story. > > Regards, > Aman > > On Wed, May 27, 2026 at 10:01 PM Aman Mittal <[email protected]> > wrote: > >> Hi Adam, >> >> Archiving seems to be best option here for these two so >> +1 for that. >> >> But curious about their use cases. >> >> What are the intended purpose. Maybe these repos are for poc. >> >> Regards, >> Aman >> >> On Wed, 27 May, 2026, 9:46 pm Adam Monsen, <[email protected]> wrote: >> >>> Looks like we have a couple of repositories with no activity in years: >>> >>> https://github.com/apache/fineract-credit-scorecard/ >>> https://github.com/apache/fineract-open-banking-app/ >>> >>> Shall we archive those? >>> >>> I've been ignoring them but a PR landed the other day >>> <https://github.com/apache/fineract-open-banking-app/pull/2>. I'd >>> rather these repositories are archived to avoid any review effort. >>> >>> If we're OK with archiving, I think the process is to file a ticket with >>> ASF infra. >>> >>
