These are very valid concerns... even if all else goes smoothly, there's probably lots of "noise" on the #openvpn channel. Any objections against moving the meeting(s) to #openvpn-discussion?
-- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock twitter com: samuli_openvpn > All the official discussions I've seen on IRC so far, have had the channel > moderated and only the participants got the permissions to write. > Else you might and will get disturbed in multiple ways. > However it was me as well, who was asking Eric for a moderated discussion. > > An alternative approach might be choosing another channel, e.g. > #openvpn-discussion or just continue on the -devel mailinglist. > > Kind regards > Thomas > > > > Am 06.01.10 19:08, schrieb richard -rw- weinberger: > >> 2010/1/6, Eric F Crist<ecr...@secure-computing.net>: >> >> >>> This forum will be moderated. To apply for +v during the conversation, >>> please send an email to open...@secure-computing.net with your registered >>> IRC nickname and reason for requesting +v. >>> >>> >>> >> This is the first step in the wrong direction of making __Open__VPN >> more open. :-( >> >> >> > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel >
