Atlantis

<@U0144ERR2QP> <@UFC8E63HA> <@U03KXV0RQLQ> <@U01R9NM2SFR>

I'm not against it, this is great way to involve people more even if they aren't "coders"

we might need to have metrics to have insights for the real need :joy:

along with that issue, we can also probably create separate channels to identify the tractions

&gt; do we have metrics on our labels? 
do you refer to the label filter?

Rui is suggesting looking at this page

<https://github.com/runatlantis/atlantis/labels|https://github.com/runatlantis/atlantis/labels>

Heres an example of searching for all the gitlab prs and issues (provided they are properly labeled)

<https://github.com/runatlantis/atlantis/issues?q=+label%3Aprovider%2Fgitlab+|https://github.com/runatlantis/atlantis/issues?q=+label%3Aprovider%2Fgitlab+>

Should we have separated slack channels too?

#provider-gitlab
#provider-azuredevops
#provider-bitbucket

how many labels and how many channels? , I don't like much the too many channels idea if we are going to have very few posts per month

I think we should be careful to overdo it pre-maturely

we need to curate the people first and let them run with it

Then if that simply implies that we dont have too many contributions to deal with. In other words, we dont need that many maintainers.

I would suggest office hour might be a better idea.

Came here after reading the note and wanted to volunteer for gitlab support

Hi <@U050NUBM4HK> thank you for volunteering. Please comment on the <https://github.com/runatlantis/atlantis/issues/3202|issue> so we know who to contact for the next gitlab issue

For now please feel free to peruse the <https://github.com/runatlantis/atlantis/issues?q=is%3Aopen+is%3Aissue+label%3Aprovider%2Fgitlab+sort%3Areactions-%2B1-desc|current gitlab tickets ordered by up votes>