Archived
15
23
Fork
You've already forked meta
6

Offering to lead the decision about Forgejo's license #198

Open
opened 2023年03月18日 11:56:32 +01:00 by fr33domlover · 3 comments
Contributor
Copy link

Situation

There have been very long discussions about relicensing Forgejo:

Many thoughts, opinions, points of view, and tensions.

Does anyone among the Forgejo developers have an intuition about how to proceed?

If not, here's my proposal offering to help move this decision forward.

Question

Which license model for Forgejo would most serve the project's purpose and values, now and in foreseeable future?

Proposal

Gather a small group of trusted people, who will design and execute a process for the community to decide about the license. This small group will figure out a way to move forward, based on the discussions that happened so far.

I will be the default facilitator of this group's meetings.

Time commitment: 3 weekly audio/video meetings of 90 minutes each (we'll pick weekday and hour once the group is gathered

Group size: Best is 3-4 people (including me), we can have more if we struggle to find 3-4 people that everyone trusts with this

I'd like to have in this small trusted group:

  • At least 1 person who's a core contributor of tech/code to Forgejo
  • At least 1 person who's familiar with Free Software license options and their impacts and cares about this topic
  • At least 1 person who deeply cares about this project and its future, someone investing time and energy in it
  • At least 1 person who has participated in the discussions and has a sense of the various concerns about the various options
  • At least 2 people with strong opposite opinions
  • At least 1 person who isn't triggered by the licensing question, who is able to see the various concerns and support distilling them into a non-controversial summary

How to self-assess whether to be in the small group:

  • You match at least one of the criteria I just listed, and/or you're passionate about the licensing decision
  • You're motivated and able to meet via audio/video (or using Jitsi's text chat, if you think it can work for you and still support the group's efficiency)
  • You're willing to do this in service of the project, i.e. the focus is on hearing the various concerns and opinions in the community and finding a path forward, rather than just expressing your own voice and opinions
  • You're interested in practicing leadership and developing a leadership mindset and skill, i.e. seeing the whole and creating the underlying conditions needed for the project to achieve its purpose

Once a group is gathered, we'll wait a bit to make sure everyone else (who is impacted by the license decision) approves the group and has time to raise concerns.

To clarify: This small group will NOT make the decision about the license. It will only figure out a PATH FORWARD to bring the decision to a conclusion.

Request

About approval/concern:

  • If you're comfortable with this proposal and approving it, react with 👍
  • If you have any concern, comment below
  • If you're a core contributor to Forgejo, participated in the license discussions, and you already see a clear path forward and consider this proposal unnecessary, please comment

About forming the small trusted group:

  • If you'd like to be in the small group (or willing, in connection with the project's purpose and its importance for you), please comment and briefly (1-2 senetences) explain why, based on the hints I wrote above (this is to help me make sure we create a diverse group with the various roles/skills/impacts covered)
  • If you believe there's someone else in the Forgejo team/community who should be in the group but hasn't yet offered themselves, please either @mention them or ask them on Matrix to consider being in the small group
# Situation There have been very long discussions about relicensing Forgejo: - https://codeberg.org/forgejo/meta/issues/86 - https://codeberg.org/forgejo/meta/issues/183 Many thoughts, opinions, points of view, and tensions. Does anyone among the Forgejo developers have an intuition about how to proceed? If not, here's my proposal offering to help move this decision forward. # Question Which license model for Forgejo would most serve the project's purpose and values, now and in foreseeable future? # Proposal Gather a small group of trusted people, who will design and execute a process for the community to decide about the license. This small group will figure out a way to move forward, based on the discussions that happened so far. I will be the default facilitator of this group's meetings. Time commitment: 3 weekly audio/video meetings of 90 minutes each (we'll pick weekday and hour once the group is gathered Group size: Best is 3-4 people (including me), we can have more if we struggle to find 3-4 people that everyone trusts with this I'd like to have in this small trusted group: - At least 1 person who's a core contributor of tech/code to Forgejo - At least 1 person who's familiar with Free Software license options and their impacts and cares about this topic - At least 1 person who deeply cares about this project and its future, someone investing time and energy in it - At least 1 person who has participated in the discussions and has a sense of the various concerns about the various options - At least 2 people with strong opposite opinions - At least 1 person who isn't triggered by the licensing question, who is able to see the various concerns and support distilling them into a non-controversial summary How to self-assess whether to be in the small group: - You match at least one of the criteria I just listed, and/or you're passionate about the licensing decision - You're motivated and able to meet via audio/video (or using Jitsi's text chat, if you think it can work for you and still support the group's efficiency) - You're willing to do this in *service* of the project, i.e. the focus is on *hearing the various concerns and opinions in the community* and finding a path forward, rather than just expressing your own voice and opinions - You're interested in practicing leadership and developing a leadership mindset and skill, i.e. seeing the whole and creating the underlying conditions needed for the project to achieve its purpose Once a group is gathered, we'll wait a bit to make sure everyone else (who is impacted by the license decision) approves the group and has time to raise concerns. To clarify: This small group will NOT make the decision about the license. It will only figure out a PATH FORWARD to bring the decision to a conclusion. # Request About approval/concern: - If you're **comfortable** with this proposal and approving it, react with 👍 - If you have any **concern**, comment below - If you're a core contributor to Forgejo, participated in the license discussions, and you already see a **clear path forward** and consider this proposal unnecessary, please comment About forming the small trusted group: - If you'd like to **be in the small group** (or willing, in connection with the project's purpose and its importance for you), please comment and briefly (1-2 senetences) explain why, based on the hints I wrote above (this is to help me make sure we create a diverse group with the various roles/skills/impacts covered) - If you believe there's **someone else** in the Forgejo team/community who should be in the group but hasn't yet offered themselves, please either @mention them or ask them on Matrix to consider being in the small group
Author
Contributor
Copy link

I'm proposing myself (relatively not triggered by the licensing question, able to see the various concerns and support distilling them into a non-controversial summary).

Also encouraging the following people to consider being in the small group (because I've noticed their participation in Forgejo): @crystal @dachary @earl-warren @fnetX @Ryuno-Ki

I'm proposing myself (relatively not triggered by the licensing question, able to see the various concerns and support distilling them into a non-controversial summary). Also encouraging the following people to consider being in the small group (because I've noticed their participation in Forgejo): @crystal @dachary @earl-warren @fnetX @Ryuno-Ki

Can we move this to https://codeberg.org/forgejo/discussions please?

Can we move this to https://codeberg.org/forgejo/discussions please?
Owner
Copy link

I am available to have some eye on the process, to conduct interviews and help out where I can, but I cannot do the commitment fr33domlover explains, and I completely trust them with this task. I see that the debate is heated, and that some people who push for a certain option try to move as quickly as possible and don't show much respect to opposite opinions, so I see the need for mediation.

Self-assesment of the criteria
  • no: core contributor of tech/code to Forgejo
  • no: familiar with Free Software license options and their impacts
    • partly: cares about this topic
  • yes: deeply cares about this project and its future, someone investing time and energy in it
  • partly (I think I understand the concerns involved): participated in the discussions and has a sense of the various concerns about the various options
  • yes (I have a small bias, but I can perfectly live with both options): not triggered by the licensing question, who is able to see the various concerns and support distilling them into a non-controversial summary
I am available to have some eye on the process, to conduct interviews and help out where I can, but I cannot do the commitment fr33domlover explains, and I completely trust them with this task. I see that the debate is heated, and that some people who push for a certain option try to move as quickly as possible and don't show much respect to opposite opinions, so I see the need for mediation. <details><summary>Self-assesment of the criteria</summary> - no: core contributor of tech/code to Forgejo - no: familiar with Free Software license options and their impacts - partly: cares about this topic - yes: deeply cares about this project and its future, someone investing time and energy in it - partly (I think I understand the concerns involved): participated in the discussions and has a sense of the various concerns about the various options - yes (I have a small bias, but I can perfectly live with both options): not triggered by the licensing question, who is able to see the various concerns and support distilling them into a non-controversial summary </details>
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
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
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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#198
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "%!s()"

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?