akabiru/faker-bot

faker-bot should be a separate gem

vbrazo opened this issue ยท 8 comments

Checklist

  • Invite @akabiru to be collaborator of this repository
  • Move original fakerbot repository to organization
  • Grant admin access to @stympy, @akabiru, @vbrazo on Rubygems.org
  • Publish faker-bot as a separate gem

@akabiru thanks ๐Ÿ‘

Cheers Vitor, I have some time. I'll amend the namespaces shortly. ๐Ÿ‘ ๐Ÿ™‚

I'm not able to push the gem to Rubygems.org. We'll need your help on that @akabiru

(base) VOLIVEIRA-MBP:faker-cli voliveira$ gem push faker-cli-0.4.5.gem
Pushing gem to https://rubygems.org...
You do not have permission to push to this gem. Ask an owner to add you with: gem owner faker-cli --add vbrazo@email.com
(base) VOLIVEIRA-MBP:faker-cli voliveira$ gem owner faker-cli --add vbrazo@email.com
Adding vbrazo@email.com: You do not have permission to manage this gem.

@vbrazo Looks like somebody alrealy owns faker-cli on ruby gems https://rubygems.org/gems/faker-cli ๐Ÿ˜ž

โ‹Š> ~/p/a/faker-cli on master โ—ฆ gem owner faker-cli                                  21:15:05
Owners for gem: faker-cli
- ich@dwgadf.de

Seems like we have to go with another name.

Some options off the top of my head:

1.) faker-cli-ruby - not as nice
2.) faker-bot - namespace Faker::Bot instead of Faker::CLI
3.) fakerbot (original name, I own this one)

@stympy which one would you prefer: fakerbot or faker-bot?

Let's do faker-bot.

@stympy @akabiru I've just granted access for your users on Rubygems.org. Now you can release new faker-bot versions.