On Wed, May 16, 2018 at 03:46:06PM +0100, Grant Likely wrote:
> To match convention used by many projects on GitHub, put the
> contribution details into a separate file instead of the top level
> README. Also tighten up some of the language around contributing to be
> clearer.
>
> Suggested-by: Ji
On the weekly call today I suggested for people to assign issues to
themselves if they wanted to take it on. Turns out GitHub doesn't allow
that unless you've got write access to the project. So, if you want to
take on an issue, add a comment saying so and I'll send you an invite to
join the proje
Hi folks,
Weekly EBBR meeting is in a couple of hours. Let me know if there is
anything you want on the agenda:
- Action/Issue review
- Any other business
Actions & Issues are now being tracked in GitHub. I'll go through this
list during the call:
https://github.com/ARM-software/EBBR/issues
A
On 05/17/2018 02:56 PM, Grant Likely wrote:
To match convention used by many projects on GitHub, put the
contribution details into a separate file instead of the top level
README. Also tighten up some of the language around contributing to be
clearer.
Suggested-by: Jilayne Lovejoy
Signed-off-by
To match convention used by many projects on GitHub, put the
contribution details into a separate file instead of the top level
README. Also tighten up some of the language around contributing to be
clearer.
Suggested-by: Jilayne Lovejoy
Signed-off-by: Grant Likely
---
CONTRIBUTING.rst | 70 +++
