[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: Issues (Re: KDE e.V. Community Report for 2018 available)
From:       Philippe Cloutier <chealer () gmail ! com>
Date:       2019-11-30 16:11:07
Message-ID: 5da4260b-ffb6-c43c-e45c-1760582242b2 () gmail ! com
[Download RAW message or body]

Thanks Paul,

Le 2019-11-29 à 12:22, Paul Brown a écrit  :
> On viernes, 29 de noviembre de 2019 13:39:26 (CET) Philippe Cloutier wrote:
>> Le 2019-11-27 à 14:05, Aleix Pol a écrit :
>>> Dear KDE community,
>>> Some of you already saw it at Akademy, but we wanted to make sure that
>>> you were all aware of all the great things we did last year 2018
>>>
>>> https://ev.kde.org/reports/ev-2018/
>> Thank you Aleix and everyone involved in producing this report, which is
>> more extensive than any of this kind I've seen from an open source project.
>>
>> What are the proper ways to report issues in this report (or on
>> ev.kde.org in general)? https://ev.kde.org/contact.php mentions "sending
>> email to kde-ev-board@kde.org <mailto:kde-ev-board@kde.org>", but is it
>> possible to determine if an issue was already reported there?
> If you find issues with the report (inaccuracies, spelling mistakes, etc.), can
> you post them here?


There is some information I would like to see in the report which is not 
there, though I don't know if that can be suggested for a template for 
future years. But the main issues I noticed are the following:

  * The lack of production or/and publication dates
  * The "Streamline the onboarding of new contributors" section links to
    https://webchat.kde.org/#/room/#kde-welcome:kde.org
    I was not expecting that a "KDE Welcome team" link in an
    organization's yearly report would point to some instant messaging
    channel, but if that's intentional, I am not sure it was intended to
    link to a "welcome" channel which can't even be consulted without an
    account. If it's really intentional to link to that channel in its
    current state, it would surely be less misleading to have that link
    labelled "a discussion channel created by the new team" or something
    like that.
  * The "Financial working group" section is unclear about the year(s)
    covered. It seems to cover 2018, but also 2017. If it covers both,
    the paragraph in the 2017 Financial Data section is extremely
    confusing at best.

> [...]
>
> Cheers
>
> Paul

-- 
Philippe Cloutier
http://www.philippecloutier.com


[Attachment #3 (text/html)]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Thanks Paul,<br>
    </p>
    <div class="moz-cite-prefix">Le 2019-11-29 Ã  12:22, Paul Brown a
      écrit  :<br>
    </div>
    <blockquote type="cite" cite="mid:4437079.rxFBeN9rhi@rachel">
      <pre class="moz-quote-pre" wrap="">On viernes, 29 de noviembre de 2019 13:39:26 \
(CET) Philippe Cloutier wrote: </pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">Le 2019-11-27 à 14:05, Aleix Pol a écrit \
: </pre>
        <blockquote type="cite">
          <pre class="moz-quote-pre" wrap="">Dear KDE community,
Some of you already saw it at Akademy, but we wanted to make sure that
you were all aware of all the great things we did last year 2018

<a class="moz-txt-link-freetext" \
href="https://ev.kde.org/reports/ev-2018/">https://ev.kde.org/reports/ev-2018/</a> \
</pre>  </blockquote>
        <pre class="moz-quote-pre" wrap="">
Thank you Aleix and everyone involved in producing this report, which is
more extensive than any of this kind I've seen from an open source project.

What are the proper ways to report issues in this report (or on
ev.kde.org in general)? <a class="moz-txt-link-freetext" \
href="https://ev.kde.org/contact.php">https://ev.kde.org/contact.php</a> mentions \
"sending email to <a class="moz-txt-link-abbreviated" \
href="mailto:kde-ev-board@kde.org">kde-ev-board@kde.org</a> <a \
class="moz-txt-link-rfc2396E" \
href="mailto:kde-ev-board@kde.org">&lt;mailto:kde-ev-board@kde.org&gt;</a>", but is \
it possible to determine if an issue was already reported there?
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
If you find issues with the report (inaccuracies, spelling mistakes, etc.), can 
you post them here? </pre>
    </blockquote>
    <p><br>
    </p>
    <p>There is some information I would like to see in the report which
      is not there, though I don't know if that can be suggested for a
      template for future years. But the main issues I noticed are the
      following:</p>
    <ul>
      <li>The lack of production or/and publication dates</li>
      <li>The "Streamline the onboarding of new contributors" section
        links to <a class="moz-txt-link-freetext" \
href="https://webchat.kde.org/#/room/#kde-welcome:kde.org">https://webchat.kde.org/#/room/#kde-welcome:kde.org</a><br>
  I was not expecting that a "KDE Welcome team" link in an
        organization's yearly report would point to some instant
        messaging channel, but if that's intentional, I am not sure it
        was intended to link to a "welcome" channel which can't even be
        consulted without an account. If it's really intentional to link
        to that channel in its current state, it would surely be less
        misleading to have that link labelled "a discussion channel
        created by the new team" or something like that.<br>
      </li>
      <li>The "Financial working group" section is unclear about the
        year(s) covered. It seems to cover 2018, but also 2017. If it
        covers both, the paragraph in the 2017 Financial Data section is
        extremely confusing at best.</li>
    </ul>
    <blockquote type="cite" cite="mid:4437079.rxFBeN9rhi@rachel">
      <pre class="moz-quote-pre" wrap="">[...]

Cheers

Paul
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Philippe Cloutier
<a class="moz-txt-link-freetext" \
href="http://www.philippecloutier.com">http://www.philippecloutier.com</a></pre>  \
</body> </html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic