This page is out of date. The term Echo cannot be used for legal reasons (explained in NameItEchoConflict). This discussion has moved to ProjectNameProposals; see also: ProjectNameProcess, ProjectNameGuidelines.
[InvisibleHand] At this point, I'm declaring consensus for Echo, unless someone comes up with a really convincing reason otherwise.
[GrantCarpenter] The fact that another open source project is using the name, would like to keep it as their own and has a pending trademark application on the name seem like compelling reasons to me. I refactored the existing name proposals and tried to come up with something less chaotic as a process: ProjectNameProcess, ProjectNameProposals.
There is an issue with this name -- as Joe Shelby mentioned in comments attached to a weblog posting (at http://weblog.burningbird.net/fires/001306.htm), Echo was the name of a Java framework released earlier this month. This is only going to cause confusion between both efforts. And since they were first...I strongly recommend this group NOT use Echo -- or justify 'hijacking' the name from a product that's being released LGPL. I will ask that there be consensus from this group that you're willing to use the name of another technology. [ShelleyPowers]
+1, much as I like the sound of Echo. [ChristianCrumlish]
Need to secure a web domain name for it. I already checked for availability of echoformat and echoschema in com, net, org, info. They are both available now -- FrançoisGranger Not wild about it, but taking a page from Mono, go-echo is available in com, net and org flavors. [GrantCarpenter]
echostandards is also available in .com, .net, and .org flavors [MichaelBernstein]
I registered purl.org/echo/ for use in namespaces, specs, official documentation. This is just a redirection service though; we'd still need a domain name and a place to actually host the specs and whatnot. [MarkPilgrim]
[JamesSnell] My domain host provider Robert Dodd of Brink Technologies said he is willing to donate the server space for free if the bandwidth to the site can be contained within 10,000 requests per day. More than that, and we'll need to make other plans.
We need a name for what we're doing. Here are the ground rules (for more extensive guidelines and requirements, see ProjectNameGuidelines):
Has to be something reasonably appropriate. We're going to have to get lots of people to support this.
Can't be already used by something related (i.e. anything like RSS is off-limits). Please do a quick Google search to look for obvious conflicts.
We need a name for everything in the RoadMap:
the project/process that's doing all of this
the format for log entries
the syndication and archving formats
the log editing protocol
Ideally, 2-4 would be some simple modification of 1. For now, let's just discuss the name for 1, unless your suggestions for 2-4 are really clever.
A poll was taken on the name Pie with no clear consensus met. It has been moved to NameItPiePoll.
A poll was taken on the name Echo and consensus was reached. See NameItDiscussion.
New ideas are being proposed on ProjectNameProposals.