[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:       Martin Klapetek <martin.klapetek () gmail ! com>
Date:       2019-11-30 2:47:29
Message-ID: CAPLgePqzUp2+Th_iY3kevUBw9qgMmx9w=tU2Ui=Z1pm=H_ngTA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Nov 29, 2019 at 12:23 PM Paul Brown <paul.brown@kde.org> wrote:

> On viernes, 29 de noviembre de 2019 13:39:26 (CET) Philippe Cloutier wrot=
e:
> > Le 2019-11-27 =C3=A0 14:05, Aleix Pol a =C3=A9crit :
> > > Dear KDE community,
> > > Some of you already saw it at Akademy, but we wanted to make sure tha=
t
> > > 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 i=
s
> > 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 "sendin=
g
> > 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? This would allow several of us to solve the problems
> right
> away.
>

One suggestion for the report - it'd be awesome if the sprint group photos
had names under the photo. The names are already in the text so this
would just help put a face to a name.

Cheers
--
Martin Klapetek

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Fri, Nov 29, 2019 at 12:23 PM Paul Brown &lt;<a \
href="mailto:paul.brown@kde.org">paul.brown@kde.org</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On viernes, 29 de \
noviembre de 2019 13:39:26 (CET) Philippe Cloutier wrote:<br> &gt; Le 2019-11-27 Ã  \
14:05, Aleix Pol a écrit :<br> &gt; &gt; Dear KDE community,<br>
&gt; &gt; Some of you already saw it at Akademy, but we wanted to make sure that<br>
&gt; &gt; you were all aware of all the great things we did last year 2018<br>
&gt; &gt; <br>
&gt; &gt; <a href="https://ev.kde.org/reports/ev-2018/" rel="noreferrer" \
target="_blank">https://ev.kde.org/reports/ev-2018/</a><br> &gt; <br>
&gt; Thank you Aleix and everyone involved in producing this report, which is<br>
&gt; more extensive than any of this kind I&#39;ve seen from an open source \
project.<br> &gt; <br>
&gt; What are the proper ways to report issues in this report (or on<br>
&gt; <a href="http://ev.kde.org" rel="noreferrer" target="_blank">ev.kde.org</a> in \
general)? <a href="https://ev.kde.org/contact.php" rel="noreferrer" \
target="_blank">https://ev.kde.org/contact.php</a> mentions &quot;sending<br> &gt; \
email to <a href="mailto:kde-ev-board@kde.org" \
target="_blank">kde-ev-board@kde.org</a> &lt;mailto:<a \
href="mailto:kde-ev-board@kde.org" \
target="_blank">kde-ev-board@kde.org</a>&gt;&quot;, but is it<br> &gt; possible to \
determine if an issue was already reported there?<br> <br>
If you find issues with the report (inaccuracies, spelling mistakes, etc.), can <br>
you post them here? This would allow several of us to solve the problems right <br>
away.<br></blockquote><div><br></div><div>One suggestion for the report - it&#39;d be \
awesome if the sprint group photos</div><div>had names under the photo. The names are \
already in the text so this</div><div>would just help put a face to a \
name.</div><div><br></div><div>Cheers<br clear="all"><div><div dir="ltr" \
class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div><span \
style="color:rgb(102,102,102)">--</span></div><div><span \
style="color:rgb(102,102,102)">Martin \
Klapetek</span></div></div></div></div></div></div></div></div></div></div>



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

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