Skip to content

Who should have direct write access / how do we handle pull requests? #9

Description

@d70-t

From my point of understanding, there are basically two opposing forces on how to manage write access to this repository. First, the metadata repository should be sourced by the EUREC4A community, so everyone should be able to contribute and edit the repository. On the other hand, the data should be used by many people so any changes should go at least through a small amount of review. This way, the chance of accidentally breaking other peoples scripts is reduced. This review could be provided through the discussion phase of a pull request.

This gives rise to the following questions:

  • should we use pull requests?
    • should we enforce the use of pull requests for every edit?
    • who should moderate / accept / reject pull requests?
  • who should have write access to the repository?

I would offer moderation for now, but most likely having only one person is not a good idea. Also having too many may lead to a chaotic experience.

What are your opinions on this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions