Skip to content

Contribution Requirements Update #594

Open
@ryangurn

Description

@ryangurn

Can there please be clarification made in the contribution doc to explain the following items:

  1. Are there specific requirements that a repository contains tags/releases? Just one, or some arbitrary number of tags/releases?
  2. Do we want to require software being added has been “actively maintained”? What does it mean for a project to be “actively” maintained? Some commits here and there? Responding to issues? Closed PRs?
  3. Do we require code to exist in version control or just be accessible publicly?
  4. Do we want 4 months to add but 6-12 months before removal? Can we make that more explicit in the docs?
  5. What common sense items do we need to make more explicit? How do we make things explicit enough without preventing flexibility?

I have just been helping out a bit more with contributing to this project and gotten confused a couple times. There are good points brought up in issue and PR discussions that is not listed in the contribution doc, sometimes leading to confusion…

I am more than willing to update the docs, just wanted to start the conversation about what goes into the contribution.md file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    curationRemoval of abandoned projects, dead linksdiscussionGeneral discussion

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions