Hello Andrew, I tried to reply to this thread but messed up the address (wrote "user@"), however I did send the same email to dev@, see [1].
We in Apache Brooklyn would certainly be unhappy to see Jclouds move to the attic. I have thought about it over the weekend and decided I would be willing to offer to join the Jclouds PMC if that will be helpful [2]. I see that Francois Papon (fpapon) has also volunteered [3], and JB is willing to continue [4]. I do agree a formal [VOTE] email would be of value. Personally I would like to see Jclouds successfully avoid the attic. Kind regards Geoff Macartney [1] https://lists.apache.org/thread/9rlpdc5v9q2tpjcmk6bbxgf74pwkdgxy [2] https://lists.apache.org/thread/qjxrflzts889g0m5gj2ny2493q6xm9sp [3] https://lists.apache.org/thread/gv5g27c7qbx9rrd59fddcys5h5rckfzm [4] https://lists.apache.org/thread/cbp9wmzvlgqnpqc1b5rr30c33t7trc74 On 2022/11/10 12:21:08 Andrew Gaul wrote: > I will send out a formal [VOTE] after I run the potentially final 2.6.0 > release. Note that no one from the community, including anyone from the > Brooklyn project, volunteered to help maintain jclouds after a month's > notice. I agree that this is an reversible situation but asking more > from the existing maintainers is unlikely to succeed. > > On Wed, Nov 09, 2022 at 09:00:57PM +0000, Geoff Macartney wrote: > > Oops, fixing address for user@jclouds.apache.org. > > > > > > On Wed, 9 Nov 2022 at 20:57, Geoff Macartney <geom...@apache.org> wrote: > > > > > > Hello Andrew, and Jclouds PMC, > > > > > > I'm sorry to be so late in replying to this, I confess I had missed it > > > when it was sent last month and only became aware of it today. > > > > > > Speaking as a member of the Apache Brooklyn PMC I must confess I am > > > sad to hear this proposal. Jclouds is one of our most critical > > > dependencies, and I would worry about the implications for Brooklyn if > > > Jclouds moved to the Attic. I am worried in any case about the > > > implications of the lower activity in the community, but that is > > > another issue. > > > > > > I have been refreshing my memory about the PMC guidelines on moving to > > > the Attic [1]. These note that > > > > > > "In summary, the only reason for a project to move to the Attic is > > > lack of oversight due to an insufficient number of active PMC members" > > > > > > (the minimum being three), and that electing willing community members > > > to the PMC would be the best way to keep it viable. If the worst comes > > > to the worst "the Board can "reboot" a PMC by re-establishing it with > > > a new or modified PMC". > > > > > > Perhaps it would be worth doing a formal [VOTE] poll within Jclouds > > > PMC itself to see if at least three PMC members would be willing to > > > continue to carry out that role? If not, maybe other options could be > > > explored before deciding to move to the Attic, such as some community > > > members joining the PMC. > > > > > > What do you think? > > > > > > Kind regards > > > Geoff > > > > > > [1] https://apache.org/dev/pmc#move-to-attic > > > > > > > > > On Mon, 10 Oct 2022 at 14:03, Andrew Gaul <g...@apache.org> wrote: > > > > > > > > jclouds development has slowed from 123 commits from 26 contributors in > > > > 2018 to just 24 from 6 contributors in 2022. This is despite growing > > > > downloads over the last 12 months from 50,000 to 80,000 for jclouds-core > > > > alone. Unfortunately the number of active committers has shrunk and we > > > > will soon lack quorum for future releases. This means that the project > > > > must move to the Apache attic. > > > > > > > > Ideally the community could step up to sustain the project, e.g., > > > > reviewing pull requests, fixing issues, responding to mailing list > > > > queries, and eventually becoming committers themselves. Does anyone > > > > have a multi-year interest in jclouds that wants to help out? > > > > > > > > If not, I will cut a final 2.6.0 release before retiring the project. > > > > > > > > -- > > > > Andrew Gaul > > > > http://gaul.org/ > > -- > Andrew Gaul > http://gaul.org/ >
