[jira] [Updated] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[ https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-203: -- Sprint: (was: Sprint 9) > Address UserALE.js feedback from lewismc > > > Key: SENSSOFT-203 > URL: https://issues.apache.org/jira/browse/SENSSOFT-203 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Lewis John McGibbney >Assignee: Michelle Beard >Priority: Blocker > Fix For: UserALE.js 0.1.0 > > > Hi Folks, > This is straight from my identical feedback on the dev@ list. Excellent work > on UserALE.js it is looking very good. > Lewis > Some initial questions/feedback/observations > # The README [0] needs to be updated in several places, this will be obvious > when you read the README. This will need to be updated. > # Is the intention to host UserALE.js on some CDN somewhere? I see from [1] > that the intention is to release the code to NPM and/or Bower... is this work > in progress (I think it definitely is) and if so is it documented somewhere? > # It might be worth providing a more detailed description at [2] > # I would make sure that the JIRA Release Notes [3] are copied over to the > CHANGELOG.md file [4]. Additionally, I would structure it after the following > example [5] where essentially the JIRA release report is copied and pasted in > there, this tends to render nicely in Markdown. Additionally, it looks better > if the release manager provides a short link to the release report. This can > be obtained using the URL shortening service at [6]. > # Please make sure to add a DISCLAIMER, a sample can be seen at [7] > # We need to produce a KEYS file for all SensSoft developers who wish to act > as release manager and sign release artifacts. They KEYS file can live > anywhere within/across the SensSoft repositories. An example can be found at > [8]. > # We need to generate a NOTICE file which essentially details usage and > appropriate attribution of dependencies consumed within UserALE.js. An > example can be seen at [9]. > # We should probably generate a Description of a Project (DOAP) file for > every SensSoft project... however this is not a blocker for a release. > I think the above represents a minimum degree of feedback that I would like > to see addressed before we attempt to generate a release candidate for > UserALE.js. > If there are ANY questions, please let me know. > I've raised a JIRA issue for this at [10] which will enable someone(s) to > track and address the issues. > Thanks > [0] https://github.com/apache/incubator-senssoft-useralejs > [1] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md > [2] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4 > [3] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621=12339748 > [4] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md > [5] > https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md > [6] https://s.apache.org/ > [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt > [8] https://github.com/apache/incubator-joshua/blob/master/KEYS > [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[ https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-203: -- Sprint: Sprint 9 > Address UserALE.js feedback from lewismc > > > Key: SENSSOFT-203 > URL: https://issues.apache.org/jira/browse/SENSSOFT-203 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Lewis John McGibbney >Assignee: Michelle Beard >Priority: Blocker > Fix For: UserALE.js 0.1.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > Hi Folks, > This is straight from my identical feedback on the dev@ list. Excellent work > on UserALE.js it is looking very good. > Lewis > Some initial questions/feedback/observations > # The README [0] needs to be updated in several places, this will be obvious > when you read the README. This will need to be updated. > # Is the intention to host UserALE.js on some CDN somewhere? I see from [1] > that the intention is to release the code to NPM and/or Bower... is this work > in progress (I think it definitely is) and if so is it documented somewhere? > # It might be worth providing a more detailed description at [2] > # I would make sure that the JIRA Release Notes [3] are copied over to the > CHANGELOG.md file [4]. Additionally, I would structure it after the following > example [5] where essentially the JIRA release report is copied and pasted in > there, this tends to render nicely in Markdown. Additionally, it looks better > if the release manager provides a short link to the release report. This can > be obtained using the URL shortening service at [6]. > # Please make sure to add a DISCLAIMER, a sample can be seen at [7] > # We need to produce a KEYS file for all SensSoft developers who wish to act > as release manager and sign release artifacts. They KEYS file can live > anywhere within/across the SensSoft repositories. An example can be found at > [8]. > # We need to generate a NOTICE file which essentially details usage and > appropriate attribution of dependencies consumed within UserALE.js. An > example can be seen at [9]. > # We should probably generate a Description of a Project (DOAP) file for > every SensSoft project... however this is not a blocker for a release. > I think the above represents a minimum degree of feedback that I would like > to see addressed before we attempt to generate a release candidate for > UserALE.js. > If there are ANY questions, please let me know. > I've raised a JIRA issue for this at [10] which will enable someone(s) to > track and address the issues. > Thanks > [0] https://github.com/apache/incubator-senssoft-useralejs > [1] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md > [2] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4 > [3] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621=12339748 > [4] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md > [5] > https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md > [6] https://s.apache.org/ > [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt > [8] https://github.com/apache/incubator-joshua/blob/master/KEYS > [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[ https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-203: -- Remaining Estimate: 2h Original Estimate: 2h > Address UserALE.js feedback from lewismc > > > Key: SENSSOFT-203 > URL: https://issues.apache.org/jira/browse/SENSSOFT-203 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Lewis John McGibbney >Assignee: Michelle Beard >Priority: Blocker > Fix For: UserALE.js 0.1.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > Hi Folks, > This is straight from my identical feedback on the dev@ list. Excellent work > on UserALE.js it is looking very good. > Lewis > Some initial questions/feedback/observations > # The README [0] needs to be updated in several places, this will be obvious > when you read the README. This will need to be updated. > # Is the intention to host UserALE.js on some CDN somewhere? I see from [1] > that the intention is to release the code to NPM and/or Bower... is this work > in progress (I think it definitely is) and if so is it documented somewhere? > # It might be worth providing a more detailed description at [2] > # I would make sure that the JIRA Release Notes [3] are copied over to the > CHANGELOG.md file [4]. Additionally, I would structure it after the following > example [5] where essentially the JIRA release report is copied and pasted in > there, this tends to render nicely in Markdown. Additionally, it looks better > if the release manager provides a short link to the release report. This can > be obtained using the URL shortening service at [6]. > # Please make sure to add a DISCLAIMER, a sample can be seen at [7] > # We need to produce a KEYS file for all SensSoft developers who wish to act > as release manager and sign release artifacts. They KEYS file can live > anywhere within/across the SensSoft repositories. An example can be found at > [8]. > # We need to generate a NOTICE file which essentially details usage and > appropriate attribution of dependencies consumed within UserALE.js. An > example can be seen at [9]. > # We should probably generate a Description of a Project (DOAP) file for > every SensSoft project... however this is not a blocker for a release. > I think the above represents a minimum degree of feedback that I would like > to see addressed before we attempt to generate a release candidate for > UserALE.js. > If there are ANY questions, please let me know. > I've raised a JIRA issue for this at [10] which will enable someone(s) to > track and address the issues. > Thanks > [0] https://github.com/apache/incubator-senssoft-useralejs > [1] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md > [2] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4 > [3] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621=12339748 > [4] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md > [5] > https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md > [6] https://s.apache.org/ > [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt > [8] https://github.com/apache/incubator-joshua/blob/master/KEYS > [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-192) Record Interval Events
[ https://issues.apache.org/jira/browse/SENSSOFT-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-192: -- Remaining Estimate: 4h Original Estimate: 4h > Record Interval Events > -- > > Key: SENSSOFT-192 > URL: https://issues.apache.org/jira/browse/SENSSOFT-192 > Project: SensSoft > Issue Type: New Feature > Components: UserALE.js >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: UserALE.js 0.2.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > Detect repeated userale events by keeping track of an interval: > An interval event describes a sequence of identical userale events > (mouseovers, drags, etc). It must record the start of the event and the end > of the event. In the case that a userale event does not update/timeouts, the > interval is closed by the library and emitted to the logging server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-202) App Results -- Sankey Diagram
[ https://issues.apache.org/jira/browse/SENSSOFT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-202: -- Remaining Estimate: 10h Original Estimate: 10h > App Results -- Sankey Diagram > - > > Key: SENSSOFT-202 > URL: https://issues.apache.org/jira/browse/SENSSOFT-202 > Project: SensSoft > Issue Type: Task >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > Incorporate a basic sankey diagram with distill calls -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-192) Record Interval Events
[ https://issues.apache.org/jira/browse/SENSSOFT-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-192: -- Sprint: Sprint 8, Sprint 9 (was: Sprint 8) > Record Interval Events > -- > > Key: SENSSOFT-192 > URL: https://issues.apache.org/jira/browse/SENSSOFT-192 > Project: SensSoft > Issue Type: New Feature > Components: UserALE.js >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: UserALE.js 0.2.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > Detect repeated userale events by keeping track of an interval: > An interval event describes a sequence of identical userale events > (mouseovers, drags, etc). It must record the start of the event and the end > of the event. In the case that a userale event does not update/timeouts, the > interval is closed by the library and emitted to the logging server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-202) App Results -- Sankey Diagram
[ https://issues.apache.org/jira/browse/SENSSOFT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-202: -- Sprint: Sprint 8 (was: Sprint 8, Sprint 9) > App Results -- Sankey Diagram > - > > Key: SENSSOFT-202 > URL: https://issues.apache.org/jira/browse/SENSSOFT-202 > Project: SensSoft > Issue Type: Task >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > > Incorporate a basic sankey diagram with distill calls -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENSSOFT-210) Integrate SankeyPlot with Demo Site
[ https://issues.apache.org/jira/browse/SENSSOFT-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087663#comment-16087663 ] Joshua Poore commented on SENSSOFT-210: --- [~arthivez] please update time needed to complete 10h+ > Integrate SankeyPlot with Demo Site > --- > > Key: SENSSOFT-210 > URL: https://issues.apache.org/jira/browse/SENSSOFT-210 > Project: SensSoft > Issue Type: Task > Components: TAP >Affects Versions: Tap 0.1.0 >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > Integrate the sankey plot with live logs from the demo site. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SENSSOFT-209) Hand off data format request to Distill
[ https://issues.apache.org/jira/browse/SENSSOFT-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reassigned SENSSOFT-209: - Assignee: Arthi Vezhavendan > Hand off data format request to Distill > --- > > Key: SENSSOFT-209 > URL: https://issues.apache.org/jira/browse/SENSSOFT-209 > Project: SensSoft > Issue Type: Task > Components: TAP >Affects Versions: Tap 0.1.0 >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > Give Michelle the format we want to receive data from Distill for the sankey > plot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[ https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-203: -- Sprint: Sprint 9 > Address UserALE.js feedback from lewismc > > > Key: SENSSOFT-203 > URL: https://issues.apache.org/jira/browse/SENSSOFT-203 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Lewis John McGibbney >Assignee: Rob Foley >Priority: Blocker > Fix For: UserALE.js 0.1.0 > > > Hi Folks, > This is straight from my identical feedback on the dev@ list. Excellent work > on UserALE.js it is looking very good. > Lewis > Some initial questions/feedback/observations > # The README [0] needs to be updated in several places, this will be obvious > when you read the README. This will need to be updated. > # Is the intention to host UserALE.js on some CDN somewhere? I see from [1] > that the intention is to release the code to NPM and/or Bower... is this work > in progress (I think it definitely is) and if so is it documented somewhere? > # It might be worth providing a more detailed description at [2] > # I would make sure that the JIRA Release Notes [3] are copied over to the > CHANGELOG.md file [4]. Additionally, I would structure it after the following > example [5] where essentially the JIRA release report is copied and pasted in > there, this tends to render nicely in Markdown. Additionally, it looks better > if the release manager provides a short link to the release report. This can > be obtained using the URL shortening service at [6]. > # Please make sure to add a DISCLAIMER, a sample can be seen at [7] > # We need to produce a KEYS file for all SensSoft developers who wish to act > as release manager and sign release artifacts. They KEYS file can live > anywhere within/across the SensSoft repositories. An example can be found at > [8]. > # We need to generate a NOTICE file which essentially details usage and > appropriate attribution of dependencies consumed within UserALE.js. An > example can be seen at [9]. > # We should probably generate a Description of a Project (DOAP) file for > every SensSoft project... however this is not a blocker for a release. > I think the above represents a minimum degree of feedback that I would like > to see addressed before we attempt to generate a release candidate for > UserALE.js. > If there are ANY questions, please let me know. > I've raised a JIRA issue for this at [10] which will enable someone(s) to > track and address the issues. > Thanks > [0] https://github.com/apache/incubator-senssoft-useralejs > [1] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md > [2] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4 > [3] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621=12339748 > [4] > https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md > [5] > https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md > [6] https://s.apache.org/ > [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt > [8] https://github.com/apache/incubator-joshua/blob/master/KEYS > [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SENSSOFT-209) Hand off data format request to Distill
Arthi Vezhavendan created SENSSOFT-209: -- Summary: Hand off data format request to Distill Key: SENSSOFT-209 URL: https://issues.apache.org/jira/browse/SENSSOFT-209 Project: SensSoft Issue Type: Task Reporter: Arthi Vezhavendan Give Michelle the format we want to receive data from Distill for the sankey plot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Deleted] (SENSSOFT-194) Sequence Generation
[ https://issues.apache.org/jira/browse/SENSSOFT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard deleted SENSSOFT-194: > Sequence Generation > --- > > Key: SENSSOFT-194 > URL: https://issues.apache.org/jira/browse/SENSSOFT-194 > Project: SensSoft > Issue Type: New Feature >Reporter: Michelle Beard >Assignee: Michelle Beard > > Given UserALE.js data, want to be able to generate sequence counts by path > (dom tree). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SENSSOFT-198) Remove Demographics Info
[ https://issues.apache.org/jira/browse/SENSSOFT-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed SENSSOFT-198. - Resolution: Fixed > Remove Demographics Info > > > Key: SENSSOFT-198 > URL: https://issues.apache.org/jira/browse/SENSSOFT-198 > Project: SensSoft > Issue Type: Task >Affects Versions: Tap 0.1.0 >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 8h > Remaining Estimate: 8h > > Decouple demographics filters from bar charts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SENSSOFT-208) Simplify TAP Dev Setup
[ https://issues.apache.org/jira/browse/SENSSOFT-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reassigned SENSSOFT-208: - Assignee: Arthi Vezhavendan > Simplify TAP Dev Setup > -- > > Key: SENSSOFT-208 > URL: https://issues.apache.org/jira/browse/SENSSOFT-208 > Project: SensSoft > Issue Type: Improvement >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Original Estimate: 3h > Remaining Estimate: 3h > > Simplify TAP dev environment by changing the gulpfile. Then we will not have > to rebuild via docker upon every change during development and testing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SENSSOFT-193) Cleanup Distill
[ https://issues.apache.org/jira/browse/SENSSOFT-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard resolved SENSSOFT-193. - Resolution: Fixed Deprecated STOUT integration. > Cleanup Distill > > > Key: SENSSOFT-193 > URL: https://issues.apache.org/jira/browse/SENSSOFT-193 > Project: SensSoft > Issue Type: Improvement > Components: Distill >Affects Versions: Distill 0.1.0 >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: Distill 0.1.0 > > > Revisit Distill and cleanup any references to UserALE 3.0 (deprecated). Work > on supporting UserALE.js. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SENSSOFT-201) Finalize Sankey Diagram Wireframe
[ https://issues.apache.org/jira/browse/SENSSOFT-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthi Vezhavendan resolved SENSSOFT-201. Resolution: Fixed > Finalize Sankey Diagram Wireframe > - > > Key: SENSSOFT-201 > URL: https://issues.apache.org/jira/browse/SENSSOFT-201 > Project: SensSoft > Issue Type: Task >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 1h > Remaining Estimate: 1h > -- This message was sent by Atlassian JIRA (v6.4.14#64029)