Unified internal communications channel

[Joshua Goins]

Hi Carl,

> Adding a new channel that is either a mailing list, rss feed or a forum
> category won't help and will probably only makes it worse. It's also very
> difficult to defines that is an important internal news for the whole
> community is as it will be different for every subproject in KDE. The
> plasma logo discussion would have not been very relevant for any app
> developers. Similarly discussion about the new default database backend for
> Akonadi won't be interesting for Plasma developers but might be interesting
> for KMyMoney and other non-PIM apps using Akonadi.

Yeah this is kind of tough to define, and I'm also wondering about the best way 
to handle this. Ideally, the communication channel would be low traffic (hence 
my suggestion to not allow discussions at all, and point people to a relevant 
issue if they're interested) so people won't easily ignore it. That doesn't 
solve the scope issue though, but might help anyway.

> Something that might help is merging the kde-core-devel and kde-devel
> mailing lists as those are very similar and should hopefully not be too
> complicated to do.

+1 to this idea, they usually have the same kind of discussions anyway. Some 
posts are usually cross-posted between them.

Thanks,
Josh