This post generated no response. I’ll take that as a clue that removing the repos isn’t a problem.
Sent from Gmail Mobile On Mon, Dec 4, 2023 at 3:56 PM James Dailey <jdai...@apache.org> wrote: > TL;DR - Archive the Fineract-CN (cloud native) repos? > This is a call for discussion, not for a vote. I will call for a binding > VOTE in one week. > > HISTORY > The Apache Fineract(R) Community accepted a completely new architecture > about five years ago. That new concept was intended to revise and refactor > Fineract into new microservices. The PMC voted to accept the code and our > wiki pages and communication shifted to gather devs around the new > cloud-native microservice concept. > > Unfortunately, until a project - or sub-project in this case - can produce > a release, it does not get acceptance. There was never a release of the > software. In the Apache process, this is a key requirement. > > In the meantime, the Apache Fineract(R) main github was significantly > updated and continues to be the focus of work and refactoring. One of the > main things achieved in recent months is to make Fineract "cloud native" in > ways that matter. > > DECISIONS > We took the decision in May 2023 to deprecate the content and we have done > so. There may still be some outside links pointing to our site for this > sub-project, but effectively, we have made it clear that this is not the > focus on the Fineract Community. > > DISCUSS > We may now want to archive the github repositories. There are 40 (forty) > repos. There was an attempt in Jan 2023 to get a release out but it was > not completed. The problem is that there are FORTY repos, compared to ONE > for our main dev repo. > > We think that when we archive them, they remain available but are marked > as "archive", and won't allow for write access. > > If you disagree, now is the time to make your opinion known. We will have > a vote in a week. We are looking for any objections. If there is an > objection, we can hold off for another 6 months or a year. > > > >
