Pre-RFC: Extend CoC to cover Conflict of Interest Disclosure and Rules

Open
#170 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the three questions in the RFC: conflicts to disclose, rules or guidelines, and how disclosures should be captured. Done means the Working Group has agreed on the scope and recorded the resulting policy or process; no source files or tests are identified in the issue.

Written by the indexing model from the issue text.

Description

RFC triage-2024-keep

As the market for embedded Rust expands, more developers involved with the Working Group will have a business interest in supporting and expanding the embedded Rust efforts.

At the current point, some members of the Embedded WG have personal or full time businesses focused on the embedded rust domain.

This RFC would aim to address the following topics:

  • What possible conflicts of interest must be disclosed, and to what extent, as being part of the embedded working group?
  • What rules or guidelines should be put in place, to avoid possible perception of conflict of interest?
  • How should these rules, guidelines, and/or disclosures be captured?
Dominant language
No language data
Stars
2.1k
Forks
116
No merged PRs in 30d

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.

More from rust-embedded/wg

All issues in rust-embedded/wg

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.