RSC Code Draft

[vrurg]

I open this issue for general matters related to the Code.

[vrurg]

Pure technical question: when we talk about core team voting, are there any platform we can use? GitHub doesn't seem to be the best on this task.

[lizmat]

I think for the election of the first proper RSC, we can ask someone like [Coke] to tally the votes by mail.

[rba]

While reading the Steering Council document I realised we have to do a step before:

Defining the current startup list of "core team" members.

In the github raku team (https://github.com/orgs/Raku/teams/raku) there are currently 169 members and then don't forget the members family https://github.com/MoarVM and https://github.com/rakudo

So the placeholder in the document "Raku" team on Github https://github.com/orgs/__ needs to be filled with something valuable befor annoucing.

I see different options to do this:

• Call the full list of three repository members for an election
• Check last two years commits
• Nominate active IRC people
• Start with problem-solving reviewers
• ...

The Swiss democratic style would be, to elect the core team by votes of all the community members. :-)

[vrurg]

For the first time I think the most straightforward approach is to be taken: the right to vote is given to anybody with commit bit in each org, and who contributed to a project over the span of the last year or two. I.e. the first two items of @rba list.

This rule has the primary advantage of simplicity to be understood and implemented. It would allow to to have things done fast, without extra talking.

For the next election the procedure can be polished further.

[lizmat]

I think this issue can be closed now?

[vrurg]

Do we consider the paper finalized? I planned to submit a few PRs today, but it seems to be too late.

[lizmat]

Let's see the PR's. I think that ultimately the people mentioned in the announcement can decide on accepting / rejecting them. At least until the actual voting starts?

[codesections]

Closing since the RSC has been elected.