Hi Andrew
I agree. I propose to wait a month or so now 2.6.0 has been released.
If there's no request/feedback, then we should start a formal vote
imho.
Thanks !
Regards
JB
On Sun, Mar 10, 2024 at 7:58 AM Andrew Gaul wrote:
>
> On Mon, Oct 10, 2022 at 10:03:07PM +0900, Andrew Gaul wrote:
> >
Agreed, if any show stoppers, I can carve out time to help.
On Sat, Mar 9, 2024 at 10:58 PM Andrew Gaul wrote:
> On Mon, Oct 10, 2022 at 10:03:07PM +0900, Andrew Gaul wrote:
> > jclouds development has slowed from 123 commits from 26 contributors in
> > 2018 to just 24 from 6 contributors in
On Mon, Oct 10, 2022 at 10:03:07PM +0900, Andrew Gaul 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.
at if I did so I would just be kidding myself and everyone else. I
don't want to do that. I imagine others feel similarly.
As regards
> We've had plenty of emails from other project contributors indicating
that they'd have to fork if jclouds move to the attic.
It's not clear right now to
l discussion and vote.
> >
> > On Fri, Jan 13, 2023 at 08:44:27AM +0100, Jean-Baptiste Onofré wrote:
> > > Hi Geoff,
> > >
> > > To Geoff and others, happy new year :)
> > >
> > > Yes, I agree: it seems the bandwidth is limited.
> > >
indicating that they'd have to fork if jclouds move to
the attic. Well, if you have to fork, then you'd have to maintain. Why not
help maintain it over here instead of over there? I'm guessing it's because
you're hoping it won't come to that.
John
On Mon, Feb 13, 2023 at 7:16 AM Rich Bowen wrote:
&
> > think accurately captures the current state of affairs. Let's run a
> > > > final release then we can proceed with a formal discussion and vote.
> > > >
> > > > On Fri, Jan 13, 2023 at 08:44:27AM +0100, Jean-Baptiste Onofré wrote:
> > > > > Hi Geoff,
&g
d with a formal discussion and vote.
> > >
> > > On Fri, Jan 13, 2023 at 08:44:27AM +0100, Jean-Baptiste Onofré wrote:
> > > > Hi Geoff,
> > > >
> > > > To Geoff and others, happy new year :)
> > > >
> > > > Yes, I agre
formal discussion and vote.
> >
> > On Fri, Jan 13, 2023 at 08:44:27AM +0100, Jean-Baptiste Onofré wrote:
> > > Hi Geoff,
> > >
> > > To Geoff and others, happy new year :)
> > >
> > > Yes, I agree: it seems the bandwidth is limited.
&
and vote.
>
> On Fri, Jan 13, 2023 at 08:44:27AM +0100, Jean-Baptiste Onofré wrote:
> > Hi Geoff,
> >
> > To Geoff and others, happy new year :)
> >
> > Yes, I agree: it seems the bandwidth is limited.
> >
> > So, I think it makes sense to
vote.
>> >
>> > On Fri, Jan 13, 2023 at 08:44:27AM +0100, Jean-Baptiste Onofré wrote:
>> > > Hi Geoff,
>> > >
>> > > To Geoff and others, happy new year :)
>> > >
>> > > Yes, I agree: it seems the b
members
> don't
> > > > > want to be involved anymore.
> > > > >
> > > > > As most of the volunteers are not jclouds PMC members (I think I'm
> the
> > > > > only one), you have to accept the decision from PMC members.
> > >
l discussion and vote.
>
> On Fri, Jan 13, 2023 at 08:44:27AM +0100, Jean-Baptiste Onofré wrote:
> > Hi Geoff,
> >
> > To Geoff and others, happy new year :)
> >
> > Yes, I agree: it seems the bandwidth is limited.
> >
> > So, I think it makes sense
off,
>
> To Geoff and others, happy new year :)
>
> Yes, I agree: it seems the bandwidth is limited.
>
> So, I think it makes sense to move jclouds into attic; and let other
> projects find an alternative (forking part of jclouds, finding a brand
> new alternative, ...).
>
>
Hi Geoff,
To Geoff and others, happy new year :)
Yes, I agree: it seems the bandwidth is limited.
So, I think it makes sense to move jclouds into attic; and let other
projects find an alternative (forking part of jclouds, finding a brand
new alternative, ...).
Regards
JB
On Thu, Jan 12, 2023
PMC members accept to extend/expand the committer list (and
> PMC) to have new people volunteer to maintain jclouds, so projects can
> still use jclouds. I don't want to be pushy in this direction. It's
> important to have the long time PMC members, if they want to move
> jclouds in
s. I don't want to be pushy in this direction. It's
important to have the long time PMC members, if they want to move
jclouds in the attic, it's fair and we have to accept that.
2. replace jclouds with something else. That's probably the preferred
approach, replacing jclouds directly with cloud prov
Hi all,
Hope you had a restful Christmas break.
Andrew, thanks very much for these details, that is helpful to scope the
effort required to maintain jclouds. Of course what takes 10 hours for
Andrew, with his familiarity with jclouds, will take perhaps significantly
longer for those of us who
On Sun, Dec 11, 2022 at 03:25:04PM +, Geoff Macartney wrote:
> Can we try to get some data on what amount of effort is required here?
> Andrew, Ignasi, here are some questions for you.
>
> If we want to at least keep Jclouds going, without necessarily doing much
> fresh feature development on
meant to add dev@brooklyn.a.o
On Sun, 11 Dec 2022 at 15:25, Geoff Macartney wrote:
> Can we try to get some data on what amount of effort is required here?
> Andrew, Ignasi, here are some questions for you.
>
> If we want to at least keep Jclouds going, without necessarily doing much
> fresh
Can we try to get some data on what amount of effort is required here?
Andrew, Ignasi, here are some questions for you.
If we want to at least keep Jclouds going, without necessarily doing much
fresh feature development on it:
1. What do you think is a desirable *minimum* number of active
Il Sab 10 Dic 2022, 12:47 Jean-Baptiste Onofré ha scritto:
> Ok. Fair enough.
>
> Imho Karaf-jclouds is probably different as the number of users is very
> very thin.
>
> But I understand your points.
>
> I will support of moving to attic anyway. Just wanted to give a chance for
> the community
Ok. Fair enough.
Imho Karaf-jclouds is probably different as the number of users is very
very thin.
But I understand your points.
I will support of moving to attic anyway. Just wanted to give a chance for
the community to speak up.
The users will find alternatives (maybe forking part of
Even if it is maintenance, now it's not time for just good intentions
(which are very much appreciated), but time for action, and action is not
there and my confidence in it happening any time soon is very low.
Let me give you a concrete example:
* In 2019, we voted on moving jcloud-karaf under
Hi Andrey,
Side note, I think we could be interested by Apache Sunny (it's a Java
stack/runtime/deployer for the cloud, not really a library, more a
runtime focusing on Kubernetes).
As it seems your use case is Karaf focus, another option is to
contribute to Karaf (and probably Cellar).
I think
That's a fair comment. As we are mostly talking about "maintenance", I
don't wait for any new big features in the short term.
As said, the main concern for these guys is about jclouds as an
important dependency in their project.
I can't speak on their behalf, but I assume Pulsar and Brooklyng
ojects here for working with various
service API's.
https://github.com/cdancy/bitbucket-rest
https://github.com/cdancy/jenkins-rest
From: Andrey Rusev
Sent: Friday, December 9, 2022 1:25 PM
To: dev
Cc: jb ; dev
Subject: ExtMsg: Re: move jclouds to the attic?
Actually, I think I can just go ahead and give you a few more examples of what
we need ... in general... and I think might be a good fit to jclouds, not sure
if you guys think jclouds is the right place for this, but... if you do - I'd
be happy to support the development for these... They're
Hi,
I don't know if I will be really helping here, but I thought ... as the
conversation is shifting towards 'will there be volunteers to join' ... I might
share my perspective here, as someone who has been observing this mail list
(and also this thread) for years... Quietly observing, that is
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
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
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
My understanding is that other communities (at least pulsar and Brooklyn)
are using still jclouds.
So they are volunteer to maintain jclouds more for the need of their
project.
If it doesn’t work, then these projects will find an alternative to jclouds
or fork jclouds.
If people wants to help,
I want to understand what the potential new committers plan to _do_.
Currently I am the only active PMC writing code, reviewing PRs, and
cutting releases. I do not see anyone volunteering to run the 2.6.0
release so I do not understand how the volunteers plan to continue the
larger goal of
That's also my point (sorry I was probably not clear): we still have
PMC active, so, I just propose to move forward with maintenance and
releases, and follow the regular process to add new committers/PMC
members when it makes sense.
Regards
JB
On Tue, Dec 6, 2022 at 7:17 PM Geoff Macartney
(To be clear: I would love to help out, I just doubt I would be much use.
Sorry!)
On Tue, 6 Dec 2022 at 18:17, Geoff Macartney wrote:
> Hi all,
>
> Andrew's point earlier in this thread was that jclouds needs people not
> people on the PMC as such but people to help with
>
> > Ideally the
Hi all,
Andrew's point earlier in this thread was that jclouds needs people not
people on the PMC as such but people to help with
> Ideally the community could step up to sustain the project, e.g.,
> reviewing pull requests, fixing issues, responding to mailing list
> queries, and eventually
Sounds good to me!
regards,
Francois
On 06/12/2022 13:18, Jean-Baptiste Onofré wrote:
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é a
écrit :
Hi
I was
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é a
écrit :
> Hi
>
> I was about to reply.
>
> As it seems we have interest and volunteers, if the current PMC
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 ?
Any updates here?
Enrico
Il Mer 16 Nov 2022, 16:53 Juan Cabrerizo 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
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
Hi Andrew,
Fair point. However, it seems we have a new "trend" around jclouds
(according to this thread). I have some ideas to give a new "taint" to
jclouds (it's the plan I will send asap).
So, if we have a new "community" around to maintain and move forward
on jclouds, I think it's worth to do
Hi Andrew
I take your point. I can speak only for myself, of course. I work full
time on things unconnected to Apache and the development I do in my
own time tends to be work related. I don't even get as much time as I
would like to work on Apache Brooklyn, and I would probably not be
able to
Il giorno lun 14 nov 2022 alle ore 11:59 Andrew Gaul
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
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
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
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
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 wrote:
> I would also be willing to join the Jclouds PMC if that would be helpful.
>
> Regards
> Geoff
>
> On Thu,
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é wrote:
>
> I’m in ;)
>
> Regards
> JB
>
> Le jeu. 10 nov. 2022 à 11:56, fpapon a écrit :
>
> > Hi,
> >
> > After some discussions with JB, we are ok to
I’m in ;)
Regards
JB
Le jeu. 10 nov. 2022 à 11:56, fpapon 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
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,
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
Hi Andrew,
fair discussion.
I think you are right: the numbers are speaking ;)
+1
Regards
JB
On Mon, Oct 10, 2022 at 3:03 PM Andrew Gaul 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
Thanks for starting this thread Gaul!
+1 to move the project to the Attic if there is no active community anymore,
On Mon, Oct 10, 2022 at 3:03 PM Andrew Gaul wrote:
> jclouds development has slowed from 123 commits from 26 contributors in
> 2018 to just 24 from 6 contributors in 2022. This
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
56 matches
Mail list logo
