Skip to content

Process Documentation: Nivenly, project, trade, and community working relationships #27

@quintessence

Description

@quintessence

What Nivenly:

  • Promises to projects
  • Promises to community
  • Promises to trade orgs

What projects:

  • Promise to Nivenly
  • Promise to community
  • Promises to trade orgs

What trade orgs:

  • Promise to Nivenly
  • Promise to community
  • Promise to projects

What community / general members:

  • Promise to Nivenly
  • Promise to projects
  • Promise to trade orgs

The scope of this is an ethos to state how all each of the above promise to work with each others. For example, community and trade orgs can promise to give constructive criticism to projects relevant to each of their domains (no trolling, combative, etc. behavior). This would mean that:

  • Nivenly promises to respond to requests for information in a timely manner -> In scope ✅
  • Nivenly promises to provide governance support -> Out of scope ❌ (it's true, just not this document)
  • Trade orgs promise to provide relevant feedback from their perspective, needs -> In scope ✅
  • Trade orgs are financial sponsors of Nivenly and/or individual projects -> Out of scope ❌ (it's true, just not this document)

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type
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