As a member of the Apache Brooklyn PMC I'd be pleased to see jclouds
sustained a bit longer.

Increasingly in AB people are using custom containers (eg AWS CLI),
terraform, helm, and other tools to drive creation, but for well-behaved
VMs without much thought jclouds is usually simpler than any of those.  So
while the long-term future of jclouds in AB isn't clear to me, in the near
term it would be great to have maintenance support for jclouds at least, if
people are willing.  Thank you!

Re (2) I am definitely curious how much effort it would be for both
Brooklyn and jclouds to move to karaf5.  I think in both there's a lot of
subtle use of OSGi capabilities so they would be interesting exercises, and
if not too hard would be a great step forward for lightweightness.

Best
Alex


On Mon, 14 Nov 2022 at 04:53, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:

> Hi guys,
>
> thanks for your update !
>
> I propose to prepare a quick plan describing:
> 1. PMC set proposal
> 2. Roadmap/ideas for jclouds future (I would like to mention Karaf Minho
> here)
> 3. Send the proposal on the mailing list to move forward on vote and
> inform the board
>
> Thoughts ?
>
> Regards
> JB
>
> On Sun, Nov 13, 2022 at 11:12 AM Juan Cabrerizo <j...@cloudsoft.io> wrote:
> >
> > Hi, I'm a PMC member of Brooklyn, happy to try to help JClouds and
> joining
> > the committee. It's a core dependency for us.
> >
> > Regards
> > Juan
> >
> > On Sat, 12 Nov 2022 at 16:22, Geoff Macartney <geom...@apache.org>
> wrote:
> >
> > > I would also be willing to join the Jclouds PMC if that would be
> helpful.
> > >
> > > Regards
> > > Geoff
> > >
> > > On Thu, 10 Nov 2022 at 11:15, Jean-Baptiste Onofré <j...@nanthrax.net>
> > > wrote:
> > > >
> > > > I’m in ;)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > Le jeu. 10 nov. 2022 à 11:56, fpapon <fpa...@apache.org> a écrit :
> > > >
> > > > > Hi,
> > > > >
> > > > > After some discussions with JB, we are ok to propose our help to
> join
> > > > > the PMC of JCloud and contribute to keep the project alive if
> anybody
> > > is
> > > > > ok.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Francois
> > > > >
> > > > > On 09/11/2022 21:57, Geoff Macartney 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/
> > > > >
> > > > > --
> > > > > --
> > > > > François
> > > > >
> > > > >
> > >
> >
> >
> > --
> > Juan Cabrerizo
> > Senior Software Engineer
> >
> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > j...@cloudsoft.io
> > https://www.linkedin.com/in/juancabrerizo
> > https://github.com/jcabrerizo
> > <https://github.com/jcabrerizo>
>

Reply via email to