[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-29 6:33:01
Message-ID: AANLkTiksVpvLgQcMAkgQtF3n82FT4K3CuGtFivKjXeS5 () mail ! gmail ! com
[Download RAW message or body]

2010/10/28 Sven Langkamp <sven.langkamp@gmail.com>:
> On Thu, Oct 28, 2010 at 10:38 AM, Andrij Zinchenko
> <andrez.the.slacker@gmail.com> wrote:
>>
>> 2010/10/28 Sven Langkamp <sven.langkamp@gmail.com>:
>> > On Thu, Oct 28, 2010 at 12:22 AM, Andrij Zinchenko
>> > <andrez.the.slacker@gmail.com> wrote:
>> >>
>> >> OK, I understand many things. I may concede that there is a need for a
>> >> "clean break". But you can not any longer try to keep it secret from
>> >> community without seriously hurting it. Develop a message for the
>> >> community and show the clear way of keeping with it! If you need such
>> >> a message, I can help with that - I am PR guy anyway.
>> >
>> > We are not keeping it secret as this is a public mailinglist anyway. It
>> > still needs some days until the terms of the split are decided (names,
>> > which
>> > app goes where, etc)
>> > If you rush out a announcement that might soon be obsolete and even more
>> > confusing, so I think it's better to take the time to get it right. It's
>> > certainly not done with "three lines".
>> >
>> Sven, I think it is still more pleasant to see the announcement "Our
>> team have decided to postpone the RC release. Please, hold on - we
>> will provide you with details in couple of weeks". That is it.
>>
>> Noone expects from anyone any obligations. But it feels way better if
>> we communicate to people that we remember about them waiting for the
>> release, that we care about the dates stated in KOffice wiki.
>>
>> It is the same as call a person to warn that You might be late - the
>> person may get somehow sad but you will still be trusted. If You do
>> not show up at the meeting which was previously scheduled and did not
>> call to warn about that - that leaves You with no trust from that
>> person.
>
> The dates in the KOffice wiki are not official and can change. In case there
> are still release blockers more betas are scheduled, the RC date is pushed
> back. It would be a bit strange if we announce several times that the
> release might be pushed back.

Sven, it might sound a bit of overkill, but yes, if we warn people on
all these delays, that results in more trust. :)

It is like NASA delaying their flights even 5 times when needed, but
still announcing about that. And again, I am not asking You to do
that. I volunteer to fix that :)

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.

>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
>
_______________________________________________
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]