MoM \ MON \ 26th \ DEC 2016

[peeyush-tm]

Minutes of Meeting

1. Issue #24 - has all the work details
   • need to atleast have LogBook in place and working
   • think about what we are building - a platform to server instant app
   • then think about the problem to solve
   • think about the approaches that can be taken
   • define what can be achieved and what will be compromised between different approaches
   • have your doubts as precise as possible, which can be answered in yes or no (along with pros and cons)
   • build one app, build a thousand apps, it is one and the same thing
2. Forms should be the base class to serve all the screens (abstraction done right)
   • web
   • app (todo)
3. Forms would have two more components
   • PDF viewer
   • Sign Capture
   • depends on point 2
4. Portrait and Landscape modes - should be supported in all the terminal apps (web or native)
   • depends on point 2
5. Use Case - Queue management
   • user comes in, puts in his details
   • generate a TOKEN for user
   • display the NOW and NEXT token number on another Terminal
   • Check the TOKEN and User Details and let the queue work normally (FIFO)
   • eg: Bank Queues
   • eg: Hospital Queues
   • eg: Interview Queues
6. Exponent \ User App - Delayed - Start in January
7. Tute: What is serverless? Why is makes sense?
   • please ask away your doubts
8. Sat \ Sun - write personal blog posts
   • what did you want to achieve
   • what did you want to build
   • what were the components required
   • component document links and a short description, from your point of view, and how it fits in your goal
   • how you build it
   • problems you faced
   • future work
   • link to code
9. Team: Next 1 year, we will be a Machine Learning Company. Find out resources to start with, good resources.
   • we want to build a SDK, which any developer would be able to use and provide his user with a personal experience
10. Think about the NOTIFICATION experience, where it makes sense and where it does not
    • it does not make sense to tell GUEST that they have checked out, they know
      • but it makes sense to notify HOST about checkout. Security!
11. Market: Instant apps - GSuite, Famous have launched apps and platforms. We need to move fast!

Add any other point that I might have missed. Questions. Doubts. Inputs.

Be Awesome!

Daily Meeting Details and Schedule

Day	Time	Length	What?
MON	11:00 AM	1 Hour	Current Week's Work discussion. Discussion about SAT & SUN Projects. Previous Week's Discussion.
MON	7:30	30 Min	Day Closing discussion
TUE	11:00 AM	30 Min	Previous work details and Today's focus
TUE	7:30	30 Min	Day Closing discussion
WED	11:00 AM	30 Min	Previous work details and Today's focus
WED	7:30	30 Min	Day Closing discussion
THU	11:00 AM	30 Min	Previous work details and Today's focus
THU	7:00	1 Hour	Current week's work details and plan to finish it
FRI	11:00 AM	30 Min	Based on THU discussion, plan for the best plan to close the week
FRI	7:00	1 Hour	Closing week's discussion and next work discussion. What is pending? What to focus on next?
SAT	Anytime	30 Min per person	Share what you have learned and Blog. and Q&A
SUN	Anytime	30 Min per person	Share what you have learned and Blog. and Q&A

[veris-neerajdhiman]

[26, Dec 2016]

[In Progress] : kong integrations at API G/W, Some issue sin adding plugins fo enabling duynamic urls support.

[veris-ankitpopli]

26 Dec, 2016

• :construction: Kong API Mangement using wicked . [Kong not accessible from wicked docker container].
• :thinking: Unifying VRTs. (User App badge + Terminal)

Update: moved to #24