Add guide for contributors related to fork repository mechanism

[andriawan]

to propose a change, contributors should follow guide about forking mechanism. I think we could state it in README for clarity

[fzn0x]

how about state it in #319 separated files?

[zainfathoni]

@andriawan could you please track this issue and any other issues you have created inside the related epics for the sake of discoverability?

I have invited you as a Collaborator to the repository so you can edit the epic issue descriptions by yourself to do so.

Thanks, @andriawan!

[apraditya]

@zainfathoni, now that #319 is merged & closed, is there anything else left to be done for this issue?

[andriawan]

I think it could be taken mas @apraditya

[apraditya]

I don't quite get it @andriawan. Do you think we can close this issue?

[andriawan]

I think adding this infromation to documentation is quite important for new comer as i found several contributors is not quite familiar with forking mechanism

[zainfathoni]

I don't quite get it @andriawan. Do you think we can close this issue?

No, he meant that you could take this issue, @apraditya. @andriawan, please try to avoid passive sentences as much as possible to avoid ambiguity. Your "it could be taken" sentence is unclear on who gets to take the issue. 😅

@adityapurwa, please create a draft pull request as explained in our contributing guidelines.

[andriawan]

sorry, i lost the context mas @zainfathoni. Sorry for my miss understanding 😅 🙏🏼 @zainfathoni @apraditya