TeamNewPipe
Create CONTRIBUTING.md file
This should probably copy most of https://github.com/TeamNewPipe/NewPipe/blob/dev/.github/CONTRIBUTING.md save for NewPipe-specific parts.
Some other things to note:
- No Kotlin is allowed in the codebase
I guess that would work, but then we would need to sync the two versions together, right?
Another option is to share the same contributing guidelines, but note when guidelines differ between the two projects. Yet another option (that I do not prefer) is to link to the NewPipe guidelines in NPE, and then state the differences.
Hmmm. Syncing seems like it would be an effort to set up. I would go with the least complicated option of linking the URL and noting the differences.
Sharing the contributing guidelines between both projects is a better idea in my opinion, as the idea of linking to the NP guidelines in the NPE guidelines might cause the NPE guidelines to get outdated.
My understanding is that some sort of GH Action would need to be set up to keep them in sync.
No, my idea is to link to the NP guidelines in the NPE guidelines, and state the differences in the earlier.
What happened to this?
Do we have a list of differences? Or should we just create the initial version referring to the NewPipe version?
I think we should hold off on this for now. This can be harmonised with the rewrite, and whatever practices and conventions are used there.