code of conduct
This commit is contained in:
parent
47390e2c9b
commit
aea1923caf
@ -20,6 +20,8 @@ For more details on how we prioritize and process feedback, please see our [Proc
|
||||
|
||||
To learn how to contribute to this project through pull requests, please refer to our [Contribution Guide](process/contribute.md).
|
||||
|
||||
We value a respectful and inclusive community. Please review our [Code of Conduct](process/code_of_conduct.md) to understand our community values and expectations.
|
||||
|
||||
## Contributing
|
||||
|
||||
We welcome contributions and feedback from all community members. Please feel free to open issues, comment on existing ones, or submit proposals through the appropriate channels.
|
||||
|
@ -0,0 +1,23 @@
|
||||
> NOT CLEAR NEED MORE THINKING & INFO
|
||||
|
||||
# Proposition
|
||||
|
||||
DAO Revenues: Farming + Public Staking Vault Revenues
|
||||
1. A % of POU revenues go to the vault wallet (e.g. 10%)
|
||||
2. Vault revenues are distributed to the DAO voters after each complete quarter (e.g. 4 times per year)
|
||||
|
||||
|
||||
# References
|
||||
|
||||
Part of the community brainstorm to improve the 3.0 decentralized grid.
|
||||
|
||||
https://threefold.info/tfgrid3/tfgrid3/gep_comm_brainstorm.html
|
||||
|
||||
# Related Issue
|
||||
|
||||
- farmers staking vault: #41
|
||||
- public staking vault: #42
|
||||
|
||||
# Notes
|
||||
|
||||
Previously here: https://git.ourworld.tf/tfgrid/circle_engineering/issues/43
|
53
ideas_not_ready/internal_node_hosting.md
Normal file
53
ideas_not_ready/internal_node_hosting.md
Normal file
@ -0,0 +1,53 @@
|
||||
# Idea
|
||||
|
||||
We should have a program that everyone working at TF has and runs a 3node. If everyone at TF knows how to run a node, it means it's simple enough for the crowd. And we practice what we preach.
|
||||
|
||||
# Benefits
|
||||
|
||||
This would mean the whole TF team knows inside-out our products and we are truly decentralized.
|
||||
|
||||
# TF Closed Network
|
||||
|
||||
We would have 3Nodes of all team members create a private TF network
|
||||
|
||||
We can use the new Mycelium function that creates encrypted safe network between nodes to implement a closed-circuit encrypted network of all TF nodes.
|
||||
|
||||
# Grants?
|
||||
|
||||
TF members/employees can do DIY or we send them certified node. This could be part of the grant program.
|
||||
|
||||
# Think Big
|
||||
|
||||
Once we should how to be 100% decentralized & autonomous as a single community-based entity (ThreeFold), we can show this to other entities (enterprises, corporations, depin organization, etc.).
|
||||
|
||||
# Phases
|
||||
|
||||
We see different phases and where this could go
|
||||
|
||||
- Phase 0: We already have at least +5 team members who have nodes
|
||||
- Phase 1: grant for everyone in team to have diy or certified node
|
||||
- Phase 2: mycelium private network between nodes
|
||||
- Phase 3: Communal nextcloud (or other?) complete web suite (to replace gdrive), CI/CD, AI bots, git hosting all on private grid.
|
||||
- Phase 4: Synthesis of all procedures and documentation to achieve this
|
||||
- Phase 5: Commercial service offering: can implement our system to any IT/web enterprises so they go fully decentralized
|
||||
|
||||
# Final Outcome
|
||||
|
||||
Any enterprise can have a private network of a complete Internet web suite (all apps, data never lost, never corrupted, etc.) built for them and they can host the servers themselves at different locations (e.g. each employee has a node at their home, together the nodes are the enterprise's private network ran on mycelium).
|
||||
|
||||
# Link with 99.9% Uptime Project
|
||||
|
||||
We use the grid ourselves as an entity so we try first hand what organizations will experience by using our services.
|
||||
|
||||
If we have issues we go through the same route an external entity would use (e.g. alerta.io, etc.) and fix the issues. This makes us understand well our escalation matrix and make sure we are able to answer any queries.
|
||||
|
||||
The whole ecosystem is of two parts in that case:
|
||||
|
||||
- Client
|
||||
- TF as an entity using the grid (private network of nodes)
|
||||
- Cloud
|
||||
- TF as a cloud provider offering the services to the TF as an entity part
|
||||
|
||||
Once we know inside out how to do client-cloud relationship + work, we can offer this to any entity out there:
|
||||
|
||||
> Own and grow your own Internet private network for your company/organization/entity
|
88
process/code_of_conduct.md
Normal file
88
process/code_of_conduct.md
Normal file
@ -0,0 +1,88 @@
|
||||
# TFGrid3 Community Code of Conduct
|
||||
|
||||
This document outlines the values and principles that guide our community interactions and collaborations.
|
||||
|
||||
## Our Community Values
|
||||
|
||||
### Mutual Respect
|
||||
|
||||
We are committed to providing a friendly, safe, and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.
|
||||
|
||||
### Planet People First
|
||||
|
||||
We identify as "a Planet People first community" - individuals who prioritize the well-being of our planet and its inhabitants above all else. This means:
|
||||
|
||||
- We make decisions with consideration for their environmental impact
|
||||
- We value sustainable solutions and long-term thinking
|
||||
- We recognize our responsibility as stewards of technology to create systems that benefit the planet and humanity
|
||||
- We understand that our work has real-world implications beyond code and infrastructure
|
||||
|
||||
### Positive Attitude
|
||||
|
||||
We maintain a positive outlook and constructive approach, even when facing challenges:
|
||||
|
||||
- We view problems as opportunities for improvement
|
||||
- We focus on solutions rather than dwelling on difficulties
|
||||
- We support each other through setbacks
|
||||
- We celebrate progress and achievements, both large and small
|
||||
|
||||
### Human Connections
|
||||
|
||||
We value human connections and relationships within our community:
|
||||
|
||||
- We prefer to collaborate with people we know and and can be open to
|
||||
- We encourage contributors to build genuine relationships with team members
|
||||
- We believe that strong human connections lead to better collaboration and outcomes
|
||||
- **While we welcome all contributions, we prioritize building a community where members know each other** and don't have to hide.
|
||||
|
||||
### Transparency and Free Speech
|
||||
|
||||
We believe in:
|
||||
|
||||
- Open and honest communication
|
||||
- Transparency in decision-making processes
|
||||
- The right to express opinions freely
|
||||
- The responsibility to use that freedom respectfully and constructively
|
||||
- Balancing transparency with sensitivity to different perspectives and experiences
|
||||
|
||||
### Diversity and Safety
|
||||
|
||||
We recognize and celebrate that:
|
||||
|
||||
- Everyone is different and brings unique perspectives and strengths
|
||||
- Different people have different needs to feel safe and comfortable
|
||||
- Some community members, including many engineers, may be sensitive to harsh or confrontational communication
|
||||
- Creating an inclusive environment means adapting our communication styles to ensure everyone can participate fully
|
||||
|
||||
## Expected Behavior
|
||||
|
||||
- Use welcoming and inclusive language
|
||||
- Be respectful of differing viewpoints and experiences
|
||||
- Gracefully accept constructive criticism
|
||||
- Focus on what is best for the community
|
||||
- Show empathy towards other community members
|
||||
- Communicate openly and thoughtfully
|
||||
|
||||
## Unacceptable Behavior
|
||||
|
||||
- The use of sexualized language or imagery and unwelcome sexual attention or advances
|
||||
- Trolling, insulting/derogatory comments, and personal or political attacks
|
||||
- Public or private harassment
|
||||
- Publishing others' private information without explicit permission
|
||||
- Other conduct which could reasonably be considered inappropriate in a professional setting
|
||||
|
||||
## Enforcement
|
||||
|
||||
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior. They will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
|
||||
|
||||
## Reporting
|
||||
|
||||
If you experience or witness unacceptable behavior, or have any other concerns, please report it by contacting the project team. All complaints will be reviewed and investigated promptly and fairly.
|
||||
|
||||
## Attribution
|
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html, with additional elements specific to our community values.
|
||||
|
||||
---
|
||||
|
||||
By participating in our community, you agree to abide by this code of conduct and uphold our values in all community spaces, both online and offline.
|
Loading…
Reference in New Issue
Block a user