Hi,
I'm going to create gem with ruby bindings for Foreman API and am
looking for good name. Any prefs?
foreman-ruby perhaps?
Regards,
Martin
> Hi,
>
> I'm going to create gem with ruby bindings for Foreman API and am looking
> for good name. Any prefs?
>
> foreman-ruby perhaps?
>
calling something ruby inside a gem probably not ideal, does anyone knows
whats the standard way to describe a api binding in a gem name?
Ohad
···
On Tue, Jul 24, 2012 at 3:25 PM, Martin Bačovský wrote:Regards,
Martin
Well we've got an issues in the gem namespace, that we should probably
think about, in that there is a tool called foreman already out there:
capistrano-foreman (0.0.3)
foreman (0.53.0 ruby java, 0.50.0 mingw32 x86-mingw32 x86-mswin32)
foreman-export-daemontools (0.0.1)
foreman-export-monit (0.0.2)
foreman-upstart-daemon (0.0.1)
foreman-upstart-scaling (0.4)
foreman_upstart_boot (0.0.1)
we have:
foremancli (1.0)
Doing a grep on the remote gem list looks like api bindings typically
take three forms:
-
If the project itself is just an api binding that interfaces with a
third party library, it takes the form of the service name: e.g. -
freshbooks (2.2.1) Variants of this add an r to the name of the
project. e.g - rshoeboxed (When a project has API bindings in multiple
languages.) -
Otherwise it looks like a split between projectnameapi and
projectname-api. check out:
gem list --remote |grep api
e.g. foremanapi or foreman-api
Honestly, it seems that there really isn't a standard, but I do agree
that ruby-foreman is probably not the way we want to go.
Cheers,
Brain
···
On Tue, Jul 24, 2012 at 10:24 AM, Ohad Levy wrote: > > > On Tue, Jul 24, 2012 at 3:25 PM, Martin Bačovský > wrote: >> >> Hi, >> >> I'm going to create gem with ruby bindings for Foreman API and am looking >> for good name. Any prefs? >> >> foreman-ruby perhaps? > > > calling something ruby inside a gem probably not ideal, does anyone knows > whats the standard way to describe a api binding in a gem name? > > Ohad >> >> >> Regards, >> Martin > >> Well we've got an issues in the gem namespace, that we should probably
> think about, in that there is a tool called foreman already out there:
>
> capistrano-foreman (0.0.3)
> foreman (0.53.0 ruby java, 0.50.0 mingw32 x86-mingw32 x86-mswin32)
> foreman-export-daemontools (0.0.1)
> foreman-export-monit (0.0.2)
> foreman-upstart-daemon (0.0.1)
> foreman-upstart-scaling (0.4)
> foreman_upstart_boot (0.0.1)
>
> we have:
>
> foremancli (1.0)
>
> Doing a grep on the remote gem list looks like api bindings typically
> take three forms:
>
> 1) If the project itself is just an api binding that interfaces with a
> third party library, it takes the form of the service name: e.g. -
> freshbooks (2.2.1) Variants of this add an r to the name of the
> project. e.g - rshoeboxed (When a project has API bindings in multiple
> languages.)
>
> 2) Otherwise it looks like a split between projectnameapi and
> projectname-api. check out:
> gem list --remote |grep api
> e.g. foremanapi or foreman-api
>
> Honestly, it seems that there really isn't a standard, but I do agree
> that ruby-foreman is probably not the way we want to go.
>
> Cheers,
> Brain
Thanks for the research.
Given that said, I would go with foreman-api_bindings (as from
foreman-api I would expect gem extending foreman with api)
if there are no objections, I'll use foreman-api_bindings as a new name.
Martin
···
On 07/24/2012 07:10 PM, Brian Gupta wrote:On Tue, Jul 24, 2012 at 10:24 AM, Ohad Levy ohadlevy@gmail.com wrote:
On Tue, Jul 24, 2012 at 3:25 PM, Martin Bačovský martin.bacovsky@gmail.com >> wrote:
Hi,
I’m going to create gem with ruby bindings for Foreman API and am looking
for good name. Any prefs?foreman-ruby perhaps?
calling something ruby inside a gem probably not ideal, does anyone knows
whats the standard way to describe a api binding in a gem name?Ohad
Regards,
Martin
>>
>> Well we've got an issues in the gem namespace, that we should probably
>> think about, in that there is a tool called foreman already out there:
>>
>> capistrano-foreman (0.0.3)
>> foreman (0.53.0 ruby java, 0.50.0 mingw32 x86-mingw32 x86-mswin32)
>> foreman-export-daemontools (0.0.1)
>> foreman-export-monit (0.0.2)
>> foreman-upstart-daemon (0.0.1)
>> foreman-upstart-scaling (0.4)
>> foreman_upstart_boot (0.0.1)
>>
>> we have:
>>
>> foremancli (1.0)
>>
>> Doing a grep on the remote gem list looks like api bindings typically
>> take three forms:
>>
>> 1) If the project itself is just an api binding that interfaces with a
>> third party library, it takes the form of the service name: e.g. -
>> freshbooks (2.2.1) Variants of this add an r to the name of the
>> project. e.g - rshoeboxed (When a project has API bindings in multiple
>> languages.)
>>
>> 2) Otherwise it looks like a split between projectnameapi and
>> projectname-api. check out:
>> gem list --remote |grep api
>> e.g. foremanapi or foreman-api
>>
>> Honestly, it seems that there really isn't a standard, but I do agree
>> that ruby-foreman is probably not the way we want to go.
>>
>> Cheers,
>> Brain
>
> Thanks for the research.
> Given that said, I would go with foreman-api_bindings (as from foreman-api I
> would expect gem extending foreman with api)
>
> if there are no objections, I'll use foreman-api_bindings as a new name.
>
> Martin
Just to be clear, this gem would be something ruby developers can
include if they want to write against our api, no? In that case, I do
think that foreman-api, or foremanapi is the way to go as I don't
think we are looking to ship a gem that adds api capabilities to
foreman. (As the API is going to be part of core foreman, no?)
···
On Wed, Jul 25, 2012 at 9:01 AM, Martin Bačovský wrote: > On 07/24/2012 07:10 PM, Brian Gupta wrote:On Tue, Jul 24, 2012 at 10:24 AM, Ohad Levy ohadlevy@gmail.com wrote:
On Tue, Jul 24, 2012 at 3:25 PM, Martin Bačovský >>> martin.bacovsky@gmail.com >>> wrote:
Hi,
I’m going to create gem with ruby bindings for Foreman API and am
looking
for good name. Any prefs?foreman-ruby perhaps?
calling something ruby inside a gem probably not ideal, does anyone knows
whats the standard way to describe a api binding in a gem name?Ohad
Regards,
Martin
>>> Well we've got an issues in the gem namespace, that we should probably
>>> think about, in that there is a tool called foreman already out there:
>>>
>>> capistrano-foreman (0.0.3)
>>> foreman (0.53.0 ruby java, 0.50.0 mingw32 x86-mingw32 x86-mswin32)
>>> foreman-export-daemontools (0.0.1)
>>> foreman-export-monit (0.0.2)
>>> foreman-upstart-daemon (0.0.1)
>>> foreman-upstart-scaling (0.4)
>>> foreman_upstart_boot (0.0.1)
>>>
>>> we have:
>>>
>>> foremancli (1.0)
>>>
>>> Doing a grep on the remote gem list looks like api bindings typically
>>> take three forms:
>>>
>>> 1) If the project itself is just an api binding that interfaces with a
>>> third party library, it takes the form of the service name: e.g. -
>>> freshbooks (2.2.1) Variants of this add an r to the name of the
>>> project. e.g - rshoeboxed (When a project has API bindings in multiple
>>> languages.)
>>>
>>> 2) Otherwise it looks like a split between projectnameapi and
>>> projectname-api. check out:
>>> gem list --remote |grep api
>>> e.g. foremanapi or foreman-api
>>>
>>> Honestly, it seems that there really isn't a standard, but I do agree
>>> that ruby-foreman is probably not the way we want to go.
>>>
>>> Cheers,
>>> Brain
>> Thanks for the research.
>> Given that said, I would go with foreman-api_bindings (as from foreman-api I
>> would expect gem extending foreman with api)
>>
>> if there are no objections, I'll use foreman-api_bindings as a new name.
>>
>> Martin
> Just to be clear, this gem would be something ruby developers can
> include if they want to write against our api, no?
Exactly.
> In that case, I do
> think that foreman-api, or foremanapi is the way to go as I don't
> think we are looking to ship a gem that adds api capabilities to
> foreman. (As the API is going to be part of core foreman, no?)
As I understand the gems naming conventions the thing after dash extends
the gem before the dash. So in this case foreman-api should mean
extension to foreman that implements API (Foreman::API).
We need something more like ForemanApi thus foreman_api should more
appropriate, right?
Martin
···
On 07/25/2012 05:17 PM, Brian Gupta wrote: > On Wed, Jul 25, 2012 at 9:01 AM, Martin Bačovský > wrote: >> On 07/24/2012 07:10 PM, Brian Gupta wrote:On Tue, Jul 24, 2012 at 10:24 AM, Ohad Levy ohadlevy@gmail.com wrote:
On Tue, Jul 24, 2012 at 3:25 PM, Martin Bačovský >>>> martin.bacovsky@gmail.com >>>> wrote:
Hi,
I’m going to create gem with ruby bindings for Foreman API and am
looking
for good name. Any prefs?foreman-ruby perhaps?
calling something ruby inside a gem probably not ideal, does anyone knows
whats the standard way to describe a api binding in a gem name?Ohad
Regards,
Martin
I created gem named foreman_api with the Foreman API bindings.
If you are interested check it [1] out.
Cheers,
Martin
[1] https://github.com/mbacovsky/foreman_api