Why not just "waveinabox"? Or just "wavebox"? It is something that people already recognize. Although I would not mind something like "org.waveprotocol.serenity" :)
On Sep 18, 8:48 pm, Alex North <[email protected]> wrote: > Some nice suggestions so far! > > I might just note that we're specifically hunting for a package name here: > org.waveprotocol.[something], and it needs to be different from "wave" so > that we don't clash with the package name of all the general re-usable > libraries in the libraries repo. A package name is somewhat internal to the > code - users don't need to ever see it, though if it matches a product name > that's nice too. > > A. > > On 18 September 2010 20:06, Graham Simpson <[email protected]> wrote: > > > > > > > > > Second, although just to be a pain in the neck, I think the option > > 'sendwave' should be definitely mentioned at least once! > > > On Sep 18, 5:52 am, Anders <[email protected]> wrote: > > > Hmm... You could have a point there. The name wave is more like the > > > word email than some brand name. > > > > On Sep 17, 4:05 pm, ThomasWrobel <[email protected]> wrote: > > > > > I think the confusion is "wave" is used just too much. > > > > Its a protocol name, a product name, and a name for a thread within > > > > the protocol. > > > > One would be fine, but all 3 is just confusing. > > > > > I do like the Wave In A Box name though, and (personally) I think > > > > Federation is a pretty darn cool goal for anything too. > > > > > Maybe "Wave" should be kept purely for the federation name, and > > > > variants for the server name, but clients should be given completely > > > > unrelated names? > > > > > On Sep 17, 2:13 pm, Anders <[email protected]> wrote: > > > > > > +1 The brand name Wave can include all wave service providers, be > > used > > > > > consistently in news articles etc and is easy for end users to > > > > > remember. > > > > > > On Sep 17, 1:54 pm, Graham Simpson <[email protected]> wrote: > > > > > > > Even simpler, people don't really think of Wave in a box as a name > > > > > > either, Let's just call it Wave! If that's what it is, and if > > Google > > > > > > is shutting down Google Wave and thus avoiding a branding clash - > > Wave > > > > > > will do fine as the name of the server. > > > > > > > On Sep 17, 7:57 am, Dave butlerdi <[email protected]> wrote: > > > > > > > > +1 > > > > > > > > On 17 September 2010 08:41, Joseph Gentle <[email protected]> > > wrote: > > > > > > > > > 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]<wave-protocol%2bunsubscr...@goog > > > > > > > > > legroups.com> > > <wave-protocol%2bunsubscr...@goog legroups.com> > > > > > > > > . > > > > > > > > > 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]<wave-protocol%2bunsubscr...@goog > > > > > > > > legroups.com> > > <wave-protocol%2bunsubscr...@goog legroups.com> > > > > > > > > . > > > > > > > > For more options, visit this group at > > > > > > > >http://groups.google.com/group/wave-protocol?hl=en. > > > > > > > > -- > > > > > > > Regards > > > > > > > > Dave Butler > > > > > > > butlerdi-at-pharm2phork-dot-org > > > > > > > > Also on Skype as pharm2phork > > > > > > > > Get Skype herehttp://www.skype.com/download.html > > > ********************************************************************** > > > > > > > This email and any files transmitted with it are confidential and > > > > > > > intended solely for the use of the individual or entity to whom > > they > > > > > > > are addressed. If you have received this email in error please > > notify > > > > > > > the system manager. > > > > > > > > This footnote also confirms that this email message has been > > swept by > > > > > > > MIMEsweeper for the presence of computer viruses. > > > > > > > >www.mimesweeper.com > > > ********************************************************************** > > > -- > > 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%2bunsubscr...@goog > > legroups.com> > > . > > 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.
