This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2HTATJLCWUCGDCRGFFHJC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 02/24/2013 01:42 AM, Kiril Nesenko wrote:
=20 =20 ----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Kiril Nesenko" <kiril@redhat.com> Cc: infra@ovirt.org Sent: Sunday, February 24, 2013 11:25:41 AM Subject: Re: New ideas to grow the community
On Sun, Feb 24, 2013 at 04:00:29AM -0500, Kiril Nesenko wrote:
Hi team, I have few ideas regarding the project, any feedback will be appreciated !
### IRC ### 1. I think that we should create new channels on irc, #ovirt is not enough.
Would you explain why it's time to fork #ovirt? I do not see TOO much traffic or confusion there. =20 I think that we need to prepare for the future and do things correctly.=
I think that this will help the project to grow.
There's also the idea that we don't want to split communication channels (mailing lists, IRC, etc.) until it's really necessary. We can always create new channels if we get too busy in the main location= =2E The risk is that if we create N channels and split people there, we reduce the energy in the community. As Mike points out, we only have 3 meetings in the course of a week. We do get a little bit of interruption during the meeting, but it's not too bad. Also, we're showing all the IRC activity of the community in one location, so we increase visibility to contributors and interested people= =2E Generally, I prefer to create new channels when it's extremely clear it's needed. (I can tend to overthink this by creating too much at the start, so I've learned to pull back to the basics and grow as needed.) I don't think I see that we've reached the "extremely clear" traffic level.= - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 ------enig2HTATJLCWUCGDCRGFFHJC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iD8DBQFRK5ko2ZIOBq0ODEERAqCPAJ9WE0+F0CWqGfZf3YIofOoGzhy9YgCfR2s4 E3D9TkuvN1lRaAcZXPhJJEA= =m3of -----END PGP SIGNATURE----- ------enig2HTATJLCWUCGDCRGFFHJC--