Isn't the contributors guide needed on readme?

[vikaskyadav]

No description provided.

[ajayns]

Right now the prime focus is to complete the starter with all the major features, adding this guide has been left for later. But would be more than glad to accept PRs! :)

[vinay72]

@ajayns Can I work on the contributor guide to add README.rst file for new contributors to know how to contribute to this repository?

[ajayns]

Sure! Maybe @cekk or @tisto can help us with a repo with a good contributors guide which can be used as reference.

[vinay72]

@datakurre @ajayns Can I add this file in this repository by sending a PR? You can check this link : https://docs.plone.org/develop/coredev/docs/agreement.html .

[datakurre]

@vinay72 Just create a PR and discussion would be easier to handle in that PR.

Technically this package is not yet under Plone Foundation, so it does not require to follow those rules, but sure it would not do any harm to follow them.

[vinay72]

@datakurre Whenever I try to push my commit from my remote branch, I am getting the following error in my terminal

[datakurre]

Yes, you need to fork the repository and create fork from the pull. That’s common practise.

…

On 10 Feb 2019, 21.45 +0200, Vinay Sagar Sharma ***@***.***>, wrote: @datakurre Whenever I try to push my commit from my remote branch, I am getting the following error in my terminal — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[ajayns]

Please read through the commonly used practices while contributing to open source and maybe work your way through Github before opening a proper PR. It doesn't make sense spamming this repo with PRs @vinay72

[vinay72]

@ajayns I am sorry for inconvenience. I'll take care next time.