weloveinterns is the main entrance to Project Jiachen's joint open-source internship programme, and a repository written from 2017 to today. It introduces what we do, the people doing it, and the first batch of open-source projects you can start on.
Project Jiachen (RISC-V Prosperity 2036) was founded on Chinese New Year's Eve 2024 by a group of RISC-V software and chip teams in China. It has no financial entity, no membership fee and no board — just one lead and a shared vision: a cooperation network built on consensus.
Before the next Bingchen year (2036, the Year of the Dragon), build on RISC-V an open standard system and open-source system software stack that covers the whole information industry, from data centres to desktop offices, from wearables to the intelligent IoT, so that the RISC-V hardware and software ecosystem reaches or exceeds the maturity of other mainstream architectures.
The goal is to bring together more than 100 chip and solution vendors and more than 500 software companies, complete RISC-V adaptation and optimisation in more than 18 foundational industries, and jointly port and deploy more than 1,000 important industry and commercial applications; and to build a RISC-V talent identification system connecting more than 10,000 professionals.
Join by endorsing the vision, leave whenever you like; members are equal, with no hierarchy; the more you contribute, the more influence you have.
No financial entity, no membership fee, no board; members start projects and raise funds themselves, and PLCT Lab and Kubuds provide the initial momentum.
From chip vendors and distribution communities to universities and research institutes, several independent projects have already been launched under Project Jiachen.
Launched on 8 June 2024, the programme starts from a very practical sentence: let member organisations accelerate the RISC-V ecosystem work that matters to their own business, with the smallest possible spend of money and management resources.15
Every student who wants to enter the open-source world gets a real stepping stone: a mentor, a real upstream task, a merged PR, a stipend.
Be the interface between companies and young people: companies provide positions and mentors; we screen, train, grade and endorse. Since the Jiachen Dragon year, more than 2,000 internship places have opened each year.
Verifiable numbers for positions, internships, community mentors and maintainers; more than 10 companies and institutions offer positions.7
3k+ 1k+ 50+
We don't look at 985 or 211, at your major or your year ranking; selection is based entirely on ability and potential. We believe in women's potential in STEM and reserve at least 30% of internship places for women applicants.1
There is one criterion: can you complete the day-to-day development work of a joint-programme host? Abilities the work does not need are outside the assessment. Capability levels run LV0–LV5 and are assessed by the lead as a 'benevolent dictator'; LV4 is the default level for a full-time hire. See the full grading and process →
The list is not 'a number of excellent interns' but specific people. Behind each card is a merged commit, an output that upstream recognises.
Maintains and adapts a large number of Arch Linux RISC-V packages; leads or takes part in the RISC-V port, optimisation and long-term maintenance of large projects such as Electron and Chromium (the riscv-forks series)
Maintainer of the LuaJIT RISC-V port; strong learning ability in compilers, and has given a public talk on the porting work
Lead of the RustSBI project, guiding its sub-projects; provided a complete Rust bare-metal-to-kernel support package for Bouffalo BL808; fixed points defined too loosely in the RISC-V SBI specification
Contributed RISC-V patches to Linux Kernel, GCC, QEMU, gem5, FireSim, OpenSSL, XiangShan and Rocket-Chip; submitted mainline Linux kernel support for Canaan K230; fixed two ambiguous points in the RISC-V ISA manual
Maintains the eunomia-bpf community project; with the eBPF team built the first runtime and toolchain that builds, publishes and runs general-purpose eBPF programs on Wasm, and pushed the bcc ecosystem to move to libbpf
RISC-V software and hardware ability accumulation above the PLCT staff average; joined ITEM as an expert consultant
Has deep contributions on both the software and hardware sides of RISC-V, and has independently carried out a "domain expansion" in several fields including Chisel/RocketChip and RISC-V Linux distributions
Contributed GCC and Binutils implementations for several new RISC-V extensions
Independently created and maintains Eulaceura, an openEuler RISC-V derivative distribution
Adapted and debugged a series of open-source applications on new RISC-V development boards and announced the demos at the RISC-V China Summit; the derivative distribution was named RobinOS and is maintained long-term
LV4 since 2021-12-01; remembered by teammates as "the LV4 who recovered the rm -rf", and also mentors and helps out within the team
Took part in implementing the Aya programming language and theorem prover
Took part in several projects in the eunomia-bpf community, including bpftime, eunomia-bpf and wasm-bpf.
Responsible for build fixes and maintenance of ROS 2 Humble packages: about 60+ PRs, 40+ merged, mainly fixing build failures caused by multiple architectures and new versions, filling in dependency chains, and backporting to release branches; also contributed BSP and simulator work upstream in RT-Thread. Specialises in embedded and RISC-V adaptation, and in fixing distribution package builds.
Named an outstanding intern in Huawei's open-source internship. Worked on the Ascend NPU ecosystem, completing framework adaptation, large-model tuning and deployment, and hardware module development, with several results merged into the open-source community. Good at collaborative development with AI tools, proactively looks things up to solve problems, and keeps project progress and feedback in sync so tasks land efficiently.
Internship: led the PLCT J139 team in developing the MoonBit community ecosystem, and organised the community Demo Day and community website; an important voice in MoonBit's early community. Specialises in compilers and formal proofs.
Interned on MoonBit development in PLCT Lab's J139 team; now actively working on improving long-term memory and context management for LLMs.
An internship follows a master — the contract exists only once a mentor accepts you. This section is filled in over time.
Founder and lead of Project Jiachen, founder of PLCT Lab, co-founder of Kubuds. Member of the RISC-V International Technical Steering Committee (TSC), chair of the ISA Infra HC, board member of the LLVM Foundation, acting chair of the RISC-V China Summit steering committee.
Hefei University of Technology (BSc Mathematics) | Institute of Software, Chinese Academy of Sciences (PhD, not completed); career: Institute of Software, CAS | Zhongke Chongde | PLCT Lab | Kubuds
500 of this repository's 779 commits come from him — including the recruitment notices, grading updates and intern report clean-ups for most cohorts.
Maintainer of Fedora RISC-V, Fedora RVA23 and Fedora 64ILP32 during his internship, working mainly on the RISC-V Linux software ecosystem; also mentors the RuyiSDK IDE and takes part in community work in the deepin DE SIG and the openGauss RISC-V SIG.
On the first day of the Bingwu year, 2026, Project Jiachen announced the RISC-V Global Leadership Training Programme, known as the Five-Colour Stone Project: taking its meaning from Nüwa smelting five-colour stones to mend the sky, it works on a ten-year cycle and moves from 'finding and screening talent' to 'training talent systematically and over the long term'.2
Figure: drawn by this site after the structure on slide 44 of “Project Jiachen: For the Prosperity of the RISC-V Software Ecosystem” (CCF Open Source Software Conference, 2026-08-16). The original image is not used.
Under Project Jiachen, member organisations have launched a number of projects; below them is another set of repositories recommended for interns — all real upstreams where you get real review.
The repository behind this site. 3,000+ positions and 1,000+ internships to date; the main entrance to this talent programme.
A trust network of personal endorsements; number 0 is self-signed by the lead, all are publicly verifiable on GitHub, and it echoes the PLCT intern level system.
'Every RISC-V development board deserves to be plugged in and loved.' Donating and claiming both run on drifting points; every donation is accepted optimistically, as it comes.
An integrated development environment and package manager (ruyi) for RISC-V developers, reducing the fetching and configuration of toolchains, simulators and system images to a few commands.
A documentation project launched by Project Jiachen member organisations, with the goal that Chinese-language RISC-V technical material is no longer scattered.
Two special programmes around the RISC-V software ecosystem; details and progress are in Project Jiachen announcements.
A competition aimed at RISC-V chip security, linked to the talent identification system.
Using AI to design a high-performance RISC-V processor for laptops: CPU/GPU performance per watt benchmarked against Apple M1, taped out at foundries in three regions, a thousand units to be delivered before Chinese New Year 2029, the Jiyou year.
Sipeed's minimal AI assistant framework, built around "small, fast, deployable anywhere"; a good first real upstream task for embedded and edge AI.
Making an AI assistant cheap: a small agent written in C within the RT-Thread ecosystem, with a manageable amount of code, suitable as a first contribution in the embedded direction.
Lightweight, clear and extensible AI agent infrastructure in Rust, emphasising "easy to learn, anything can be changed".
An MLIR-based compiler framework that bridges DSLs to DSAs. One of the main practice grounds for interns working on MLIR.
A unified compiler supporting multiple AI chip backends, aimed at custom deep-learning operators; the RISC-V backend work in the FlagOS system happens here.
A domain-specific language for high-performance GPU/CPU/accelerator kernel development, making operator writing as direct as writing Python.
From the launch announcement of June 2024 to the nine-year retrospective of 2026.
From a 2017 wiki of robotics assignments to the 2026 Five-Colour Stone Project, the weloveinterns repository has carried four signboards and seen several teams come and go over nine years; the only continuity is people.
The original launch announcement of Project Jiachen's joint open-source internship recruitment and training project (2024-06-08): 2,000 places a year, contracts signed directly between companies and students, monthly settlement against an externally visible delivery list, Kubuds as the backstop employer, and the share of places reserved for women. With notes added three years later.
This repository waits for the next email every day. Put 'position number - name - phone number - school' in the subject, attach a PDF CV, and send it to wuwei@rv2036.org.
On 2 May 2017, a repository called weloveinterns appeared on GitHub. Its first commits were "Initial commit", "Initial Home page" and "Created _Sidebar" — back then it was still a wiki, holding interns' materials, assignments and reports, like a noticeboard by a lab door.
Nine years on, the same repository holds 779 commits, 500 of them from one person (lazyparser, Wu Wei). Its signboard has changed four times: Zhongke Chongde, PLCT Lab, Kubuds, Project Jiachen; in the Bingwu year of 2026 it gained another layer of name, the Five-Colour Stone Project. Only 10 files remain today; 286 have existed over its history — on 12 October 2024 a single commit deleted 253 of them, gathering up every intern report from 2021 and earlier, and left only a forwarding address in the README: git checkout 664048d.
But the repository's name has never changed: we love interns.
Only two things on this line have been genuinely stable: a joint programme that opens every year, and batch after batch of interns who come for three months, three years, or just long enough to submit a single PR. Most come and then leave, and are now written into the MAINTAINERS files of other companies, other foundations, other open-source projects — which is exactly the result this system was meant to produce.
This site wants to do one thing: lay out those names and that line for you to see.