Re: [DISCUSS] Re: FLOGOS! Plz review logos

[Michael Schreiber]

Josh,
Do you have an example of the "spray paint effect" from another logo, or
similar?

As far as background, I thought maybe a conglomeration of words in a
repeating background. But with only partial transparency, because otherwise
it'd be WAY too busy.
https://www.123rf.com/clipart-vector/grammar.html?sti=nnv33o0rk9snbgnfws|=52613707

Those background(s) could be on alternating blocks (i.e. the white, or the
grey/dark) so it's not too overwhelming.

Another option could be gears or something like that:
https://www.alamy.com/mechanical-seamless-vector-background-pattern-monochromatic-gray-image217739171.html

Just some thoughts.


On Sun, Oct 27, 2019 at 11:23 PM Joshua C. Poore  wrote:

> Hi Folks!
>
> As some of you know, I just had my second kid. Needless to say, I've had
> my hands full and haven't been as active. However, I got some more work
> done on Logos today. I need to keep working on flaglorien, but I took
> the rough design of flagonSaveTheQueen, kept the geometry and sharpened
> it up a bit... The results are pretty cool and theres a lot we can do
> with it. Check it out:
>
>
> https://github.com/apache/incubator-flagon/blob/master/site/images/flagonMaster.svg
>
> I haven't figured out yet how to get that nice spray paint effect I
> wanted with the original flagonSaveTheQueeen, so stand by on that.
>
> Making some progress...
>
> Also looking for any thoughts on background art to replace the current
> artwork on the website, or at least mix it up a bit... Although, I think
> the new logo I produced (above) would transfer well on to the existing
> "darktheme" art.
>
> Josh
>
> On 10/5/2019 2:41 PM, Furkan KAMACI wrote:
> > Hi Joshua,
> >
> > Great sketches! From a user perspective, I liked the #1 just because of
> it
> > seems cool.
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Sun, Sep 29, 2019 at 9:40 PM Austin Bennett <
> whatwouldausti...@gmail.com>
> > wrote:
> >
> >> Sensible response and believe am in agreement -- and, related, I don't
> have
> >> any better ideas for logos at the moment.
> >>
> >> On Sat, Sep 28, 2019 at 10:16 PM Joshua C. Poore 
> >> wrote:
> >>
> >>> Austin!
> >>>
> >>> Thanks so much for the input. #2 is my favorite, too.
> >>>
> >>> Flagon is user analysis for the masses. It's open source, scalable
> >>> business analytics for some. It's usability analysis for others. And,
> >>> its turning the web into a decision-sciences laboratory for others.
> >>> We're trying to make user analysis open source and safe for all time.
> >>> We're trying to up the game, too. Clickstream is dumb, we're about
> >>> patterns of life and real behavioral science.
> >>>
> >>> Check out the website: http://flagon.incubator.apache.org/
> >>>
> >>> As for what the logo has to do with anything about our project: Its all
> >>> history, just like Apple's Apple, Microsoft's Window, and Google's
> >>> Wheel. Our first UserALE (our logging service) developer was super into
> >>> beer. So he named it User-ALE (Analytic Logging Engine). The alcohol
> >>> reference became a thing for the dev team--we started naming all our
> >>> apps after booze (ALE, Distill, TAP, STOUT). So, when we changed our
> >>> name, the name really aligned with the history of the products  (e.g.,
> >>> Flagon of ALE) more than the products' scope. So, our logos don't
> really
> >>> have to have anything to do with our product, or a Flagon, they just
> >>> have to be cool, fun, and energize people.
> >>>
> >>> If there are better ideas for something that aligns with behavioral
> >>> logging, or actual Flagons (tough, I tried...), I'm all ears. But, we
> >>> don't need to constrain ourselves, especially not at the cost of having
> >>> fun and doing awesome things. I'd rather someone see something and ask,
> >>> "whats that?" than see something completely obvious and have no
> >>> motivation to explore. Our logo won't affect hits on Google, it will
> >>> affect how much people spent time on our website or our booth at the
> >>> next Apache con...
> >>>
> >>> Thoughts?
> >>>
> >>>
> >>> On 9/29/2019 12:42 AM, Austin Bennett wrote:
>  #2 looks super cool; still don't have a great sense of what project is
>  trying to do as to whether sufficiently in-line.
> 
>  On Sat, Sep 28, 2019 at 9:38 PM Joshua C. Poore 
> >>> wrote:
> > Hi Folks,
> >
> > I've been doing some sketches on Flagon logos. Probably we'll want a
> >> few
> > for various things, but we need a primary logo to use on Twitter,
> > website, etc., etc. I can't get them to go through unscathed through
> >> the
> > dev lists. You can find them at this link:
> > https://cwiki.apache.org/confluence/display/FLAGON/Flagon+Logos
> >
> > These are just sketches I made. I have someone (probably) who can
> >> finish
> > them off, touch them up for us and make them web-ready. Of course, if
> > someone from the community would like to do that, I'll take it! Just
> > remember that the final will be copyright 

Re: Could Use Help on Testing for 2.0.1 RC1

[Michael Schreiber]

I can test when I return from travel Sunday evening, assuming it hasn’t
been resolved.

Michael

On Sat, Jul 27, 2019 at 10:39 AM Joshua Poore 
wrote:

> Hi Dave, thanks!
>
> I went into Jenkins configs and flipped off “build periodically” on the
> bionic node—as per INFRA guidance, we’re only allowed to use the ‘Ubuntu'
> tag (and probably ‘xenial'). This will keep it from running unless we push,
> merge, or manually trigger, and hopefully not get the Hadoop folks angry at
> us.
>
> If you look at build #73—was successful build after final merge of v2.0.0
> RC into master. This was a successful build on xenial using node v12.2.0
> linux x64, on machine H22. I’ll pin to this machine and see if the 12.7.0
> build doesn’t work on it. If so, then we have some issue with servers and
> labels in Jenkins, if not, it could be a node or package issue, in which
> case I’ll regress gulp-eslint back to a previous version and retest, and
> we’ll keep running CI on node 12.2.0 until we see that node has worked out
> any kinks with their new version. We know it builds on 12.7.0 on darwin and
> linux, so I don’t think we need to walk back our package.json.
>
> Thanks for the assist folks! #community #boosh!
>
> Josh
>
> > On Jul 27, 2019, at 6:27 AM, Dave Meikle  wrote:
> >
> > Yes, it looks like it works on Bionic but not Xenial. I pinned the CI
> build
> > to confirm.
> >
> > I need to go offline just now but will try to see the difference. It
> looks
> > like a node version from the error but can see it dynamically downloads.
> >
> > Cheers,
> > Dave
> >
> > On Sat, 27 Jul 2019 at 09:47, Dave Meikle  wrote:
> >
> >>
> >>
> >> On Fri, 26 Jul 2019 at 21:01, Joshua Poore  wrote:
> >>
> >>> Going insane. Can someone please try and build the RC branch (
> >>> https://github.com/apache/incubator-flagon-useralejs <
> >>> https://github.com/apache/incubator-flagon-useralejs>) on a Linux X64
> >>> machine and see if builds/tests run on npm 12.7 (I’ll take 12.2 too).
> This
> >>> would be super helpful in debugging this issue. Should only take a
> minute
> >>> or two to run install, built, and test.
> >>>
> >>>
> >> Builds and tests fine here. Ubuntu 19.04 x64 with:
> >>
> >>   - Node v12.6.0, NPM 6.4.1
> >>   - Node v12.7.0, NPM 6.10.0
> >>
> >> Cheers,
> >> Dave
> >>
>
>

Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.0

[Michael Schreiber]

+1

On Wed, Jun 26, 2019 at 12:31 AM Joshua Poore  wrote:

> Hi Folks,
>
> I’ve added the minor mods I mentioned as a new release candidate. Please
> VOTE. Details follow:
>
> Git source tag (909b531):
> https://github.com/apache/incubator-flagon-useralejs/commit/909b5315888d2bd89fa4570b46d80f77318b58bb
> <
> https://github.com/apache/incubator-flagon-useralejs/commit/909b5315888d2bd89fa4570b46d80f77318b58bb>
>
>
> Staging repo: https://dist.apache.org/repos/dist/dev/incubator/flagon/ <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/>
>
> Source Release Artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.0.0-RC2/
> <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.0.0-RC2/
> >
>
> PGP release keys (signed using F9374FAE3FCADF6E):
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS>
>
>
> > On Jun 25, 2019, at 11:53 PM, Joshua Poore  wrote:
> >
> > TO DOs:
> >
> > Note that I need to fix our License file and remove all copyright
> attribution (the copyright in the appendix is meant for instruction for
> others how to apply license to derivative works).
> >
> > That’s pretty minor, but important. Unless anyone objects, let’s proceed
> with the VOTE. I’ll prepare a new release package with that correction
> prior to moving from dev to release in bistro. In the meantime, I’ll make
> that change to master.
> >
> > Thanks + please VOTE.
> >
> > Josh
> >
> >> On Jun 25, 2019, at 7:23 PM, Joshua Poore  wrote:
> >>
> >> Hi Folks,
> >>
> >> Reminder: please VOTE on the Apache Flagon v2.0.0 release as described
> below. We’ll be in great shape once this release is out and our releases
> have caught up with our development. Also, critical for community building.
> >>
> >> Best,
> >>
> >> Josh
> >>
> >>> On Jun 23, 2019, at 8:52 PM, Joshua Poore  wrote:
> >>>
> >>> Hi Folks,
> >>>
> >>> Please VOTE on the Apache Flagon 2.0.0 Release Candidate # 1.
> >>>
> >>> This Major release includes a wealth of additional features beyond
> v1.0.0, notably:
> >>>
> >>> 1. Interval Logs
> >>> 2. WebExtensionSupport for Chrome/Firefox
> >>> 3. API support for filtering, mapping, and custom logs
> >>> 4. Overhauled Unit Tests
> >>>
> >>> We solved 59 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343068=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Ceda9fbce2795c14b56345bf5daee2a8a893d249c%7Clin
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343068=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED|eda9fbce2795c14b56345bf5daee2a8a893d249c|lin
> >
> >>>
> >>> Git source tag (fb31f6882e309e92b64b019f757ad4770ff979b0):
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.0-RC1_06_23_2019
> <
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.0-RC1_06_23_2019
> >
> >>>
> >>> Staging repo: https://dist.apache.org/repos/dist/dev/incubator/flagon/
> 
> >>>
> >>> Source Release Artifacts:
> https://dist.apache.org/repos/dist/release/flagon/2.0.0/ <
> https://dist.apache.org/repos/dist/release/flagon/2.0.0/>
> >>>
> >>> PGP release keys (signed using F9374FAE3FCADF6E):
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS> (new keys
> will be moved over to /release after ReRelease completes)
> >>>
> >>> Vote will be open for 72 hours.
> >>>
> >>> Thank you to everyone that is able to VOTE as well as everyone that
> contributed to Apache Flagon 2.0.0
> >>>
> >>> [ ] +1, let's get it released!!!
> >>> [ ] +/-0, fine, but consider to fix few issues before...
> >>> [ ] -1, nope, because... (and please explain why)
> >>
> >
>
>

Re: [VOTE] (Re)Release Apache Flagon UserALE.js (Incubating) 1.0.0

[Michael Schreiber]

+1

On Mon, Jun 17, 2019 at 9:35 PM Joshua Poore  wrote:

> Hello,
>
> I am calling a VOTE to (re)Release Apache Flagon UserALE.js (Incubating)
> v1.0.0.
>
> There are two reasons for this (re)Release:
>
> 1. Original release artifacts were not properly annotated with
> (incubating) flag—IPMC asked us to regenerate the release with appropriate
> annotation.
> 2. Our name was officially changed from Apache SensSoft —> Flagon. This
> release bears our new project name.
>
> We conducted a VOTE within our own community, resulting in +6 votes in
> favor of the (re)Release, including +1 binding vote from PPMC:
>
> VOTE thread:
> https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
> <
> https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
> >
> VOTE thread II (split accidentally to private):
> https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
> <
> https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
> >
>
> Please VOTE on Apache FLAGON UserALE.js 1.0.0 Release Candidate #3:
>
> We solved 50 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin>
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED|d2c9eccb98c0590b13b40b9d863a18bfc463546f|lin
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED|d2c9eccb98c0590b13b40b9d863a18bfc463546f|lin
> >>
>
> Git source tag (d99ad9a2757fb5e412437227c6f9508d06c192e1):
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
> <
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019>
> <
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
> <
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
> >>
>
> Source Release Branch:
> https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease
>  ><
> https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease
> >
>
>
> Source Release Candidate Artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/flagon/ <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/><
> https://dist.apache.org/repos/dist/dev/incubator/flagon/ <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/>>
>
> PGP release keys (signed with F9374FAE3FCADF6E):
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS><
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS>> (new keys
> must must be copied over to http://apache.org/dist/incubator/flagon/ <
> http://apache.org/dist/incubator/flagon/> <
> http://apache.org/dist/incubator/flagon/ <
> http://apache.org/dist/incubator/flagon/>>)
>
> Vote will be open for 72 hours.
>
> Thank you to everyone that is able to VOTE as well as everyone that
> contributed to Apache FLAGON 1.0.0 & 1.0.0r.
>
> [ ] +1, let's get it released!!!
> [ ] +/-0, fine, but consider to fix few issues before...
> [ ] -1, nope, because... (and please explain why)

[jira] [Commented] (FLAGON-395) Add ability to send data via Sockets (as opposed to POST)

[Michael Schreiber (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLAGON-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863084#comment-16863084
 ] 

Michael Schreiber commented on FLAGON-395:
--

Yup, yup. sounds good! I'll do that!

> Add ability to send data via Sockets (as opposed to POST)
> -
>
> Key: FLAGON-395
> URL: https://issues.apache.org/jira/browse/FLAGON-395
> Project: Flagon
>  Issue Type: Improvement
>  Components: UserALE.js
>    Reporter: Michael Schreiber
>Assignee: Rob Foley
>Priority: Minor
>  Labels: features
>
> It would be nice to add the capability to send via sockets, as opposed to 
> POST requests, however, this adds some additional complication with how to 
> reference the app.
> I have some work in progress 
> ([https://github.com/mschreib28/UserALE-sockets]). But anyone is welcome to 
> work on this.



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

[jira] [Commented] (FLAGON-395) Add ability to send data via Sockets (as opposed to POST)

[Michael Schreiber (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLAGON-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863069#comment-16863069
 ] 

Michael Schreiber commented on FLAGON-395:
--

Thanks!

Two things:
1) I updated so this is a proper fork and branch linked to FLAGON-395.

2) I don't like that by introducing this feature it's introducing dependencies. 
I hope to resolve that (somehow), but not sure how, quite yet...

New branch: 
[https://github.com/mschreib28/incubator-flagon-useralejs/tree/FLAGON-395]

> Add ability to send data via Sockets (as opposed to POST)
> -
>
> Key: FLAGON-395
> URL: https://issues.apache.org/jira/browse/FLAGON-395
> Project: Flagon
>  Issue Type: Improvement
>  Components: UserALE.js
>    Reporter: Michael Schreiber
>Assignee: Rob Foley
>Priority: Minor
>  Labels: features
>
> It would be nice to add the capability to send via sockets, as opposed to 
> POST requests, however, this adds some additional complication with how to 
> reference the app.
> I have some work in progress 
> ([https://github.com/mschreib28/UserALE-sockets]). But anyone is welcome to 
> work on this.



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

[jira] [Created] (FLAGON-395) Add ability to send data via Sockets (as opposed to POST)

[Michael Schreiber (JIRA)]

Michael Schreiber created FLAGON-395:


 Summary: Add ability to send data via Sockets (as opposed to POST)
 Key: FLAGON-395
 URL: https://issues.apache.org/jira/browse/FLAGON-395
 Project: Flagon
  Issue Type: Improvement
  Components: UserALE.js
Reporter: Michael Schreiber
Assignee: Rob Foley


It would be nice to add the capability to send via sockets, as opposed to POST 
requests, however, this adds some additional complication with how to reference 
the app.

I have some work in progress ([https://github.com/mschreib28/UserALE-sockets]). 
But anyone is welcome to work on this.



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

[jira] [Commented] (FLAGON-297) Add Kafka producer capability to UserALE.js

[Michael Schreiber (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLAGON-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862015#comment-16862015
 ] 

Michael Schreiber commented on FLAGON-297:
--

(New to this project). My current project may end up doing this. If we do, I'll 
create the appropriate PR.

> Add Kafka producer capability to UserALE.js
> ---
>
> Key: FLAGON-297
> URL: https://issues.apache.org/jira/browse/FLAGON-297
> Project: Flagon
>  Issue Type: New Feature
>  Components: UserALE.js
>Affects Versions: UserALE.js 2.4.0
>Reporter: Joshua Poore
>Assignee: Rob Foley
>Priority: Major
>
> Likely additional meta-data would need be added to a cannonical kafka wrapper 
> so that userALE.js logs can be received and appropriately routed by a Kafka 
> Broker 
>  
>  * UserAle Web Extension can be configured to send User Activity Data to a 
> Kafka broker/cluster
>  * Verified with a manual test which will require the deployment of a dev 
> Kafka broker/cluster



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