Since its inception, the deepin open-source community has been upholding the concept of openness and transparency, firmly becoming a link between internal developers and products, and external developers and users.
In the past, we have faced difficulties and stumbled a few times, but fortunately, with the support and companionship of everyone, we are not alone on the road of exploration.
Now we're going back in the correct direction, working together - migrating all of deepin's open source development processes back to GitHub, and getting our friends around the world to participate in our projects.
In 2019, deepin's project development process was migrated to in-house, which left many developers expecting to participate in deepin projects at their wits' end, and some of them eventually gave up on the idea of continuing to contribute, or even on using DDE.
The deepin community has been working on the problem for a while now, and we are aware of the problem and are working on a solution.
For those of you who follow deepin, you know that last year, we set up the Deepin Open Source Community Center and shared our plans for 2022 in DDUC. In the sharing, we mentioned our plan to build an "open and transparent" community. Part of the plan is to migrate the development process of all our open source projects back to GitHub, and to make the steps and process of participating in deepin development public, so that people around the world can take part in our development together.
Currently, most of our DDE-related open source community components have been migrated to GitHub for development, and those that have not yet been migrated are scheduled for completion in the coming month.
First, you can follow the migration progress of each project on the developer-center discussion board on GitHub. For projects that have already been migrated, you can get involved in the actual development by following the contribution guidelines provided on the developer-center Wiki page.
By contributing to the project via GitHub's Pull Request, your name will appear in the contributor list of the corresponding repository!
It is worth mentioning that we have received a lot of active feedback and code contributions during these months of project migration, and some of them have been merged in as a result of the project migration. We would like to thank hillwoodroc, ikerexxe, msojocs, kt286, openarun, panhaitao, ZhongYic00 (in no particular order) and other friends for their support and contributions to the deepin community, and we look forward to the participation of those reading this article!
Of course, code contribution is not the only way to contribute to participate in a deepin community. Even if you don't know how to write code, you can still choose to submit quality issues, participate in Wiki editing and documentation contributions, help other community members answer questions, and contribute in a variety of ways!
We are aware that the deepin community has gone through a stormy journey, encouraged by your courageous exploration, and motivated by your love, but still facing some problems, such as some of the community work in the process of restarting, community documentation is waiting for further improvement, the project is still on the road of continuous migration, and the project team needs to adapt to the new development environment.
If you encounter any problems in the process of participating in the deepin community contributions, you are very welcome to give us feedback and brainstorm through the developer-center discussion board or the deepin community forum.
Every question and suggestion you make helps us move forward with more determination! We look forward to your coming and building a better deepin with us!
Developer-center Discussion Board：https://github.com/linuxdeepin/developer-center/discussions/3051
Deepin Developer Center Guidelines:https://github.com/linuxdeepin/developer-center/wiki/Home-en
Submit Quality Issues：https://github.com/linuxdeepin/developer-center