This is precisely what I was typing up when your mail hit my inbox. :D I like #zfdev. We can make it clear on the framework.zend.com- and maybe the #zftalk- site what the topics are for #zftalk and #zfdev. We already have a password-protected channel for the team. :o It's not that we want to exclude anyone, it's simply because the team often works on things that Zend is keeping hush-hush for whatever reason. Usually this involves unannounced partners- like the Dojo Foundation. There has been interest on the team for a general dev channel that we could include the contributor community in; my take on it is that's fine as long as they can keep track of which is which. :) Does anyone from the community want to take this on? I generally prefer that the community take on stuff that's communication related because it decentralizes ZF somewhat and encourages more channels of communication than we can reasonably maintain ourselves. Perhaps Geoffrey Tran would be interested, since I believe he already maintains the #zftalk channel and zftalk.com website, and there certainly is a lot of potential for reuse of resources there. Also, there has been some resistance to logging on the #zftalk channel. Considering what often is said there, I hardly blame them. ;) If we can stay more on-topic for the contributor channel, would there be any objection to logging and making the logs available on the web?
,Wil > > However, we'll have the problem of keeping the channel on topic and > not > > simply achieve the effect of moving customer support over to that new > > channel. > > We can religiously direct people to #zftalk :) > > How about #zfdev ? > > The channel will need a good set of ZF developers (including zend > staff) > to be effective. It needs to be promoted to all proposal authors at the > very least. > > Christoph >
