Loading feed…
OpenSearch1 Hot0 comments3 min read
Climbing the ladder: Understanding OpenSearch’s Contribution Ladder policy
AI summary
Bối cảnh của chính sách Contribution Ladder trong OpenSearch tạo ra lộ trình rõ ràng dựa trên năng lực cho người đóng góp. Nguyên nhân kỹ thuật là hệ thống này chia các cấp độ từ contributor mới đến maintainer dựa trên số lượng pull request được chấp nhận và chất lượng code. Hệ quả chính là giúp dự maintain được chất lượng code cao trong khi vẫn khuyến khích được nhiều người mới tham gia. Điều đáng học là mô hình này sử dụng metric cụ thể như 10+ pull request được review để đạt vai trò Active Contributor, giúp định hướng rõ ràng cho người muốn phát triển trong cộng đồng OpenSearch.
AI summaries can be wrong. Read the original before relying on anything important.
Why read it: Bài viết này giúp lập trình viên hiểu rõ con đường thăng tiến dựa trên năng lực từ người đóng góp mới đến người bảo trì trong dự án OpenSearch.
What do you remember?
Answer 3 short questions to earn reward points for this article. Only do it if you want the points.
up to +17 points
3 questions · under a minute · optional
Source: https://opensearch.org/blog/climbing-the-ladder-understanding-opensearchs-contribution-ladder-policy. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
8 Sync ecosystem
One account, the whole ecosystem
Read the news here, practice coding, follow structured courses and train for IELTS on our sibling products — all connected through one 8 Sync account.
8syncdev.com
8syncdev.comThe ecosystem home: product overviews, blog and full pricing.
ExploreCourses
course.8syncdev.comLearn along a clear roadmap: videos, auto-graded quizzes, certificates and mentors who ship for a living.
View the roadmapCoding practice
coding.8syncdev.com1,000 DSA problems in Vietnamese, auto-graded across 7 languages — many FREE, right in your browser.
Practice for freeIELTS
ielts.8syncdev.comAI grading for all four IELTS skills with detailed rubric feedback.
Try it freeZUS — AI IDE
zus.8syncdev.comA 22 MB AI IDE for Vietnamese devs.
Download freemind0
mind0.8syncdev.comOrganizational memory for AI agents.
ExploreAcoLeads
home-acoleads.8syncdev.comAI that staffs your Fanpage and qualifies leads for you.
Try itRecommended for you
DEV104 Hot7 min
I Built a Visual System Design Reference — Switch Any Architecture Between AWS, Azure, GCP & Open Source
I Built a Visual System Design Reference — Switch Any Architecture Between AWS, Azure, GCP... Tagged with systemdesign, webdev, opensource, showdev.
Noted141 Hot5 min
openGym: Self-Hosted Workout and Fitness Tracker
openGym is a free, self-hosted fitness tracker that lets you manage workouts and follow your progress on your own server.
XDA Developers3 Hot4 min
I tried 5 open-source Obsidian alternatives, and one was an easy winner
Five promising apps, one clear winner.
XDA Developers1 Hot2 min
Someone used Claude Code to reverse-engineer the Apple AirPods 3, and now head-tracking works on Linux
Claude does it again.
Hacker News1 Hot4 min
The Lisp curse, now coming to your ecosystem
The LISP curse is often quoted as the reason why so few libraries and reusable components exist for LISP dialects. According to the concept, LISP is so power...
It's Foss1 Hot7 min
Passbolt is an Open Source Password Manager Built Specially For Teams
Passbolt offers both a free self-hosted edition and a managed cloud version of its team focused password management solution.
Hacker News63 Hot1 min
OccupySaaS
OccupySaaS is a protest movement in code: laid-off developers building clean-room, open-source, drop-in replacements for the SaaS giants. First up: ZeroAuthy (Auth0) and SalesCompel (Salesforce).
Zac Sweers1 Hot2 min
Stop Sending Tall PR Stacks
Stacked PRs are being overused and should stay the exception, not the norm, Zac Sweers argues. Small, logical commits reviewed commit by commit already make even large PRs reviewable, he says, criticizing GitHub for forcing reviews through an alphabetical files tab instead. Now that GitHub supports stacked PRs, he's seen stacks of 15 changes that must be merged serially, which multiply overhead, CI runs and code reviews by 15x. He suggests capping stack height around 5, and only for genuinely large changes.
Comments
Loading comments…