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 219555
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 07:27 UTC in reply to "RE[5]: jumping the gun?"
aseigo
Member since:
2005-07-06

> At which point there doesn't really seem to be any
> point to having the discussion in the open at all

wrong! to *you* there wouldn't have been any point. but to everyone actually trying to actively get involved with the process (e.g. not just post it on their blog or personal news site) it would matter. they can't do that if the conversation is hermetically sealed.

iow, this is screwing it up for those people with a bit of initiative, talent and time (aka "the next generation of developers").

the fact that those who aren't actually involved are ok with taking actions that result in the degradation of service that allows those who can be involved to do so is really short sighted and, to be honest, pathetic.

Edited 2007-03-08 07:28

Reply Parent Score: 5

RE[7]: jumping the gun?
by smitty on Thu 8th Mar 2007 07:39 in reply to "RE[6]: jumping the gun?"
smitty Member since:
2005-10-13

I think we're just going to have to agree to disagree. :-)
This is my last post on the subject.

wrong! to *you* there wouldn't have been any point. but to everyone actually trying to actively get involved with the process (e.g. not just post it on their blog or personal news site) it would matter. they can't do that if the conversation is hermetically sealed.

It seems like you could just make it an invitation only discussion, since you don't want people like me to know about it anyway. The people you tell to get involved would have an invite while Thom and I would be blocked. The only tough part would be to set up the framework so you could automatically invite, say, everyone who's made a commit to kde svn in the past year. Then if it leaked you could only get mad at people within the project and possibly bar them from future discussions.

Reply Parent Score: 2