Re: Hyperledger project naming guidelines - draft for discussion
toggle quoted messageShow quoted text
A good start! If these are meant to be policies,they should probably be written up with more explanation and guidance. Maybe the prose could include references to external sources that provide more in-depth discussion of the topics being covered. T
The implication of your email is that teams have not been doing the very basic things listed, and I think the opposite is probably true -- that teams have put a lot of time and effort into the names. Still, these are good things to have clearly articulated.
In the "New Project Naming Process", you should add something like "Google your potential project name with the terms 'Open Source'" to see if it is already taken". This seems in-line with the rest of the items listed, and is a better approach than the tools mentioned. This would have helped identify Apache Aries as a conflict with Hyperledger Aries (or maybe it was known already, but some of us found it surprising).
In the "New Project Branding Considerations", we should have something in there the logo not overlapping with existing projects. It seems very odd that Aries and Ursa share a theme, and that Hyperledger Aries and Apache Aries essentially have the same logo (a ram).
During the logo discussions, there is a form that we help fill out - that could probably be included in one of these documents as a way to help make some of the list items more concrete. (Ali has the doc - the questions seem pretty well thought out.)
In the "New Project Naming Process" - HL shouldn't dictate via TSC policy a requirement to sign up for survey monkey. There are a lot of ways to do it without mandating a particular commercial service.
Who are the current members of the MC?
On Thu, Jun 6, 2019 at 12:57 AM Brian Behlendorf <bbehlendorf@...> wrote:
We have seen a small handful of projects join Hyperledger in recent