Thanks Shawn for your comments. Look
for changes that reflect them soon.
Arnaud, the existence of an "Apache
Aries" wasn't really a big deal, there were other concerns around
names of projects this year I'd rather not resurface now. Coming
up with a clearer set of best practices and a process seemed to be
what people we talked to felt would be the most constructive way
to avoid churn and angst in the future.
On 6/6/19 2:24 PM, Arnaud Le Hors
shouldn't dictate via TSC policy a requirement to sign up for
There are a lot of ways to do it
> without mandating a particular
says the guy
should add something like "Google your potential project name
the terms 'Open Source'" to see if it is already taken"
Joke aside, I
actually agree with Shawn and thought the same when I saw it. I
ought to be neutral on this sort of thing and only mention
as examples to help those who may not know any.
situation is totally news to me and rather baffling. Biran, is
actually motivated this whole thing to start with?
Arnaud Le Hors - Senior Technical Staff Member, Blockchain
Web Open Technologies - IBM
Re: [Hyperledger TSC] Hyperledger project naming guidelines -
A good start! If these are meant to
policies,they should probably be written up with more
explanation and guidance.
Maybe the prose could include references to external sources
more in-depth discussion of the topics being covered. T
The implication of your email is
teams have not been doing the very basic things listed, and I
opposite is probably true -- that teams have put a lot of time
into the names. Still, these are good things to have clearly
In the "New Project Naming Process",
you should add something like "Google your potential project
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
than the tools mentioned. This would have helped identify Apache
as a conflict with Hyperledger Aries (or maybe it was known
some of us found it surprising).
In the "New Project Branding
we should have something in there the logo not overlapping with
projects. It seems very odd that Aries and Ursa share a theme,
Hyperledger Aries and Apache Aries essentially have the same
logo (a ram).
During the logo discussions, there
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
(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
monkey. There are a lot of ways to do it without mandating a
Who are the current members of the
On Thu, Jun 6, 2019 at 12:57 AM
have seen a small handful of projects join Hyperledger in
months, and it's likely we'll see a similar number if not more
through the rest of this year. Naming has at times been an
submissions. While it's important that the developers behind
set the name for their project, the Hyperledger Marketing
some of the LF staff put together a set of guidelines and
recommendations for new project names and a process for the
TSC, and HL/MC to use to arrive at a name.
The result is two new draft articles for your review in the
Tools section of the Wiki.
The first is a step-by-step process found under the how-to
The second provides our branding considerations, common
avoid, and questions to help guide the evaluation process,
We are open to taking your comments on tomorrow's TSC call,
we can iterate it based on feedback and get the TSC's approval
upcoming call. We are asking the same of the Marketing
Committee on our
monthly call this upcoming Tuesday, with the goal of closing
approvals in the next two weeks.
Executive Director, Hyperledger
Executive Director, Hyperledger