From: Kenneth Wilke <kenneth.wilke@RACKSPACE.COM>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
OpenBMC Patches <openbmc@lists.ozlabs.org>
Subject: Re: naming conventions
Date: Fri, 26 Aug 2016 19:18:23 +0000 [thread overview]
Message-ID: <1472239103290.78011@RACKSPACE.COM> (raw)
In-Reply-To: <2EB33EE8-EFD0-4EA1-A54F-8C6A03FDEBDC@fuzziesquirrel.com>
Makes sense to me, seems like a good way to quickly identify the scope of purpose for each application.
________________________________________
From: openbmc <openbmc-bounces+kenneth.wilke=rackspace.com@lists.ozlabs.org> on behalf of Brad Bishop <bradleyb@fuzziesquirrel.com>
Sent: Friday, August 26, 2016 1:53 PM
To: OpenBMC Patches
Subject: naming conventions
I wanted to take a stab at standardizing our naming conventions a little better.
In general, applications would be (loosely) named after the layer they are associated with. For example:
phosphor-foo: application that can run on any card running OpenBMC
op-foo: application that can only run on OpenPOWER systems
ibm-foo: application that can only run on IBM systems
palmetto-foo: application specific to the Palmetto system
I chose phosphor-foo rather than obmc-foo to draw attention to the fact that ‘Phosphor’ refers to a reference implementation/distribution (ideally) of OpenBMC (similar to Poky/OpenEmbedded).
When naming things or filling out description fields in recipes, etc, please avoid the overly redundant name or description: obmc-phosphor or “Phosphor OpenBMC”. Given that Phosphor is the reference for OpenBMC you can just say “Phosphor."
thoughts/feedback?
-brad
_______________________________________________
openbmc mailing list
openbmc@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/openbmc
next prev parent reply other threads:[~2016-08-26 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 18:53 naming conventions Brad Bishop
2016-08-26 19:18 ` Kenneth Wilke [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-23 3:29 John de la Garza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1472239103290.78011@RACKSPACE.COM \
--to=kenneth.wilke@rackspace.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.