Re: [RESULT] WAS Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Mattmann, Chris A (3980)]

:-) Congrats and more to come! :)

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++










On 6/21/16, 12:29 AM, "Poore, Joshua C." <jpo...@draper.com> wrote:

>Wow. We’re so excited about this and we’re looking forward for the hard work 
>toward full foundation membership. Thanks all!
>
>Josh
>
>From: Lewis John Mcgibbney [mailto:lewis.mcgibb...@gmail.com]
>Sent: Thursday, June 16, 2016 9:20 PM
>To: general@incubator.apache.org
>Cc: Poore, Joshua C. <jpo...@draper.com>
>Subject: [RESULT] WAS Re: [VOTE] Accept SensSoft into the Apache Incubator WAS 
>Re: [VOTE] Accept
>
>Hi general@,
>72 hours has come and gone I am therefore closing off this VOTE'ing thread.
>Thank you to everyone that was able to VOTE.
>
>[4] +1 Accept SensSoft into the Apache Incubator
>Lewis John Mcgibbney*
>Chris A Mattmann*
>Tom Barber*
>Henry Saptura*
>
>[0] +/-0 Not overly bothered either way
>[0] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
>*IPMC binding
>So great news, SensSoft is accepted into the Incubator :) :) :)
>I'll progress with workflow.
>Thanks folks.
>Lewis
>
>On Mon, Jun 13, 2016 at 3:07 PM, Lewis John Mcgibbney 
><lewis.mcgibb...@gmail.com<mailto:lewis.mcgibb...@gmail.com>> wrote:
>Title here should be [VOTE] Accept SensSoft into the Apache Incubator
>
>On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney 
><lewis.mcgibb...@gmail.com<mailto:lewis.mcgibb...@gmail.com>> wrote:
>Hi general@,
>Since I am back from a bit of vacation and it seems the discussion has died 
>down, I am now calling a vote on accepting SensSoft into the Apache Incubator.
>For those who are interested the DISCUSS thread can be found at
>https://s.apache.org/senssoft_discuss
>
>This vote will run for the usual 72 hours.
>Please VOTE as follows
>[ ] +1 Accept SensSoft into the Apache Incubator
>[ ] +/-0 Not overly bothered either way
>[ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
>Thanks everyone who contributed to DISCUSS and is able to participate in VOTE
>Best
>Lewis
>P.S. Here is my +1
>
>#
>
>= SensSoft Proposal =
>
>== Abstract ==
>The Software as a Sensor™ (SensSoft) Project offers an open-source (ALv2.0)
>software tool usability testing platform. It includes a number of
>components that work together to provide a platform for collecting data
>about user interactions with software tools, as well as archiving,
>analyzing and visualizing that data. Additional components allow for
>conducting web-based experiments in order to capture this data within a
>larger experimental framework for formal user testing. These components
>currently support Java Script-based web applications, although the schema
>for “logging” user interactions can support mobile and desktop
>applications, as well. Collectively, the Software as a Sensor Project
>provides an open source platform for assessing how users interacted with
>technology, not just collecting what they interacted with.
>
>== Proposal ==
>The Software as a Sensor™ Project is a next-generation platform for
>analyzing how individuals and groups of people make use of software tools
>to perform tasks or interact with other systems. It is composed of a number
>of integrated components:
> * User Analytic Logging Engine (User ALE) refers to a simple Application
>Program Interface (API) and backend infrastructure. User ALE provides
>“instrumentation” for software tools, such that each user interaction
>within the application can be logged, and sent as a JSON message to an
>Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
>   * The API provides a robust schema that makes user activities human
>readable, and provides an interpretive context for understanding that
>activity’s functional relevance within the application. The schema provides
>highly granular information best suited for advanced analytics. This
>hierarchical schema is as follows:
> * Element Group: App features that share function (e.g., map group)
> * Element Sub: Specific App feature (e.g., map tiles)
> * Element Type: Category of

RE: [RESULT] WAS Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Poore, Joshua C.]

Wow. We’re so excited about this and we’re looking forward for the hard work 
toward full foundation membership. Thanks all!

Josh

From: Lewis John Mcgibbney [mailto:lewis.mcgibb...@gmail.com]
Sent: Thursday, June 16, 2016 9:20 PM
To: general@incubator.apache.org
Cc: Poore, Joshua C. <jpo...@draper.com>
Subject: [RESULT] WAS Re: [VOTE] Accept SensSoft into the Apache Incubator WAS 
Re: [VOTE] Accept

Hi general@,
72 hours has come and gone I am therefore closing off this VOTE'ing thread.
Thank you to everyone that was able to VOTE.

[4] +1 Accept SensSoft into the Apache Incubator
Lewis John Mcgibbney*
Chris A Mattmann*
Tom Barber*
Henry Saptura*

[0] +/-0 Not overly bothered either way
[0] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
*IPMC binding
So great news, SensSoft is accepted into the Incubator :) :) :)
I'll progress with workflow.
Thanks folks.
Lewis

On Mon, Jun 13, 2016 at 3:07 PM, Lewis John Mcgibbney 
<lewis.mcgibb...@gmail.com<mailto:lewis.mcgibb...@gmail.com>> wrote:
Title here should be [VOTE] Accept SensSoft into the Apache Incubator

On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney 
<lewis.mcgibb...@gmail.com<mailto:lewis.mcgibb...@gmail.com>> wrote:
Hi general@,
Since I am back from a bit of vacation and it seems the discussion has died 
down, I am now calling a vote on accepting SensSoft into the Apache Incubator.
For those who are interested the DISCUSS thread can be found at
https://s.apache.org/senssoft_discuss

This vote will run for the usual 72 hours.
Please VOTE as follows
[ ] +1 Accept SensSoft into the Apache Incubator
[ ] +/-0 Not overly bothered either way
[ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
Thanks everyone who contributed to DISCUSS and is able to participate in VOTE
Best
Lewis
P.S. Here is my +1

#

= SensSoft Proposal =

== Abstract ==
The Software as a Sensor™ (SensSoft) Project offers an open-source (ALv2.0)
software tool usability testing platform. It includes a number of
components that work together to provide a platform for collecting data
about user interactions with software tools, as well as archiving,
analyzing and visualizing that data. Additional components allow for
conducting web-based experiments in order to capture this data within a
larger experimental framework for formal user testing. These components
currently support Java Script-based web applications, although the schema
for “logging” user interactions can support mobile and desktop
applications, as well. Collectively, the Software as a Sensor Project
provides an open source platform for assessing how users interacted with
technology, not just collecting what they interacted with.

== Proposal ==
The Software as a Sensor™ Project is a next-generation platform for
analyzing how individuals and groups of people make use of software tools
to perform tasks or interact with other systems. It is composed of a number
of integrated components:
 * User Analytic Logging Engine (User ALE) refers to a simple Application
Program Interface (API) and backend infrastructure. User ALE provides
“instrumentation” for software tools, such that each user interaction
within the application can be logged, and sent as a JSON message to an
Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
   * The API provides a robust schema that makes user activities human
readable, and provides an interpretive context for understanding that
activity’s functional relevance within the application. The schema provides
highly granular information best suited for advanced analytics. This
hierarchical schema is as follows:
 * Element Group: App features that share function (e.g., map group)
 * Element Sub: Specific App feature (e.g., map tiles)
 * Element Type: Category of feature (e.g., map)
 * Element ID: [attribute] id
 * Activity: Human imposed label (e.g., “search”)
 * Action: Event class (e.g., zoom, hover, click)
   * The API can either be manually embedded in the app source code, or
implemented automatically by inserting a script tag in the source code.
   * Users can either setup up their own Elastic stack instance, or use
Vagrant, a virtualization environment, to deploy a fully configured Elastic
stack instance to ship and ingest user activity logs and visualize their
log data with Kibana.
   * RESTful APIs allow other services to access logs directly from
Elasticsearch.
   * User ALE allows adopters to own the data they collect from users
outright, and utilize it as they see fit.
 * Distill is an analytics stack for processing user activity logs
collected through User ALE. Distill is fully implemented in Python,
dependent on graph-tool to support graph analytics and other external
python libraries to query Elasticsearch. The two principle functions of
Distill are segmentation and graph analytics:
   * Segmentation allows for partitioning of the available data along
multiple axes. Subse

Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Sergio Fernández]

+1 (binding)

On Fri, Jun 17, 2016 at 1:24 AM, Henry Saputra 
wrote:

> +1 (binding)
>
> Good luck guys!
>
> On Mon, Jun 13, 2016 at 3:07 PM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
> > Title here should be [VOTE] Accept SensSoft into the Apache Incubator
> >
> > On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney <
> > lewis.mcgibb...@gmail.com> wrote:
> >
> > > Hi general@,
> > > Since I am back from a bit of vacation and it seems the discussion has
> > > died down, I am now calling a vote on accepting SensSoft into the
> Apache
> > > Incubator.
> > >
> > > For those who are interested the DISCUSS thread can be found at
> > > https://s.apache.org/senssoft_discuss
> > >
> > > This vote will run for the usual 72 hours.
> > >
> > > Please VOTE as follows
> > >
> > > [ ] +1 Accept SensSoft into the Apache Incubator
> > > [ ] +/-0 Not overly bothered either way
> > > [ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state
> > why)
> > >
> > > Thanks everyone who contributed to DISCUSS and is able to participate
> in
> > > VOTE
> > >
> > > Best
> > > Lewis
> > > P.S. Here is my +1
> > >
> > > #
> > >
> > > = SensSoft Proposal =
> > >
> > > == Abstract ==
> > > The Software as a Sensor™ (SensSoft) Project offers an open-source
> > (ALv2.0)
> > > software tool usability testing platform. It includes a number of
> > > components that work together to provide a platform for collecting data
> > > about user interactions with software tools, as well as archiving,
> > > analyzing and visualizing that data. Additional components allow for
> > > conducting web-based experiments in order to capture this data within a
> > > larger experimental framework for formal user testing. These components
> > > currently support Java Script-based web applications, although the
> schema
> > > for “logging” user interactions can support mobile and desktop
> > > applications, as well. Collectively, the Software as a Sensor Project
> > > provides an open source platform for assessing how users interacted
> with
> > > technology, not just collecting what they interacted with.
> > >
> > > == Proposal ==
> > > The Software as a Sensor™ Project is a next-generation platform for
> > > analyzing how individuals and groups of people make use of software
> tools
> > > to perform tasks or interact with other systems. It is composed of a
> > number
> > > of integrated components:
> > >  * User Analytic Logging Engine (User ALE) refers to a simple
> Application
> > > Program Interface (API) and backend infrastructure. User ALE provides
> > > “instrumentation” for software tools, such that each user interaction
> > > within the application can be logged, and sent as a JSON message to an
> > > Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
> > >* The API provides a robust schema that makes user activities human
> > > readable, and provides an interpretive context for understanding that
> > > activity’s functional relevance within the application. The schema
> > provides
> > > highly granular information best suited for advanced analytics. This
> > > hierarchical schema is as follows:
> > >  * Element Group: App features that share function (e.g., map
> group)
> > >  * Element Sub: Specific App feature (e.g., map tiles)
> > >  * Element Type: Category of feature (e.g., map)
> > >  * Element ID: [attribute] id
> > >  * Activity: Human imposed label (e.g., “search”)
> > >  * Action: Event class (e.g., zoom, hover, click)
> > >* The API can either be manually embedded in the app source code, or
> > > implemented automatically by inserting a script tag in the source code.
> > >* Users can either setup up their own Elastic stack instance, or use
> > > Vagrant, a virtualization environment, to deploy a fully configured
> > Elastic
> > > stack instance to ship and ingest user activity logs and visualize
> their
> > > log data with Kibana.
> > >* RESTful APIs allow other services to access logs directly from
> > > Elasticsearch.
> > >* User ALE allows adopters to own the data they collect from users
> > > outright, and utilize it as they see fit.
> > >  * Distill is an analytics stack for processing user activity logs
> > > collected through User ALE. Distill is fully implemented in Python,
> > > dependent on graph-tool to support graph analytics and other external
> > > python libraries to query Elasticsearch. The two principle functions of
> > > Distill are segmentation and graph analytics:
> > >* Segmentation allows for partitioning of the available data along
> > > multiple axes. Subsets of log data can be selected via their attributes
> > in
> > > User ALE (e.g. Element Group or Activity), and by users/sessions.
> > Distill
> > > also has the capability to ingest and segment data by additional
> > attributes
> > > collected through other channels (e.g. survey data, demographics).This
> > > allows adopters to focus 

[RESULT] WAS Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Lewis John Mcgibbney]

Hi general@,
72 hours has come and gone I am therefore closing off this VOTE'ing thread.
Thank you to everyone that was able to VOTE.


[4] +1 Accept SensSoft into the Apache Incubator
Lewis John Mcgibbney*
Chris A Mattmann*
Tom Barber*
Henry Saptura*

[0] +/-0 Not overly bothered either way
[0] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)

*IPMC binding

So great news, SensSoft is accepted into the Incubator :) :) :)
I'll progress with workflow.
Thanks folks.
Lewis

On Mon, Jun 13, 2016 at 3:07 PM, Lewis John Mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Title here should be [VOTE] Accept SensSoft into the Apache Incubator
>
> On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
>> Hi general@,
>> Since I am back from a bit of vacation and it seems the discussion has
>> died down, I am now calling a vote on accepting SensSoft into the Apache
>> Incubator.
>>
>> For those who are interested the DISCUSS thread can be found at
>> https://s.apache.org/senssoft_discuss
>>
>> This vote will run for the usual 72 hours.
>>
>> Please VOTE as follows
>>
>> [ ] +1 Accept SensSoft into the Apache Incubator
>> [ ] +/-0 Not overly bothered either way
>> [ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
>>
>> Thanks everyone who contributed to DISCUSS and is able to participate in
>> VOTE
>>
>> Best
>> Lewis
>> P.S. Here is my +1
>>
>> #
>>
>> = SensSoft Proposal =
>>
>> == Abstract ==
>> The Software as a Sensor™ (SensSoft) Project offers an open-source
>> (ALv2.0)
>> software tool usability testing platform. It includes a number of
>> components that work together to provide a platform for collecting data
>> about user interactions with software tools, as well as archiving,
>> analyzing and visualizing that data. Additional components allow for
>> conducting web-based experiments in order to capture this data within a
>> larger experimental framework for formal user testing. These components
>> currently support Java Script-based web applications, although the schema
>> for “logging” user interactions can support mobile and desktop
>> applications, as well. Collectively, the Software as a Sensor Project
>> provides an open source platform for assessing how users interacted with
>> technology, not just collecting what they interacted with.
>>
>> == Proposal ==
>> The Software as a Sensor™ Project is a next-generation platform for
>> analyzing how individuals and groups of people make use of software tools
>> to perform tasks or interact with other systems. It is composed of a
>> number
>> of integrated components:
>>  * User Analytic Logging Engine (User ALE) refers to a simple Application
>> Program Interface (API) and backend infrastructure. User ALE provides
>> “instrumentation” for software tools, such that each user interaction
>> within the application can be logged, and sent as a JSON message to an
>> Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
>>* The API provides a robust schema that makes user activities human
>> readable, and provides an interpretive context for understanding that
>> activity’s functional relevance within the application. The schema
>> provides
>> highly granular information best suited for advanced analytics. This
>> hierarchical schema is as follows:
>>  * Element Group: App features that share function (e.g., map group)
>>  * Element Sub: Specific App feature (e.g., map tiles)
>>  * Element Type: Category of feature (e.g., map)
>>  * Element ID: [attribute] id
>>  * Activity: Human imposed label (e.g., “search”)
>>  * Action: Event class (e.g., zoom, hover, click)
>>* The API can either be manually embedded in the app source code, or
>> implemented automatically by inserting a script tag in the source code.
>>* Users can either setup up their own Elastic stack instance, or use
>> Vagrant, a virtualization environment, to deploy a fully configured
>> Elastic
>> stack instance to ship and ingest user activity logs and visualize their
>> log data with Kibana.
>>* RESTful APIs allow other services to access logs directly from
>> Elasticsearch.
>>* User ALE allows adopters to own the data they collect from users
>> outright, and utilize it as they see fit.
>>  * Distill is an analytics stack for processing user activity logs
>> collected through User ALE. Distill is fully implemented in Python,
>> dependent on graph-tool to support graph analytics and other external
>> python libraries to query Elasticsearch. The two principle functions of
>> Distill are segmentation and graph analytics:
>>* Segmentation allows for partitioning of the available data along
>> multiple axes. Subsets of log data can be selected via their attributes in
>> User ALE (e.g. Element Group or Activity), and by users/sessions.  Distill
>> also has the capability to ingest and segment data by additional
>> attributes
>> collected through other 

Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Henry Saputra]

+1 (binding)

Good luck guys!

On Mon, Jun 13, 2016 at 3:07 PM, Lewis John Mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Title here should be [VOTE] Accept SensSoft into the Apache Incubator
>
> On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
> > Hi general@,
> > Since I am back from a bit of vacation and it seems the discussion has
> > died down, I am now calling a vote on accepting SensSoft into the Apache
> > Incubator.
> >
> > For those who are interested the DISCUSS thread can be found at
> > https://s.apache.org/senssoft_discuss
> >
> > This vote will run for the usual 72 hours.
> >
> > Please VOTE as follows
> >
> > [ ] +1 Accept SensSoft into the Apache Incubator
> > [ ] +/-0 Not overly bothered either way
> > [ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state
> why)
> >
> > Thanks everyone who contributed to DISCUSS and is able to participate in
> > VOTE
> >
> > Best
> > Lewis
> > P.S. Here is my +1
> >
> > #
> >
> > = SensSoft Proposal =
> >
> > == Abstract ==
> > The Software as a Sensor™ (SensSoft) Project offers an open-source
> (ALv2.0)
> > software tool usability testing platform. It includes a number of
> > components that work together to provide a platform for collecting data
> > about user interactions with software tools, as well as archiving,
> > analyzing and visualizing that data. Additional components allow for
> > conducting web-based experiments in order to capture this data within a
> > larger experimental framework for formal user testing. These components
> > currently support Java Script-based web applications, although the schema
> > for “logging” user interactions can support mobile and desktop
> > applications, as well. Collectively, the Software as a Sensor Project
> > provides an open source platform for assessing how users interacted with
> > technology, not just collecting what they interacted with.
> >
> > == Proposal ==
> > The Software as a Sensor™ Project is a next-generation platform for
> > analyzing how individuals and groups of people make use of software tools
> > to perform tasks or interact with other systems. It is composed of a
> number
> > of integrated components:
> >  * User Analytic Logging Engine (User ALE) refers to a simple Application
> > Program Interface (API) and backend infrastructure. User ALE provides
> > “instrumentation” for software tools, such that each user interaction
> > within the application can be logged, and sent as a JSON message to an
> > Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
> >* The API provides a robust schema that makes user activities human
> > readable, and provides an interpretive context for understanding that
> > activity’s functional relevance within the application. The schema
> provides
> > highly granular information best suited for advanced analytics. This
> > hierarchical schema is as follows:
> >  * Element Group: App features that share function (e.g., map group)
> >  * Element Sub: Specific App feature (e.g., map tiles)
> >  * Element Type: Category of feature (e.g., map)
> >  * Element ID: [attribute] id
> >  * Activity: Human imposed label (e.g., “search”)
> >  * Action: Event class (e.g., zoom, hover, click)
> >* The API can either be manually embedded in the app source code, or
> > implemented automatically by inserting a script tag in the source code.
> >* Users can either setup up their own Elastic stack instance, or use
> > Vagrant, a virtualization environment, to deploy a fully configured
> Elastic
> > stack instance to ship and ingest user activity logs and visualize their
> > log data with Kibana.
> >* RESTful APIs allow other services to access logs directly from
> > Elasticsearch.
> >* User ALE allows adopters to own the data they collect from users
> > outright, and utilize it as they see fit.
> >  * Distill is an analytics stack for processing user activity logs
> > collected through User ALE. Distill is fully implemented in Python,
> > dependent on graph-tool to support graph analytics and other external
> > python libraries to query Elasticsearch. The two principle functions of
> > Distill are segmentation and graph analytics:
> >* Segmentation allows for partitioning of the available data along
> > multiple axes. Subsets of log data can be selected via their attributes
> in
> > User ALE (e.g. Element Group or Activity), and by users/sessions.
> Distill
> > also has the capability to ingest and segment data by additional
> attributes
> > collected through other channels (e.g. survey data, demographics).This
> > allows adopters to focus their analysis of log data on precisely the
> > attributes of their app (or users) they care most about.
> >* Distill’s usage metrics are derived from a probabilistic
> > representation of the time series of users’ interactions with the
> elements
> > of the application. A directed network is constructed from 

Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Tom Barber]

Sorry Lewis,

I read through it the other day and though I'd replied, clearly not.

+1 binding.

On Thu, Jun 16, 2016 at 11:40 PM, Lewis John Mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Hi Folks,
> The SensSoft proposal needs a bit of TLC from general@
> If software-as-a-sensor, usability testing and user characterization are
> your thing then please consider giving the proposal a read through.
> At this stage in the game we are looking at obtaining one more binding PPMC
> VOTE in order to push through with acceptance and incubation.
> Thanks in advance to anyone who can facilitate this.
> Lewis
>
> On Mon, Jun 13, 2016 at 3:07 PM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
> > Title here should be [VOTE] Accept SensSoft into the Apache Incubator
> >
> > On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney <
> > lewis.mcgibb...@gmail.com> wrote:
> >
> >> Hi general@,
> >> Since I am back from a bit of vacation and it seems the discussion has
> >> died down, I am now calling a vote on accepting SensSoft into the Apache
> >> Incubator.
> >>
> >> For those who are interested the DISCUSS thread can be found at
> >> https://s.apache.org/senssoft_discuss
> >>
> >> This vote will run for the usual 72 hours.
> >>
> >> Please VOTE as follows
> >>
> >> [ ] +1 Accept SensSoft into the Apache Incubator
> >> [ ] +/-0 Not overly bothered either way
> >> [ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state
> why)
> >>
> >> Thanks everyone who contributed to DISCUSS and is able to participate in
> >> VOTE
> >>
> >> Best
> >> Lewis
> >> P.S. Here is my +1
> >>
> >> #
> >>
> >> = SensSoft Proposal =
> >>
> >> == Abstract ==
> >> The Software as a Sensor™ (SensSoft) Project offers an open-source
> >> (ALv2.0)
> >> software tool usability testing platform. It includes a number of
> >> components that work together to provide a platform for collecting data
> >> about user interactions with software tools, as well as archiving,
> >> analyzing and visualizing that data. Additional components allow for
> >> conducting web-based experiments in order to capture this data within a
> >> larger experimental framework for formal user testing. These components
> >> currently support Java Script-based web applications, although the
> schema
> >> for “logging” user interactions can support mobile and desktop
> >> applications, as well. Collectively, the Software as a Sensor Project
> >> provides an open source platform for assessing how users interacted with
> >> technology, not just collecting what they interacted with.
> >>
> >> == Proposal ==
> >> The Software as a Sensor™ Project is a next-generation platform for
> >> analyzing how individuals and groups of people make use of software
> tools
> >> to perform tasks or interact with other systems. It is composed of a
> >> number
> >> of integrated components:
> >>  * User Analytic Logging Engine (User ALE) refers to a simple
> Application
> >> Program Interface (API) and backend infrastructure. User ALE provides
> >> “instrumentation” for software tools, such that each user interaction
> >> within the application can be logged, and sent as a JSON message to an
> >> Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
> >>* The API provides a robust schema that makes user activities human
> >> readable, and provides an interpretive context for understanding that
> >> activity’s functional relevance within the application. The schema
> >> provides
> >> highly granular information best suited for advanced analytics. This
> >> hierarchical schema is as follows:
> >>  * Element Group: App features that share function (e.g., map group)
> >>  * Element Sub: Specific App feature (e.g., map tiles)
> >>  * Element Type: Category of feature (e.g., map)
> >>  * Element ID: [attribute] id
> >>  * Activity: Human imposed label (e.g., “search”)
> >>  * Action: Event class (e.g., zoom, hover, click)
> >>* The API can either be manually embedded in the app source code, or
> >> implemented automatically by inserting a script tag in the source code.
> >>* Users can either setup up their own Elastic stack instance, or use
> >> Vagrant, a virtualization environment, to deploy a fully configured
> >> Elastic
> >> stack instance to ship and ingest user activity logs and visualize their
> >> log data with Kibana.
> >>* RESTful APIs allow other services to access logs directly from
> >> Elasticsearch.
> >>* User ALE allows adopters to own the data they collect from users
> >> outright, and utilize it as they see fit.
> >>  * Distill is an analytics stack for processing user activity logs
> >> collected through User ALE. Distill is fully implemented in Python,
> >> dependent on graph-tool to support graph analytics and other external
> >> python libraries to query Elasticsearch. The two principle functions of
> >> Distill are segmentation and graph analytics:
> >>* Segmentation allows for partitioning 

Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Lewis John Mcgibbney]

Hi Folks,
The SensSoft proposal needs a bit of TLC from general@
If software-as-a-sensor, usability testing and user characterization are
your thing then please consider giving the proposal a read through.
At this stage in the game we are looking at obtaining one more binding PPMC
VOTE in order to push through with acceptance and incubation.
Thanks in advance to anyone who can facilitate this.
Lewis

On Mon, Jun 13, 2016 at 3:07 PM, Lewis John Mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Title here should be [VOTE] Accept SensSoft into the Apache Incubator
>
> On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
>
>> Hi general@,
>> Since I am back from a bit of vacation and it seems the discussion has
>> died down, I am now calling a vote on accepting SensSoft into the Apache
>> Incubator.
>>
>> For those who are interested the DISCUSS thread can be found at
>> https://s.apache.org/senssoft_discuss
>>
>> This vote will run for the usual 72 hours.
>>
>> Please VOTE as follows
>>
>> [ ] +1 Accept SensSoft into the Apache Incubator
>> [ ] +/-0 Not overly bothered either way
>> [ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
>>
>> Thanks everyone who contributed to DISCUSS and is able to participate in
>> VOTE
>>
>> Best
>> Lewis
>> P.S. Here is my +1
>>
>> #
>>
>> = SensSoft Proposal =
>>
>> == Abstract ==
>> The Software as a Sensor™ (SensSoft) Project offers an open-source
>> (ALv2.0)
>> software tool usability testing platform. It includes a number of
>> components that work together to provide a platform for collecting data
>> about user interactions with software tools, as well as archiving,
>> analyzing and visualizing that data. Additional components allow for
>> conducting web-based experiments in order to capture this data within a
>> larger experimental framework for formal user testing. These components
>> currently support Java Script-based web applications, although the schema
>> for “logging” user interactions can support mobile and desktop
>> applications, as well. Collectively, the Software as a Sensor Project
>> provides an open source platform for assessing how users interacted with
>> technology, not just collecting what they interacted with.
>>
>> == Proposal ==
>> The Software as a Sensor™ Project is a next-generation platform for
>> analyzing how individuals and groups of people make use of software tools
>> to perform tasks or interact with other systems. It is composed of a
>> number
>> of integrated components:
>>  * User Analytic Logging Engine (User ALE) refers to a simple Application
>> Program Interface (API) and backend infrastructure. User ALE provides
>> “instrumentation” for software tools, such that each user interaction
>> within the application can be logged, and sent as a JSON message to an
>> Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
>>* The API provides a robust schema that makes user activities human
>> readable, and provides an interpretive context for understanding that
>> activity’s functional relevance within the application. The schema
>> provides
>> highly granular information best suited for advanced analytics. This
>> hierarchical schema is as follows:
>>  * Element Group: App features that share function (e.g., map group)
>>  * Element Sub: Specific App feature (e.g., map tiles)
>>  * Element Type: Category of feature (e.g., map)
>>  * Element ID: [attribute] id
>>  * Activity: Human imposed label (e.g., “search”)
>>  * Action: Event class (e.g., zoom, hover, click)
>>* The API can either be manually embedded in the app source code, or
>> implemented automatically by inserting a script tag in the source code.
>>* Users can either setup up their own Elastic stack instance, or use
>> Vagrant, a virtualization environment, to deploy a fully configured
>> Elastic
>> stack instance to ship and ingest user activity logs and visualize their
>> log data with Kibana.
>>* RESTful APIs allow other services to access logs directly from
>> Elasticsearch.
>>* User ALE allows adopters to own the data they collect from users
>> outright, and utilize it as they see fit.
>>  * Distill is an analytics stack for processing user activity logs
>> collected through User ALE. Distill is fully implemented in Python,
>> dependent on graph-tool to support graph analytics and other external
>> python libraries to query Elasticsearch. The two principle functions of
>> Distill are segmentation and graph analytics:
>>* Segmentation allows for partitioning of the available data along
>> multiple axes. Subsets of log data can be selected via their attributes in
>> User ALE (e.g. Element Group or Activity), and by users/sessions.  Distill
>> also has the capability to ingest and segment data by additional
>> attributes
>> collected through other channels (e.g. survey data, demographics).This
>> allows adopters to focus their analysis of log 

Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Mattmann, Chris A (3980)]

+1

Sent from my iPhone

> On Jun 13, 2016, at 4:34 PM, Lewis John Mcgibbney  
> wrote:
> 
> Title here should be [VOTE] Accept SensSoft into the Apache Incubator
> 
> On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
> 
>> Hi general@,
>> Since I am back from a bit of vacation and it seems the discussion has
>> died down, I am now calling a vote on accepting SensSoft into the Apache
>> Incubator.
>> 
>> For those who are interested the DISCUSS thread can be found at
>> https://s.apache.org/senssoft_discuss
>> 
>> This vote will run for the usual 72 hours.
>> 
>> Please VOTE as follows
>> 
>> [ ] +1 Accept SensSoft into the Apache Incubator
>> [ ] +/-0 Not overly bothered either way
>> [ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
>> 
>> Thanks everyone who contributed to DISCUSS and is able to participate in
>> VOTE
>> 
>> Best
>> Lewis
>> P.S. Here is my +1
>> 
>> #
>> 
>> = SensSoft Proposal =
>> 
>> == Abstract ==
>> The Software as a Sensor™ (SensSoft) Project offers an open-source (ALv2.0)
>> software tool usability testing platform. It includes a number of
>> components that work together to provide a platform for collecting data
>> about user interactions with software tools, as well as archiving,
>> analyzing and visualizing that data. Additional components allow for
>> conducting web-based experiments in order to capture this data within a
>> larger experimental framework for formal user testing. These components
>> currently support Java Script-based web applications, although the schema
>> for “logging” user interactions can support mobile and desktop
>> applications, as well. Collectively, the Software as a Sensor Project
>> provides an open source platform for assessing how users interacted with
>> technology, not just collecting what they interacted with.
>> 
>> == Proposal ==
>> The Software as a Sensor™ Project is a next-generation platform for
>> analyzing how individuals and groups of people make use of software tools
>> to perform tasks or interact with other systems. It is composed of a number
>> of integrated components:
>> * User Analytic Logging Engine (User ALE) refers to a simple Application
>> Program Interface (API) and backend infrastructure. User ALE provides
>> “instrumentation” for software tools, such that each user interaction
>> within the application can be logged, and sent as a JSON message to an
>> Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
>>   * The API provides a robust schema that makes user activities human
>> readable, and provides an interpretive context for understanding that
>> activity’s functional relevance within the application. The schema provides
>> highly granular information best suited for advanced analytics. This
>> hierarchical schema is as follows:
>> * Element Group: App features that share function (e.g., map group)
>> * Element Sub: Specific App feature (e.g., map tiles)
>> * Element Type: Category of feature (e.g., map)
>> * Element ID: [attribute] id
>> * Activity: Human imposed label (e.g., “search”)
>> * Action: Event class (e.g., zoom, hover, click)
>>   * The API can either be manually embedded in the app source code, or
>> implemented automatically by inserting a script tag in the source code.
>>   * Users can either setup up their own Elastic stack instance, or use
>> Vagrant, a virtualization environment, to deploy a fully configured Elastic
>> stack instance to ship and ingest user activity logs and visualize their
>> log data with Kibana.
>>   * RESTful APIs allow other services to access logs directly from
>> Elasticsearch.
>>   * User ALE allows adopters to own the data they collect from users
>> outright, and utilize it as they see fit.
>> * Distill is an analytics stack for processing user activity logs
>> collected through User ALE. Distill is fully implemented in Python,
>> dependent on graph-tool to support graph analytics and other external
>> python libraries to query Elasticsearch. The two principle functions of
>> Distill are segmentation and graph analytics:
>>   * Segmentation allows for partitioning of the available data along
>> multiple axes. Subsets of log data can be selected via their attributes in
>> User ALE (e.g. Element Group or Activity), and by users/sessions.  Distill
>> also has the capability to ingest and segment data by additional attributes
>> collected through other channels (e.g. survey data, demographics).This
>> allows adopters to focus their analysis of log data on precisely the
>> attributes of their app (or users) they care most about.
>>   * Distill’s usage metrics are derived from a probabilistic
>> representation of the time series of users’ interactions with the elements
>> of the application. A directed network is constructed from the
>> representation, and metrics from graph theory (e.g. betweenness centrality,
>> in/out-degree of nodes) 

[VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Lewis John Mcgibbney]

Title here should be [VOTE] Accept SensSoft into the Apache Incubator

On Mon, Jun 13, 2016 at 10:55 AM, Lewis John Mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Hi general@,
> Since I am back from a bit of vacation and it seems the discussion has
> died down, I am now calling a vote on accepting SensSoft into the Apache
> Incubator.
>
> For those who are interested the DISCUSS thread can be found at
> https://s.apache.org/senssoft_discuss
>
> This vote will run for the usual 72 hours.
>
> Please VOTE as follows
>
> [ ] +1 Accept SensSoft into the Apache Incubator
> [ ] +/-0 Not overly bothered either way
> [ ] -1 DO NOT accept SensSoft into the Apache Incubator (please state why)
>
> Thanks everyone who contributed to DISCUSS and is able to participate in
> VOTE
>
> Best
> Lewis
> P.S. Here is my +1
>
> #
>
> = SensSoft Proposal =
>
> == Abstract ==
> The Software as a Sensor™ (SensSoft) Project offers an open-source (ALv2.0)
> software tool usability testing platform. It includes a number of
> components that work together to provide a platform for collecting data
> about user interactions with software tools, as well as archiving,
> analyzing and visualizing that data. Additional components allow for
> conducting web-based experiments in order to capture this data within a
> larger experimental framework for formal user testing. These components
> currently support Java Script-based web applications, although the schema
> for “logging” user interactions can support mobile and desktop
> applications, as well. Collectively, the Software as a Sensor Project
> provides an open source platform for assessing how users interacted with
> technology, not just collecting what they interacted with.
>
> == Proposal ==
> The Software as a Sensor™ Project is a next-generation platform for
> analyzing how individuals and groups of people make use of software tools
> to perform tasks or interact with other systems. It is composed of a number
> of integrated components:
>  * User Analytic Logging Engine (User ALE) refers to a simple Application
> Program Interface (API) and backend infrastructure. User ALE provides
> “instrumentation” for software tools, such that each user interaction
> within the application can be logged, and sent as a JSON message to an
> Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
>* The API provides a robust schema that makes user activities human
> readable, and provides an interpretive context for understanding that
> activity’s functional relevance within the application. The schema provides
> highly granular information best suited for advanced analytics. This
> hierarchical schema is as follows:
>  * Element Group: App features that share function (e.g., map group)
>  * Element Sub: Specific App feature (e.g., map tiles)
>  * Element Type: Category of feature (e.g., map)
>  * Element ID: [attribute] id
>  * Activity: Human imposed label (e.g., “search”)
>  * Action: Event class (e.g., zoom, hover, click)
>* The API can either be manually embedded in the app source code, or
> implemented automatically by inserting a script tag in the source code.
>* Users can either setup up their own Elastic stack instance, or use
> Vagrant, a virtualization environment, to deploy a fully configured Elastic
> stack instance to ship and ingest user activity logs and visualize their
> log data with Kibana.
>* RESTful APIs allow other services to access logs directly from
> Elasticsearch.
>* User ALE allows adopters to own the data they collect from users
> outright, and utilize it as they see fit.
>  * Distill is an analytics stack for processing user activity logs
> collected through User ALE. Distill is fully implemented in Python,
> dependent on graph-tool to support graph analytics and other external
> python libraries to query Elasticsearch. The two principle functions of
> Distill are segmentation and graph analytics:
>* Segmentation allows for partitioning of the available data along
> multiple axes. Subsets of log data can be selected via their attributes in
> User ALE (e.g. Element Group or Activity), and by users/sessions.  Distill
> also has the capability to ingest and segment data by additional attributes
> collected through other channels (e.g. survey data, demographics).This
> allows adopters to focus their analysis of log data on precisely the
> attributes of their app (or users) they care most about.
>* Distill’s usage metrics are derived from a probabilistic
> representation of the time series of users’ interactions with the elements
> of the application. A directed network is constructed from the
> representation, and metrics from graph theory (e.g. betweenness centrality,
> in/out-degree of nodes) are derived from the structure. These metrics
> provide adopters ways of understanding how different facets of the app are
> used together, and they capture canonical usage patterns of their
> application. This