I hate the proliferation of meaningless names. Its like unnecessary
product complexity - it makes users think and learn unnecessarily.
We have used up our quota of stupid names already anyway - "wave",
"splash", "fedone", "wavelet", "gadget", "fedone"...
You may see 'wave in a box' as a milestone, but I think everybody else
thinks of wave in a box as a product. From a marketing standpoint, the
name "wave in a box" is perfect. It both keeps the wave identity and
differentiates itself from what is running on wave.google.com. Its
funny enough to be memorable. When wave in a box is finished and we
put out an announcement releasing it, the media should say "Google
releases wave in a box" and not "Google releases Pirrama, which is a
new name for that wave in a box thing you heard about awhile ago".
Having another silly name will also make it more difficult for users
to google, and more confusing when you do. ("I was looking for
waveinabox. Is Pirrama what I wanted?")
In short, we already have a name. Lets run with that.
-J
On Fri, Sep 17, 2010 at 4:19 PM, Alex North <[email protected]> wrote:
> The example wave server is currently named "FedOne" as its purpose was to
> demonstrate federation. We now have grander goals for this code though,
> beginning with the "Wave in a Box" milestone. It's time for a new name.
> Let's rename the "fedone" package in the repository, removing the "examples"
> package while we're there.
> I propose a default repo layout resembling:
>
> org/waveprotocol/pirrama/
>
> client/common (was examples/client/common)
> webclient/ (was examples/client/webclient)
> consoleclient/ (was examples/client/console)
> server/ (was examples/fedone/)
> agents/ (was examples/fedone/agents)
> common/ (for code shared between client and server)
>
> For reference, the libraries repository provides code (re-usable for any
> clients and servers) with the following layout:
> org/waveprotocol/wave/
>
> client/
> common/
> concurrencycontrol/
> crypto/
> federation/
> media/
> model/
> waveserver/
>
> The name "pirrama" is a placeholder in the new layout - I think we need a
> new name to encompass this particular server and bunch of clients.
> waveinabox seems like an obvious candidate, but apart from being cumbersome
> it describes a milestone for the project rather than a particular product. I
> don't think it will age well when we later come to scaling the system
> (though we'll keep "in a box" as a working deployment).
> So - we need a new name. What do you suggest?
> Alex
> * "Pirrama" is the Aboriginal name for "Pyrmont", where the Google Sydney
> office is.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Wave Protocol" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/wave-protocol?hl=en.
>
--
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
