lazyingfei
New Member
Hi All,
We want to bring obs-studio project to a new platform called OpenHarmony Next. We think it would be very useful on this new system.
This is a big project, and we want to do it the right way. We need your advice on how to manage our source code.
What is the best way to set up our work so we can share it back with you later?
We have a few ideas:
- Work in a separate copy: We could keep our code separate from the main project. This might be easier for us at the start, but maybe harder to share back later.
- Work in a special branch: We can make a copy (a fork) of your project and create a new branch just for OpenHarmony Next.
Your suggestion: Is there another way you think is better? We are open to your ideas.
Our main goal is to add our work back to the official project project if you think it is a good fit.
Any help or advice you can give us would be great.
Best
We want to bring obs-studio project to a new platform called OpenHarmony Next. We think it would be very useful on this new system.
This is a big project, and we want to do it the right way. We need your advice on how to manage our source code.
What is the best way to set up our work so we can share it back with you later?
We have a few ideas:
- Work in a separate copy: We could keep our code separate from the main project. This might be easier for us at the start, but maybe harder to share back later.
- Work in a special branch: We can make a copy (a fork) of your project and create a new branch just for OpenHarmony Next.
Your suggestion: Is there another way you think is better? We are open to your ideas.
Our main goal is to add our work back to the official project project if you think it is a good fit.
Any help or advice you can give us would be great.
Best