RE: [RESULT] WAS Re: [VOTE] Graduate the Apache SensSoft (Incubating) Project

[Poore, Joshua C.]

Yay!

-Original Message-
From: lewis john mcgibbney 
Sent: Tuesday, May 1, 2018 10:38 PM
To: dev@senssoft.incubator.apache.org; u...@senssoft.incubator.apache.org
Subject: [RESULT] WAS Re: [VOTE] Graduate the Apache SensSoft (Incubating) 
Project

Hi Folks,
72 hours has come and gone. I'm going to close this VOTE with the RESULT 
below...
Thank you everyone that was able to VOTE

[ ] +1 Graduate the Apache SensSoft (Incubating) Project lewis john mcgibbney* 
Joshua Poore* Rob Foley* Laura Mariano Arthi Vezhavendan*

[ ] -1 NO NOT Graduate the Apache SensSoft (Incubating) Project... please 
provide reasoning

* SensSoft PPMC Binding

The VOTE therefore passes... :)
I'll progress with the remainder of the Graduation as per the hyperlink below.
Best
Lewis

On Tue, Apr 24, 2018 at 10:01 PM, lewis john mcgibbney 
wrote:

> Hi Folks,
> I would like to open a VOTE for graduating the Apache SensSoft
> (Incubating) project.
> For those that are interested, the Incubator guidelines on graduation
> can be found at [0].
> SensSoft has been reporting to the IPMC since 17th August 2016 and
> made one Incubating release.
>
> SensSoft Basics
>
>- Podling Proposal 
>- Status: current
>- Established: 2016-07-13
>- Incubating for 651 days
>- Prior Board Reports
>
>
> There are a few issues to resolve before drafting the graduation
> resolution however this community VOTE is timely. The VOTE will be
> open at least 72 hours and will pass if 3 +1's are received from the SensSoft 
> PPMC.
>
> [ ] +1 Graduate the Apache SensSoft (Incubating) Project [ ] -1 NO NOT
> Graduate the Apache SensSoft (Incubating) Project... please provide
> reasoning
>
> P.S. Here is my binding +1
>
> [0] https://incubator.apache.org/guides/graduation.html#the_
> graduation_process
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>



--
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.

RE: [DISCUSS] Drafting Graduation Template

[Poore, Joshua C.]

Lewis,

SOLD. Have spoken to some of our committers about this. A few were nervous 
about this, but some of those felt better when they looked through the 
portfolio and realized that Top Level projects aren't just monsters like Open 
Office, Kafka, Solr, and Tika.

Let's get the process started. Now is the right time--we have some funding to 
push some major upgrades to our back-end, and do some much needed house keeping 
on our website.

We're also about ready to clean up our UserALE.js branches, and believe it or 
not, we're a few tickets away from a releasable 1.1., which features our 
browser plugin packaging.

The road map after that is going to be... very exciting. We have a few million 
behind us for some really great stuff.

Josh

-Original Message-
From: lewis john mcgibbney <lewi...@apache.org>
Sent: Wednesday, April 18, 2018 2:07 PM
To: dev@senssoft.incubator.apache.org
Subject: Re: [DISCUSS] Drafting Graduation Template

Hi Josh,
Replies inline

On Sun, Apr 15, 2018 at 5:27 PM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: "Poore, Joshua C." <jpo...@draper.com>
> To: "dev@senssoft.incubator.apache.org"
> <dev@senssoft.incubator.apache.org
> >
> Cc:
> Bcc:
> Date: Fri, 13 Apr 2018 02:14:04 +
> Subject: RE: [DISCUSS] Drafting Graduation Template @lewismc
>
> I think this is really cool. Leading with userale and some offerings
> for back end configs, I think this makes sense. Distill and TAP aren't
> far behind.
>
> Quick run through of materials (will do more thorough scrub this
> weekend) and I have two questions:
>
> 1. Beyond the basics of project management, product ownership, and
> documentation/marketing, what additional administrative or
> organizational duties (beyond Quarterly reports, etc.) can we expect
> to take on after graduating?
>

Honestly, not a lot. We would elect a PMC Chair. I would most likely nominate 
yourself. The PMC Chair would deal with the above. It is a minimal 
responsibility.


> 2. Will you show us how to use all the cool Apache bots for licensing,
> checksums, etc., etc., :)
>

Absolutely, I will be around for quite a while post graduation. I am always 
available to answer questions.


> 3. Big question: Given that there aren't many (if any) projects like
> ours in the big data portfolio, do you see us as graduating to top
> level project, or a child of which project?
>

Top-level project without a doubt.


> 4. Do you think we have the support from the ASF Board to graduate?
>

Yes I think we have demonstrated the ability to 1) release software, 2) grow 
community through election and VOTE'ing of committers and a project management 
committee, and 3) use VOTE'ing as a mechanism for driving progress e.g. 
releases, addition to committer-base, etc.


>
> Besides these questions (and maybe a lot more follow-ups), I'm ready
> to commit to this.
>

Great, I am glad. I'm pretty busy right now so I will come back to this as soon 
as a I can.
Thanks for the continued support from you all.
Driving towards another release of any components within the SensSoft stack 
would be the primary goal moving forward.
Lewis

 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.

RE: [DISCUSS] Drafting Graduation Template

[Poore, Joshua C.]

@lewismc

I think this is really cool. Leading with userale and some offerings for back 
end configs, I think this makes sense. Distill and TAP aren't far behind.

Quick run through of materials (will do more thorough scrub this weekend) and I 
have two questions:

1. Beyond the basics of project management, product ownership, and 
documentation/marketing, what additional administrative or organizational 
duties (beyond Quarterly reports, etc.) can we expect to take on after 
graduating?
2. Will you show us how to use all the cool Apache bots for licensing, 
checksums, etc., etc., :)
3. Big question: Given that there aren't many (if any) projects like ours in 
the big data portfolio, do you see us as graduating to top level project, or a 
child of which project?
4. Do you think we have the support from the ASF Board to graduate?

Besides these questions (and maybe a lot more follow-ups), I'm ready to commit 
to this.

Josh

-Original Message-
From: lewis john mcgibbney 
Sent: Wednesday, April 11, 2018 5:05 PM
To: dev@senssoft.incubator.apache.org
Subject: [DISCUSS] Drafting Graduation Template

Hi Folks,
I would like to move SensSoft towards a graduation scenario out f the Incubator.
Please have a read through [0] and let me know if there are any issues.
Please voice issues here and we can address them together.
If I do not hear anything, I will progress with the graduation proposal as 
outlined in [0].
Thanks
Lewis

[0] https://incubator.apache.org/guides/graduation.html

--
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.

Next Steps on SensSoft post release

[Poore, Joshua C.]

Hi Lewis,

WE're very excited to be at 1.0.0 through Apache!

I'm going to be digging into the JIRA release boards to clean up the tickets 
under 1.0.0 (moving what needs to be moved to back log, enhancement, future 
releases, or deleting old/legacy tickets). Once you approve, then we would post 
the release through JIRA, correct?

Also, now that we're released, can we go ahead and start merging our branches. 
Now is the right time, and to avoid confusion in our community, we really have 
to merge the 192 branch, at minimum with Master. Can we go ahead and do that?

Josh

Joshua C. Poore, Ph.D.
Draper, Human Analytics Group
Software as a Sensor Portfolio Lead
Email [1]: jpo...@draper.com
Email [2]: poor...@apache.org
Desk: 617 258 4023
Cell: 617 352 1700


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.

RE: [VOTE] Release Apache SensSoft (Incubating) UserALE.js 1.0.0 RC#1

[Poore, Joshua C.]

+1

-Original Message-
From: Rob Foley [mailto:r...@apache.org]
Sent: Wednesday, February 21, 2018 12:29 PM
To: dev@senssoft.incubator.apache.org
Subject: Re: [VOTE] Release Apache SensSoft (Incubating) UserALE.js 1.0.0 RC#1

I'll give it a +1.

On Tue, Feb 20, 2018 at 11:29 PM, lewis john mcgibbney 
wrote:

> I missed the following
>
> [ ] +1, let's get it released!!!
> [ ] +/-0, fine, but consider to fix few issues before...
> [ ] -1, nope, because... (and please explain why)
>
> P.S. Here is my +1
>
> On Tue, Feb 20, 2018 at 8:12 PM, lewis john mcgibbney
> 
> wrote:
>
> > Hi Folks,
> > This thread is an official VOTE to release the Apache SensSoft
> > (Incubating) UserALE.js 1.0.0 RC#1.
> > The VOTE will be open for at least 72 hours and will pass if at
> > least 3 SensSoft PPMC members VOTE +1.
> > Apache SensSoft (Incubating) UserALE.js is released in a number of
> > forms
> >
> > 1) source and binary artifacts which can be found at [0] alongside
> > accompanying .asc, .md5 and .sha512 accompanying signatures.
> >
> > 2) The tagged source [1] commitId b29542e6cc1e74c4caccdeb9ed4191
> 013498e9ee
> >
> > All artifacts were signed by 48BAEBF6 2013-10-28 Lewis John
> > McGibbney (CODE SIGNING KEY)  included within
> > the SensSoft
> KEYS
> > file [2].
> >
> > Further to the VOTE passing, artifacts will also be published via
> > the NPM channel for wider distribution.
> >
> > Lewis
> >
> > [0] https://dist.apache.org/repos/dist/dev/incubator/senssoft/
> > apache-senssoft-useralejs-1.0.0/
> > [1] https://s.apache.org/fzXf
> > [2] https://dist.apache.org/repos/dist/dev/incubator/senssoft/KEYS
> >
> > --
> > http://home.apache.org/~lewismc/
> > http://people.apache.org/keys/committer/lewismc
> >
>
>
>
> --
> 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.

UserALE.js release candidate

[Poore, Joshua C.]

Hi @lewis,

Any thoughts on when we should prepare for the release candidacy?

Josh

Joshua C. Poore, Ph.D.
Draper, Human Computer Interaction Group
Software as a Sensor Portfolio Lead
Email [1]: jpo...@draper.com
Email [2]: poor...@apache.org
Desk: 617 258 4023
Cell: 617 352 1700


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.

RE: Issues with Release Management Procedure

[Poore, Joshua C.]

@msbeard has that, she's on vacation, but will get it to you Monday.

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Thursday, January 18, 2018 1:27 PM
To: dev@senssoft.incubator.apache.org
Subject: Issues with Release Management Procedure

Hi Folks,
I am following the documentation but getting hung up on [1]. The script '
./senssoft-dist/release/make-release-artifacts.sh' does not exist in any source 
code management.
Can someone make it available?
Thanks
Lewis

[0]
https://cwiki.apache.org/confluence/display/SENSSOFT/UserALE.js+Release+Management+Procedure#UserALE.jsReleaseManagementProcedure-Makingthereleaseartifacts

--
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.

RE: Creating Release Candidate for UserALE.js

[Poore, Joshua C.]

We have a bi-monthly webEx for the committers, and would like to start opening 
this up to the public. I'd love it if you could join. Would you be able to join 
@lewis if we made this Friday's @ 1600 EST (1300 PST). Twice a month. Might be 
good for getting guidance from you about and pacing the flurry of release 
candidates that are on the horizon.

@lewis if you can make this time. I will post details of this meeting to @dev 
as well as on Confluence.

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Thursday, January 11, 2018 9:50 AM
To: dev@senssoft.incubator.apache.org
Subject: Re: Creating Release Candidate for UserALE.js

Hi Josh,
Replies inline

On Thu, Jan 11, 2018 at 8:31 AM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: Joshua Poore 
> To: dev@senssoft.incubator.apache.org
> Cc:
> Bcc:
> Date: Tue, 09 Jan 2018 20:57:47 -0500
> Subject: Re: Creating Release Candidate for UserALE.js None.
> UserAle.js 0.1.0 is ready. It’s a solid product. Distill 0.1.0 is also
> ready. It’s very simple and primarily works with Tap, but we are
> building 0.2.0 now.
>

OK doke. Moving forward, I would encourage anyone from the existing SensSoft 
community to come forward and act as release manager.
We have the following documentation to guide existing and new release managers, 
so I encourage anyone to come forward so we can start spinning up new releases. 
This is a major part of moving towards graduation and growing awareness of 
SensSoft.

https://cwiki.apache.org/confluence/display/SENSSOFT/UserALE.js+Release+Management+Procedure

I'll personally go ahead and make a release for UserAle.js 0.1.0 and Distill 
0.1.0 and also augment the release documentation with whatever issues I 
encounter.

>
> I’ll admit we still remain confused about the lingering issue the
> Apache bot found with UserAle.js commits.
>

I am not aware of this, can you point me to the issue please?
Thanks

 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.

RE: Creating Release Candidate for UserALE.js

[Poore, Joshua C.]

Hi Lewis,

I've gone through and made sure our tickets in each release are accurate.

UserALE.js 0.1.0 is good to go. The blocker is SENSSOFT-250. I'm not sure we 
understand what needs to happen. Can you comment and give a bit more clarity?

We're also confirming whether some of the remaining tickets under UserALE.js 
0.2.0 are still lingering. That could be a candidate for release VERY soon 
after 0.1.0.

Distill 0.1.0 and TAP 0.1.0 are very much tethered. We are rebuilding Distill 
now (0.2.0; see requirements and discussion here: 
https://cwiki.apache.org/confluence/display/SENSSOFT/Distill+0.2.0

We could either released Distill 0.1.0 and TAP 0.1.0 together. Or we could wait 
and make Distill 0.2.0 the first release. Major overhaul on TAP on the horizon.

Thoughts??

Noted about release managers. The Draper contingent of the community has some 
interesting operating assumptions as you know--we service some very odd 
contracts, which don't necessarily align 100% with the products here. We commit 
back sometimes at deluges and sometimes at a trickle. That is changing and soon 
we'll have 3 release managers--Alex Ford, Michelle Beard, and Laura Mariano 
with projects that should produce more regular releases.

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Thursday, January 11, 2018 9:50 AM
To: dev@senssoft.incubator.apache.org
Subject: Re: Creating Release Candidate for UserALE.js

Hi Josh,
Replies inline

On Thu, Jan 11, 2018 at 8:31 AM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: Joshua Poore 
> To: dev@senssoft.incubator.apache.org
> Cc:
> Bcc:
> Date: Tue, 09 Jan 2018 20:57:47 -0500
> Subject: Re: Creating Release Candidate for UserALE.js None.
> UserAle.js 0.1.0 is ready. It’s a solid product. Distill 0.1.0 is also
> ready. It’s very simple and primarily works with Tap, but we are
> building 0.2.0 now.
>

OK doke. Moving forward, I would encourage anyone from the existing SensSoft 
community to come forward and act as release manager.
We have the following documentation to guide existing and new release managers, 
so I encourage anyone to come forward so we can start spinning up new releases. 
This is a major part of moving towards graduation and growing awareness of 
SensSoft.

https://cwiki.apache.org/confluence/display/SENSSOFT/UserALE.js+Release+Management+Procedure

I'll personally go ahead and make a release for UserAle.js 0.1.0 and Distill 
0.1.0 and also augment the release documentation with whatever issues I 
encounter.

>
> I’ll admit we still remain confused about the lingering issue the
> Apache bot found with UserAle.js commits.
>

I am not aware of this, can you point me to the issue please?
Thanks

 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.

RE: Apache + React.js = OK?

[Poore, Joshua C.]

Awesome. We may still end up abandoning it, but if we keep using React.js, 
we'll update to the new release and update all the license headers in our code.

Thanks! Hope you're well Chris! Good to hear from you!

Josh

-Original Message-
From: Chris Mattmann [mailto:mattm...@apache.org]
Sent: Monday, September 25, 2017 1:16 PM
To: dev@senssoft.incubator.apache.org; Mcgibbney, Lewis J (398M) 
<lewis.j.mcgibb...@jpl.nasa.gov>
Subject: Re: Apache + React.js = OK?

Yes it’s OK….starting from release 16 (whatever the new release is that they 
switch to MIT on).

Cheers,
Chris




On 9/25/17, 7:25 AM, "Poore, Joshua C." <jpo...@draper.com> wrote:

Lewis,

Looks like React is moving to the MIT license this week. Does that mean 
that Apache will embrace React again?


https://thenextweb.com/dd/2017/09/25/facebook-re-licenses-react-mit-license-developer-backlash/#.tnw_uvHpQBGl

Josh

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.





 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.

FW: .sha Release Distribution Policy

[Poore, Joshua C.]

May not be relevant, but worth putting in your noggins' as we're working on 
releases.

-Original Message-
From: Henk P. Penning [mailto:penn...@uu.nl]
Sent: Wednesday, August 16, 2017 5:06 AM
To: he...@apache.org
Subject: .sha Release Distribution Policy

Hi PPMC,

 The Release Distribution Policy[1] changed regarding .sha files.
 See under "Cryptographic Signatures and Checksums Requirements" [2].

   Old policy :

 -- use extension .sha for any SHA checksum (SHA-1, SHA-256, SHA-512)

   New policy :

   -- use .sha1 for a SHA-1 checksum
   -- use .sha256 for a SHA-256 checksum
   -- use .sha512 for a SHA-512 checksum
   -- [*] .sha should contain a SHA-1

   Why this change ?

   -- Verifying a checksum under the old policy is/was not handy.
  You have to inspect the .sha to find out which algorithm
  should be used ; or try them all (SHA-1, SHA256, etc).
  The new scheme avoids this ambiguity.
   -- The last point[*] was only added for clarity. Most of the
  old, stale .sha's contain a SHA-1. The relatively new .sha's
  contain a SHA-512. The expectation is that the last catagory will
  disappear, when active projects adapt to the 'new' convention.

   Impact :

   -- Should be none ; many projects already use the 'new' convention.
   -- Please ask your release managers to use .sha1, .sha256, .sha512
  instead of the .sha extension.
   -- Please fix your build-tools if you have any.

   Piggyback :

   -- The policy requires a .md5 for every package ;
  providing a .sha512 is recommended.
  Since MD5 is essentially broken, it is to be expected that
  in the future a .sha512 will be required.
  Perhaps it is wize to start providing .sha512's
  with your releases if you do not already do so.

   -- Visit http://mirror-vm.apache.org/checker/
  to check the health of your /dist/-area ;
  my stuff ; any feedback is most welcome.

   Thanks ; regards,

   Henk Penning

 [1] http://www.apache.org/dev/release-distribution
 [2] http://www.apache.org/dev/release-distribution#sigs-and-sums


Henk P. Penning ; apache.org infrastructure volunteer.
he...@apache.org ; http://mirror-vm.apache.org/~henkp/

 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.

RE: Preparing for UserALE.js Release

[Poore, Joshua C.]

@Lewis-

Confirm. No code for UserALE.js is in any other repo.

Thanks,

J

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Friday, June 16, 2017 9:58 AM
To: dev@senssoft.incubator.apache.org
Subject: Re: Preparing for UserALE.js Release

ACk Josh,
So to clarify the source code which the PPMC is proposing to release is 
https://github.com/apache/incubator-senssoft-useralejs
Is this correct?
Lewis

On Fri, Jun 16, 2017 at 6:54 AM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: "Poore, Joshua C." <jpo...@draper.com>
> To: "dev@senssoft.incubator.apache.org"
> <dev@senssoft.incubator.apache.org
> >
> Cc:
> Bcc:
> Date: Thu, 15 Jun 2017 04:00:04 +
> Subject: RE: Preparing for UserALE.js Release All of the above is
> excellent. I am glad to see that UserALE.js is in this condition and
> this far along. A lot of work has been going on and it is looking tip
> top.
>
> Can I ask, does the release work apply to the entire SensSoft stack or
> is it just UserALE?
>
>
>
> This will just be UserALE.js 0.1 for now. Distill isn’t hard behind
> and that’s the next step. But, the committers and I came to the
> conclusion that USerALE.js is ready for release, going forward with
> UserALE.js would be a good walkthrough of the process, and that we’ll
> need different release procedures for our python products (Distill and
> TAP). So, UserALE.js will be the first domino.
>
>
>

 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.

RE: Preparing for UserALE.js Release

[Poore, Joshua C.]

All of the above is excellent. I am glad to see that UserALE.js is in this 
condition and this far along. A lot of work has been going on and it is looking 
tip top.

Can I ask, does the release work apply to the entire SensSoft stack or is it 
just UserALE?



This will just be UserALE.js 0.1 for now. Distill isn’t hard behind and that’s 
the next step. But, the committers and I came to the conclusion that USerALE.js 
is ready for release, going forward with UserALE.js would be a good walkthrough 
of the process, and that we’ll need different release procedures for our python 
products (Distill and TAP). So, UserALE.js will be the first domino.



I am going to go ahead and begin some source code analysis tasks as well as 
walk m way through the Incubator release checklist which is a pretty solid 
resource for release candidate preparation and review.

I'll begin opening Jira issues if and when I encounter issues sp keep your eyes 
peeled. I'll post back here once I'm done with the first pass.

Thanks



Cool!



-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Tuesday, June 13, 2017 5:18 PM
To: dev@senssoft.incubator.apache.org
Subject: Re: Preparing for UserALE.js Release



Hi Josh,



On Tue, Jun 13, 2017 at 12:48 PM, <

dev-digest-h...@senssoft.incubator.apache.org<mailto:dev-digest-h...@senssoft.incubator.apache.org>>
 wrote:



>

> From: "Poore, Joshua C." <jpo...@draper.com<mailto:jpo...@draper.com>>

> To: 
> "dev@senssoft.incubator.apache.org<mailto:dev@senssoft.incubator.apache.org>"

> <dev@senssoft.incubator.apache.org

> >

> Cc:

> Bcc:

> Date: Tue, 13 Jun 2017 19:48:01 +

> Subject: Preparing for UserALE.js Release @PMC, @Lewis-

>

> We have just a few tickets left in our UserALE.js v 0.1. pipeline in

> preparation for a release. https://issues.apache.org/

> jira/secure/RapidBoard.jspa?rapidView=135=

> SENSSOFT=planning=SENSSOFT-184=visible&

> selectedVersion=12339748

>

> Very soon, you should see an update to our UserALE.js docs (

> senssoft.apache.org) reflecting updated test and contribution guides.

> http://senssoft.apache.org/docs/useralejs/contributing.html

>

> We have also updated our Release Management Procs for UserALE.js

> https://cwiki.apache.org/confluence/display/SENSSOFT/

> UserALE.js+Release+Management+Procedure

>

>

All of the above is excellent. I am glad to see that UserALE.js is in this 
condition and this far along. A lot of work has been going on and it is looking 
tip top.

Can I ask, does the release work apply to the entire SensSoft stack or is it 
just UserALE?





> Can you walk us through the next steps leading up to a vote, including

> scanning for licensing, staging code @release, and give us some

> guidance as to where Apache might want us to put sensitive items like

> our NPM keys for UserALE.js (if you have a preference).

>

>

I am going to go ahead and begin some source code analysis tasks as well as 
walk m way through the Incubator release checklist which is a pretty solid 
resource for release candidate preparation and review.

I'll begin opening Jira issues if and when I encounter issues sp keep your eyes 
peeled. I'll post back here once I'm done with the first pass.

Thanks


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.

Preparing for UserALE.js Release

[Poore, Joshua C.]

@PMC, @Lewis-

We have just a few tickets left in our UserALE.js v 0.1. pipeline in 
preparation for a release. 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=135=SENSSOFT=planning=SENSSOFT-184=visible=12339748

Very soon, you should see an update to our UserALE.js docs 
(senssoft.apache.org) reflecting updated test and contribution guides. 
http://senssoft.apache.org/docs/useralejs/contributing.html

We have also updated our Release Management Procs for UserALE.js 
https://cwiki.apache.org/confluence/display/SENSSOFT/UserALE.js+Release+Management+Procedure

Can you walk us through the next steps leading up to a vote, including scanning 
for licensing, staging code @release, and give us some guidance as to where 
Apache might want us to put sensitive items like our NPM keys for UserALE.js 
(if you have a preference).

Many thanks... almost there, excited!

J


Joshua C. Poore, Ph.D.
[Technologist, Analyst, Psychologist, Software as a Sensor(tm) Porfolio Lead]
The Charles Stark Draper Laboratory, Inc.
555 Technology Square
Cambridge MA, 02139
Phone[Desk] 617 258 4023
Phone[Mobile] 617 352 1700
Email[0] jpo...@draper.com
Email[1] poor...@apache.org
Find Apache SensSoft Code, Demos, and Docs @ http://senssoft.apache.org/

"...the benefits of scientific discoveries can extend to the whole of mankind, 
and can last for all time...
This is nowhere more obvious than ... the arts of printing, gunpowder, and the 
natural compass...
there seems to have been no empire, no philosophical system,
no star that has exerted greater power and influence in human affairs than 
these mechanical discoveries"

-Francis Bacon, Novum Organum (1620), Aphorism 129

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.


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.

RE: [jira] [Commented] (SENSSOFT-180) [RELEASE PROC] Generate NPM Keys

[Poore, Joshua C.]

I meant account credentials. Do we need another ticket or two? If so, please 
add.

Thanks

-Original Message-
From: Rob Foley (JIRA) [mailto:j...@apache.org]
Sent: Friday, May 19, 2017 11:44 AM
To: Dev@senssoft.incubator.apache.org
Subject: [jira] [Commented] (SENSSOFT-180) [RELEASE PROC] Generate NPM Keys


[ 
https://issues.apache.org/jira/browse/SENSSOFT-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017567#comment-16017567
 ]

Rob Foley commented on SENSSOFT-180:


What is meant by NPM keys? The hashes of the release artifacts, or is this 
equivalent to the NPM account credentials?

> [RELEASE PROC] Generate NPM Keys
> 
>
> Key: SENSSOFT-180
> URL: https://issues.apache.org/jira/browse/SENSSOFT-180
> Project: SensSoft
>  Issue Type: Task
>  Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Joshua Poore
>Assignee: Rob Foley
> Fix For: UserALE.js 0.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

 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.

FW: [jira] [Commented] (SENSSOFT-27) [RELEASE PROC] NPM Package for UserALE.js

[Poore, Joshua C.]

@lewis

We're pushing hard on the release of UserALE.js

Just so that out tickets are right, any guidance on credentials for package 
management? I'm not sure we saw guidance through various Apache Docs.

-Original Message-
From: Rob Foley (JIRA) [mailto:j...@apache.org]
Sent: Tuesday, May 16, 2017 3:09 PM
To: Dev@senssoft.incubator.apache.org
Subject: [jira] [Commented] (SENSSOFT-27) [RELEASE PROC] NPM Package for 
UserALE.js


[ 
https://issues.apache.org/jira/browse/SENSSOFT-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012956#comment-16012956
 ]

Rob Foley commented on SENSSOFT-27:
---

How should we proceed managing the credentials for these various package 
managers?

> [RELEASE PROC] NPM Package for UserALE.js
> -
>
> Key: SENSSOFT-27
> URL: https://issues.apache.org/jira/browse/SENSSOFT-27
> Project: SensSoft
>  Issue Type: Task
>  Components: UserALE.js
>Affects Versions: UserALE.js 1.0.0
>Reporter: Joshua Poore
>Assignee: Rob Foley
>Priority: Critical
> Fix For: UserALE.js 1.0.0
>
>   Original Estimate: 5h
>  Remaining Estimate: 5h
>
> Enable Userale.js to be used and distributed as a NPM package. Release over 
> NPM, Bower, etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

 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.

Heatmaps

[Poore, Joshua C.]

@Lewis-

Dropped in some tix with research. Searchable: use [Heatmaps] string.

Also dropped in an idea about user reports (see [SKIM] ticket).

Joshua C. Poore, Ph.D.
[Technologist, Analyst, Psychologist, Software as a Sensor(tm) Porfolio Lead]
The Charles Stark Draper Laboratory, Inc.
555 Technology Square
Cambridge MA, 02139
Phone[Desk] 617 258 4023
Phone[Mobile] 617 352 1700
Email[0] jpo...@draper.com
Email[1] poor...@apache.org
Find Apache SensSoft Code, Demos, and Docs @ http://senssoft.apache.org/

"...the benefits of scientific discoveries can extend to the whole of mankind, 
and can last for all time...
This is nowhere more obvious than ... the arts of printing, gunpowder, and the 
natural compass...
there seems to have been no empire, no philosophical system,
no star that has exerted greater power and influence in human affairs than 
these mechanical discoveries"

-Francis Bacon, Novum Organum (1620), Aphorism 129

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.


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.

RE: Generating Heatmaps for User Behaviour

[Poore, Joshua C.]

TIX RE heatmaps will go in today. Sry for delay.

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Friday, April 28, 2017 5:04 PM
To: dev@senssoft.incubator.apache.org
Subject: Re: Generating Heatmaps for User Behaviour

This is fantastic feedback thanks folks. I'll maybe have a look at implementing 
the Heatmap issue myself as i think it would be a nice addition to SensSoft.

On Fri, Apr 28, 2017 at 1:37 PM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: Joshua Poore 
> To: dev@senssoft.incubator.apache.org
> Cc:
> Bcc:
> Date: Thu, 27 Apr 2017 23:49:48 -0400
> Subject: Re: Generating Heatmaps for User Behaviour @Lewis
>
> Some more info, but out of the order in which you asked:
>
> >> session reconstruction e.g. What does an end-to-end browning
> >> session look like?
>
>
> Browsing session reconstruction defines a good amount of the work
> we’re doing now and for the remainder of the year on a number of
> projects. We’re actually already working on this now, and it will be
> the basis of a ton more work that will start mid-late June.
>
> What our solution looks like is UserALE.js packaged in a FireFox
> browser plugin. The plugin drops UserALE.js into the client without
> having to touch source code. So, you can get all the data you’d expect
> from UserALE.js, but be able to capture data from sites that
> UserALE.js script tags haven’t been embedded in (the source code). The
> use case is that orgs and users can just deploy a browser that
> captures userALE logs with disc images—bam. Chris Muto (new
> contributor) built a prototype. @fordar is picking that project up and
> resolving some of the major/obvious issues like mixed media/CORS
> issues. You’ll see this code in the UserALE.js repo probably next week when 
> @fordar get’s his bearings.
>
> >> what type of client e.g. Firefox, safari, etc
>
> Plugin will be FireFox to start. But FireFox and Chrome are playing
> nice in plugin portability… Once the plugin is in the .js repo, feel
> free to reach out or combine forces with @fordar if you know of
> someone that needs this very soon.
>
> >>  heatmap generation representing user activity overlaid over
> >> Webpage
> >> * dot plotting similar to the above
>
>
> First... what Rob said
>
> Second, I actually have some tickets to move over to Apache Jira about
> investigations of open source code for grabbing screen caps from browsers.
> If we can coregister those screens with cursor x,y, then heat maps
> should be a snap (if you can deal with pushing around and storing
> those screen caps). The browser plugin logging solution will also make
> this easier, building off the plugin should give us more data available to 
> the client.
>
> Next week, I’ll get my investigation tix moved over (going on short
> vacation tomorrow—back next week). Unlikely we’ll have a ton of
> bandwidth (as a team) to work on heat maps specifically in the next month or 
> two.
> However, later this year we’ll be focusing very hard on visualization
> and TAP. Something like heat maps are a big part of that, but I can’t
> talk about that with specifics yet. @lmariano is very interested in
> this, but she can’t talk specifics yet either.
>
> Again, comprehensive browsing session capture is a major theme for us
> this year. A number of us will be under contract to do some of this
> work and it will all be Apache. If you know of other interested
> parties, let’s talk offline so that we can coordinate sooner than
> later. Things will start percolating up to our roadmap pretty soon.
>
> >> * ability to see where people visiting your webpage/webapp came
> >> from e.g where did the client come from?
>
> No immediate plans to do this. No current capability to capture
> origin/destination data, but likely something that could be deployable
> through the script tag. We should have some wish list tix on this. The
> browser plugin deployment use case will drive a lot of upgrades to
> UserALE.js that will push this along. Of course, we’ll get this data
> from the client easy, but the “visiting your website” deployment is
> different than the “websites you visit” use case the browser plugin supports.
>
>
> I hope that helps, too.
>
>
> > On Apr 27, 2017, at 10:48 PM, Rob Foley  wrote:
> >
> > Hi Lewis,
> >
> > While I haven't taken to plotting it out myself, I think the data we
> > generate would be sufficient to plot out a heatmap on a page, since
> > many
> of
> > the logs contain X,Y coordinate pairs. Using a library like
> > heatmap.js or simpleheat you could probably get a decent overlay for a page 
> > that way.
> Dot
> > plotting would be a similar answer with something like D3. Seeing
> > where someone came from may be a bit tricky, since that'd rely on
> > the referer
> > (sic) header being set, which some clients may ignore. If you only
> > wanted to track between pages on a particular domain, that may be a bit 
> > easier.
> >
> > User 

First Release Strategy

[Poore, Joshua C.]

Hi All,

In a meeting today it became apparent that we're a bit further behind on TAP 
than we thought, at least from a test perspective. We'll be working on that 
next month.

In the interim, UserALE.js and Distill look to be healthy. We're configuring 
npm and pip managers for those two products in the next few weeks. We will also 
be updating our release guide thusly. In a few weeks, these two products should 
be releasable. TAP will be releasable, likely next month. Rather than do a 
massive release of the entire system, I think we're going to do a phased 
release of our components to expedite our growth in Apache.

@Lewis, this strategy is open to discussion and commenting. Let us know if the 
PMC feels differently.

Josh

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.

RE: Maven alternatives for Analyzing Builds in JS and Python

[Poore, Joshua C.]

Hi Chris,

Thanks! Pip should work. In fact, we were hoping you'd say that :)

Best,

Josh

-Original Message-
From: Mattmann, Chris A (3010) [mailto:chris.a.mattm...@jpl.nasa.gov]
Sent: Tuesday, April 4, 2017 6:11 PM
To: dev@senssoft.incubator.apache.org
Cc: Mcgibbney, Lewis J (398M) <lewis.j.mcgibb...@jpl.nasa.gov>
Subject: Re: Maven alternatives for Analyzing Builds in JS and Python

Hey Josh, how about setuptools, and pip?

++
Chris Mattmann, Ph.D.
Principal Data Scientist, Engineering Administrative Office (3010) Manager, NSF 
& Open Source Projects Formulation and Development Offices (8212) NASA Jet 
Propulsion Laboratory Pasadena, CA 91109 USA
Office: 180-503E, Mailstop: 180-503
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 4/4/17, 2:31 PM, "Poore, Joshua C." <jpo...@draper.com> wrote:

Lewis,


We're looking into build tools for our releases. None of our projects are 
currently in Java, so we'll need guidance as to your favorite approaches to 
analyzing JavaScript and Python. See  
https://issues.apache.org/jira/browse/SENSSOFT-165



We are currently investigating the PMD plugin for Maven, and Pip, PyBuilder 
and Distutils. Please let us know if we're going down the Apache-compliant 
track for analyzing builds given our needs.


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.




 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.

RE: [DISCUSS] SensSoft Release

[Poore, Joshua C.]

Hi Lewis!

New contract has started and we're back in action.

As far as prior releases, we would release the code and an example 
implementation in tandem. We would have a getting started guide for how to 
build a vagrant file, for example, from the source, and then make the source 
available, too. Going forward, we would like to do similar things with the 
Apache project. We would like to release, as artifacts, our source code, and 
release a deployable container, or bundle (e.g., SensSoft v.1.0.0 ) as a 
separate artifact. This is pretty close to what we discussed with Peter Wang in 
September.

We're going to start by going through our tickets and connecting each of our 
committed/resolved/closed to the right version for release. I can explain why 
that needs to be done; part of it has to do with our roadmapping activities... 
Once we know all the tickets that correspond to the current version of the 
repos, which are ready for release. We will validate our builds...

One of the questions we have after going through the release documentation is 
about Maven, and whether this is something that's applicable to us. Maven 
appears to be geared for Java applications, of which we have none--we're mostly 
JavaScript and Python. Any guidance there on build verification (we're already 
set up on Jenkins for CI)?

Does that help address some of your questions?

Josh

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Wednesday, February 22, 2017 5:17 PM
To: dev@senssoft.incubator.apache.org
Subject: [DISCUSS] SensSoft Release

Hi Folks,
I'm going to work on getting some of the SensSoft release management material 
addressed.
Can someone elaborate on what a source code release for SensSoft has looked 
like in the past?
From that, we can plan on how to move forward.
Thanks
Lewis

--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

 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.

Website is Up and Lovely

[Poore, Joshua C.]

All,

Really excited that our Apache website is finally live. 
http://senssoft.incubator.apache.org/

Great place for docs, demos, and linking out to a larger community.

Special thanks to cgimenez and arthivez

--poorejc

Joshua C. Poore, Ph.D.
Senior Member of the Technical Staff
Draper
555 Technology Square, Rm. 2242
Cambridge, MA 02139-3563
Phone: (617) 258-4023
Cell: (617) 352-1700
Email[1]: jpo...@draper.com
Email[2]: poor...@apache.org
Participate in Operation XDATA: http://xdataonline.com!


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.

RE: Senssoft VM + Website

[Poore, Joshua C.]

Oof! Yeah, css is way off.

Still, big progress! Thanks @Lewis!

Josh

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Thursday, January 19, 2017 9:48 AM
To: dev@senssoft.incubator.apache.org
Subject: Re: Senssoft VM + Website

Website is live
http://senssoft.incubator.apache.org/
Looks like some CSS or other presentation may be off slightly... changes can be 
committed directly to the repos.
Good work folks.

On Wed, Jan 18, 2017 at 11:43 AM, lewis john mcgibbney 
wrote:

> Hi Folks,
> I just saw that the Senssoft VM has been completed and that the INFRA
> ticket has been resolved.
> Is there any action being taken to get a demo up and running.
> On the track of the Website, I've addressed the INFRA issues and I
> hope the Website will be live pretty shortly. If you want you can
> track progress at https://issues.apache.org/jira/browse/INFRA-13323
> Thanks
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>



--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

 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.

RE: Updated SensSoft Incubation Project Status Page

[Poore, Joshua C.]

Looks good for now, until we have a vote for arthivez, sunfei, and kfinley.

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Wednesday, January 11, 2017 12:38 PM
To: dev@senssoft.incubator.apache.org
Subject: Updated SensSoft Incubation Project Status Page

Hi Folks,
I've made an attempt to update the status page, if there is anything I've 
missed then please let me know 
http://incubator.apache.org/projects/senssoft.html
Thanks
Lewis

--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

 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.

RE: Updated SensSoft Incubation Project Status Page

[Poore, Joshua C.]

Forgot to ask @Lewis...

Do you have everything you need for the quarterly board report? Let me know if 
you need any inputs. I'm also happy to mock something up if you're strapped for 
time and send it to you.

Thanks for burning through these issues, Lewis.

J

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Wednesday, January 11, 2017 12:38 PM
To: dev@senssoft.incubator.apache.org
Subject: Updated SensSoft Incubation Project Status Page

Hi Folks,
I've made an attempt to update the status page, if there is anything I've 
missed then please let me know 
http://incubator.apache.org/projects/senssoft.html
Thanks
Lewis

--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

 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.

UserALE Log Halt

[Poore, Joshua C.]

Hi Michelle,

Would you mind adding the log halt to a ticket in our Apache roadmaps for

UserALE.js 0.3: 
https://issues.apache.org/jira/browse/SENSSOFT-99?jql=fixVersion%20%3D%20%22UserALE.js%200.3%22%20AND%20project%20%3D%20SENSSOFT

And

UserALE.pyqt 0.1.6: 
https://issues.apache.org/jira/browse/SENSSOFT-77?jql=project%20%3D%20SENSSOFT%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%20%22UserALE.PyQt5%200.1.6%22
  (if not already).

Thanks,

Josh

Joshua C. Poore, Ph.D.
Senior Member of the Technical Staff
Draper
555 Technology Square, Rm. 2242
Cambridge, MA 02139-3563
Phone: (617) 258-4023
Cell: (617) 352-1700
Email[1]: jpo...@draper.com
Email[2]: poor...@apache.org
Participate in Operation XDATA: http://xdataonline.com!


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.

RE: incubator_senssoft Repo

[Poore, Joshua C.]

Hi Lewis,

We'll look after the release as per www.apache.org/dev/#releases, your guidance 
in the process will be MUCH appreciated.

As per the roadmap on the JIRA board:

What you're seeing is a roadmap that extends beyond SensSoftv1.0.0

SensSoft v1.0.0 includes:

UserALE.js v .2
Distill v 0.1.3
TAP v 0.0.1

(and all supporting APIs, etc., within a nice container)

UserALE.PyQt5 and STOUT are non-essential extensions for logging for web-app 
usability, and aren't at this point meant to be included in the first release 
(PyQt5 is for desktop apps written in python, when we develop a version of 
UserALE for another language (e.g., C#) we might bundle up a desktop SensSoft 
release).

UserALE.js v.3,.4 and Distill 0.1.4 will be added to SensSoft v1.1.0.

Does that make sense?

Josh


Joshua C. Poore, Ph.D.
Senior Member of the Technical Staff
Draper
555 Technology Square, Rm. 2242
Cambridge, MA 02139-3563
Phone: (617) 258-4023
Cell: (617) 352-1700
Email[1]: jpo...@draper.com
Email[2]: poor...@apache.org
Participate in Operation XDATA: http://xdataonline.com!





-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Monday, November 21, 2016 12:49 PM
To: dev@senssoft.incubator.apache.org
Subject: Re: incubator_senssoft Repo

Hi Josh,

On Mon, Nov 21, 2016 at 7:22 AM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

> From: "Poore, Joshua C." <jpo...@draper.com>
> To: "dev@senssoft.incubator.apache.org"
> <dev@senssoft.incubator.apache.org
> >
> Cc:
> Date: Mon, 21 Nov 2016 15:21:07 +
> Subject: RE: incubator_senssoft Repo
> @Lewis,
>
> No, this is for a repo to collect our full releases (e.g., packages of
> applications published in deployable formats). The website will need
> its own repo.
>
>
OK. We'll there are a few hurdles first.
Initially, I've created our dev and release staging areas as follows

https://dist.apache.org/repos/dist/dev/incubator/senssoft
https://dist.apache.org/repos/dist/release/incubator/senssoft

The dev one is used to stage whilst we conduct a VOTE internally within the 
Senssoft community and then over n general@incubator. The release area is for 
use when the VOTE passes and we are ready to ship the release.

Until then, there is a procedure to be followed (this is mandatory for all 
Incubator projects wishing to release incubating artifacts as official 
releases). The documentation can be seen at http://www.apache.org/dev/#releases

I am fine with undertaking the initial release management procedure and 
documenting it thoroughly over on our wiki. If this is fine with folks then I 
will progress whenever you give the green light.

First things first, lets get the Roadmap sorted out.
https://issues.apache.org/jira/browse/SENSSOFT/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
Right now it seems that there are a number of issues open for several 
components. Is it your intention to bump everything to 1.0.0 version?

Lewis

 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.

Sprint Meeting Notes `11/22

[Poore, Joshua C.]

Attendance:
Joshua Poore
Arthi Vezhavendan
Rob Foley (remote)
Michelle Beard (remote)

Items:

Accomplishment: SensSoft v 1.0.0 is ready for release! Need incubator-senssoft 
repo up to deploy


1.   TAP.

a.   TAP is completed and tested.

b.  Performing last minute branch merges and testing.

c.   Future developments will need to focus on Django back-end and user 
registration features.

d.  TAP is container-ready.


2.   Website:

a.   Arthi and Clay to comment on INFRA-12671 ASAP!

b.  Josh to approve new layouts next week



3.   DISTILL

a.   Michelle wants to update to ELK 5

b.  Table for after the holiday (not a blocker)

Convene

Joshua C. Poore, Ph.D.
Senior Member of the Technical Staff
Draper
555 Technology Square, Rm. 2242
Cambridge, MA 02139-3563
Phone: (617) 258-4023
Cell: (617) 352-1700
Email[1]: jpo...@draper.com
Email[2]: poor...@apache.org
Participate in Operation XDATA: http://xdataonline.com!


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.

incubator_senssoft Repo

[Poore, Joshua C.]

Hi @Lewis,

We're very close to a releasable version of SensSoft v1.0.0. We'll need the 
incubator-senssoft repo up. We used to have a ticket out for this 
(INFRA-12751), however it looks like those requests are served through a web 
app. When you have a sec, can you submit the request so that we can drop our 
container in and start compiling our documentation and guides?

Thanks,

Josh


Joshua C. Poore, Ph.D.
Senior Member of the Technical Staff
Draper
555 Technology Square, Rm. 2242
Cambridge, MA 02139-3563
Phone: (617) 258-4023
Cell: (617) 352-1700
Email[1]: jpo...@draper.com
Email[2]: poor...@apache.org
Participate in Operation XDATA: http://xdataonline.com!


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.

I'm Here

[Poore, Joshua C.]

Anyone else on my team, should be on the private list, too:

private-subscr...@senssoft.incubator.apache.org

Joshua C. Poore, Ph.D.
Senior Member of the Technical Staff
Draper
555 Technology Square, Rm. 2242
Cambridge, MA 02139-3563
Phone: (617) 258-4023
Cell: (617) 352-1700
Email[1]: jpo...@draper.com
Email[2]: poor...@apache.org
Participate in Operation XDATA: http://xdataonline.com!


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.

Corporate SensSoft Site is UP!

[Poore, Joshua C.]

All-

Our corporate website is up @ http://www.draper.com/softwareasasensor. Videos 
will be up soon, and the "integrate with SensSoft" stub will eventually read 
something like Go to Apache SensSoft, which will link to the Apache page.

Joshua C. Poore, Ph.D.
Senior Member of the Technical Staff
Draper
555 Technology Square, Rm. 2242
Cambridge, MA 02139-3563
Phone: (617) 258-4023
Cell: (617) 352-1700
Email[1]: jpo...@draper.com
Email[2]: poor...@apache.org
Participate in Operation XDATA: http://xdataonline.com!


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.

RE: Website Repo Request

[Poore, Joshua C.]

Awesome! Thanks for pushing on this @Clay and @Lewis!

-Original Message-
From: Lewis John Mcgibbney [mailto:lewis.mcgibb...@gmail.com]
Sent: Friday, October 14, 2016 3:52 PM
To: Gimenez, Clayton C. 
Cc: dev@senssoft.incubator.apache.org
Subject: Re: Website Repo Request

Dynamite.
The request has been submitted and we will have a new repos asap.
Thanks clay

On Friday, October 14, 2016, Gimenez, Clayton C. 
wrote:

> Hi Lewis,
>
> Request  for
> website git repo has been submitted to Infra — they say we need you to
> request the repo at http://reporeq.apache.org.
>
> Thanks!
> Clay
> --
> 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.
> --
>


--

*Lewis*
Dr. Lewis J. McGibbney Ph.D, B.Sc
Director
Phone: +1(626)498-3090
Skype: lewis.john.mcgibbney
Email: lewis.mcgibb...@gmail.com

 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.

RE: Access to apache.github repos to add github.io pages [SENSSOFT]

[Poore, Joshua C.]

@Lewis

I think my team was operating under some different assumptions regarding our 
ability to push our github docs pages that are currently posted on 
Draperlaboratory/github to apache. I'll round up with them RE Greg's email. I 
think we all have consensus on the effect we want, but maybe some disconnects 
in how we think we can get it done.

For clarity's sake, here is the schema of how our websites/documentation will 
be managed.

Corporate Branding of SensSoft: softwareasasensor.com redirects to 
draper.com/softwareasasensor (note that we will still be compliant with Apache 
marketing and branding rules regarding incubator projects). This page will of 
course link to Apache community and repos.

Apache Community: incubator.apache.org/projects/sensoft.html will be our home 
page for our Apache projects, this will connect to vm requested (INFRA-12671) 
and host demos. Links to documentation redirect to git.io pages, which we are 
trying to build on Apache git resources (currently built on 
draperlaboratory/git repos). If we can just push these into git-wip.a.o as Greg 
suggests, then that problem is solved.

More soon...

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Tuesday, October 04, 2016 5:57 PM
To: dev@senssoft.incubator.apache.org
Subject: Re: Access to apache.github repos to add github.io pages [SENSSOFT]

@Josh,

On Tue, Oct 4, 2016 at 1:24 PM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: "Poore, Joshua C." <jpo...@draper.com>
> To: "infrastruct...@apache.org" <infrastruct...@apache.org>
> Cc: "Mcgibbney, Lewis J (398M)" <lewis.j.mcgibb...@jpl.nasa.gov>,
> "Mattmann, Chris A (3980)" <chris.a.mattm...@jpl.nasa.gov>, "
> dev@senssoft.incubator.apache.org" <dev@senssoft.incubator.apache.org>
> Date: Tue, 04 Oct 2016 20:07:42 +
> Subject: Access to apache.github repos to add github.io pages
> [SENSSOFT]
> Hello-
>
> We're incubating at Apache. We'd like to move our github.io docs pages
> from our old repos to our apache.github mirrors to consolidate
> documentation. How best/who best to ask for permissions to stand these up?
> Ideally, we'd like to generate sphinx templates for all Apache
> SensSoft documentation that would live in these repos.
>

This was previously open over on
https://issues.apache.org/jira/browse/INFRA-12264
Essentially if we can decide on a strategy then we can open a ticket within the 
INFRA Jira ticket and request resources there.
As Greg has mentioned, we can do most of this ourselves.
Would you want INFRA to create a new, separate Git-based repository at 
something like 
https://git-wip-us.apache.org/repos/asf/incubator-senssoft-website.git ?
We could then create all documentation in sphinx, build it locally and push the 
docs to the Website for deployment. Honestly to me it doesn't matter but it 
would be good to get some consensus.
 Lewis

 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.