Repository navigation
Separate leftover providers #3942
Description
Activity
- Sure. I did a very basic document on it in the past. You can find it here: https://github.com/fog/fog/wiki/Create-New-Provider-from-Scratch Is that what you are looking for? Em sex, 10 de fev de 2017 02:49, Artem Yakimenko <notifications@github.com> escreveu:…Ok, let's get this ball rolling, here's the list of providers that I've generated from lib: find . -maxdepth 1 -type f | sed 's/\.\//- [] /g' - [] bare_metal_cloud.rb - [] bluebox.rb - [] clodo.rb - [] cloudsigma.rb - [] cloudstack.rb - [] dnsimple.rb - [] dnsmadeeasy.rb - [] dreamhost.rb - [] fogdocker.rb - [] glesys.rb - [] go_grid.rb - [] ibm.rb - [] internet_archive.rb - [] joyent.rb - [] linode.rb - [] ninefold.rb - [] opennebula.rb - [] openvz.rb - [] ovirt.rb - [] rage4.rb - [] vcloud.rb - [] vcloud_director.rb - [] version.rb - [] zerigo.rb For every provider we need to make a decision: - Separate or - Remove @plribeiro3000 <https://github.com/plribeiro3000> / @geemus <https://github.com/geemus> PTAL Also - can you give an idea (very general is ok, but at least something) on how should separation should be done ideally? I'll format it so it looks straightforward. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3942>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AApEuE_j3-bvHkHz2S-BgrJDJAL9v27Pks5ra-xIgaJpZM4L9AIE> .
Looks like
fog-dnsimplejust needs removal from this gem as https://github.com/fog/fog-dnsimple already exists. @weppos can you confirm?Good catch @lanej !
Awesome. If you are taking on something, please edit the comment above (or add a comment here) that says which provider, who you are and what date (so we can judge staleness). That way we don't step on one another's toes. I'll update the listing above with ones I know about.
I also manually removed
bin.rbandversion.rbfrom the listing (just noting as the find/sed would no longer match).I think ninefold can be dropped entirely.
ouch. Good catch @lanej.
- added 2 commits that reference this issue
on Feb 23, 2017 Easiest, extraction, evar. Thanks!
I'm going to take ownership of internet_archive.
Reacted by Paulo Ribeiro and Wesley BearyThanks!
I need to start taking one (or some) as well, just been swamped of late...
36 remaining items
I'll look into using MIT. We should be able to figure that out soon. To help with that discussion, are there any licenses that are explicitly forbidden for repos within the
fogorg?None are forbidden at this time, but the question hasn't really come up before. If you feel a need to deviate, I would just ask you bring it up as a discussion sooner, rather than later, so there are no surprises. Thanks.
@ctreatma sounds good for licensing. I would tend to think about mocks as more of a user-facing-feature than an internal testing thing (though they get used for both purposes). It's not uncommon for us to have providers that start out without mocks (because it is a lot of of work and difficult), and then add mocks only later (or sometimes not at all). So I think it is reasonable to focus on the implementation first, and worry about mocks later. Beyond that, you should use what works well for you. Some consistency with existing things is valuable, but not if it makes things a lot harder for you to work on. ie VCR should probably be fine if you think that will be helpful.
We are ready to transfer our
fog-linodeprovider to thefogorg. Is there a formal process for doing that? If so, what should we do to get started?@displague @ctreatma I believe it should be tranferred, and I invited @ctreatma as an admin. Should I add you as well? Also, could you please add me as a gem owner? I'm unlikely to actually release it, but I like to have access just in case (ie if there was a security flaw or something I needed to respond to quickly across the various gems).
@geemus I added you as a gem owner. Please add @displague as an admin for the repo as well.
@ctreatma - thanks. I realized you were not a maintainer-role of the fog-linode team, so I updated that for you. I think that means you should be able to add @displague yourself. (I'd prefer you did, so we can be sure the permissions are all fixed up in case you need them in the future). Just let me know if that doesn't work out though. Thanks!
Thanks @geemus! Could you also invite @sarahelizgray to the org so that I can add her to the
fog-linodeteam as well?Sure, invite sent.
Could any effort be made to update vCloud Director?
Ok, let's get this ball rolling, here's the list of providers that I've generated from lib:
find . -maxdepth 1 -type f | sed 's/\.\//- [ ] /g'14 providers left including 2 to check if are still available.
For every provider we need to make a decision:
or
@plribeiro3000 / @geemus PTAL
Also - can you give an idea (very general is ok, but at least something) on how should separation should be done ideally? I'll format it so it looks straightforward.