Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drafting governance document #324

Merged
merged 17 commits into from
Aug 18, 2020
Merged

Drafting governance document #324

merged 17 commits into from
Aug 18, 2020

Conversation

mloning
Copy link
Contributor

@mloning mloning commented Jun 30, 2020

What does this implement/fix? Explain your changes.

Outlines and formalises how we want to run our community, including rights/responsibilities of contributors and decision making processes in case of deadlocks.

Governance for a unified time series analysis framework

To dos

  • create initial list of core devs, give access in alan-turing-institute/sktime and add to teams in sktime GitHub group
  • create code ownership file if desired
  • migrate enhancement proposal to new repo
  • migrate minutes/agendas to new repo

Resources

Comments

This is a first draft. Anyone is welcome to comment on it or propose changes.

@mloning mloning added the governance Governance and community management label Jun 30, 2020
Copy link
Collaborator

@fkiraly fkiraly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added some comments, for discussion.
Major thing to discuss is perhaps the "algorithm curation" issue.

GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.rst Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated

sktime is a meritocratic, consensus-based community project. Anyone with an interest in the project can join the community, contribute to the project, and participate in the governance process. This document describes how that participation takes place and how to set about earning merit within our community.

We are particularly motivated to support new and/or anxious collaborators, people who are looking to learn and develop their skills, and anyone who has experienced discrimination in the past.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while strictly speaking correct, the reference to discrimination is a bit unusual, since it reference negative experiences - so it carries a strange sub-vibe that we like community members to have had past negative experiences. Maybe "diversity" type phrasing is less awkward here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's the same in the CoC, but happy to replace it with other formulations, any ideas?

GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated

### Algorithm maintainer

Algorithm maintainers are contributors who have contributed an algorithm. They have the same voting rights as core developers with regard to their algorithm.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we define algorithm? This could also be an interface to an external package, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if that's necessary, they're intended to be guidelines, not rules.

GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
@mloning
Copy link
Contributor Author

mloning commented Aug 17, 2020

Thanks for the review @fkiraly! Pushed new changes in line with your comments.

@mloning
Copy link
Contributor Author

mloning commented Aug 18, 2020

Reviewed and agreed in community-council meeting: https://github.com/sktime/community-council/blob/master/previous_meetings/20200817-meeting.md

@mloning mloning merged commit e181f18 into master Aug 18, 2020
@mloning mloning deleted the governance branch August 19, 2020 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
governance Governance and community management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants