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

List:       kde-promo
Subject:    Re: New Long Term Goal
From:       Valorie Zimmerman <valorie.zimmerman () gmail ! com>
Date:       2019-03-10 22:54:44
Message-ID: CACpu026p9VCdmRwQJiPiT5+Eag7iK=DOpjCK2wF+BQW2WUTuLA () mail ! gmail ! com
[Download RAW message or body]

On Sat, Mar 9, 2019 at 6:03 PM Paul Brown <paul.brown@kde.org> wrote:

> On domingo, 10 de marzo de 2019 1:00:00 (CET) Valorie Zimmerman wrote:
> > On Fri, Mar 8, 2019 at 7:58 AM Lydia Pintscher <lydia@kde.org> wrote:
> > > On Fri, Mar 8, 2019 at 1:32 PM Paul Brown <paul.brown@kde.org> wrote:
> > > > Hello Promoers,
> > > >
> > > > Today we added a new Long Term Goal to our list at
> > > >
> > > > https://community.kde.org/Promo%27s_Long_Term_Goals
> > > >
> > > > The goal reads:
> > > >
> > > > """
> > > Help establish a working durable and stable relationships with
> large, long-
> > > standing, FLOSS-friendly organisations, such as Mozilla, Wikipedia,
> > >
> > > Apache, Blender, the Document Foundation, etc. Over the next 5 years
> we want to
> > > help increase by ten the number of organisations that we work closely
> with
> > > and, preferably have them join the advisory board. This will help us
> have an
> > > even better integration of popular software (such as Firefox, Blender
> 3D,
> > >  LibreOffice, etc.) with Plasma, and increment the number of developers
> > >  supporting Plasma and KDE-related applications and technologies
> outside
> > > our community. This will not only help increase the number of
> contributors
> > > to our project, but also offer a better and more coherent experience
> to our
> > > users. We will carry out this goal by leveraging our connections,
> talking directly
> > > to people we already know within each project, inviting them to
> joint activities
> > > (events and sprints), inviting them to become part of the
> Advisory Board, and
> > >  in general listening and solving their concerns they have with regard
> to
> > > > working upstream with us.
> > > > """
> > >  We have a similar goal for distributions, but nothing for non-distro,
> > >  but FLOSS-related communities, so I think this covers a hole.
> > > >
> > > > If you think otherwise, or think this should be amended please say so
> > > here, in the Telegram/Matrix/IRC group/room, or commenting on the
> "Discussion"
> > > page of the Wiki entry.
> > >
> > > Hey :)
> > >
> > > That sounds good! Given that it has implications way beyond promo it'd
> > > be good to take this to the community mailinglist.
> > >
> > > Cheers
> > > Lydia
>
> Hello Valorie,
>
> > I agree with Lydia on this because the community is bigger than just the
> > Promo group and thus posting on the Community list will give us more
> chance
> > of finding folks with ties to whatever group we are focusing on. In fact
> > some community members may even be employed by one of these groups and
> thus
> > may have inside knowledge to the best people to contact.
>
> As I explain elsewhere, the goal is not a task. The goal is what we hope
> to
> achieve by carrying out specific tasks. If you want, the goal is what
> gives a
> task its focus and the tasks are what require involvement from the rest of
> the
> community.
>
> If we want of get Firefox developers to improve integration with Plasma
> for
> example,  we may float the idea of having them attend a sprint. If we do
> the
> groundwork and reach the conclusion that it would be good for us to have
> the
> Apache Foundation join the Advisory Board, we would go and talk to the
> Board
> and the e.V.
>
> These are two very different tasks that involve different people within
> the
> community, which Promo will talk to first, before approaching Mozilla or
> the
> Apache Foundation. These tasks themselves have very little in common with
> each
> other, probably the only thing is that they both help to achieve the
> overall
> goal.
>
> This is a roundabout way of saying: yes, we will involve the rest of the
> community, of course... But for each concrete task, as the tasks are what
> require other people to work or what other people could object to, not the
> goal.
>
> Cheers
>
> Paul
>

Yes, that makes sense. On the other hand, Promo is part of the community,
so staying transparent there is a good way to get more contributors. -v

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">On Sat, Mar 9, 2019 at \
6:03 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 domingo, 10 de marzo de 2019 1:00:00 (CET) \
Valorie Zimmerman wrote:<br> &gt; On Fri, Mar 8, 2019 at 7:58 AM Lydia Pintscher \
&lt;<a href="mailto:lydia@kde.org" target="_blank">lydia@kde.org</a>&gt; wrote:<br> \
&gt; &gt; On Fri, Mar 8, 2019 at 1:32 PM Paul Brown &lt;<a \
href="mailto:paul.brown@kde.org" target="_blank">paul.brown@kde.org</a>&gt; \
wrote:<br> &gt; &gt; &gt; Hello Promoers,<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Today we added a new Long Term Goal to our list at<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <a href="https://community.kde.org/Promo%27s_Long_Term_Goals" \
rel="noreferrer" target="_blank">https://community.kde.org/Promo%27s_Long_Term_Goals</a><br>
 &gt; &gt; &gt; <br>
&gt; &gt; &gt; The goal reads:<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; &quot;&quot;&quot;<br>
&gt; &gt; Help establish a working durable and stable relationships with large,  \
long-<br> &gt; &gt; standing, FLOSS-friendly organisations, such as Mozilla, \
Wikipedia,<br> &gt; &gt; <br>
&gt; &gt; Apache,  Blender, the Document Foundation, etc. Over the next 5 years we \
want to<br> &gt; &gt; help  increase by ten the number of organisations that we work \
closely with<br> &gt; &gt; and,  preferably have them join the advisory board. This \
will help us have an  <br> &gt; &gt; even  better integration of popular software \
(such as Firefox, Blender 3D,<br> &gt; &gt;   LibreOffice, etc.) with Plasma, and \
increment the number of developers<br> &gt; &gt;   supporting Plasma and KDE-related \
applications and technologies outside<br> &gt; &gt; our  community. This will not \
only help increase the number of contributors<br> &gt; &gt; to our  project, but also \
offer a better and more coherent experience to our<br> &gt; &gt; users. We  will \
carry out this goal by leveraging our connections, talking directly<br> &gt; &gt; to  \
people we already know within each project, inviting them to joint  \
activities<br>&gt; &gt; (events and sprints), inviting them to become part of the \
Advisory  Board, and<br> &gt; &gt;   in general listening and solving their concerns \
they have with regard to<br> &gt; &gt; &gt; working upstream with us.<br>
&gt; &gt; &gt; &quot;&quot;&quot;<br>
&gt; &gt;   We have a similar goal for distributions, but nothing for non-distro,<br>
&gt; &gt;   but  FLOSS-related communities, so I think this covers a hole.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; If you think otherwise, or think this should be amended please say \
so<br> &gt; &gt; here, in  the Telegram/Matrix/IRC group/room, or commenting on the \
&quot;Discussion&quot;<br> &gt; &gt; page of  the Wiki entry.<br>
&gt; &gt; <br>
&gt; &gt; Hey :)<br>
&gt; &gt; <br>
&gt; &gt; That sounds good! Given that it has implications way beyond promo \
it&#39;d<br> &gt; &gt; be good to take this to the community mailinglist.<br>
&gt; &gt; <br>
&gt; &gt; Cheers<br>
&gt; &gt; Lydia<br>
<br>
Hello Valorie,<br>
<br>
&gt; I agree with Lydia on this because the community is bigger than just the<br>
&gt; Promo group and thus posting on the Community list will give us more chance<br>
&gt; of finding folks with ties to whatever group we are focusing on. In fact<br>
&gt; some community members may even be employed by one of these groups and thus<br>
&gt; may have inside knowledge to the best people to contact.<br>
<br>
As I explain elsewhere, the goal is not a task. The goal is what we hope to <br>
achieve by carrying out specific tasks. If you want, the goal is what gives a <br>
task its focus and the tasks are what require involvement from the rest of the <br>
community. <br>
<br>
If we want of get Firefox developers to improve integration with Plasma for <br>
example,   we may float the idea of having them attend a sprint. If we do the <br>
groundwork and reach the conclusion that it would be good for us to have the <br>
Apache Foundation join the Advisory Board, we would go and talk to the Board <br>
and the e.V.<br>
<br>
These are two very different tasks that involve different people within the <br>
community, which Promo will talk to first, before approaching Mozilla or the <br>
Apache Foundation. These tasks themselves have very little in common with each <br>
other, probably the only thing is that they both help to achieve the overall <br>
goal.<br>
<br>
This is a roundabout way of saying: yes, we will involve the rest of the <br>
community, of course... But for each concrete task, as the tasks are what <br>
require other people to work or what other people could object to, not the <br>
goal.<br>
<br>
Cheers<br>
<br>
Paul<br></blockquote><div><br></div><div>Yes, that makes sense. On the other hand, \
Promo is part of the community, so staying transparent there is a good way to get \
more contributors. -v  </div></div><div dir="ltr" \
class="gmail_signature"><br></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