View source for Connected Devices/Projects/Magnet/Sprint 11

== General info ==
* Sprint 11 from January 23th to February 3rd (2017)
* Participants Development Sprint: Francisco, Wilson, Sam, Guillaume, Francis, Isabel and Maria

* Links of interest:
** [https://github.com/mozilla-magnet Magnet Code Repository] 
** [https://waffle.io/mozilla-magnet/magnet?milestone=Sprint%2010%20%5BJan%209th%20-%20Jan%2020th%5D Waffle board for Sprint 10]
** [https://waffle.io/mozilla-magnet/magnet?milestone=Sprint%2011%20%5BJan%2023rd%20-%20Feb%203rd%5D Waffle board for Sprint 11]

== Sprint objectives ==
According to the planned engineering work, last sprint (Sprint 10) we worked hard on the React components, so we are in good shape to finish them at the end of the first week of Sprint 11. We finished the App Navigation and Deep linking tasks too that were scheduled to be done in Sprint 11 but at the same time, we couldn't move too far in the Backend part.

During this sprint 11, we are not going to have visuals yet, we need to do all the work that doesn't require UI (Visual work will not be started until Jan 30th)
It will include:
* Finishing all the React Components (at the end of the next week, Jan 27th)
* and all the backend part including the libraries. We expected to be finished at the end of next week, but probably it will take until the end of sprint 11. Sam will start working on API, and documenting it
 
Apart of this:
* Wilson started to post some mock up concept and we will continue with that until we have the final UI.
* Francisco wants also to build the the Geolocation component, no the geofencing, to ensure the app has the the localization ready to distribute it to the rest of the components and probably later he will try to give a hand in the offline strategy and the client API as both things have to be built together.

== Development tasks Planning ==
Modified Engineering tasks according to the work done in Sprint 10 and also planned in Sprint 11
[[File:Magnet Engineering sprints postGate1 Sprint11.png|800px]]


=== Tasks or Bugs committed for this sprint ===
{| class="wikitable"
! style="text-align: center;" | Task
! style="text-align: center;" | Assigned
! style="text-align: center;" | Status
! style="text-align: center;" | Status Notes
|-
| Create a MediaPlayer element for iOS and Android supporting the Opus codec
| Sam
! style="background:#FFFF00;" | Ongoing
| 
|-
| Document development process for services
| Sam
! style="background:#FFFF00;" | Ongoing
| 
|-
| Render POI view with dummy data
| Wilson
! style="background:#FFFF00;" | Ongoing
| Now we have dummy data for home view we need to be able to transition to a POI view from one of the tiles in the home view. This will require reshuffling the Redux store structure to work from a central item-cache. The home view will reference a list of POIs by ID and the POI view will reference a single POI by id. When the view is rendered we will fetchItemIfNeeded(). The cloud API will likely return a list of POIs so we should cache each of these separately so that they can be reused by the POI view.
|-
| Audio component
| 
! style="background:#C1C6CA;" | Not started
| Not just the player that is being done in "Create a MediaPlayer element for iOS and Android supporting the Opus codec" task but the screen that looks like a phone call, etc.
|-
| Create cron to kick off nightly builds
| Sam
! style="background:#C1C6CA;" | Not started
| 
|-
| First testing round
| Isabel
! style="background:#C1C6CA;" | Not started
| 
|-
| Fav component
| 
! style="background:#C1C6CA;" | Not started
| 
|-
| Share component
| 
! style="background:#C1C6CA;" | Not started
| 
|-
| Carousel component
| Francisco
! style="background:#C1C6CA;" | Not started
| 
|-
| Create database "model" objects with a view to reuse in a library on the client
| 
! style="background:#C1C6CA;" | Not started
| 
|-
| Generate and save terraform plans for creating the k8s cluster and document deis installation
| Sam
! style="background:#C1C6CA;" | Not started
| 
|-
|}

== Other comments/talks during the Sprint Planning ==
* Compass Component: Francisco was able to solve the cocoa pods issue. It seems the pods change the way you specify where your react native libraries are so it took him a day figuring out what was happening. Francisco is also planning to write a blog post about it as he didn't find anything in the Internet about this issues.
** Francisco has also to check with Wilson, as when he created the pods, he created them without enabling them to use swift or dynamic frameworks (It seems it's a flag). The problem is that when executing pods install, it's getting crazy.
** So far Francisco has committed it and merged, if you debug you can see the compass component pointing to the Shark and you can see how it moves and the direction changes. It's written in native, not java script. It's working fine, there could be issues if you are in the antipodes. Wilson says that if we are very far from the point we could hide the compass to avoid issues, we can play around
* Waffle connected to, what repos?: Journey, Journey services. We would need to disconnect the rest of repos. 
** Scanners ones? We will use it after releasing the first version of the app. In the previous version we had the GPS and the physical web scanners together, we would need to create one repo specific for the Geolocation staff in Journey
* What happens if we need to use "Project Magnet" name for the beta version of the app we are working on? It would be really bad if we had to use the same name because users will update the app and we'll download a complete different application without physical browser. Right now the documentation in github is really confusing. Journey is a code name and we are waiting for Porfirio to let us know about the definitive name

* Timeline execution and Usability Test? Possible dates 20th Feb - 24th Feb while Jakuv (Visual designer) is on PTO that week


== Issues during this sprint ==

== Demos ==

== Retrospective ==
=== Actions taken from last sprint ===
* ['''Maria'''] to remove simplify the Milestones, dropping the "Gate - 1" part

=== Things that went well ===


=== Things that went not that well ===

=== Actions for this sprint ===