chore: add non-code files

Signed-off-by: Daniel Hu <tao.hu@merico.dev>

Author: daniel-hutao

.editorconfig

@@ -0,0 +1,17 @@
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{go,mod}]
+indent_style = tab
+
+[Makefile]
+indent_style = tab
+
+[*.md]
+max_line_length = off
+trim_trailing_whitespace = false

.gitattributes

@@ -0,0 +1,3 @@
+* text=auto eol=lf
+
+*.{png,jpg,jpeg,gif,webp,woff,woff2} binary

.gitignore

@@ -0,0 +1,21 @@
+# Mac OS X files
+.DS_Store
+
+# Binaries for programs and plugins
+*.exe
+*.dll
+*.so
+*.dylib
+
+# Test binary, build with `go test -c`
+*.test
+
+# Output of the go coverage tool, specifically when used with LiteIDE
+*.out
+
+# Project-local glide cache, RE: https://github.com/Masterminds/glide/issues/736
+.glide/
+
+# IDE
+.idea/
+.vscode/

.golangci.yml

@@ -0,0 +1,4 @@
+# options for analysis running
+run:
+  # timeout for analysis, e.g. 30s, 5m, default is 1m
+  timeout: 10m

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+## Conduct
+
+We are committed to providing a friendly, safe and welcoming environment for all, regardless of the level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristics.
+
+Please avoid using overtly sexual aliases or other nicknames that might detract from a friendly, safe, and welcoming environment for all.
+
+Please be kind and courteous. There’s no need to be mean or rude.
+
+Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.
+
+Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.
+
+We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term “harassment” as including the definition in the Citizen Code of Conduct; if you lack clarity about what might be included in that concept, please read their definition. In particular, we don’t tolerate behavior that excludes people in socially marginalized groups.
+
+Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please get in touch with one of the channel ops or any of the DevStream moderation team immediately. Whether you’re a regular contributor or a newcomer, we care about making this community a safe place for you, and we’ve got your back.
+
+Any spamming, trolling, flaming, baiting, or other attention-stealing behavior is not welcome.
+
+[Email The Moderation Team](mailto:tao.hu@merico.dev)
+
+## Moderation
+
+These are the policies for upholding our community’s standards of conduct. If you feel that a thread needs moderation, please get in touch with the DevStream moderation team.
+
+Remarks that violate the DevStream standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hostile manner.)
+
+Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.
+
+Moderators will first respond to such remarks with a warning.
+
+If the warning is unheeded, the user will be “kicked,” i.e., kicked out of the communication channel to cool off.
+
+If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded.
+
+Moderators may choose at their discretion to un-ban the user if it was the first offense, and they offer the offended party a genuine apology.
+
+If a moderator bans someone and you think it was unjustified, please take it up with that moderator or a different moderator in private. Complaints about bans in-channel are not allowed.
+
+Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others.
+
+In the DevStream community, we strive to go the extra step to look out for each other. Don’t just aim to be technically unimpeachable; try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they’re off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.
+
+And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could’ve communicated better - remember that it’s your responsibility to make your fellows comfortable. Everyone wants to get along, and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.
+
+The enforcement policies listed above apply to all official DevStream venues, including Discord channels and GitHub repository. 
+
+The DevStream code of conduct is adapted from the [Rust code of conduct](https://www.rust-lang.org/policies/code-of-conduct).

CONTRIBUTING.md

@@ -0,0 +1,12 @@
+# Contributing
+
+Welcome to DevStream!
+
+Thanks for contributing, and thanks for reading this doc before doing it!
+
+The [DevStream Docs website](https://docs.devstream.io) contains information about how to get started, how the community organizes, and more. See the followings for more details before you decide to contribute:
+
+- [Contributing Guide](https://docs.devstream.io/en/latest/contributing_guide/).
+- [Development Workflow](https://docs.devstream.io/en/latest/development/git-workflow/git-workflow/), and other docs under the "Developer Guide" section.
+
+Those guidelines, as the name suggests, are only guidelines, not rules. So, use your best judgment, and feel free to propose changes to the contribute/development docs.

GOVERNANCE.md

@@ -0,0 +1,52 @@
+# Project Governance
+
+## Values
+
+DevStream and its leadership embrace the following values:
+
+- Inclusivity: We innovate through different perspectives and skill sets, which can only be accomplished in a welcoming and respectful environment.
+
+- Insist on the Highest Standards: Contributors have relentlessly high standards — many people may think these standards are unreasonably high. Contributors are continually raising the bar and drive their teams to deliver high quality products, services, and processes. Contributors ensure that defects do not get sent down the line and that problems are fixed so they stay fixed.
+
+- Ownership: Contributors are owners. They think long term and don’t sacrifice long-term value for short-term results. They act on behalf of the entire community, beyond just their own. They never say "that’s not my job."
+
+- Participation: Responsibilities within the project are earned through participation, and there is a clear path up the contributor ladder into leadership positions.
+
+- Community over Product or Company: Sustaining and growing our community takes priority over shipping code or sponsors' organizational goals. Each contributor participates in the project as an individual.
+
+- Openness: Communication and decision-making happen in the open and is discoverable for future reference as much as possible. All discussions and work take place in public Slack channels and open repositories.
+
+- Fairness: All stakeholders have the opportunity to provide feedback and submit contributions, which will be considered on their merits.
+
+## Maintainers
+
+DevStream Maintainers have write access to the [DevStream GitHub repository](https://github.com/devstream-io/devstream). They can merge their patches or patches from others. The current maintainers can be found in [CODEOWNERS](./CODEOWNERS). Maintainers collectively manage the project's resources and contributors.
+
+This privilege is granted with some expectation of responsibility: maintainers are people who care about the DevStream project and want to help it grow and improve. A maintainer is not just someone who can make changes, but someone who has demonstrated their ability to collaborate with the team, get the most knowledgeable people to review code and docs, contribute high-quality code, and follow through to fix issues (in code or tests).
+
+A maintainer is a contributor to the project's success and a citizen helping the project succeed.
+
+## Becoming a Maintainer
+
+See [here](https://docs.devstream.io/en/latest/contributor_ladder/#maintainer).
+
+## Meetings
+
+Time zones permitting, Maintainers are expected to participate in the public developer meeting, which is published [here](https://github.com/devstream-io/devstream/wiki).
+
+Maintainers will also have closed meetings to discuss security reports or Code of Conduct violations.  Such meetings should be scheduled by any Maintainer on receipt of a security issue or CoC report. All current Maintainers must be invited to such closed meetings, except for any Maintainer who is accused of a CoC violation.
+
+## CNCF Resources
+
+Any Maintainer may suggest a request for CNCF resources during a meeting. A simple majority of Maintainers approve the request.  The Maintainers may also choose to delegate working with the CNCF to non-Maintainer community members.
+
+## Code of Conduct
+
+[Code of Conduct](./CODE_OF_CONDUCT.md) violations by community members will be discussed and resolved during the private maintainer meeting. If the reported CoC violator is a Maintainer, the Maintainers will instead designate two Maintainers to work with CNCF staff in resolving the report.
+
+## Voting
+
+While most business in DevStream is conducted by "lazy consensus", periodically the Maintainers may need to vote on specific actions or changes. A vote can be taken during a community meeting or a private maintainer meeting for security or conduct matters. Any Maintainer may
+demand a vote be taken.
+
+Most votes require a simple majority of all Maintainers to succeed. Maintainers can be removed by a 2/3 majority vote of all Maintainers, and changes to this Governance require a 2/3 vote of all Maintainers.