Fork the brand of Metamaps.cc from the core technology
As we get more clarity about the difference between the core engine and the specific instance that lives at Metamaps.cc, we're considered calling them different things. Currently its difficult to differentiate them from one another. This discussion is about deciding to make a clear differentiation between Metamaps.cc and the engine which powers Metamaps.cc.
Poll Created Mon 25 Nov 2013 10:07PM
Adopt the name "Veqtor" for the core engine powering Metamaps.cc Closed Wed 27 Nov 2013 10:00PM
Veqtor it is. Robert is going ahead and buying the domain name - we'll migrate the playground to veqtor.cc and change the branding to prepare for the hackathon that we'll run on the 14th and 15th of december.
First proposed by Ishan in a chat - seconded by Connor in an email proposal below:
“I’m excited about the name Ishan brought up, personally I like it a lot, and as Ishan mentioned it would be great to have a different name for this very different technology that we are actually building the next generation of metamaps with. I would be pretty happy to see things within the metamaps-playground slightly rebranded/tweaked towards Veqtor, and also about moving it to Linode, and hosting it at some veqtor domain name of our choosing :) What say you?”
If we go ahead to do this, we will start referring to the core engine as “Veqtor” and start to build out this presence in the creative direction and design.
|Results||Option||% of points||Voters|
5 of 8 people have voted (62%)
Wed 27 Nov 2013 4:06PM
Still ambivalent, for reasons offered in discussion here. Willing to go with 'consensus minus one' protocol to move ahead swiftly, as I don't have quite the same depth of insight or ownership as of yet!