Weekly: MAR \ Wk-1 \ FEB (27 - 28) MAR (1 - 4) \ 2017

[peeyush-tm]

• Timelines - @veris-neerajdhiman @veris-ankitpopli
• V2 Support - @veris-neerajdhiman
  • tree rebuild everynight - celery job
  • ❤️
  • ⏭ Make it Pretty 💄
  • move all the code that impacts user's passes to celery.
  • move all the code that impacts user's UGVP to celery
  • ⏭ keep the interaction faster and move maintenance tasks in celery.
    • ⏭ identify the critical data that needs to be updated ASAP (eg: otp, onboard, verify, create pass, check in etc)
    • ⏭ identify the maintenance tasks that could be moved to celery
• ⏭ web server -> API gateway - @veris-ankitpopli @veris-neerajdhiman
• ⏭ V3 Clients - @veris-amoghbanta @veris-abhinavanand
  • ⏭ Test Suites

Q&A

@veris-ankitpopli

Q

❓ Should client be aware of the various services available?
Currently the client calls the Process API
then creates a Widget.
Shouldn't it just send the list of processes to the Widget API.
Ideally it should be done, but not urgently, so waiting for inputs from

A

Any two, or more, layers must not perform the same functionality. The abstraction is more important that performance, for the initial development.

A < widget > is basically mapping < processes and data > to the < components >.
The < process > calls < various services >, also that response from the < process call > can be enriched with more data.
I am expecting the user interface to work in following way -

1. user comes in and check for various micro-services
2. now he will start creating process
3. once he has compiled all the process: eg: imagine logbook (if this then that and stuff)
4. now he wants to serve this to his users, but he needs display templates
5. choose templates (that means components)
6. he will know the data in and data our of all the processes and all the rules
7. he will map everything to the template components
8. check the list of Members the admin has, assign them the new VRT
9. VRT is simple - map widgets and rules and users
10. widget is simple - map templates (components) to the processes in and out
11. so first there is always the process.

I would need more details about the problem and possible solutions to think about how to do it the best way.

Closure

@peeyush-tm the comment answers what I was looking for, will discuss it in detail when you are back, & yes maybe it's just an optimization. So this can wait.

[veris-ankitpopli]

27th Feb, 2017

Work

• Admin Panel. (Static)
  • Components to retrieve & render Runtimes, Widgets, Processes & Members.
  • Create Widget ( simple template creation - click on component to add it vertically to template )

TODO:

• Allow adding props to components from the Admin.
• Reference Weekly: FEB \ Week-4 \ 20th-25th \ 2017 \ [ 10:30 - 11:00 ] #43
• Create a unified Runtime Locker for Organization (for admins) 🤔
• Open Source Lib: Networking the React Way. 🥇

Problems:

• Touch events don't bubble up when nesting TouchableHighlight components facebook/react-native#6796 (comment). Hack/Solution: we obscure the touch events to be handled by an overlay 😎
• React native has a unconventional API - Children do not inherit position (as opposed to DOM in HTML) 😞 . @veris-amoghbanta to the rescue, saved ⏳

28th Feb, 2017

Work:

• Admin Panel (Static)
  • Attach a list of Processes to the Widget, that the Widget can call.
  • Create the widget once the processes has been selected, & template has been added.
• Open Source 🤔 RecyclerView Component 😎

TODO

• Component Editor 🤔 (Allow adding props to components from the Admin)
• Component Doc / Prop builder 🤔 💭 Maybe something like an IDL.
• Load existing Widget for editing.

Problems:

• ❓ Should client be aware of the various services available ?. Currently the client calls the Process API & then creates a Widget. Shouldn't it just send the list of processes to the Widget API. Ideally it should be done, but not urgently, so waiting for inputs from @veris-neerajdhiman @peeyush-tm .

1st Mar, 2017

Work:

• Admin Panel (Static)
• Assign a list of runtimes to a member
• Assign a list of widgets to a runtime

TODO:

• Editing existing Runtimes/Widgets
• cleanup before proceeding

2nd Mar, 2017

Work:

• V2 Support/Debugging
• User PWA improvements
• Cleanup: Changed networking pattern 😎 Maybe a blog on it this/next weekend 🤔

3rd Mar, 2017

Work:

• V2 Support/Debugging
• Timelines for V3

[veris-neerajdhiman]

27th Feb, 2017

Done :

• Tree rebuild using celery task (rt now its scheduled weekly and is on sandbox 👀, Saturday midnight)
• Django Admin updates, enhanced View/Filter/Search for models, enjoy @veris-st

In-Process :

• Notification Manager : One can Turn OFF/Proxy any notification from here. By default all notifications are ON.

28th Feb, 2017

Done :

• Tree rebuild Celery job scheduled on live.
• Notification Manager (Proxy Related settings & Proper Testing pending )

ToDo:

• Store QR as image and access IT from shorten url

1st March, 2017

Done :

• Store QR as image.
• Script for making QR image of their Veris Badges.

In Process :

• Member Contact merge in Members Uploading (Backend is Done, Portal Integration Remaining)
• Note : Contact merge in Members uploading is very risky So it will need regression testing 👉 @veris-st

2nd-3rd March, 2017

• Worked on Customer Support suggestions
• Fixed KPMG issues

[veris-amoghbanta]

27th Feb, 2017

Done:

• Making v2 web terminal responsive (added media queries) and limiting it's view to centre in case of big screens (laptops, etc.)

Working on:

• Bug fixes on web-terminal and bringing it on the same level with iOS terminal.

28th Feb, 2017

Done:

• Bug fixes on iOS terminal.
• Completed(ready for testing) and released web-terminal (is on the same level as iOS terminal) 🎉 🏆, will be giving it for testing to anshika and aditi (since ST is not here).

1st of March, 2017

• Release on iOS terminal (v1.2.5)
• fixes on web terminal
• Back to v3-client

2nd and 3rd of March

Done:

• Revamped maximum logic and structure of v2 iOS terminal.
• Tested new logics and structure like a 100 times.
• Added feedback and exception handling to every bloody possible event/element (image, button, meeting-with, just name it and it is there).
  
• Every thing now is super clear and super fast (ND and AP also optimized the performance of image upload API).
• Made a new release for same (1.3.0), a major release with lots of performance optimizations and all known bugs fixed (all means all).

Working on/To do:

• Finish off with all optimizations and fixes of web terminal ASAP and get back to v3 without distractions.

P.S.: Damn V2, good thing being "Spend whole night at office working" is down the bucket list (wanted it to be for v3 or RNE, not v2 😝 ).
P.S.S.: Office gets scary at night.

[veris-abhinavanand]

27th-28th FEB 2017

• User App web new release fulfilling @veris-st demands 😆
• Polymer country code picker component released country-picker 🏆

March 1

• User app web, more feature requests by aditi.mahajan@veris.in

March 2

• Figured how to use WSDL files (finally) 🤓
• Though those files are useless

March 3

• Bug fixes on user app web
• Bug fixes on react terminal (meeting with)