+1 for adding any source of contributions as long as it's automated or
close to automated (like executing one command/request and
copy/pasting the result)
On Mon, Feb 6, 2017 at 10:26 AM, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
+1
Thanks,
Marius
On Sun, Feb 5, 2017 at 12:07 PM, Vincent Massol <vincent(a)massol.net> wrote:
> Hi devs,
>
> Right now we’ve started acknowledging the committers in the Release notes.
>
> I’d like to propose to extend that try to ack everyone who participates in
> one way or another to a release, and not just developers.
>
> I can think of 3 more items to add:
>
> A) All the JIRA issue reporters that have had an issue fixed for the
> release (bug, improvement, new feature, etc). They took the time to report
> an issue and thus they’ve helped the committers to improve the quality of
> the release and thus they should be acknowledged. This allows us to also
> ack QA. We could decide to exclude the reporters who’ve also been
> committers or leave them in.
>
> B) The people who’ve contributed translations done after the start of the
> release development.
>
> Ideally we would also ack:
>
> C) The people who’ve helped on the list for the release
> D) The people who’ve helped on the Design and made proposals that made it
> to the release. I’m thinking of Caty for example. Luckily Caty also commits
> some code and often she’s recognised through commits.
>
> The problem with C) and D) is that they’re hard to gather. But we could do
> it on an ad-hoc basis by adding them to the RN during the development (when
> they help) instead of doing it at the end.
>
> In any case I’d like to focus on A) and B) FTM and I’m proposing to add
> them to the Release Plan since they’re easy to find out.
>
> WDYT?
>
> Thanks
> -Vincent
>
>
--
Thomas Mortagne