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

List:       koffice-devel
Subject:    Re: thoughts from community member on a split
From:       Andrij Zinchenko <andrez.the.slacker () gmail ! com>
Date:       2010-10-30 17:23:23
Message-ID: AANLkTikbpAhd7FOtyZ5dzwNiH5iVM06z1uQ2EinNs2hA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2010/10/29 Cyrille Berger Skott <cberger@cberger.net>:
> On Friday 29 October 2010, Jaroslaw Staniek wrote:
>
>> On 29 October 2010 08:33, Andrij Zinchenko <andrez.the.slacker@gmail.com>
>> wrote:
>
>> > As for releases being pushed back, it makes sense to make a time
>
>> > disclamer, linked from every schedule page at the KOffice wiki. It can
>
>> > say something like this "Please, note that these schedules are dynamic
>
>> > in their nature, as is open-source. Since much of work on KOffice is
>
>> > done by volunteers, these dates are more of oriented dates than
>
>> > iron-fixed release dates. To speed up the development, consider
>
>> > donation to KOffice project". This small disclaimer kills
>
>> > overexpectations and gently explains the flexibility of the project`s
>
>> > schedule.
>
>>
>
>> +1
>
> You mean something like this "All information and plans must be taken with
> caution and are subject to changes without notices, decisions are taken on
> the koffice-devel@kde.org mailing list." [1] :)
>
> [1] http://wiki.koffice.org/index.php?title=Schedules/KOffice
>
> Also note that nothing is decided with RC1 and/or beta4.
>
> --
>
> Cyrille Berger Skott
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
>
Something like this but:

   - bit less corporate :).  "Is a subject to change withought notice" -
   sorry, but it sounds like a passage from some bank's credit agreement.
   - and a bit more elaborate (explain to users, why the process is such and
   that this is natural for open-souce project, especially of this scale)
   - and on every Wiki page related to planning on the top of it highlited
   with some color or otherwise marked

I am not asking You to do that. when You will be ready for that - just tell
me and I will gladly write this text. Users/testers will love reading it.

I am also ready to write a donation page materials, because it is a shame
that this project does not ask people for money. As we could see from
Krita's experience people will graldy provide KOffice with funding, because
http://www.koffice.org/contribute/ page does not provide an easy way for
people to donate :(

[Attachment #5 (text/html)]

<br>2010/10/29 Cyrille Berger Skott &lt;<a \
href="mailto:cberger@cberger.net" \
target="_blank">cberger@cberger.net</a>&gt;:<br>&gt; On Friday 29 October \
2010, Jaroslaw Staniek wrote:<br>&gt;<br>&gt;&gt; On 29 October 2010 08:33, \
Andrij Zinchenko &lt;<a href="mailto:andrez.the.slacker@gmail.com" \
target="_blank">andrez.the.slacker@gmail.com</a>&gt;<br>

&gt;&gt; wrote:<br>&gt;<br>&gt;&gt; &gt; As for releases being pushed back, \
it makes sense to make a time<br>&gt;<br>&gt;&gt; &gt; disclamer, linked \
from every schedule page at the KOffice wiki. It can<br>&gt;<br>&gt;&gt; \
&gt; say something like this &quot;Please, note that these schedules are \
dynamic<br>

&gt;<br>&gt;&gt; &gt; in their nature, as is open-source. Since much of \
work on KOffice is<br>&gt;<br>&gt;&gt; &gt; done by volunteers, these dates \
are more of oriented dates than<br>&gt;<br>&gt;&gt; &gt; iron-fixed release \
dates. To speed up the development, consider<br>

&gt;<br>&gt;&gt; &gt; donation to KOffice project&quot;. This small \
disclaimer kills<br>&gt;<br>&gt;&gt; &gt; overexpectations and gently \
explains the flexibility of the project`s<br>&gt;<br>&gt;&gt; &gt; \
schedule.<br>&gt;<br>

&gt;&gt;<br>&gt;<br>&gt;&gt; +1<br>&gt;<br>&gt; You mean something like \
this &quot;All information and plans must be taken with<br>&gt; caution and \
are subject to changes without notices, decisions are taken on<br>&gt; the \
<a href="mailto:koffice-devel@kde.org" \
target="_blank">koffice-devel@kde.org</a> mailing list.&quot; [1] :)<br>

&gt;<br>&gt; [1] <a href="http://wiki.koffice.org/index.php?title=Schedules/KOffice" \
target="_blank">http://wiki.koffice.org/index.php?title=Schedules/KOffice</a><br>&gt;<br>&gt; \
Also note that nothing is decided with RC1 and/or beta4.<br>

&gt;<br>&gt; --<br>&gt;<br>&gt; Cyrille Berger Skott<br>&gt;<br>&gt; \
_______________________________________________<br>&gt; koffice-devel \
mailing list<br>&gt; <a href="mailto:koffice-devel@kde.org" \
target="_blank">koffice-devel@kde.org</a><br>

&gt; <a href="https://mail.kde.org/mailman/listinfo/koffice-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/koffice-devel</a><br>&gt;<br>&gt;<br>Something \
like this but:<br><ul><li>bit less corporate :).  &quot;Is a subject to \
change withought notice&quot; - sorry, but it sounds like a passage from \
some bank&#39;s credit agreement.</li>

<li>and a bit more elaborate (explain to users, why the process is such and \
that this is natural for open-souce project, especially of this \
scale)</li><li>and on every Wiki page related to planning on the top of it \
highlited with some color or otherwise marked</li>

</ul>I am not asking You to do that. when You will be ready for that - just \
tell me and I will gladly write this text. Users/testers will love reading \
it. <div><br></div><div>I am also ready to write a donation page materials, \
because it is a shame that this project does not ask people for money. As \
we could see from Krita&#39;s experience people will graldy provide KOffice \
with funding, because <a \
href="http://www.koffice.org/contribute/">http://www.koffice.org/contribute/</a> \
page does not provide an easy way for people to donate :(</div> <meta \
http-equiv="content-type" content="text/html; charset=utf-8">



_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


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

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