Hi Linkis Community,

**Date:** April 14, 2026
**Topic:** Contributor Onboarding Program
**Participants:** 汉雨唐落, lgq, 深圳-..., 小微有...
**Discussion Period:** 2026-04-14 09:30 - 11:25

---

**[09:30] 汉雨唐落:**
Want to discuss ways to encourage more community contributions:

- Good First Issue labels
- Mentorship for new contributors
- Contribution guide improvements
- Recognizing community champions

What would make you more likely to contribute?

**[09:39] lgq:**
Having a mentor to guide through the first PR would be really helpful.

**[09:48] 深圳-...:**
Recognition goes a long way. Highlighting contributors in release notes or blog 
posts.

**[09:57] 小微有...:**
What kind of contributions interest you most (code, docs, testing)?

**[10:06] 汉雨唐落:**
Good First Issues are a great way to get started. Low barrier to entry.

**[10:11] lgq:**
Clear contribution guidelines make a big difference. What to do, what to expect.

**[10:19] 深圳-...:**
Would a Slack/Discord channel for contributors help?

**[10:24] 小微有...:**
This aligns well with what we are seeing in production.

**[10:28] 汉雨唐落:**
Happy to contribute to this effort.

**[10:39] lgq:**
What stopped you from contributing in the past?

**[10:57] 深圳-...:**
I would love to help with this initiative.

**[11:15] 小微有...:**
This aligns well with what we are seeing in production.

**[11:25] 汉雨唐落:**
Great discussion! Here is what we have so far:

✅ Contributor Onboarding Program - Community feedback collected
✅ More discussion needed - Continue on dev list
✅ Volunteers welcome - Join the conversation

Sending this to the dev mailing list to get more community input.
Everyone is welcome to chime in!


---
Best regards,
Apache Linkis Community Member

Note: This is an automated discussion starter to engage community members.
Reply to this email to continue the discussion on the dev mailing list.

Apache Linkis - https://linkis.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to