On Thursday 09 October 2008, Matthew Woehlke wrote: It finally dawned on me that you aren't complaining about the "moderators" failing to pass your posts from a non-subscriber through, but rather you think our lists are actually moderated in the sense that every post must be approved.
I looked at the KDE lists, and while I didn't try posting to any of them, they all have subscribe links, and they look like pretty normal lists to me, where you have to be subscribed in order to post to them. Is that not the case? Our lists aren't moderated. We just reject posts from non-subscribers. The poster gets a "you must be subscribed" message, and we have the opportunity to pass that message through in spite of it being from a non-subscribed address. Most of the time the poster has already subscribed and reposted the message by the time we get those, but there are exceptional cases once in a blue moon where a real message is sitting there in the reject bin, and we pass it through. If a poster does this more than twice, we start making noises about getting them to subscribe please. But as far as moderation in the sense of some of these uptight snotty lists out there where you can't break any of the rules or you'll be banned for life, no, our lists aren't like that at all. I think these spasms we're experiencing right now are due to SourceForge doing a huge data center migration. Their service has been more prone to random breakages than usual, though random breakages are nothing new with SourceForge. Well, we get what we pay for after all. > > It's really not that bad. At least we're not switching to GNOME. If > > Rosegarden ever did that, I'd vomit in my hat, and then shoot someone. > > > :-D People regularly ask us when we're going to offer a GTK2 port. As if. > My problem with moving away from KDE is that a: it means I can't work on > KDE integration (which is what I probably would have been most > interested in), and b: (apparently) means more of a bias towards qmake > instead of cmake, which in turn means I can't use my build > infrastructure (not to mention having to learn Yet Another Build > System). And working on a qt-only project makes me feel somehow dirty :-). Oh, screw QMake. We're not using QMake. I agree that working on a Qt only project make me feel somehow dirty too, but there's so much pure Qt4 in KDE4 already. A lot of old KDE3 things are just replaced with new Qt4 things anyway. Frankly, I'm pretty disgusted with all of it across the board. I don't really like KDE4 so far, and it seems like a lot of effort and hullabaloo to wreck the best graphical desktop in the world. > Technically, I could fork it, but that's probably more effort than I'm > willing to expend at the moment. Well, true, but that would just be pointless in the long run. > It's also discouraging that I can't recall any mention of rosegarden on, > say, kde-devel. I think the KDE crowd would have been happy to help with > the porting effort I rather doubt it. Most of KDE is of broad interest to a lot of people, whereas we're highly specialized, complicated, and downright bitchy to work on. We've never had any help from people who didn't have a personal interest, and if anyone at KDE had such an interest, we probably would have crossed paths. > Anyway, it's your decision Not really mine, but majority rules and all that. I could fork it too, but it isn't worth it. -- D. Michael McIntyre ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
