FlyWeb: Difference between revisions
m (→Security) |
(update) |
||
Line 1: | Line 1: | ||
[[File:FlyWeb.png| | <div style="float: right; margin: 0px 0px 10px 25px;">[[File:FlyWeb.png|link=]]</div> | ||
=='''Program Description'''== | |||
The web already powers the world's email, media, shopping, and more. Interacting with these things is a breeze because they all use the web. What if the electronics around us were the same? | The web already powers the world's email, media, shopping, and more. Interacting with these things is a breeze because they all use the web. What if the electronics around us were the same? | ||
Meet | Meet FlyWeb. FlyWeb is a very simple idea at its core. Instead of phones interacting only with the cloud, they can discover and interact with electronics around them that are running empty web clients, such as TV's, projectors, game consoles, etc. The electronics come to life when connected to phones. The key here is that either the phones serve web apps to these electronics, or the electronics serve web apps to the phones. | ||
For more information: https://wiki.mozilla.org/FlyWeb | |||
==Why?== | ==Why?== | ||
Line 18: | Line 18: | ||
The web is the best platform for serving all of these needs. Indeed, it has been designed for them for over a decade. | The web is the best platform for serving all of these needs. Indeed, it has been designed for them for over a decade. | ||
===User Stories and Acceptance Criteria=== | |||
Coming soon! | |||
<!--- {| class="wikitable" | |||
! style="text-align: center;" | Title | |||
! style="text-align: center;" | BUG ID | |||
! style="text-align: center;" | User story | |||
! style="text-align: center;" | Acceptance Criteria | |||
|- | |||
| Bugzilla Lite | |||
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1180660 1180660] | |||
| As a user I want to be able to raise bugs directly from the device so that I can inform Mozilla directly of any of my requirements. | |||
| it should be easy to attach logs - it should be easy to attach screenshots - it should receive feedback on the ID of the bug i have raised - it should be easy to get an overview of all the items I have raised | |||
|} ---> | |||
=='''Program Status'''== | |||
{| class="wikitable" | |||
! style="text-align: center;" | Milestone | |||
! style="text-align: center;" | Date | |||
! style="text-align: center;" | Status | |||
|- | |||
| MozFest Demo | |||
| 11/6-7/2015 | |||
! style="background:#00B2FF;" | DONE | |||
|- | |||
| Mozlando Demo | |||
| 12/7-11/2015 | |||
! style="background:#00B2FF;" | DONE | |||
|- | |||
| Platform Development | |||
| 1/2016 | |||
! style="background:#00EC00;" | ON TARGET | |||
|- | |||
| Land on Masters | |||
| 6/2016 | |||
! style="background:#00EC00;" | ON TARGET | |||
|- | |||
| London All Hands Conference | |||
| 6/2016 | |||
! style="background:#00EC00;" | ON TARGET | |||
|} | |||
'''Status Key''' | |||
{| class="wikitable" | |||
! style="text-align: center;" | Color | |||
! style="text-align: center;" | Status | |||
! style="text-align: center;" | Key | |||
|- | |||
! style="background:#00EC00;" | | |||
| On Target | |||
| The project or deliverable is expected to meet its due date. | |||
|- | |||
! style="background:#FFFF00;" | | |||
| Challenged | |||
| The project or deliverable is facing an issue that might cause it to miss its due date, but a “get well” plan has been developed to get it back on track. | |||
|- | |||
! style="background:#FF2800;" | | |||
| At Risk or Late | |||
| The project or deliverable is blocked or facing an issue that might cause it to miss its due date, and there’s no “get well” plan to get it back on track, or it is already late. | |||
|- | |||
! style="background:#00B2FF;" | | |||
| Done | |||
| The project or deliverable has been completed. | |||
|- | |||
! style="background:#C1C6CA;" | | |||
| On Hold | |||
| The project or deliverable has been placed on hold. | |||
|} | |||
---- | |||
=='''Program Timeline'''== | |||
[[File:Flyweb Milestones.png]] | |||
---- | |||
=='''MVP Scope'''== | |||
<bugzilla> | |||
{ | |||
"blocks":"1228662", | |||
"status":["NEW","REOPENED","UNCONFIRMED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"], | |||
"include_fields": "id, summary, status, target_milestone, resolution, assigned_to, depends_on, blocks, whiteboard, cf_feature_b2g" | |||
} | |||
</bugzilla> | |||
---- | |||
=='''Program Stakeholders'''== | |||
{| class="wikitable" | |||
! style="text-align: center;" | Role | |||
! style="text-align: center;" | Name | |||
! style="text-align: center;" | IRC | |||
|- | |||
| EPM | |||
| Nicole Yee | |||
| nicoleyee | |||
|- | |||
| EM | |||
| Jonas Sicking | |||
| sicking | |||
|- | |||
| TL | |||
| Kannan Vijayan | |||
| djvj | |||
|- | |||
| Engineering | |||
| Justin D'Arcangelo | |||
| justindarc | |||
|- | |||
|} | |||
*EPM = Engineering Program Manager | |||
*EM = Engineering Manager | |||
*TL = Tech Lead | |||
---- | |||
==Reference Links== | |||
=Demo Videos= | =Demo Videos= | ||
Line 40: | Line 160: | ||
* [mailto:nyee@mozilla.com Nicole Yee (:nicoleyee)] - project management | * [mailto:nyee@mozilla.com Nicole Yee (:nicoleyee)] - project management | ||
=Communication= | =Communication= |
Revision as of 17:26, 2 February 2016

Program Description
The web already powers the world's email, media, shopping, and more. Interacting with these things is a breeze because they all use the web. What if the electronics around us were the same?
Meet FlyWeb. FlyWeb is a very simple idea at its core. Instead of phones interacting only with the cloud, they can discover and interact with electronics around them that are running empty web clients, such as TV's, projectors, game consoles, etc. The electronics come to life when connected to phones. The key here is that either the phones serve web apps to these electronics, or the electronics serve web apps to the phones.
For more information: https://wiki.mozilla.org/FlyWeb
Why?
The connected devices market is ready to explode. As the market grows, much like the early internet, these devices are being segregated into walled gardens of one-off proprietary initiatives, such as AirPlay, the Google Cast API, etc. These solutions not only lock their users into specific vendor ecosystems -- to the benefit of those vendors and detriment of their users -- but also require significant investment to solve each use case.
Many of these connected devices initiatives have common underlying platform needs:
- to discover and connect devices together,
- enable bi-directional communication,
- allow arbitrary, but secure code execution on each side,
- and require knowledge of as few details of a device's peers as possible.
The web is the best platform for serving all of these needs. Indeed, it has been designed for them for over a decade.
User Stories and Acceptance Criteria
Coming soon!
Program Status
Milestone | Date | Status |
---|---|---|
MozFest Demo | 11/6-7/2015 | DONE |
Mozlando Demo | 12/7-11/2015 | DONE |
Platform Development | 1/2016 | ON TARGET |
Land on Masters | 6/2016 | ON TARGET |
London All Hands Conference | 6/2016 | ON TARGET |
Status Key
Color | Status | Key |
---|---|---|
On Target | The project or deliverable is expected to meet its due date. | |
Challenged | The project or deliverable is facing an issue that might cause it to miss its due date, but a “get well” plan has been developed to get it back on track. | |
At Risk or Late | The project or deliverable is blocked or facing an issue that might cause it to miss its due date, and there’s no “get well” plan to get it back on track, or it is already late. | |
Done | The project or deliverable has been completed. | |
On Hold | The project or deliverable has been placed on hold. |
Program Timeline
MVP Scope
54 Total; 1 Open (1.85%); 52 Resolved (96.3%); 1 Verified (1.85%);
Program Stakeholders
Role | Name | IRC |
---|---|---|
EPM | Nicole Yee | nicoleyee |
EM | Jonas Sicking | sicking |
TL | Kannan Vijayan | djvj |
Engineering | Justin D'Arcangelo | justindarc |
- EPM = Engineering Program Manager
- EM = Engineering Manager
- TL = Tech Lead
Reference Links
Demo Videos
Proposal
Security
- A discussion about FlyWeb security by Ekr
- A list of example scenarios that are useful when discussing security
Team
- Kannan Vijayan (:djvj) - engineering
- Justin D'Arcangelo (:justindarc) - engineering
- Jonas Sicking (:sicking) - engineering / specifications
- Nicole Yee (:nicoleyee) - project management
Communication
Video Conferencing - Vidyo Room
Quick link to join with the Vidyo app (prompts install if needed)
We have our own Vidyo room for meetings. Contributors and non-employees are welcome to attend all meetings. Here are the full details for joining:
"FlyWeb" Vidyo Room |
---|
Hello, |
Project Management
We use Trello for project management. All ongoing tasks are listed there.
Meetings
Calendar
The FlyWeb team has a public calendar with every team meeting.
Instructions for Adding to your Calendar
- Open the calendar.
- Click on the "+ Google Calendar" button in the very bottom right of your screen.
You can also use the XML and ICS methods, but these are not recommended.
Note: The "Find a Time" feature will not work for other people if you import this calendar. As a consequence, others will not see that you are unavailable when attending a FlyWeb meeting. We suggest either accepting this, or adding the meetings to your main calendar as well.
Standups
We have two weekly standups, with both times available on the Public Calendar. These standups happen in the FlyWeb Vidyo room.
All meeting minutes
2015-Q3
- 2015-08-20 - FlyWeb+Presentation API
- 2015-08-13 - Standup, late
- 2015-08-12 - Use case culling
- 2015-08-12 - Technical materials compilation
See Also
- User and Market Research: Due to the confidential nature of the interviews, and our respect for our interviewees' privacy, we are restricting access to this information.