For completeness...
On Tue, Jul 12, 2011 at 3:43 AM, Perry Myers <pmyers(a)redhat.com> wrote:
On 07/11/2011 11:37 AM, Adam Stokes wrote:
> Some possible names (thanks thesaurus :)):
>
> compose
> construct
This was asked on irc but no answer...
Because it was 3am here :-)
Why is 'Config Agent' a bad name?
Because (almost) everything in matahari is about config.
Agreed on sysconfig.
The agent's primary responsibilities would be:
* using augeas to expose arbitrary configuration file editing
* using puppet to expose puppetConfig which takes a puppet
configuration file and processes it
* API to ask "have I been configured yet?" wrt calling a puppetConfig
or similar function
* APIs for editing Windows registry
All of this seems to fall under the general idea of 'system
configuration', so Config Agent seems like it would be the most sensible
name, no?
on the other hand, 'Postboot' doesn't really convey what the agent does,
so I agree that this is a bad name.
If folks thing config is too generic, then how about 'Sysconfig Agent'
or 'Generic Config Agent (genconfig)' to differentiate it from the fact
that _all_ of the agents allow you to do configuration, but this agent
is sort of the catch-all for things which aren't exposed by another
specific agent (like Network, Host, etc)
Perry
_______________________________________________
Matahari mailing list
Matahari(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/matahari