# AUCS getting even closer to get everyone engaged

**URL:** <https://discourse.aurelia.io/t/aucs-getting-even-closer-to-get-everyone-engaged/692>\
**Category:** Uncategorized\
**Created:** [January 24, 2018, 11:25pm UTC](https://discourse.aurelia.io/t/aucs-getting-even-closer-to-get-everyone-engaged/692 "2018-01-24T23:25:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![adriatic](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/adriatic/32/96_2.png) [@adriatic](https://discourse.aurelia.io/u/adriatic)\
**Post date:** [January 24, 2018, 11:25pm UTC](https://discourse.aurelia.io/t/aucs-getting-even-closer-to-get-everyone-engaged/692/1 "2018-01-24T23:25:11Z")

</div>

At some point in the very near future I would have to stop stating how we are almost there. So, let me explain what is still left to do for a few guys that were activated so far (on the infrastructure creation tasks)

- Make a few finishing touches on the **[portal application](https://aurelia-community.github.io/)**:

- collect the feedback from the first survey (that is something I cannot accelerate other than saying that those who do not respond until tomorrow will forfeit their chance to have an active vote on our first few project’s topic.

- create the second survey, where the first set of topics with most votes will be presented with the prompt to place yourselves in the team that will handle these topics.

- assign these teams to projects (this is completely GitHub based provisioning) and define the text initializing these project, very briefly. I am expecting that once this step is done each team will discuss the design and implementation of their task using the standard GitHub tools: issues, kanban projects and wikis). These details will be explained to some extent in my next discourse post, tomorrow.

Please do respond to the first survey at **[AUCS Topics survey #1, January 22, 2018](https://surveyhero.com/c/861faab3)** if you have not already