<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>ReHLDS Blog</title>
        <link>https://rehlds.dev/zh-Hans/blog/</link>
        <description>ReHLDS Blog</description>
        <lastBuildDate>Thu, 12 Dec 2024 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>zh-Hans</language>
        <item>
            <title><![CDATA[Why You Shouldn't DM Developers]]></title>
            <link>https://rehlds.dev/zh-Hans/blog/2024/12/12/why-not-to-dm-developers/</link>
            <guid>https://rehlds.dev/zh-Hans/blog/2024/12/12/why-not-to-dm-developers/</guid>
            <pubDate>Thu, 12 Dec 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[Explanation of why direct messaging developers is not an effective way to solve problems in open-source projects.]]></description>
            <content:encoded><![CDATA[<p>Every day, open-source developers encounter questions and problems from users. But did you know that sending questions via direct message is far from the best way to get an answer? In reality, many issues are solved much faster and more efficiently when discussed in public channels. This applies to the ReHLDS project and many other open-source initiatives.</p>
<p>When you DM, the issue remains "in the shadows." Only you and the developer are aware of the problem. Posting a question or bug on GitHub Issues or GitHub Discussions allows not only the developer but also other community members to assist you in finding a solution. After all, the open-source community operates on the principles of mutual help and knowledge exchange. The more people involved in solving the issue, the quicker it will be resolved.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-post-on-github-not-dm">Why Post on GitHub, Not DM?<a href="https://rehlds.dev/zh-Hans/blog/2024/12/12/why-not-to-dm-developers/#why-post-on-github-not-dm" class="hash-link" aria-label="Why Post on GitHub, Not DM?的直接链接" title="Why Post on GitHub, Not DM?的直接链接" translate="no">​</a></h2>
<p>Developers are busy people. Every direct message response takes time away from tasks like fixing bugs, adding new features, or optimizing performance. While the developer spends time gathering information about your issue, other users could be offering a solution.</p>
<p>Why is this important?</p>
<ol>
<li class="">
<p><strong>Open discussions</strong>: When an issue or question becomes public, other users can share their solutions or suggestions. This fosters an active collaborative atmosphere.</p>
</li>
<li class="">
<p><strong>Public visibility</strong>: Everyone can see your question and help you find a solution, significantly increasing the chance of a quick resolution.</p>
</li>
<li class="">
<p><strong>Resource conservation</strong>: Developers' time is limited, and it should be focused on addressing larger and more complex issues, not resolving simple cases that could be handled in public spaces.</p>
</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-effectiveness-of-communication-in-open-source">The Effectiveness of Communication in Open Source<a href="https://rehlds.dev/zh-Hans/blog/2024/12/12/why-not-to-dm-developers/#the-effectiveness-of-communication-in-open-source" class="hash-link" aria-label="The Effectiveness of Communication in Open Source的直接链接" title="The Effectiveness of Communication in Open Source的直接链接" translate="no">​</a></h2>
<p>Platforms like GitHub Issues or Discussions are designed for users and developers to discuss projects and their issues. It's important to understand that end-users can't always objectively assess the scale of a problem. Sometimes, what seems like a critical bug may actually be a simple misunderstanding or installation error. This is why open discussions help all project participants assess the real importance of an issue and resolve it as quickly as possible.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-to-ask-questions-on-github">How to Ask Questions on GitHub<a href="https://rehlds.dev/zh-Hans/blog/2024/12/12/why-not-to-dm-developers/#how-to-ask-questions-on-github" class="hash-link" aria-label="How to Ask Questions on GitHub的直接链接" title="How to Ask Questions on GitHub的直接链接" translate="no">​</a></h2>
<ol>
<li class="">Be specific: Describe the steps that led to the error.</li>
<li class="">Provide context: Specify the system you're using and the versions involved.</li>
<li class="">Attach logs: This significantly speeds up diagnosis and issue resolution.</li>
</ol>
<p>Instead of DMing, create an issue with a detailed description of the problem. This will not only speed up the resolution but also help you avoid unnecessary waiting and uncertainty.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="contributing-to-the-project">Contributing to the Project<a href="https://rehlds.dev/zh-Hans/blog/2024/12/12/why-not-to-dm-developers/#contributing-to-the-project" class="hash-link" aria-label="Contributing to the Project的直接链接" title="Contributing to the Project的直接链接" translate="no">​</a></h2>
<p>Remember, every question or message in public channels, whether it's a discussion on GitHub or in a chat, is a contribution to the project's development. This is much more valued than just communicating via DMs. Public channels help create a community where knowledge and ideas are exchanged faster than they would be in private messages.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="resources">Resources<a href="https://rehlds.dev/zh-Hans/blog/2024/12/12/why-not-to-dm-developers/#resources" class="hash-link" aria-label="Resources的直接链接" title="Resources的直接链接" translate="no">​</a></h2>
<ul>
<li class=""><a href="https://github.com/ReHLDS/ReHLDS/issues" target="_blank" rel="noopener noreferrer" class="">GitHub Issues</a></li>
<li class=""><a href="https://github.com/orgs/rehlds/discussions" target="_blank" rel="noopener noreferrer" class="">GitHub Discussions</a></li>
<li class=""><a href="https://rehlds.dev/to/discord" target="_blank" rel="noopener noreferrer" class="">Discord Community</a></li>
<li class=""><a href="https://github.com/orgs/ReHLDS/projects" target="_blank" rel="noopener noreferrer" class="">GitHub Boards</a></li>
</ul>
<p>By creating issues, pull requests, or simply participating in discussions, you're already making an important contribution to the project's development. All discussions, bugs, and suggestions help not only you but also other community members, improving the project for everyone.</p>]]></content:encoded>
            <category>open source</category>
            <category>community building</category>
            <category>collaboration</category>
            <category>GitHub</category>
            <category>developer guidelines</category>
            <category>volunteer support</category>
            <category>problem solving</category>
        </item>
        <item>
            <title><![CDATA[Join the ReHLDS Community Managers Team]]></title>
            <link>https://rehlds.dev/zh-Hans/blog/2024/11/01/welcome/</link>
            <guid>https://rehlds.dev/zh-Hans/blog/2024/11/01/welcome/</guid>
            <pubDate>Fri, 01 Nov 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[The ReHLDS community is looking for passionate Community Managers to help create a welcoming environment for all members. Apply now to contribute to our growing community!]]></description>
            <content:encoded><![CDATA[<p>Our ReHLDS community is growing, and we’re on a mission to make it a more welcoming and engaging place for all members—whether they're new or seasoned contributors. To help support our goals, we’re looking for enthusiastic Community Managers who are passionate about making a positive impact.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-join-us">Why Join Us?<a href="https://rehlds.dev/zh-Hans/blog/2024/11/01/welcome/#why-join-us" class="hash-link" aria-label="Why Join Us?的直接链接" title="Why Join Us?的直接链接" translate="no">​</a></h2>
<p>As a Community Manager, you’ll play a crucial role in shaping the experience for users and developers in our community. From moderating discussions and helping newcomers to organizing resources and supporting content creation, you’ll have a variety of opportunities to contribute meaningfully.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-youll-do">What You’ll Do<a href="https://rehlds.dev/zh-Hans/blog/2024/11/01/welcome/#what-youll-do" class="hash-link" aria-label="What You’ll Do的直接链接" title="What You’ll Do的直接链接" translate="no">​</a></h2>
<p>We have a <a href="https://github.com/orgs/rehlds/projects/1/views/1" target="_blank" rel="noopener noreferrer" class="">🤝 Community &amp; UX Initiatives</a> with a list of tasks and community priorities that our team will be focusing on. You’ll be encouraged to select tasks that interest you most or propose ideas that align with our goals.</p>
<p><strong>Key Responsibilities</strong>:</p>
<ul>
<li class="">Engage with community members to foster a friendly and supportive environment.</li>
<li class="">Help organize, tag, and manage issues and pull requests.</li>
<li class="">Assist with community feedback collection and improvements to our resources.</li>
<li class="">Work collaboratively with other contributors on community initiatives.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="flexible-contribution">Flexible Contribution<a href="https://rehlds.dev/zh-Hans/blog/2024/11/01/welcome/#flexible-contribution" class="hash-link" aria-label="Flexible Contribution的直接链接" title="Flexible Contribution的直接链接" translate="no">​</a></h2>
<p>While we have a set plan of tasks to accomplish, we value flexibility. If there’s a particular area you’re passionate about, we welcome your ideas and support in those areas as well.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-to-apply">How to Apply<a href="https://rehlds.dev/zh-Hans/blog/2024/11/01/welcome/#how-to-apply" class="hash-link" aria-label="How to Apply的直接链接" title="How to Apply的直接链接" translate="no">​</a></h2>
<p>If you’re interested in joining us, please fill out <a href="https://forms.gle/fhyrnhnSFu4g4Cmz8" target="_blank" rel="noopener noreferrer" class="">this Google Form</a> with some basic information about your experience, contact details, and interests. We look forward to learning more about you!</p>
<p><strong>Let’s work together to create a more welcoming and vibrant ReHLDS community!</strong></p>
<!-- -->
<div class="wrapper_lbM2"><iframe class="iframe_UxNo" src="https://docs.google.com/forms/d/e/1FAIpQLSd3fFLzeEGKKOTOQFK3cl6EjgswXhm3SvPCvaYCbZz0PmGhfg/viewform?embedded=true" frameborder="0" marginheight="0" marginwidth="0"><p>Loading…</p></iframe></div>]]></content:encoded>
            <category>recruitment</category>
            <category>community</category>
            <category>open source</category>
            <category>volunteer</category>
        </item>
    </channel>
</rss>