dotnet-foundation / dotnet-foundation/projects

.NET Foundation Project Archival Process - Input wanted

Open
#298 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
157
Forks
37
PR merge metrics
No merged PRs in 30d

Description

In the Project Committee meeting on July 13th, @sbwalker alerted everyone to the news that the .NET Foundation Board approved starting the Project Archival Process at the June Board Meeting.

".NET Foundation Project Membership is predicated upon a project maintaining its eligibility status, abiding by the code of conduct, and demonstrating continuous contributions via its public activity metrics (ie. code commits to their repository within the past 18 months). If a project fails to meet any of these requirements, the project maintainer will be notified so that they can return the project to good standing. If the project is still unable to meet its obligations, it will be archived. Archival means that the project will no longer be represented as an official Member Project and will no longer be eligible to receive Member Project benefits."

The committee members will start the work on defining what this means for projects that fall into this status and how it will work.
Feel free to leave any feedback or comments here if you are unable to attend the next meeting.

Idea on guidelines:
Projects that don't have any commits for 18 months
Archival process steps

The next meeting is scheduled for August 10th.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the issue body and the quoted .NET Foundation membership requirements. Define the archival guidelines and process steps for projects with no commits for 18 months, then use the resulting proposal as input for committee discussion.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.