Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions .github/ISSUE_TEMPLATE/emeritus.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
name: Change Emeritus Steering Status
description: Use this form to request moving a member to/from Emeritus Steering status.
title: '[Emeritus Steering Status]: '

body:
- type: markdown
attributes:
value: |
## Change Emeritus Steering Status

Use this form to request moving a member to/from Emeritus Steering status.

> [!NOTE]
> To learn more about Emeritus status, please see [Emeritus Steering in Conda Governance](https://github.com/conda/governance#emeritus-steering).

- type: input
id: username
attributes:
label: GitHub Username
description: The GitHub username of the person to move to/from Emeritus Steering.
validations:
required: true

- type: dropdown
id: status_change
attributes:
label: Status Change Type
description: Select the type of status change being requested.
options:
- Steering Concil → Emeritus Steering
- Emeritus Steering → Steering Council
validations:
required: true

- type: textarea
id: reason
attributes:
label: Reason for Status Change
description: Provide a clear explanation for this status change request.
validations:
required: true
12 changes: 11 additions & 1 deletion .github/ISSUE_TEMPLATE/new_team.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,13 @@ body:
- type: markdown
attributes:
value: |
## Basic Information
## New Sub-team/Project Team

Use this form to request a new sub-team or project team.

> [!NOTE]
> To learn more about the different types of teams and their charters, please see [Teams & Roles in Conda Governance](https://github.com/conda/governance#teams--roles).

- type: dropdown
id: type
attributes:
Expand All @@ -19,20 +23,23 @@ body:
- Project Team
validations:
required: true

- type: input
id: name
attributes:
label: Team Name
description: Provide the name of the new sub-team or project team.
validations:
required: true

- type: input
id: handle
attributes:
label: Team Handle
description: Provide the handle of the new sub-team or project team.
validations:
required: true

- type: textarea
id: members
attributes:
Expand All @@ -45,16 +52,19 @@ body:
attributes:
value: |
## Charter and Responsibilities

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I am not sure an issue would be the best place to add the charter of new teams.
Maybe as an intake but charters IMO should be in a more permanently visible location like and MD document in the governance repo.
Would that be the expectation? Open an issue for discussion/approval then add the charter?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

If we adopt something like #147 then yes, replacing this issue forms with a yaml template to edit in a PR makes sense. I see this as a stopgap until we've figured out how to formally document the teams.


- type: textarea
id: charter
attributes:
label: Charter
description: Provide the charter for the new sub-team or project team.

- type: textarea
id: responsibilities
attributes:
label: Responsibilities
description: Outline the responsibilities and work areas of the new sub-team or project team.

- type: textarea
id: scope
attributes:
Expand Down
38 changes: 38 additions & 0 deletions .github/ISSUE_TEMPLATE/steering.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
name: Steering Council Nomination
description: Use this form to nominate yourself or others to the Steering Council.
title: '[Steering Council Nomination]: '

body:
- type: markdown
attributes:
value: |
## Steering Council Nomination

Use this form to nominate a new member to the Steering Council (including self-nominations).

> [!NOTE]
> To learn more about the Steering Council, its membership requirements and responsibilities, please see [Steering Council in Conda Governance](https://github.com/conda/governance#steering-council)/.

- type: input
id: username
attributes:
label: GitHub Username
description: The GitHub username of the person being nominated.
validations:
required: true

- type: input
id: funder
attributes:
label: Funder
description: The name of the organization or funder that supports the nominee. Review Steering Council's [shared funding membership restrictions](https://github.com/conda/governance#shared-funding-membership-restrictions).
validations:
required: true

- type: textarea
id: qualifications
attributes:
label: Qualifications & Contributions
description: Describe the nominee's contributions to the conda ecosystem and qualifications for the Steering Council.
validations:
required: true
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ We deeply appreciate all good faith contributions.

## Quick Links

- [Steering Council Nomination](https://github.com/conda/governance/issues/new?template=steering.yml)
- [Change Emeritus Steering Status](https://github.com/conda/governance/issues/new?template=emeritus.yml)
- [New Sub-team/Project Team](https://github.com/conda/governance/issues/new?template=new_team.yml)

## Code of Conduct
Expand Down