Now that we’ve collected enough nominations, I’m going to kick off the PODLINGNAMESEARCH process on each name starting next week—I’m out of town most of this week… Stay tuned. You’ll see some activity on JIRA.
-J > On Oct 30, 2018, at 6:44 PM, Joshua Poore <poor...@me.com> wrote: > > Don’t know Steve. I think regardless of the name, our new Logo should look > like an REO Speedwagon album cover with a Dragon riding a Delorean with a > Flagon of ale. We can replace Mr Fusion with an Alembic. > > Joshua Poore > > >> On Oct 30, 2018, at 9:15 AM, York, Stephen P. <sy...@draper.com> wrote: >> >> Just to clarify, if we change the name to Flagon will the logo have a >> Dragon? We wouldn't want to confuse users as to whether or not STOUT or ALE >> is the brew that is true. >> >> ________________________________ >> From: Joshua Poore <poor...@me.com.INVALID> >> Sent: Monday, October 29, 2018 8:54:08 PM >> To: dev@senssoft.incubator.apache.org >> Subject: Re: [NOMINATIONS] New Name for SensSoft >> >> I would like to propose the name “Flagon". I’m so sad Alembic is a high risk >> for infringement, brand confusion. Flagon is a kind of flask, related to >> drinking. Its a strong name and up for grabs at USPTO. >> >> If selected, the name of the Podling would be "Apache Flagon”. >> >>> On Oct 29, 2018, at 8:49 PM, Joshua Poore <poor...@me.com> wrote: >>> >>> I would like to propose Apache Delorean. Time is an important concept for >>> our technology, and we have a host of feature ideas relating to >>> manipulating time—prediction, visualization. Also, it’s awesome, its a >>> throwback to cherished cultural iconography and there are NO trademarks for >>> Delorean in the Software Domain (IC 009). In the absence of something >>> clever, do something awesome. Only short coming is that autocorrect likes >>> to replace “Delorean” with Delores, which is fine... >>> >>> If selected the name of the project would be Apache Delorean. >>> >>>> On Oct 23, 2018, at 6:57 PM, Joshua Poore <poor...@me.com.INVALID> wrote: >>>> >>>> We should probably close nominations NLT Friday. We’ll need to generate >>>> our Monthly report and iterate on it... Throw in everything you’ve got. >>>> >>>> >>>> Joshua Poore >>>> >>>> >>>>> On Oct 23, 2018, at 4:40 PM, Rob Foley <r...@apache.org> wrote: >>>>> >>>>> Alembic is a nice term fro a stack like this, but I think there is a >>>>> somewhat popular Python library by the same name used for doing database >>>>> migrations. >>>>> >>>>> Rob >>>>> >>>>> On Mon, Oct 22, 2018 at 10:45 PM Laura Mariano <laura.j.mari...@gmail.com> >>>>> wrote: >>>>> >>>>>> I would like to propose the name Alembic. >>>>>> >>>>>> Definition of *alembic * >>>>>> >>>>>> 1: an apparatus used in distillation >>>>>> >>>>>> 2: something that refines or transmutes as if by distillationphilosophy … >>>>>> filtered through the alembic of Plato's mind— B. T. Shropshire >>>>>> SensSoft was designed to collect people's interactions with software >>>>>> without influencing those interactions at all. All the components of >>>>>> SensSoft (including Distill, of course) are designed to enable the >>>>>> extraction of insights from this data-separating them from the noise. >>>>>> >>>>>> The proposed name would therefore be Apache Alembic (incubating). >>>>>> Laura >>>>>> >>>>>> On Thu, Oct 11, 2018, 12:43 PM lewis john mcgibbney <lewi...@apache.org> >>>>>> wrote: >>>>>> >>>>>>> Hi Folks, >>>>>>> This thread opens the NOMINATIONS for new candidate names to replace >>>>>>> Apache SensSoft (Incubating) with... something else! >>>>>>> !! EVERYONE IS INVITED TO PARTICIPATE !! >>>>>>> If you wish to throw a suggestion in the hat, simply reply to this >>>>>>> thread >>>>>>> with your nomination (no motivation is required but would be fun). >>>>>>> After a while, we will close the NOMINATIONS and go to a 72 hours VOTE >>>>>>> where we will hopefully determine the new name for SensSoft :) >>>>>>> Let the NOMINATIONS begin... >>>>>>> Lewis >>>>>>> >>>>>>> -- >>>>>>> http://home.apache.org/~lewismc/ >>>>>>> http://people.apache.org/keys/committer/lewismc >>>>>>> >>>>>> >>>> >>> >> >> ________________________________ >> Notice: This email and any attachments may contain proprietary (Draper >> non-public) and/or export-controlled information of Draper. If you are not >> the intended recipient of this email, please immediately notify the sender >> by replying to this email and immediately destroy all copies of this email. >> ________________________________
