It's not about me, it's about people volunteering actually stepping up and starting to take action, and that is not happening.
You say: 'After some months, we will definitely see if the project is still alive or not." It's been 2 months now. In your opinion, how many more months of inaction should we wait, and what's the reasoning behind that number? On Fri, Dec 9, 2022 at 6:01 PM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > If you don't want to continue on jclouds (I fully understand this), > fair enough. But if people still want to maintain it, I don't see any > issue there. > > Is a fork better ? I don't think so. Because, it might happen if we > retire the project. > > As I proposed earlier, if the current PMC members don't want to > continue on jclouds, but we have potential volunteers to take over, I > think it's fair to try. Apache is community driven, if we have new > people in the jclouds community, willing to help, we could be > "welcoming". > After some months, we will definitely see if the project is still alive or > not. > > If you absolutely want to retire the project, I'm with you, and then > pulsar or brooklyn (or another project) will do a fork probably. > > Regards > JB > > > On Fri, Dec 9, 2022 at 3:38 PM Ignasi Barrera <n...@apache.org> wrote: > > > > I agree with Gaul's comments. > > > > If people wants to help, worth to see if it actually happens ;) > > > > > > > It's been 2 months since the proposal of retiring the project and to > date, > > nothing real happened beyond "I'm in" comments. > > If at the time of discussing the project retirement, this is all the > energy > > that is around to maintain it, I don't think it is a setup for success > and > > agree with Gaul that we will better serve users by retiring the project. > > > > > > > > P.S. Geoff, really appreciate your honesty in accounting for your > bandwidth! >
