Archived
15
23
Fork
You've already forked meta
6

Turn VALUES.md into a full "community contract" MISSION.md #136

Merged
fr33domlover merged 1 commit from fr33domlover/forgejo-meta:mission into readme 2023年02月21日 07:51:05 +01:00
Contributor
Copy link

A common practice in projects is to start from a "mission", and from there derive a strategy and roadmap.

That sort of structure usually causes people to re-create the same problems they might be (or might not be) hoping to fix, because our frame of thinking is still within the current systems, dominated by power structures, capitalism, proprietary software, centralized services, etc.

I believe starting from the vision is a critical part of truly being able to move towards the world we want to see, and to be trusted by the community in a decentralized nonviolent governance/project/system where human interdependence determines what's possible to do, rather than money or fear of authority.

The stuff in the new MISSION.md file is therefore based on the Vision Mobilization framework, that very highly resonates with me and I very highly recommend, and contains (in addition to values, which we already had):

  • Vision: World we want to see (e.g. people freely collaborating on software and solving human problems and serving needs with it)
  • Purpose: Our part in getting there (e.g. create and maintain a software forge that allows that)
  • Mission: Our current top-level project towards the purpose (e.g. maintain Forgejo as a soft fork of Gitea with human-oriented governance and development practices)

From the mission we'll be deriving our roadmap.

I didn't fill in the vision/purpose/mission because it didn't feel right to suggest something myself. I'd like us to do this together :-) So left some "TODO" pieces where we'd put the actual content.

A common practice in projects is to start from a "mission", and from there derive a strategy and roadmap. That sort of structure usually causes people to re-create the same problems they might be (or might not be) hoping to fix, because our frame of thinking is still within the current systems, dominated by power structures, capitalism, proprietary software, centralized services, etc. I believe starting from the vision is a critical part of truly being able to move towards the world we want to see, and to be **trusted** by the community in a decentralized nonviolent governance/project/system where human interdependence determines what's possible to do, rather than money or fear of authority. The stuff in the new `MISSION.md` file is therefore based on the [Vision Mobilization](https://visionmobilisation.org) framework, that very highly resonates with me and I very highly recommend, and contains (in addition to values, which we already had): - Vision: World we want to see (e.g. people freely collaborating on software and solving human problems and serving needs with it) - Purpose: Our part in getting there (e.g. create and maintain a software forge that allows that) - Mission: Our current top-level project towards the purpose (e.g. maintain Forgejo as a soft fork of Gitea with human-oriented governance and development practices) From the mission we'll be deriving our **roadmap**. I didn't fill in the vision/purpose/mission because it didn't feel right to suggest something myself. I'd like us to do this together :-) So left some "TODO" pieces where we'd put the actual content.
Author
Contributor
Copy link

I suppose this also relates to #10, the issue about our roadmap.

I suppose this also relates to #10, the issue about our roadmap.
fsologureng changed title from (削除) Turn VALUES.md into a full "commmnity contract" MISSION.md (削除ここまで) to Turn VALUES.md into a full "community contract" MISSION.md 2023年01月27日 22:21:37 +01:00
Ghost approved these changes 2023年01月27日 23:16:04 +01:00
MISSION.md Outdated
@ -0,0 +42,4 @@
Mission is the overall kinds of action taken to bridge the gap between the
current reality and the vision; anchoring our purpose into action and tangibly
moving us towards vision. Mission is whats within our capacity to do that

replace this "right single quotation mark" with a regular apostrophe ' to clear the warning

replace this "right single quotation mark" `’` with a regular apostrophe `'` to clear the warning
Author
Contributor

Fixed 👍

Fixed 👍
fr33domlover marked this conversation as resolved
Contributor
Copy link

I agree with the change proposed, but apart from freedom of software and transparency already stated, I propose:

  • Privacy as a condition of human autonomy and self-governance

  • Accessibility as a condition of equality of opportunities and inclusion.

As far as I understand, both values has been part of an implicit agreement in the development, or at least not well documented.

I agree with the change proposed, but apart from freedom of software and transparency already stated, I propose: * Privacy as a condition of human autonomy and self-governance * Accessibility as a condition of equality of opportunities and inclusion. As far as I understand, both values has been part of an implicit agreement in the development, or at least not well documented.
Author
Contributor
Copy link

I agree with the change proposed, but apart from freedom of software and transparency already stated, I propose:

  • Privacy as a condition of human autonomy and self-governance

  • Accessibility as a condition of equality of opportunities and inclusion.

As far as I understand, both values has been part of an implicit agreement in the development, or at least not well documented.

@fsologureng, I opened #162 for this. Want to make a PR to add those values? Let's continue that in #162, I'm merging and closing here.

> I agree with the change proposed, but apart from freedom of software and transparency already stated, I propose: > > * Privacy as a condition of human autonomy and self-governance > > * Accessibility as a condition of equality of opportunities and inclusion. > > As far as I understand, both values has been part of an implicit agreement in the development, or at least not well documented. @fsologureng, I opened #162 for this. Want to make a PR to add those values? Let's continue that in #162, I'm merging and closing here.
Commenting is not possible because the repository is archived.
No reviewers
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/meta!136
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "fr33domlover/forgejo-meta:mission"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?