Third Outcobra Meetup 10. June 2017
Date: 10. June 2017 You can find the original notes here
[TOC]
- Verification of the last meetup's tasks
- Old sprint reduction
- Production Domain
- Future
We are currently not sure which license we should choose. Still TBD
Implemented. Still bit broken @needToRoll
Done
Not on develop yet
Currently still release 1.0.0. We are waiting for the frontend update PR to be merged. TODO @jmesserli
We decided to just use an DB-Dump that will be sended to multiple servers nightly. Probably we will also save an encrypted version of the dump to Dropbox or something similar. Needs implementation in the close future.
QA only needs some mere frontend tests which we are kicking for now, since it's not really beneficial in the current state. Other unresolved issues have been moved to the current Sprint as they will be resolved in there.
We bought the following domains:
- outcobra.school
- outcobra.cloud
We'll implement a solution as wireframed in the following pictures but without the checkboxes on the semester tabs.
The Exam Ui will look similar to the task ui (as described below). The Exam feature will mostly be developed by @needToRoll
We all agreed that we are not longer happy with the current look of the task ui and decided to do something similar to google inbox with the accordion popout thingy.
We are all still motivated to work on this project. In the next year we will have about 4 months on which we will not be able to work a lot on the project because of exams in the bms and the IPA and IdPA. But these 4 months are mainly in second part of the year (March-June). Joel will most likely be away for the year after this year (Summer 2018-2019) because of military service. Florian and Mario will be able to keep the project up and running in this time.
We won't be able to target a business client with the achievable features we have planned for the forseeable future so we want focus on our initial idea. We want to make a user friendly tool for students only. The first step to this goal is the beta in august.
The beta plans can be seen on the last meetup's wiki site.
We discussed some things that are important to have when we start the beta but are not actual features for the product.
- Mailbox (for instance [email protected]) @jmesserli
- Description of implemented and planned features (some thing like a news feed)
- Story of the project and the devs
- Story of the name
- Social Media/Marketing Channels (for instance Twitter)
- Logo @needToRoll
We also gathered some ideas how we could get more beta users for our product.
- BIT-Apprentices
- Cards (With logo, url, short description)
If we are funny enough we could also start something like a bug bounty programm to reward those who find and report bugs to us.