Skip to main content

欢迎贡献者

¥Welcome Contributors

你好！感谢你有兴趣为 LangChain 做出贡献。作为一个快速发展字段的开源项目，我们非常乐于接受贡献，无论它们涉及新功能、改进的基础架构、更好的文档还是错误修复。

¥Hi there! Thank you for even being interested in contributing to LangChain. As an open-source project in a rapidly developing field, we are extremely open to contributions, whether they involve new features, improved infrastructure, better documentation, or bug fixes.

🗺️ 指南​

¥🗺️ Guidelines

👩‍💻 贡献方式​

¥👩‍💻 Ways to contribute

有很多方法可以为 LangChain 做出贡献。以下是一些常见的贡献方式：

¥There are many ways to contribute to LangChain. Here are some common ways people contribute:

  • 文档：帮助改进我们的文档，包括本文档！

    ¥Documentation: Help improve our docs, including this one!

  • 代码：帮助我们编写代码、修复错误或改进我们的基础架构。

    ¥Code: Help us write code, fix bugs, or improve our infrastructure.

  • 集成：帮助我们与你喜欢的供应商和工具集成。

    ¥Integrations: Help us integrate with your favorite vendors and tools.

  • 讨论：帮助解答使用问题并与用户讨论问题。

    ¥Discussions: Help answer usage questions and discuss issues with users.

🚩 GitHub 问题​

¥🚩 GitHub Issues

我们的 issues 页面会及时更新错误、改进和功能请求。

¥Our issues page is kept up to date with bugs, improvements, and feature requests.

有一个标签分类法，可帮助你对感兴趣的问题进行排序和发现。请使用这些信息来帮助整理问题。

¥There is a taxonomy of labels to help with sorting and discovery of issues of interest. Please use these to help organize issues.

如果你开始处理某个问题，请将其分配给自己。

¥If you start working on an issue, please assign it to yourself.

如果你要添加问题，请尽量将其集中在单个模块化的错误/改进/功能上。如果两个问题相关或阻塞，请将它们链接起来，而不是合并它们。

¥If you are adding an issue, please try to keep it focused on a single, modular bug/improvement/feature. If two issues are related, or blocking, please link them rather than combining them.

我们将尽力使这些问题保持最新，尽管随着该字段的快速发展，有些问题可能会过时。如果你发现这种情况，请告知我们。

¥We will try to keep these issues as up-to-date as possible, though with the rapid rate of development in this field some may get out of date. If you notice this happening, please let us know.

💭 GitHub 讨论区​

¥💭 GitHub Discussions

我们有一个 discussions 页面，用户可以在其中提出使用问题、讨论设计决策并提出新功能建议。

¥We have a discussions page where users can ask usage questions, discuss design decisions, and propose new features.

如果你能够帮助解答问题，请尽管回答！这将使维护人员能够将更多时间专注于开发和错误修复。

¥If you are able to help answer questions, please do so! This will allow the maintainers to spend more time focused on development and bug fixing.

🙋 获取帮助​

¥🙋 Getting Help

我们的目标是尽可能简化开发者设置。如果你在设置过程中遇到任何困难，请联系维护人员！我们不仅希望帮助你解除封锁，还希望确保未来贡献者的流程顺畅。

¥Our goal is to have the simplest developer setup possible. Should you experience any difficulty getting setup, please contact a maintainer! Not only do we want to help get you unblocked, but we also want to make sure that the process is smooth for future contributors.

同样，我们在代码库中强制执行某些 linting、格式化和文档标准。如果你发现这些操作困难（甚至令人厌烦），请随时联系维护人员寻求帮助。 - 我们不希望这些阻碍我们把好的代码添加到代码库中。

¥In a similar vein, we do enforce certain linting, formatting, and documentation standards in the codebase. If you are finding these difficult (or even just annoying) to work with, feel free to contact a maintainer for help - we do not want these to get in the way of getting good code into the codebase.

🌟 识别

¥🌟 Recognition

如果你的贡献已进入发布版本，我们将在 Twitter 上给予你荣誉（但前提是你愿意）！如果你有 Twitter 账户希望我们提及，请在 PR 中或其他方式告知我们。

¥If your contribution has made its way into a release, we will want to give you credit on Twitter (only if you want though)! If you have a Twitter account you would like us to mention, please let us know in the PR or through another means.