Oh and also Francois said he’s volunteer.

So I would propose to reshape the PMC to include volunteer guys.

Thoughts ?

Regards
JB

Le mar. 6 déc. 2022 à 13:12, Jean-Baptiste Onofré <j...@nanthrax.net> a
écrit :

> Hi
>
> I was about to reply.
>
> As it seems we have interest and volunteers, if the current PMC members
> agree, we could extend the PMC to have new active people.
>
> As said I’m volunteer with Enrico to maintain jclouds as it used in other
> Apache projects.
>
> What the other PMC members are thinking ?
>
> Regards
> JB
>
> Le dim. 4 déc. 2022 à 16:32, Enrico Olivelli <eolive...@gmail.com> a
> écrit :
>
>> Any updates here?
>>
>> Enrico
>>
>> Il Mer 16 Nov 2022, 16:53 Juan Cabrerizo <j...@cloudsoft.io> ha scritto:
>>
>> > I concur with Enrico,
>> > First warranty the Jclouds is patched when needed. it has to be secure.
>> > Then keep alive the community of users/dependent projects responding to
>> > issues and requests.
>> >
>> > Adding new cloud providers features seems to be for me the next step,
>> but
>> > it depends on the evolution on the necessities and other tooling.
>> >
>> > That's what I had in mind when I volunteered and I think is enough for
>> > keeping live the project.
>> >
>> > Juan
>> >
>> > On Mon, 14 Nov 2022 at 11:14, Enrico Olivelli <eolive...@gmail.com>
>> wrote:
>> >
>> > > Il giorno lun 14 nov 2022 alle ore 11:59 Andrew Gaul <g...@apache.org
>> >
>> > > ha scritto:
>> > > >
>> > > > I would like to understand what the three potential PMC members
>> plan to
>> > > > do since jclouds already has many absentee committers and PMCs.  For
>> > > > example I seen only one commit in the last 5 years and no previous
>> help
>> > > > testing releases.  Repeating my original mail:
>> > > >
>> > > > > 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?
>> > > >
>> > > > jclouds is also a critical dependency for my project S3Proxy which
>> > > > accounts for 25% of jclouds Maven Central downloads.  I would like
>> to
>> > > > see Apache jclouds continue instead of creating a private fork but
>> > > > currently I do most of the maintenance with little community
>> support.
>> > > > How will this change under a new PMC set?
>> > >
>> > > (I am also volunteering, as posted in a previous message).
>> > > In order to keep a project alive we must at least guarantee:
>> > > - security fixes
>> > > - responding to user requests
>> > >
>> > > There are other Apache projects that are widely used but they don't
>> > > need many new features
>> > > and they are pretty stable,
>> > >
>> > > In JClouds I would expect some work to follow the new features of the
>> > > supported providers,
>> > > but this is not strictly needed, it depends on users.
>> > >
>> > > Apart from "keeping it alive" we could try to boost it a little bit by
>> > > engaging more with the well known
>> > > projects that use it and ask them to advertise more about how they use
>> > > JClouds
>> > >
>> > > my 2 cents
>> > > Enrico
>> > >
>> > >
>> > > >
>> > > > On Mon, Nov 14, 2022 at 05:53:18AM +0100, Jean-Baptiste Onofré
>> 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>
>> > > >
>> > > > --
>> > > > Andrew Gaul
>> > > > http://gaul.org/
>> > >
>> >
>> >
>> > --
>> > 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