Linked by Thom Holwerda on Wed 7th Mar 2007 22:32 UTC, submitted by twenex
KDE The KDE 4 release team started a discussion about a possible release schedule for KDE 4. Of course nothing is set yet but the topic is now hot and some interesting problems and point of views come up. In other but related news Oxygen hit the mirrors, or better, kdelibs.
Thread beginning with comment 219712
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: jumping the gun?
by aseigo on Thu 8th Mar 2007 19:07 UTC in reply to "RE[5]: jumping the gun?"
aseigo
Member since:
2005-07-06

> I'm not part of KDE

no, but you are part of the greater open source community acting as a journalistic outlet. not being part of a specific project doesn't somehow relieve you of responsibility.

> Microsoft folk gave expected release dates

right, and i had no problem when people would repeat that i'd said we were aiming for the summer. turns out we might be aiming for the autumn instead. no complaints from me here.

but this wasn't a rumbling about possible/expected release dates, this was an internal discussion to set out a release roadmap. it was something we wanted to take to the kde contributors first.

you may have even read the email where someone suggested announcing it publicly sooner, but then cornelius said we should take it to the kde developers first out of respect.

in spite of that "no, let's not announce it publicly at this point until we have done the respectful thing to our fellow developers" message in that exact thread that was linked, lurkers decided to go ahead and do so anyways.

see, there is a difference between someone (e.g. me) opening their mouth in a known "PR" context and pulling out conversation that is not yet ready for that. yes, you -can-, but it doesn't mean you -should- and nor does that make it right.

> Does the fact that OSNews reports on this
> discussion mess up the process?

not just osnews, but the other blogs and sites (e.g. linuxtoday also carried it). and to answer your question: yes, this does make the process harder than necessary.

> What you are afraid of is that you will not be able
> to make the release date mentioned in the
> discussion

when will you learn that you are miserable and figuring out what i'm thinking and stop trying to pull that trick?

what i'm concerned about is that other kde developers will hear about the discussion first from linuxtoday or osnews and figure that decisions are being made without their input and consultation. that is not how we (kde) work, and it is not how this was going. the release team is preparing a plan, then we take it for community review and then we talk about it. this process is out of respect for our fellow developers, and they know that. when it gets circumvented, people feel, quite rightfully, that they are being cut out of things. in this case, they aren't, but it's easy for that opinion to get formed. i've been around this tree before a few times, and i really would like to avoid it in the future. those carrying this story are not helping and not being respectful of our processes.

> Because, Aaron, if you are confident you can make
> the October date

that's a strawman argument. =/

Edited 2007-03-08 19:08

Reply Parent Score: 5

RE[7]: jumping the gun?
by Thom_Holwerda on Thu 8th Mar 2007 19:57 in reply to "RE[6]: jumping the gun?"
Thom_Holwerda Member since:
2005-06-29

no, but you are part of the greater open source community acting as a journalistic outlet. not being part of a specific project doesn't somehow relieve you of responsibility.

Can I please decide for myself what community I'm part of? I'm not part of any "greater open source community" at all-- you do realise that the 'OS' in OSNews does not stand for 'open source', right?

I have zero responsibility to KDE or whatever other project. I have the responsibility to inform my readers of the topics we cover, and that happens to include KDE. Like I said before, if a project is discussing in a public mailinglist the release dates for a long-awaited and much anticipated new release, then that's something my readers would like to know. Hence, it constitutes as 'news'.

in spite of that "no, let's not announce it publicly at this point until we have done the respectful thing to our fellow developers" message in that exact thread that was linked, lurkers decided to go ahead and do so anyways.

Well, uhm, maybe because you guys were discussing the release date of the next major overhaul of one of the biggest desktop environments out there on a, like, public mailing list?

what i'm concerned about is that other kde developers will hear about the discussion first from linuxtoday or osnews and figure that decisions are being made without their input and consultation.

What part of "started a discussion about a possible release schedule" don't you understand?

that's a strawman argument. =/

That doesn't make it any less accurate, Aaron.

Edited 2007-03-08 19:59

Reply Parent Score: 1

RE[8]: jumping the gun?
by robertknight on Fri 9th Mar 2007 00:29 in reply to "RE[7]: jumping the gun?"
robertknight Member since:
2007-01-28

Hello Thom,

I am a newish KDE developer, but I read the main KDE mailing lists regularly. I was surprised to read about this on OSNews before seeing it on the two main KDE mailing lists.

I think it would have been prudent to wait a little longer (say a couple of weeks) before running with this story. Your readers benefit in two ways:

- Developers have had time to reach a consensus and can respond more coherently to your readers' comments.

- Your news story will contain more facts. In this case this will probably mean a date ( month , year ).

Reply Parent Score: 5