Skip to content

Fundamental principles that the charter authors deemed important but didn't make it in the text due to the status of the community at the time of writing. #33

@smoia

Description

@smoia

This issue is meant to not loose track of principles that were deemed important by the authors of the charter, but were excluded from it due to a (hopefully) transitory status of the community.

Please feel free to add!

  • Steering committee roles should rotate after a defined amount of time, with a matching time of embargo post-role
    • We did not include this principle due to the small size of the community
    • As soon as the community is big enough (e.g. 15 active people), this principle should be activated
  • There should always be at least two seats for every section of the community in the steering committee
    • We did not enforce this principle due to the downscaling of software development, thus leading to only one development seat
    • If software development becomes active again, this principle should be activated
  • There should always be a community manager in training in the steering committee
    • We did not enforce this principle due to the lack of interest in the position, adopting instead two co-community managers
    • As soon as interest for this position arises, this should be taken into account.

Metadata

Metadata

Assignees

No one assigned

    Labels

    DiscussionDiscussion of a concept or implementation. Need to stay always open.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions