Is the project actively maintained? about vagrant-cloudstack HOT 39 CLOSED

Hi,

Sorry to say but the original Developers have left Klarna, and we are not actively using it anymore therefor we do not maintain it.

We will update the description asap.

Kind regards

from vagrant-cloudstack.

@tobpal Thanks for the quick reply.

Please let me use this post to ping the people that contributed the last so we can have a discussion about where to take the project.

ping @atsaki, @mindjiver, @lndbrg, @wico, @petrhosek
Anyone willing to jointly take over the maintenance of the plugin?

from vagrant-cloudstack.

Hi! Since me, @loa and @lndbrg are no longer employed by Klarna and have no access to a Cloudstack instance it's hard for us to perform any development or maintenance.

So if someone out there would like to take over the maintenance it would be great. I mostly did the release engineering parts of tagging and uploading the resulting gem.

from vagrant-cloudstack.

I'd be happy to see the project live on, but not with me as one of the maintainers. :)

from vagrant-cloudstack.

Good old times :)

from vagrant-cloudstack.

Hi guys,

Thanks for all the input.
We, at Schuberg Philis, would be happy to continue the project.
We run our cloud on Apache CloudStack and are actively contributing to that project as well.
So it would make much sense for us to pick this project up, since it is a key component for our development activities (i.e. it integrates two major tools we use).

Please let us know if you would be interested in passing on the development of vagrant-cloudstack to us. We would, of course, import the git tree with the original code and commits to our organisation in github, and take it from there.

from vagrant-cloudstack.

From my point of view: That's the best way forward!

from vagrant-cloudstack.

@miguelaferreira I also developed/mainted the Packer builder for Cloudstack ( https://github.com/mindjiver/packer-cloudstack ) is that something you use as well?

from vagrant-cloudstack.

@mindjiver Thanks. In principle yes. But I won't have the free cycles to commit to both projects. I've asked internally to see if someone steps up.

from vagrant-cloudstack.

I've created a repo under our organisation https://github.com/schubergphilis/vagrant-cloudstack
I've moved the entire git tree there, and merged the pending PRs.

Once we are ready to make a new release, we will probably need some help with uploading it to RubyGems.org since you guys own the gem too.

@mindjiver I found colleagues interested in committing to the packer-cloudstack project.
Shall we do the same type of transfer for this project too? Or do you have something else in mind?

from vagrant-cloudstack.

@miguelaferreira Either that or I would need a API end point to test towards. If your things are internal then I guess the best thing is to move over the development to your org. I'm happy to help out with any questions about the project.

from vagrant-cloudstack.

@loa could you add me to the gem project on rubygems.org?

My profile: https://rubygems.org/profiles/miguelaferreira

from vagrant-cloudstack.

@mindjiver Well, I think that the best would be to transfer the project since our cloud is not public. However, if you still want to contribute we can try to find a solution to give you access to a testing environment.

from vagrant-cloudstack.

@miguelaferreira It's fine by my if you continue development 😄 I have used CloudStack enough in my time.

from vagrant-cloudstack.

@miguelaferreira I'm not part of Klarna any longer. Me still being owner of the gem is probably a mistake.

It's better if @wico changes the ownership since he's working at Klarna.

from vagrant-cloudstack.

@miguelaferreira I would be happy you continue development of this project :)

from vagrant-cloudstack.

@loa I'll look at it in a less busy minute.

from vagrant-cloudstack.

As a user, I too would be quite interested in seeing this plugin continue with development. I would help out in the coding but I don't know any Ruby

from vagrant-cloudstack.

@loa @mindjiver @lndbrg I will transfer that repo to @miguelaferreira
+
I'll change the https://rubygems.org/gems/vagrant-cloudstack (gem)ownership to miguelferreira too.

Any dissenting votes?

from vagrant-cloudstack.

@wico Sounds great

from vagrant-cloudstack.

👍

from vagrant-cloudstack.

quorum reached. I'll start the repo-transfer now, the gem-ownerships comes tomorrow (I'm not at klarna actually).

from vagrant-cloudstack.

Super! Thanks a lot guy.

from vagrant-cloudstack.

"You can only transfer a repository from an organization to yourself at this time" ;)

from vagrant-cloudstack.

I guess that means you would need to do it in two steps?
I mean, I know it works from user to user, and from user to organisation.
I've never tried from organisation to user.

from vagrant-cloudstack.

"Something went wrong with that request. Please try again." ;)

However - check your inbox. There should be an incoming request.

from vagrant-cloudstack.

I did get the request and accepted it 👍

from vagrant-cloudstack.

perfect, done, looks good to me.

from vagrant-cloudstack.

I will now start by updating the README, review PRs, etc

And along the way, move the repo to Shuberg Philis organisation

from vagrant-cloudstack.

Thanks. Please keep that little piece of code in a good shape. :) Especially @mindjiver will appreciate that!

from vagrant-cloudstack.

We will do our best and contribution is, of course, always welcome.

from vagrant-cloudstack.

@loa FYI: the related gem is now owned by @miguelaferreira.

from vagrant-cloudstack.

@mindjiver OK with transfering packer-cloudstack to @miguelaferreira too?

@miguelaferreira We probably continue using that packer-"plugin" in the future, but there should be no problem to contribute to you then.

from vagrant-cloudstack.

@wico I've asked @mindjiver to change the license of the packer project to Apache 2.0 because that fits best with our open-source software policy. However, if that is too much work we can also work with the Mozilla license, although not ideal.

What we can't do, is relicense it ourselves. So, the license we get from you is the one that stays. Hence the request.

I do have some colleagues very eager to start maintaining the packer-cloudstack project since they are working on integrating terraform with cloudstack. So, please do let me know when I can give them the news :)

from vagrant-cloudstack.

As packer-cloudstack inherited the MPL2-0 license from the original packer tree, I personally think its not possible to re-license it (at least we are not allowed to do so afaik).

from vagrant-cloudstack.

I've checked with a colleague that is part of the Apache Foundation and his interpretation was that, since the packer-cloudstack project has its own code base (i.e. it does not share code with the "parent" project), ti would be fine to have a different license.

But as I said, if checking this is too much trouble, or you guys just don't feel comfortable doing it, that's fine. We can work with the Mozilla license.

from vagrant-cloudstack.

I think some code is shared (cloned) and reused from packer, thus I would stay with the MPL2-0 - however:

Its up to @mindjiver to transfer the repo and fiddle with licenses as @mindjiver's is the most up-to-date repo anyway (the version at klarna is 10 commits behind mindjiver:master).

I again say thanks for taking care of all this!

from vagrant-cloudstack.

Just to let you know that i'm interested to help, since I have access to a cloudstack instance in our private IaaS, and using the plugin.

from vagrant-cloudstack.

@dduportal you are very welcome to help in any way you can

from vagrant-cloudstack.