Sounds like pointing to projects.yaml would be best to avoid duplication of effort, with one caveat: first removing the project name capitalization to make it consistent. Unless it is there for a syntax reason? Thanks, Amanda On Wed, Sep 2, 2015 at 7:46 AM, Anne Gentle <annegentle at justwriteclick.com> wrote: > Hi all, > > The governance repo now contains the guidelines for naming and > capitalization of service and project names: > > http://governance.openstack.org/reference/service-project-naming.html > > This reference list is the "truth" for our documentation conventions, > which are described here: > > > https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names > > I've updated the wiki page but I'm wondering if it's best to stop > maintaining that list and instead point to the projects.yaml file now that > it will be reviewed with guidelines in mind? > > > http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml > > Thanks, > Anne > > > -- > Anne Gentle > Rackspace > Principal Engineer > www.justwriteclick.com > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150902/a1ef93af/attachment.html>