Policy on Tools Posting

[Andrew Jeffery]

Hi Wilfred,

On Tue, 13 Aug 2019, at 10:28, Wilfred Smith wrote:
> 
> 1. Are there guidelines/procedures specific to submitting command line 
> tools and utilities? I have heard that there may be a repository and/or 
> path dedicated to CLI tools.

There's not much in the way of commandline tools that are dedicated to
OpenBMC right now. The obvious one is `obmcutil`, but that lives in the
phosphor-state-manager repository which isn't really a spot to add other
assorted tools.

At a real stretch we could put things in openbmc-tools[1], though that's
not really intended for production code, more-so helpers for development
and debugging.

[1] https://github.com/openbmc/openbmc-tools

> 
> 2. The specific tools I’m concerned with at the moment are a D-Bus 
> enabled version of fruid-util

Maybe this could go in phosphor-inventory-manager?

>, ipmb-util 

Not really sure where we might put ipmb-util

> and sensor-util

Maybe phosphor-hwmon? Not really sure, just putting out some
straw-person suggestions.

Are there descriptions and example usage documented anywhere? That
would probably help us sort out what the possibilities are.

> as they 
> currently exist in the facebook/openbmc repository.
> Nothing to write 
> home about. I’ve removed anything Facebook-specific.

I guess at this point it just depends on whether you think they would or
could be widely adopted.

> 
> 3. I presume the correct course of action is to submit Gerrit patches 
> for layers under meta-facebook unless instructed otherwise.

You're talking about the recipes here rather than the actual tools? Or
are you proposing putting the source for the tools in meta-facebook?
In general we've tried to avoid that.

Cheers,

Andrew