The package paths are a bit redundent at the moment (e.g. waveprotocol/wave) so why not shorten "org/waveprotocol/wave" to "org/waveprotocol". And intead of "org/waveprotocol/wave/pirrama", use "com/google/wave".
So things could look like: com/google/wave/ 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) org/waveprotocol/ client/ common/ concurrencycontrol/ crypto/ federation/ media/ model/ waveserver/ But, if you're dead set on giving it a name, here's some suggestions: ocean wave4j (obligatory but please don't) woscillator (A poor attempt at combining oscillator with wave). moon (because it creates the tides) wind (because it causes the waves) hurricane (because they cause a lot of big waves) Igor (the name of a recent hurricane) -Tad On Thu, Sep 16, 2010 at 11: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]<wave-protocol%[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.
