Q&A kick-off

[pattacini]

Q&A Kick-off.
Any idea about the name? Is QA ok?

cc @lornat75 @paulfitz @randaz81 @vtikha

[lornat75]

@drdanz do we need a specific team/group to allow people to post issues?

[alecive]

@lornat75 as far as I know, any github user can post an issue in any github public repository, so I would say no :)

[kt10aan]

I think "Support" is more self explanatory :)

Any github user can post an issue in any github public repository, however, for a user to set a label for that issue, he has to be in the "contributors" group.

[pattacini]

the ability of creating new labels should be put under strict control, indeed :)

[lornat75]

@alecive, @kt10aan noted in: d639cd5

[alecive]

@pattacini problem is that only the owners group can assign a label to an issues. e.g. I cannot assign any label to this issue even though I am both in the YARP developers and in the iCub developers group.

[drdanz]

@lornat75 confirming @alecive reply, any GitHub user can post issues on a public repository

[pattacini]

@alecive I think restraining to owners is ok indeed :)
Owners = Gang of Four

[alecive]

@pattacini it means that you guys have to manually label any new issue because anybody else cannot do that. It can become quite annoying after a while.
My point was that labeling is a powerful process, and it would be nice if issues were already labeled by the users, instead of being labeled by the contributors. But I don't think that we have another choice.

[pattacini]

new labels can be proposed and then, once they get accepted, attached to open issues; otherwise, it will soon become too wild.

[pattacini]

It seems this post has some information about the labeling issue:
https://groups.google.com/forum/#!topic/tardis-devel/6IQCFJxxROk

[alecive]

The quickest way would be to create another group, e.g. robotology-collaborators, gradually put everyone in it, and assign full admin access to that group on this repository (i.e. only robotology/QA). A bit risky, though it is a manageable risk.

[pattacini]

I've created the team qa-users with write-access to address the labeling issue; we need to populate it with users...

[drdanz]

In case we want to import issues from other repositories to the QA one, this is a nice tool: https://github.com/IQAndreas/github-issues-import