hellojwilde / gossamer Goto Github PK

https://jwilde.hackpad.com/Gossamer-Sprint-Notes-8XCgRZAQ37t

https://jwilde.hackpad.com/Gossamer-Heartbeat-Sprint-Projects-PHhpF7WTKhk

and this, maybe: https://jwilde.hackpad.com/Gossamer-Sprint-Notes-8XCgRZAQ37t

Where do we publish? Who do we reach out to? What are our talking points and specific asks? Timeline?

https://wiki.mozilla.org/Participation/Lab

This way we can display an experiments button and let people login with it

This should be a mix of overall project info, goals/strategy/timeline, and contributor onboarding, how/where we're working, links to support/collaborative materials, what success of this project looks like before spinning down collaborative infra

We probably need to have a discussion to outline what this needs to look like, and how technical it needs to get. I'm thinking we can probably get rid of all of the browser.html readme text (by linking to the original repo) and completely focus on Gossamer itself.

These need to come here: https://trello.com/b/uonin7Ai/gossamer-sprint

Language can be found in the server repo: https://github.com/hellojwilde/gossamer-server/tree/master/views

I think they key thing that we've learned is that analytics are cool, but they're kinda a Demo 2 feature or something to quickly hack together with Keen.io.

Until we have a decent number of users it's kinda not that helpful.

Replace "data" with "more concrete over the shoulder test results".

We have all sorts of crazy ideas! Once they're all documented in github, let's discuss prioritizing them via milestones.

The core functionality of Gossamer is shipping experimental front-end builds to users, enabling users to provide feedback in the form of analytics and github issues, and showing real-time data about those metrics

The web service will:

• Pull code from github and run relevant build processes
• Appropriately notify clients when new builds of the experiment that they're enrolled in are available
• Receive and store time-series analytics data about the performance of the extension to the browser
• Display the analytics data in real-time

The extension to browser.html will:

• Enable a user to start joining studies after logging in with GitHub
• Contain hooks for submitting analytics data
• Reload the browser after the user selects a particular experiment

• Github readmes
• https://jwilde.hackpad.com/Gossamer-Heartbeat-Sprint-Projects-PHhpF7WTKhk
• Anything else?

The goal here is to make the wrapper around a branch as minimal as possible.

Blog submission process: https://wiki.mozilla.org/Planet_Mozilla

• Come up with specific tag or category with a feed to get added to the planet
• Submit Bugzilla form found in link above
• Let @CaptainCalliope know and he'll poke the person who responds to those bugs

this got challenging when I first tried it because of the structure of the modules in browser.html...we'll see if this gets easy in this sprint after struggling for a while

The amount of data for even a single build is pretty significant, and redis is just too expensive to run for this sort of infrequently accessed data

https://docs.google.com/document/d/17Qw2POfsE1BoQbvHPaPhy6glIMo8ZRnJPMOzbci1MDA/edit#

https://wiki.mozilla.org/Firefox_OS/Spark

Repo readmes, blog posts, cross linking, splash page.. how/where we're working, what success of this project looks like before spinning down collaborative infra.. etc

These don't add value until there is scale, so let's drop these for now