Timelines: MAR\ APR 2017

[peeyush-tm]

March Week 2 ( 6th -10th )

ND

• [x] Open source lib for Notification (for now only Email Service, SMS Service).

AP

• [ ] Make the static admin panel usable.
• [ ] Refactor & cleanup back end code. Introspect, & Inspect code.
• [x] Revisit Process/Widget Schema generation.

AA

• [x] Enable existing RN Components for Web
• [x] As many Components as possible. Refer - #51

AB

• [x] Understand Admin Panel
• [x] Get rid of V2 for at least another month.

March Week 3 ( 13th -17th )

ND

• [x] States Service
• [x] Authorization Service

AB

• [ ] Admin Panel integration
  • [x] Create Organization
  • [ ] Add Member
  • [x] View Members
  • [x] View Runtimes
  • [x] View Widgets
  • [x] View Processes

AP

• [ ] APIs for AB tasks
  • [x] Create Organization
  • [ ] Add Member
  • [x] View Members
  • [x] View Runtimes
  • [x] View Widgets
  • [x] View Processes
• [ ] As many Components as possible. Refer - #51

AA - Missing

March Week 4 ( 20th - 24th )

Main Focus

- Admin Panel (like AWS Console)
- Resource Management (like https://market.mashape.com/explore)
- Kong Logging for Microservices
- State Management via redis
    - State != Logging
    - State Change Logging
- Spotlight => for test case creation and management

ND

• [ ] Push Notification Service (Firebase)
• [ ] Keen
• [x] Revisit Organization/Members

AB

• [x] Admin Panel integration
  • [x] Create Widget
  • [x] Create Runtime
  • [x] Assign Runtimes

AP

• [x] APIs for AB tasks
• [ ] Revisit Authentication
• [ ] Veris Runtime Types (User/Terminal/Admin)
• [x] RnD Widget resolution previews - Widget States with AA

AA

• [x] RnD Widget resolution previews - Widget States with AP
• [x] As many Components as possible. Refer - #51
• [ ] Widgetization of Admin Panel ( More components in registry, more actions in registry )
• [ ] Revisit Membership - Membership type - Update clients with tweaks according to membership type.

March Week 5 ( 27th - 31st )

Main Focus

Extend Microservices => Each service will be a totally separate codebase and project
Mistral => Mistral is a workflow service. 
    - VRT => Mistral for Widget
    - Widget => Mistral for Process
    - Rules + Data Enrichment
Admin Panel 
    - Process & Data & Widget Mapping
    - Templates
Kick Off 
    - Sketch <=> Templates

ND
27 & 28- confirmed

• [x] Kong Integration (Resource Registry). Maybe directly import Swagger.
• [ ] Rule Engine for Widgets only - Add member if user emails ends with @veris.in (Moved to last, coz we need a strong base for rules & less moving parts)
• [ ] Test Suites for LogBook

AB

• [x] Create Processes
• [ ] Testing. Finishing Touches. Creating Logbook using the Admin.

AP

• [ ] Widget Templates Service
• [x] Component Actions with AA (file pickers, similar to intents).
• [ ] RnD Component Recipes

AA

• [x] Bind existing components with jasonette
• [x] Component Actions with AP (file pickers, similar to intents).
• [ ] RnD Component Recipes
• [x] Widget Template Previews

Next

• Local VRT communication <=> locally execute the data workflow <=> Embedded Mistral
• Define Sketch Prototype <=> as an App and Components
• Admin Panel
• Mistral <=> Data Binding <=> Templates
• Universal app inter-communication => User App <=> Terminal App
  • same backend service keys will map the data

April Week 1 ( 3rd - 7th )

ND

• [x] V2 support
• [x] Organization / Member Revisited
• [ ] Changes in micro-service as per client integration (if any)

AB

• [x] Mapping process schema to widget template
• [ ] Creating a schema using resources
• [x] Integration deletion Api of all services
• [x] Date/Time picker IOS test

AP

• [ ] Workflow / Rules / States using Mistral.

AA

• [x] QR display component
• [x] Scanner component
• [x] Fix react native % properties
• [x] Date/Time picker IOS dev

April Week 2 ( 10th - 14th )

ND

• [ ] Swagger client for process (import swagger client for every service operation added in kong)
• [x] V2 support (if any)
• [ ] Changes in micro-service as per client integration (if any)
• [ ] Test Cases

AB

• [ ] Member management on Admin Panel
• [ ] Native Notification Integrations (iOS)

AP

• [ ] FIrebase Integration (Async Action, Real time Data change updates)
• [ ] User Actions (Pending Actions by User, eg. allow user from meeting with widget)

AA

• [ ] Runtime Session exchanges
• [ ] Native Notification Integrations (Android)

April Week 3 ( 17th - 21st )

ND

• [ ] Notification module Revisit (SMS/EMAIL per organization support) , Push Notification integration.
• [ ] V2 support (if any)
• [ ] Changes in micro-service as per client integration (if any)
• [ ] Test Cases

AB

• [x] basic template schema creator for widgets (low priority)

AP

• [ ] Integrations with existing services (Authorization)
• [ ] Integrations with existing services (Logging)
• [ ] Integrations with existing services (State, may be not, depends on Week 1 Mistral)

AA

• [x] Allow rendering existing components via JSON (Define Higher Order Components Props)
• [x] Refactor platform -> ui -> components (use index.js, index.android.js, index.ios.js)
• [x] Image picker/Camera component abstraction to Actions

April Week 4 ( 24th - 28th )

ND

• [ ] Pending work (if any) or new RnD

AB

• [x] R&D on converting sketch file to widget template
• [ ] widgetize static admin panel (low priority)

AP

• [ ] Continue Pending Work

AA

• [ ] Introduce Web Components (Polymer/X-tag) components for web
• [x] Separate Props file from component itself (get ready for OSS library)
• [x] Switch to Context API instead of custom context object.
• [ ] Component recipes (Discuss with @veris-ankitpopli )

Discussions

• User Actions - Like JAsonette Actions - https://docs.jasonette.com/actions/ used for calling the local functions these are the system default these are widget specific
• Validation and Verification of the data
  • since the data model is shared with mobile client, validation of data is not a challenge
  • verification of the data is when a user sends an "accept" signal to backend meaning that the user is satisfied with the state of the widget on the frontend the backend will match and verify the data and which user thinks is OK
• Backend will send out the "next widget to call"
• TODO - mistral client for frontend - that can manage the basic functionality of rules and workflow on the frontend
• Data enrichment, Rules, Data conditions -> can always be another process
• UX - Solve for the users that atleast know what are web services and how to use them to create a workflow

[veris-abhinavanand]

TODO

• [x] QR display component
• [x] Scanner component
• [ ] Date/Time picker IOS test

We have a lot of components for now. No more new component development

• [x] Higher Order Components Props
• [x] Refactor platform -> ui -> components (use index.js, index.android.js, index.ios.js)
• [ ] Image picker/Camera component abstraction to Actions
• [ ] Separate Props file from component itself (get ready for OSS library)
• [ ] Component recipes (Discuss with @veris-ankitpopli )
• [ ] Introduce Polymer components for web
• [ ] Revisit Sketch
• [ ] Switch to Context API instead of custom context object.

[veris-amoghbanta]

AB

• [x] Mapping process schema to widget template
• [ ] Creating a schema using resources
• [ ] Add a member
• [x] Integration deletion Api of all services
• [ ] basic template schema creator for widgets
• [x] R&D on converting sketch file to widget template
• [ ] widgetise static admin panel (low priority)