This survey is being used to collectively define the first three - four project by selecting them from several different categories. After (likely too long) waiting, we received 17 reponses that picked from the predefined set as shown on this image
and three additional topics
I prefer to have a documentation about Aurelia framework for example what are these and how are they work?
How to structure a large application, in general: infrastructure and patterns in order to give some guidelines and best practices.
From the initial 7 topics, applyingf the mean value criteria of survey’s results, we are going to handle the following three projects initiallu
- Aurelia CLI compendium
- Authentication / Authorization
- Full stack applications with Aurelia as front end
- Aurelia Typescript compendium
Additionally, from the set of the three additionally defined topics, the offer 1 (
documentation about Aurelia framework) clearly does not belong to AUCS scope - such document belongs to Aurelia proper and we do not want to further dilute our efforts, by doing “core team work” (nor would they be happy to see us do this). After all the attempts to define what is AUCS task I clearly failed in doing that .
Offers 2. and 3. are basically the same (3. was mine, so I I can say that it perfectly fits offer 2, so I would like to add this even if we do not find too many folks that would like to register themselves as the team for that project (I will post the survey for that registration early next week)
I will create the actual repositories next, with enough initial information about these projects that we can start the design and implementation plans within the context of GitHib.
Any questions / comments?