In the followup to this, I think it's important to note that
libreoffice is "Tumbleweed enabled."
That generally means that if the package is actively supported(and
libreoffice is), the very latest updates including any bugs as well as
new features would be pushed out to the User almost immediately.
That would also imply that practically any "news" about a
Tumblewee-enabled app like libreoffice is likely "old news" and
probably obsolete
Tony
On Wed, Mar 2, 2011 at 6:14 AM, Bryen M. Yunashko <susero...@bryen.com> wrote:
> On Wed, 2011-03-02 at 11:23 +0100, Andreas Jaeger wrote:
>> Kendy and the LibreOffice developers,
>>
>> this was indeed a mistake that we should not repeat and I'm sorry for it.
>>
>> What can we do now? Would it make sense to have a news story about openSUSE
>> 11.4 as first distribution which ships LibreOffice and speak about the
>> impressive rate the LibreOffice team fixed bugs?
>>
>> Andreas
>> --
>> Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org}
>> Twitter: jaegerandi | Identica: jaegerandi
>> SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
>> Maxfeldstr. 5, 90409 Nürnberg, Germany
>> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
>
> Manu has written a very nice article and interviewed Petr about
> openOffice being the first to release LibreOffice. We should get that
> out soon.
>
> I agree with many of the points that have been raised here, but I'd also
> like to defend Helen, as well as the circumstances that lead up to
> publication of articles.
>
> In some cases, (more often than not), we're in a rush to publish an
> article because it may be time-sensitive. The ability to accurately vet
> an article does get hampered. I'm speaking generally here, not just
> pointing to the LibreOffice issue.
>
> The bigger and overlaying question is how do we do a good vetting off an
> article before it gets published? People, for whom an article may
> affect, are not always readily available and in some cases in the past
> have been downright unresponsive. For example, we've had some people
> even submitting a story-lead to the news team and then disappearing
> after that. In one case, someone recently sent an idea for a good
> article on a project he was working on, and when we asked for additional
> information so we can create a good article, that person has still yet
> to respond.
>
> We can be slower in releasing articles in order to get it properly
> vetted, or we can release articles faster in order to generate the buzz
> it deserves. Both have their positives and negatives. How do we get
> people more responsive to NEEDINFO aspect, as the news team definitely
> wants to create an atmosphere that boosts the visibility of openSUSE,
> and this will be especially a critical issue in the next two weeks with
> the 11.4 release coming up and a plethora of articles coming out.
>
> Also, in Helen's case, she needed to get the RC2 announcemnt out
> quickly, and it was weekend when she did so. My experience is that
> people are less responsive on weekends (or Mondays even) than during the
> rest of the week.
>
> I'm not diminishing the harm that the article may have presented to
> LibreOffice team nor the mistakes that were made here, but trying to
> find a solution that addresses the higher-level challenge we have on the
> news team.
>
> Bryen
>
> --
> To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org
> For additional commands, e-mail: opensuse-marketing+h...@opensuse.org
>
>
--
To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-marketing+h...@opensuse.org
