Re: Name Change to Apache Flagon (Incubating) and Fun Stuff

[Laura Mariano]

Small please :) I will think about logos...

On Mon, Mar 25, 2019, 10:14 PM Joshua Poore  wrote:

> Sry, should have asked:
>
> +1 and t-shirt size :)
>
> Will contact later for shipping and distro instructions.
>
> > On Mar 25, 2019, at 10:11 PM, Laura Mariano 
> wrote:
> >
> > +1 !!
> >
> > On Mon, Mar 25, 2019, 8:50 PM Joshua Poore  wrote:
> >
> >> Hi Folks,
> >>
> >> Haven’t heard from General RE other steps we need to take prior to
> moving
> >> our assets to the “Flagon” namesake. So, I’ve put in tickets to INFRA to
> >> initiate the name change. If you’re curious, ticket is here:
> >>
> >> https://issues.apache.org/jira/browse/INFRA-18100 <
> >> https://issues.apache.org/jira/browse/INFRA-18100>
> >>
> >> Fun Stuff:
> >>
> >> 1. We need some art. If you all have some free time and want to doodle,
> >> please sketch out what YOU think our logo should be. Likely, we’ll keep
> the
> >> art on the website (our website is awesome), and the font. But, we could
> >> use a new logo. Ask yourself, what kind of Flagon are we? Here’s a
> google
> >> image search for Flagons.
> >>
> >>
> >>
> https://www.google.com/search?q=flagon=lnms=isch=X=0ahUKEwiE3piCx57hAhXrnuAKHQCDBzMQ_AUIDigB=1228=666
> >> <
> >>
> https://www.google.com/search?q=flagon=lnms=isch=X=0ahUKEwiE3piCx57hAhXrnuAKHQCDBzMQ_AUIDigB=1228=666
> >>>
> >>
> >> 2. I’d love some thoughts a new tagline. "Instrument Software:
> Understand
> >> Humans” is super slick, but its pretty serious, pretty academic. Any
> other
> >> thoughts on something, maybe with a bit more whimsy, are totally
> welcome.
> >>
> >> 3. Swag. I’m thinking real hard about this. Beyond the obvious and the
> >> historical—bottle openers, coasters, and flagons—what do you think our
> name
> >> should be on?
> >>
> >> That being said, give a +1 to this email and you’ll receive a tshirt. It
> >> won’t be our new tagline, but it will read:
> >>
> >> I Drink
> >>
> >> +
> >>
> >> I know things about users
> >>
> >> Apache Flagon
> >>
> >>
> >> [This is happening]
> >>
> >>
>
>

Re: Name Change to Apache Flagon (Incubating) and Fun Stuff

[Joshua Poore]

Sry, should have asked: 

+1 and t-shirt size :)

Will contact later for shipping and distro instructions.

> On Mar 25, 2019, at 10:11 PM, Laura Mariano  wrote:
> 
> +1 !!
> 
> On Mon, Mar 25, 2019, 8:50 PM Joshua Poore  wrote:
> 
>> Hi Folks,
>> 
>> Haven’t heard from General RE other steps we need to take prior to moving
>> our assets to the “Flagon” namesake. So, I’ve put in tickets to INFRA to
>> initiate the name change. If you’re curious, ticket is here:
>> 
>> https://issues.apache.org/jira/browse/INFRA-18100 <
>> https://issues.apache.org/jira/browse/INFRA-18100>
>> 
>> Fun Stuff:
>> 
>> 1. We need some art. If you all have some free time and want to doodle,
>> please sketch out what YOU think our logo should be. Likely, we’ll keep the
>> art on the website (our website is awesome), and the font. But, we could
>> use a new logo. Ask yourself, what kind of Flagon are we? Here’s a google
>> image search for Flagons.
>> 
>> 
>> https://www.google.com/search?q=flagon=lnms=isch=X=0ahUKEwiE3piCx57hAhXrnuAKHQCDBzMQ_AUIDigB=1228=666
>> <
>> https://www.google.com/search?q=flagon=lnms=isch=X=0ahUKEwiE3piCx57hAhXrnuAKHQCDBzMQ_AUIDigB=1228=666
>>> 
>> 
>> 2. I’d love some thoughts a new tagline. "Instrument Software: Understand
>> Humans” is super slick, but its pretty serious, pretty academic. Any other
>> thoughts on something, maybe with a bit more whimsy, are totally welcome.
>> 
>> 3. Swag. I’m thinking real hard about this. Beyond the obvious and the
>> historical—bottle openers, coasters, and flagons—what do you think our name
>> should be on?
>> 
>> That being said, give a +1 to this email and you’ll receive a tshirt. It
>> won’t be our new tagline, but it will read:
>> 
>> I Drink
>> 
>> +
>> 
>> I know things about users
>> 
>> Apache Flagon
>> 
>> 
>> [This is happening]
>> 
>> 

Re: Name Change to Apache Flagon (Incubating) and Fun Stuff

[Laura Mariano]

+1 !!

On Mon, Mar 25, 2019, 8:50 PM Joshua Poore  wrote:

> Hi Folks,
>
> Haven’t heard from General RE other steps we need to take prior to moving
> our assets to the “Flagon” namesake. So, I’ve put in tickets to INFRA to
> initiate the name change. If you’re curious, ticket is here:
>
> https://issues.apache.org/jira/browse/INFRA-18100 <
> https://issues.apache.org/jira/browse/INFRA-18100>
>
> Fun Stuff:
>
> 1. We need some art. If you all have some free time and want to doodle,
> please sketch out what YOU think our logo should be. Likely, we’ll keep the
> art on the website (our website is awesome), and the font. But, we could
> use a new logo. Ask yourself, what kind of Flagon are we? Here’s a google
> image search for Flagons.
>
>
> https://www.google.com/search?q=flagon=lnms=isch=X=0ahUKEwiE3piCx57hAhXrnuAKHQCDBzMQ_AUIDigB=1228=666
> <
> https://www.google.com/search?q=flagon=lnms=isch=X=0ahUKEwiE3piCx57hAhXrnuAKHQCDBzMQ_AUIDigB=1228=666
> >
>
> 2. I’d love some thoughts a new tagline. "Instrument Software: Understand
> Humans” is super slick, but its pretty serious, pretty academic. Any other
> thoughts on something, maybe with a bit more whimsy, are totally welcome.
>
> 3. Swag. I’m thinking real hard about this. Beyond the obvious and the
> historical—bottle openers, coasters, and flagons—what do you think our name
> should be on?
>
> That being said, give a +1 to this email and you’ll receive a tshirt. It
> won’t be our new tagline, but it will read:
>
> I Drink
>
> +
>
> I know things about users
>
> Apache Flagon
>
>
> [This is happening]
>
>

[jira] [Created] (SENSSOFT-344) Update Install/Deploy instructions on Website

[Joshua Poore (JIRA)]

Joshua Poore created SENSSOFT-344:
-

 Summary: Update Install/Deploy instructions on Website
 Key: SENSSOFT-344
 URL: https://issues.apache.org/jira/browse/SENSSOFT-344
 Project: SensSoft
  Issue Type: Task
  Components: website
Affects Versions: SensSoft 1.0
Reporter: Joshua Poore
Assignee: Joshua Poore
 Fix For: SensSoft 1.0


Update website deploy instructions in preparation for name change. They are 
currently, hopelessly out of date. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[DISCUSS] 2019 Q2 (APR) Apache SensSoft Podling Report Draft

[Joshua Poore]

Hi Folks, 

Posting this to dev for discussion. Please review and post comments, concerns, 
mods to this thread no later than Friday, March 29th. Following that, I will 
post the final version on dev.

Mentors: this report needs to be signed and uploaded to the Incubator Wiki no 
later than Wednesday, April 3rd. 

Thank you. Report draft follows:



Apache SensSoft

Apache SensSoft is a generalized user behavioral logging platform for web pages 
and thin-client applications

Apache SensSoft has been incubating since 2016-07-13.

Three most important issues to address in the move towards graduation:

  1. Grow the Apache SensSoft (Incubating) Committer/Community Base.
  2. Complete our Podling name change
  3. Complete the issues highlighted at the SensSoft Roadmap [1]

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

We have completed our PODLINGNAMESEARCH workflow and our new name Apache Flagon 
has been approved by VP of marketing [2]. 

We have posted tickets to change the name of our core assets (JIRA, Website, 
GitBox Repos) [3], to coincide with changing website text, other content-based 
references to Apache SensSoft.

We are preparing for additional releases, immediately following our full 
transition to the Apache Flagon Namesake (UserALE.js v. 2.0.0, 2.1.0; poss. 
Flagon 1.0.0). 

How has the community developed since the last report?

The community has been:

-discussing reaching out to other open source projects to identify other 
potential communities (analytical technologies) to drive developments, as well 
as increase interest in the Podling.

-discussing research applications with university research labs in machine 
learning and social computing.

-discussing adoption of the technology with interested entities and 
identifying/eliminating barriers to adoption. 

-updating documentation on wiki and READMEs to improve community growth

How has the project developed since the last report?

Project maturity roadmaps (Wiki) and version release plans (JIRA) continue to 
be maintained.
JIRA boards continue to be maintained

Core products have been maintained for modernization and for security posture.

New features have been added to enhance adoption and make Apache SensSoft 
competitive with open-source business analytics services (e.g., OWA).

How would you assess the podling's maturity?
Please feel free to add your own commentary.

Despite challenges posed by dispersion of the original committers, the project 
is finding its footing again and continues to be desirable for consumption and 
relevant amidst alternatives. The impending name change is an opportunity for 
rebranding and acceleration of community growth.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-03-14

When were the last committers or PPMC members elected?

  Arthi Vezhavendan was added to Committer base on 2017-01-24

  Dave Meikle was added to PPMC on 2018-11-24

  Atri Sharma was added to PPMC on 2018-11-24

Have your mentors been helpful and responsive or are things falling
through the cracks?

Lewis McGibbney has been extremely helpful and has actively participated in our 
PODLINGNAMESEARCH. 

Dave Meikle has actively participated in our PODLINGNAMESEARCH process and has 
pledged to assist in growing the community following a determination of our 
PODLINGNAMESEARCH results.

Atri Sharma has offered his mentorship, but is not yet elected to IPMC, and has 
not been able to offer binding votes.

Signed-off-by:

[ ](senssoft) Lewis John McGibbney Comments:
[ ](senssoft) Dave Meikle Comments:
[ ](senssoft) Atri Sharma Comments:

[1] https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps 

[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154 

[3] https://issues.apache.org/jira/browse/INFRA-18100 

Releases and things

[Joshua Poore]

Hi Folks, 

Given we’re making serious headway toward a name change, I’d like to be 
prepared to push some releases out. Of course, prior to any official release, 
there will be a VOTE. However, I’d like to open a thread to talk release 
strategy, just to get some first impressions.

1. We’ll need to re-release Apache UserALE.js v 1.0.0. This is procedural, 
because our release artifacts were not appropriately named. This is 
essentially, exactly what’s on Master + plus a few security-driven updates to 
NPM packages. This doesn’t have to wait until the name switch, but we have been.

2. My thinking is that we release Apache UserALE.js v 2.0.0 shortly after the 
name change. This will be important for community generation. My thoughts are 
that we release the SENSSOFT-192 branch (soon to be Flagon) as version 2.0.0. 
This branch is massive and includes a lot of major updates to the base 
UserALE.js product, as well as major growth through Extension.

3. Following Apache UserALE.js v 2.0.0, I’d like to release v 2.1.0 soon 
thereafter, this will catch us up and include some recent major package updates 
and some minor features, including new log features. There are a few tickets 
left to burn down on v 2.1.0. 

4. I’d also like to release Apache Flagon v 1.0.0 (Frmly known as SensSoft 
1.0.0, our back-end). One or two big things need to happen to this branch. We 
were hesitant to release this before, but given the way Elastic is moving, and 
how our own back end works (e.g., Kubes), I believe we need to be pushing out 
official releases to Docker. 

Please comment, argue, or register concerns about this model. If we agree on 
UserALE, vs SensSoft/Flagon releases, I’ll update our release boards on JIRA to 
reflect. If I don’t hear anything, I’ll update them anyway, and then we’ll have 
to return to these questions when we start voting on releases.

Josh

Name Change to Apache Flagon (Incubating) and Fun Stuff

[Joshua Poore]

Hi Folks,

Haven’t heard from General RE other steps we need to take prior to moving our 
assets to the “Flagon” namesake. So, I’ve put in tickets to INFRA to initiate 
the name change. If you’re curious, ticket is here:

https://issues.apache.org/jira/browse/INFRA-18100 


Fun Stuff:

1. We need some art. If you all have some free time and want to doodle, please 
sketch out what YOU think our logo should be. Likely, we’ll keep the art on the 
website (our website is awesome), and the font. But, we could use a new logo. 
Ask yourself, what kind of Flagon are we? Here’s a google image search for 
Flagons.

https://www.google.com/search?q=flagon=lnms=isch=X=0ahUKEwiE3piCx57hAhXrnuAKHQCDBzMQ_AUIDigB=1228=666
 


2. I’d love some thoughts a new tagline. "Instrument Software: Understand 
Humans” is super slick, but its pretty serious, pretty academic. Any other 
thoughts on something, maybe with a bit more whimsy, are totally welcome.

3. Swag. I’m thinking real hard about this. Beyond the obvious and the 
historical—bottle openers, coasters, and flagons—what do you think our name 
should be on?

That being said, give a +1 to this email and you’ll receive a tshirt. It won’t 
be our new tagline, but it will read:

I Drink

+

I know things about users

Apache Flagon


[This is happening]