Now that we have tons of data about Pokemon (what they are, where they are, what’s their relationship, what they can transform into, which attacks they can perform, aso) we want to integrate it all into a comprehensive website. This website should contain sections about each Pokemon and its details. Additionally, the website should register the user’s location and tell the user how close is that the predicted pokemon to him/her. Additionally you will be incorporating the apps that were created by project B,C and D into the website. Your group will need to create automated builds and testing for this apps and use continuous integration to pull in new changes in the code repositories. Apps from projects B-D should be packaged and made available on NPM. Ideally when you completed these tasks the webapp component would integrate the apps by “requiring’ them. Here is a possible user story: when a user opens the website or the app the current location of the user will be shown. Additionally, the website/app will show automatically where the pokemons that are currently active are and where the pokemons that we predict to active in the nearest future (i.e. within half a day) will be located (all of this will be available from the app developed in project D). Hopefully, the website will be somewhat crowded by that data. Then, there needs to be a menu bar or something available (e.g. above the map or on the right side to it) that will list currently active or predicted pokemons. Clicking on one of them will make other pokemons on the map disappear, except of this clicked one. Separate web pages would allow the search and presentation of individual Pokemons and the information we gathered about them, including third party data (project A) and twitter analysis (project C)
Dear @PokemonGoers/catch-em-all -ers, it's time to meet the feature freeze!
I would like to set the feature freeze to coming Monday, 24th Oct, @ 23:59. What this means is: by Monday evening you should finalize the implementation of the open features and get rid of those you think are too immature to make it to production. This also means that after Monday you will still have time to fix eventual bugs, clean up code and make slight design changes.
I would like to get feedback from possibly all of you, opinions and concerns regarding this matter. Also: it would be nice to get a list of features which will not make it to production.
Lastly: after feature freeze, you will have one week to clean code. After that it's officially over (though practically, if you want, you can go on working on this as much as you like! It's after all open source, the automatic deployment is bound to this repo, etc. So: it's up to each and everyone of you).
Filter UI: Currently has data binding bugs, my three state checkbox issue open and then we need to fix the selection behavior. Assuming that the map team has implemented filtering correctly this should be doable.
Notifications: @johartl picked it up and worked on it
Pokemon Tweets: @mfkaptan is working on it. I've just bumped the issue #68
Predictions UI: The card itself was implemented by @WoH, but I've never seen a prediction on the map. That is what troubles me...
I'll try to figure out the websocket issue ( @johartl knows what I'm talking about). Reverse proxy + firewall should do, but I'm traveling to SFO so expect slight delays. @gyachdav and @goldbergtatyana will ping the s*\ out of me if anything urgent comes up :)
Dear @PokemonGoers/catch-em-all -ers, it's time to meet the feature freeze!
I would like to set the feature freeze to coming Monday, 24th Oct, @ 23:59. What this means is: by Monday evening you should finalize the implementation of the open features and get rid of those you think are too immature to make it to production. This also means that after Monday you will still have time to fix eventual bugs, clean up code and make slight design changes.
I would like to get feedback from possibly all of you, opinions and concerns regarding this matter. Also: it would be nice to get a list of features which will not make it to production.
Lastly: after feature freeze, you will have one week to clean code. After that it's officially over (though practically, if you want, you can go on working on this as much as you like! It's after all open source, the automatic deployment is bound to this repo, etc. So: it's up to each and everyone of you).