[Workman-devel] RFC: Possible rename of workman library/project

[Josh Poimboeuf]

Hi Daniel,

On 05/17/2013 05:51 AM, Daniel P. Berrange wrote:
> It was pointed out to me off-list by Ben that while there isn't
> a project called 'workman', there is in fact already a library called
> 'libworkman.so' that is used on BSD platforms at least :-( In addition
> he suggested that there are quite a few clashes in google for the phrase
> 'workman' from non-software areas.
>
> This will create undesirable confusion to people searching for our
> library/project and make google'ing for it unduly difficult. Thus it
> seems wise to choose a different name now, before it is too late.

I don't think this is much of a problem really.  A Google search of
"libworkman" has our gitorious repository as the first result.  And the
workman clashes don't seem like a big deal to me.  It's not the only use
of the word "workman" in the world, but once the project starts getting
distributed, I imagine it'll become much more searchable on Google.

>
> Some suggestions I got from Ben are
>
> 1) libsysalloc - system resource allocation
> 2) libresman - resource management
> 3) libreman - resource management (there is a race of mutated Vulcans
>     in the Star Trek Universe called the Reman)
> 4) libparalloc - partition alloc
> 5) libsyspar - system partition (there is a military piece of software
>     called Systems Planning and Requirements Software (/SYSPARS/) but that
>     should be discernable) libsyspart - isn't advised since it is a windows
>     thing and there is a lot of documentation about it)
> 6) libparsys - partition system (rolls off the tongue better but there
>     are several conflicts one with adobe and one with a company none of
>     them are too common)
>
>
> My analysis of these ideas
>
> 1) There are already quite a few software results for 'sysalloc'
> 2) there is a software cdompany called 'resman' so best to avoid that
> 3) there is a libreman project on github
> 4) No clashes, but it is a bit of a mouthfull to say
> 5) The libsyspar vs libsyspart clash puts me off this.
> 6) Again best to avoid anything that is related to existing
>     software companies.
>
>
> So libparalloc (or libpartalloc) is an option, which suggest a
> "Partition Allocator" as a name and possibly 'paralloc' as a
> command.
>
> A possible variant is  libparctl "Partition Control" with
> 'parctl' as a command.
>
> A further variant is "Work Control" as the project name and  thus
> 'libworkctrl' or 'libworkctl' as the library and  'workctl' as the
> command.
>
> Currently I'm favouring the last option 'libworkctl', or failing
> that  'libparctl'.

Of all the listed options, I like libworkctl.  And I would throw
"libworkload" into the mix.

But I don't really see much of a reason to change it...


Josh