Skip to content

[Process RFC] Clarify Community Strategy Decision Process #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Hzfengsy merged 7 commits into from
Aug 25, 2023
Merged

[Process RFC] Clarify Community Strategy Decision Process #102

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
3340d95
[Process RFC] Clarify Community Strategy Decision Process
tqchen Aug 3, 2023
078aa9d
Update 0102-clarify-strategy-decision-process.md
tqchen Aug 3, 2023
c48f207
Update rfcs/0102-clarify-strategy-decision-process.md
tqchen Aug 3, 2023
a748eba
Include description of lazy 2/3 majority
tqchen Aug 3, 2023
a1d26e8
Update 0102-clarify-strategy-decision-process.md
tqchen Aug 4, 2023
21d140e
Update 0102-clarify-strategy-decision-process.md
tqchen Aug 4, 2023
d60925d
Finish
tqchen Aug 10, 2023
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
Prev Previous commit
Next Next commit
Update rfcs/0102-clarify-strategy-decision-process.md 
Co-authored-by: Chris Sullivan <csullivan@octoml.ai>
  • Loading branch information
@tqchen @csullivan
tqchen and csullivan authored Aug 3, 2023
commit c48f20719e5187c377d65ffd14890ffee2a38430
2 changes: 1 addition & 1 deletion rfcs/0102-clarify-strategy-decision-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ are strategy decision points about overall directions and new modules adoptions.
These decisions are not fine-grained code-level changes but are important for a
community to be viable in the long term.
The process of bringing those changes is less clarified to the community, and hurdles can be high.
We have made attempts in the past to bring more verbose processes in a less successful.
We have made attempts in the past to bring a more verbose processes, but this has proven to be less successful.
Comment thread
leandron marked this conversation as resolved.
Outdated
Copy link
Copy Markdown
Contributor

@leandron leandron Aug 8, 2023

Choose a reason for hiding this comment

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

Suggested change
We have made attempts in the past to bring a more verbose processes, but this has proven to be less successful.
We have made attempts in the past to bring a more verbose processes such as (please describe), but this has proven to be less successful due to (please expand)

One observation is that it is hard for broader volunteer developers and community members to follow complicated processes.
Comment thread
leandron marked this conversation as resolved.
Copy link
Copy Markdown
Contributor

@leandron leandron Aug 8, 2023

Choose a reason for hiding this comment

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

Suggested change
One observation is that it is hard for broader volunteer developers and community members to follow complicated processes.
One observation is that it is hard for broader volunteer developers and community members to follow complicated processes such as (please expand).

Copy link
Copy Markdown

@Johnson9009 Johnson9009 Aug 9, 2023

Choose a reason for hiding this comment

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

e.g. I can't spend too much time to read a long long discussion article, if a commercial company will do a decision like this way, it will loss all customers.

Additionally, different members can have different interpretations of how to do things,
leading to stagnation and lack of participation from volunteer members.
Expand Down