How to contribute to missing functionalities?

[electricalgorithm]

Hello maintainers,

I read the blog post regarding to the new Flipper One announcement and asking for help. After diving deep to documentation, trying to follow codebases, etc., I realized that the OS-development workflow is quite intertwined and it's not clear how to contribute to kernel work particularly. I see that there are many issues exists in the repository, but they are all assigned to owners (I assume) and the issue/problem definition and acceptance criteria is not clear.

Particularly I'm missing the feature set needs to be implemented/upstreamed for the project.

I want to help you guys, let's have this issue as a chat on how to make sure that transition id a new developer is easy.

[alchark]

Hi Gyokhan,

For the kernel and U-boot development the preferred format is direct patch submission to the relevant upstream mailing lists (with b4 or git send-email). Respective upstream rules apply: see https://docs.kernel.org/process/submitting-patches.html and all adjacent docs (especially DT/bindings stuff). Feel free to put me in Cc: or in To: when sending if the patches are directly relevant for Flipper One or any of our supported test boards.

The most productive way to identify areas that might need improvement is to run any of the RK3576 boards for your own preferred workloads and see if anything doesn’t run smoothly, then address it. That ensures you have solid rationale for any changes to make the case upstream, and also that you can actually test your patches (sending untested patches is a taboo).

If you see an issue that you’d like to discuss with us first before diving into code, feel free to create an issue in our repo here (assuming that it’s relevant to the boards and the software stack we use). We are striving for the same, but surely there are more rough edges than we’ve had chance to stumble upon and describe in issues.