1) User feedback: we agreed that is needed to orient the UI/UX redesign effort. Going full trymyui way seems too costly for the first attemp.
It wasn't exaclty concretly agreed as a next step, but I think that we should start a thread in the forum to get this rolling right away.
2) Releases: once some basic functionality is integrated we should aim for early alpha releases with prebuilt packages, to get more user feedback
Alistair suggested a rolling release, being lean and releasing value where possible and in as small chunks as we can, so as to make the feedback/response and impact of each change measurable.
3) General discussion, mainly for leveling on UCI/CBI current state.
4) Adrian suggests to develop the auto UCI/CBI approach, with partial releases focused on LUCI, but with three "envisioning" goals:
a- define LUCI views
b- use the UCI description file not only for LUCI but also as a helper to UCIfy the wrapping of packages configs into UCI. It'll require sepparate sh scripts development
c- use the description to automatically keep updated documentation in the wiki
5) It was agreed to switch from Angular Boostrap to Angular Material
6) Alastair suggested to change framework from angular 1 to TS + Angular2. It was agreed that first a stable code base continuing with Angular 1 should be met.
7) Jo stated that he would preferably take a step back (from UI web development) and assist with backend and lede integration topics
luci-hackers 17.01.09
@jow- @amharris @ianchi
1) User feedback: we agreed that is needed to orient the UI/UX redesign effort. Going full trymyui way seems too costly for the first attemp. It wasn't exaclty concretly agreed as a next step, but I think that we should start a thread in the forum to get this rolling right away.
2) Releases: once some basic functionality is integrated we should aim for early alpha releases with prebuilt packages, to get more user feedback Alistair suggested a rolling release, being lean and releasing value where possible and in as small chunks as we can, so as to make the feedback/response and impact of each change measurable.
3) General discussion, mainly for leveling on UCI/CBI current state.
4) Adrian suggests to develop the auto UCI/CBI approach, with partial releases focused on LUCI, but with three "envisioning" goals: a- define LUCI views b- use the UCI description file not only for LUCI but also as a helper to UCIfy the wrapping of packages configs into UCI. It'll require sepparate sh scripts development c- use the description to automatically keep updated documentation in the wiki
5) It was agreed to switch from Angular Boostrap to Angular Material
6) Alastair suggested to change framework from angular 1 to TS + Angular2. It was agreed that first a stable code base continuing with Angular 1 should be met.
7) Jo stated that he would preferably take a step back (from UI web development) and assist with backend and lede integration topics