Nginx 已迁移至 GitHub Nginx has moved to GitHub

原始链接: https://mailman.nginx.org/pipermail/nginx-announce/2024/ITL3AOQSAJANFJXMM3VOVOIGOUADWFFK.html

NGINX 已转向 GitHub 进行开源项目管理。 这意味着开发人员现在可以使用 GitHub 上的拉取请求来贡献代码更改,而不是之前使用 Mercurial 的方法。 此外,错误报告、功能建议和改进可以直接在平台上的“问题”部分下进行。 社区论坛也已迁移至 GitHub 的“讨论”区域。 对于报告安全问题,建议遵循此处 [4] 之前建立的安全策略。 为了适应此转换期间的任何潜在困难,现有的补丁提交和通过邮件列表提供的社区援助将持续到 2024 年底。这些更新旨在简化、升级和扩大 NGINX 开发和相关社区的可访问性。 作为其持续致力于培育活跃的开源社区的一部分,本博客文章 [5] 分享了有关这些开发的更多详细信息。 该团队期待着从用户那里获得协作工作、互动和宝贵的见解。 参考: [1] [2] [3] [4] [5]

NGINX has transitioned to GitHub for its open-source project management. This means developers can now contribute code changes using pull requests on GitHub instead of the previous method, which used Mercurial. In addition, bug reports, feature suggestions, and improvements can be made directly on the platform, under the "Issues" section. The community forum has also been relocated to GitHub's "Discussions" area. For reporting security issues, it is recommended to follow the previously established security policy found here [4]. To accommodate any potential difficulties during this changeover period, existing patch submissions and community assistance via mailing lists will remain available until the end of 2024. These updates aim to streamline, upgrade, and widen accessibility for NGINX development and related communities. As part of its ongoing dedication to fostering an active open-source community, more details regarding these developments were shared in this blog post [5]. The team looks forward to receiving collaborative work, interactions, and valuable insights from users moving ahead. References: [1] [2] [3] [4] [5]


[nginx-announce] NGINX has moved to Github! Roman Arutyunyan arut at nginx.com
Fri Sep 6 15:11:21 UTC 2024
Hello from NGINX!

Today we're thrilled to announce that the official NGINX Open Source development
repository has moved from Mercurial to GitHub [1][2][3], where we will now start
accepting contributions in the form of Pull Requests. Additionally, starting
today, we will begin accepting bugs reports, feature requests and enhancements
directly through GitHub, under the "Issues" tab. Moreover, we've moved our
community forums to the GitHub "Discussions" area, where you will now be able
to engage in conversation, ask, and answer questions.

Important: to report a security vulnerability, please follow our security
policy [4].

We understand that changes like these may require adjustment, so to give you
more time, we will continue accepting patches and provide community support
via mailing lists until December 31st, 2024.

We believe these changes will serve to centralize, modernize and expand access
to NGINX development and communities. They represent our continued commitment
to open source, as outlined in the blog post [5]. Most of all, we can't wait to
see all of your contributions, discussions and feedback, as we move into this
next chapter for NGINX.

[1] https://github.com/nginx/nginx
[2] https://github.com/nginx/nginx-tests
[3] https://github.com/nginx/nginx.org
[4] https://github.com/nginx/nginx/blob/master/SECURITY.md
[5] https://www.f5.com/company/blog/nginx/meetup-recap-nginxs-commitments-to-the-open-source-community


On behalf of the NGINX Team,

Roman Arutyunyan
arut at nginx.com


More information about the nginx-announce mailing list
相关文章
联系我们 contact @ memedata.com