[FusionComm] Press Team

[Sam Spilsbury]

> A dev should write the original, we know best what we want included.
> It's not that much work, we just need a routine for it.

I agree. Last release was kind of sloppy and I do take some blame for
that as what happened is that I wrote was completely re-written in a
developer tone - resulting in us having two different release
announcements, one for the blog and one for the forums / mailinglist.
I agree that I *should* have used the one Dennis wrote, however I felt
that the tone was a bit technical and some new users may not
understand what it means. If the developer writes the announcement
first, then the press team can make it a bit more user friendly while
still being accurate.

>
> > Please excuse me if I missed other aspects of a "Press" team, but
> > release announcements are the only thing which actually matters for
> > devs.
>
> I also care about bunnies. Bunnies are great.
>

:)

> What Guillaume is saying is that wiki pages and blogs don't need a
> whole process to be proofread. Wiki pages are already being proofread
> (you know who you are, keep it up). Blogs are personal, and as such,
> it's up to the person in question to make sure it is proof read.

Here is my 2c on the whole blog / wiki issue.

A blog, by definition is personal. If you had a look at some of the
old beryl blogs, they were written with quite a personal tone, quote :

"Wooo, it's been a FUN month.  This is the first one of these
summaries I've written in a while and it feels rather good.  This week
has been focused on getting rid of some of those pesky bugs in Beryl
and ready for the upcoming 0.2.0 release.  Bugs from all walks of
beryl are being smashed left and right and the TODOLIST is getting
smaller with each passing day.  Every day svn grows more and more
polished, this is getting to feel like its almost ready for the
public."

In my opinion, there should be no *official* blog because it is
extremely hard to write a blog (which informs users in a casual tone)
in a technical and official tone. It would take years of proofreading,
and is probably not worth it for things like weekly entries.

What I think we should do in this case is to instead not have an
'official' blog, but just some of the existing blogs out there
(<self-praise>smspillaz.wordpress.com and
fusioncast.blogspot.com</self-praise>) should instead go on the
planet. This is exactly the case with many open source projects out
there, where the planet, which contains a number of personal entries,
gives us the big picture.

I also agree that these personal blogs should be somewhat open, and
while the writer does do their best to write and proofread their own
work, mistakes do happen. Maybe it would be a good idea to hand out
editing accounts of these blogs to developers and others, so we can
quietly correct others work without making a big fuss about it.

Now on to wikis. I now hail, praise and offer cookies to Fyda, who,
took the incentive to write the StyleGuidelines on the wiki. I think
this is really going to help with writers (like myself, I have
understood a few tips there) to understand how to write an article for
the wiki. Like said beforehand, a wiki is a collaborative effort and,
if you make a change, just put in a comment in explaining why you made
the change. I think that instead of bitching to each other, we can
just quietly correct others' mistakes while doing our best to make
sure that our own work is as clear, coherent and accurate as possible.
Mistakes happen. Thats why there are bugs in software ;-)

Anyways, that's just my 2c on the issue.

>
> If nobody objects, I'll take the responsibility of getting us an
> announcement ready in time for the next release. I may not be the best
> suited person, but I do have a pretty good grasp of what's going on.

I'm perfectly fine with that and I think you'd do a good job for a
release announcement ;-)

>
> - Kristian
> _______________________________________________
> Community mailing list
> Community at lists.compiz-fusion.org
> http://lists.compiz-fusion.org/mailman/listinfo/community
>