AUCS is created as a consequence of my very strong belief that:
a) Aurelia as a platform needs a lot of very well written guides, blogs, tutorials, code snippets , etc. all of which are
written by Aurelia developers for Aurelia developers.
b) Note that I am pointing out a strong difference between the Framework Developers and Application Developers, despite the fact that the intersection of these two classes is not empty. I spent about half of my life writing “system software” , including Operating Systems, System Drivers and Firmware and the other half writing applications where I will mention world first implementation of the patient centric web portal in partnership with Microsoft’s HealtVault team, some 14 years ago (citing as the evidence that I can speak with authority about the concept
written by Aurelia developers for Aurelia developers )
c) We need a team that is a lot larger than Aurelia’s core team in order to deliver a lot of very well written guides, blogs, tutorials, code snippets , etc. - and until now, we had a very few, some of them organized by @mobilemancer, other by @EisenbergEffect (both of which are also members of the framework aka core team).
d) In order to ensure the best possible outcome of AUCS, the community members will be asked to participate in all decisions (via surveys that will soon be added to our website (see next item below)
e) Our first deliverable - AUCS website, visually similar to the official Aurelia Website was first time deployed today, only 6 days after the realization that we ought to have it in order to publish our materials continuously and without interference with the core team (see next item below)
f) AUCS is completely independent from Aurelia proper and the core team although I am always sharing everything with @EisenbergEffect (most of the time after I already made the move ) . Such independence (read lack of the need to ask for permission to do something) is the only way to create what we plan to do, without overloading @EisenbergEffect with AUCS management tasks.
g) Most important part - AUCS website should be considered as the “aggregator and a transient station” between the Aurelia Community and Aurelia core team headed by @EisenbergEffect, meaning that it offers a data buffer content of which could be asynchronously moved to Aurelia proper website. To further facilitate this, all of our data is formatted as markdown files - AUCS website just provides structured interface to this data.
Using this summary, perhaps the details written in all related articles below might become more clear. I would really appreciate everyone’s feedback (in this Discourse tool, privately via Gitter or email (firstname.lastname@example.org), as the success of this “community movement” depends on clarity and enthusiasm.
- Get Aurelia Great (GAG - call for action) (at this point the bad acronym GAG got changed into AUCS).
- AUCS - proposal for the first task.
- AUCS - search for a good enough home
- AUCS - ready to make first few baby steps
- AUCS - getting close to a group start
- What in the world is the mission of AUCS
- AUCS surveys - please respond quickly
- AUCS results from the survey 1
- AUCS Survey #2 - Bios and roles