New ideas to grow the community
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. We should add: #ovirt-meeting - will be used for meetings only, need to add bot that will log the meetings #ovirt-devel - will be used for devel discussions only #ovirt - general 2. Infra meetings should start with the following topic - New folks introductions (this is a tmp subject) In this topic we will let new folks to introduce themselves. ### Ovirt website ### 1. We should add link to the infra in - http://www.ovirt.org/Community It should be possible to navigate to http://www.ovirt.org/Infra from http://www.ovirt.org/Community . First thing someone that want to join the project will navigate to http://www.ovirt.org/Community , so it is very important to add link there. 2. Update - http://www.ovirt.org/Becoming_an_Infrastructure_team_member -Kiril
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.
We should add:
#ovirt-meeting - will be used for meetings only, need to add bot that will log the meetings
meeting can generate a lot of temporary noise which can deter people from jumping in, so I would agree to create an ad-hoc channel for a meeting - but please update the main #ovirt topic to indicate where the meeting takes place.
#ovirt-devel - will be used for devel discussions only
Have users complained that there are to many technical discussions on #ovirt? I think that it's important to keep the devels near users until devels become a nuisance.
#ovirt - general
2. Infra meetings should start with the following topic - New folks introductions (this is a tmp subject) In this topic we will let new folks to introduce themselves.
### Ovirt website ###
1. We should add link to the infra in - http://www.ovirt.org/Community It should be possible to navigate to http://www.ovirt.org/Infra from http://www.ovirt.org/Community . First thing someone that want to join the project will navigate to http://www.ovirt.org/Community , so it is very important to add link there.
2. Update - http://www.ovirt.org/Becoming_an_Infrastructure_team_member
----- 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.
I think that we need to prepare for the future and do things correctly. I think that this will help the project to grow.
We should add:
#ovirt-meeting - will be used for meetings only, need to add bot that will log the meetings
meeting can generate a lot of temporary noise which can deter people from jumping in, so I would agree to create an ad-hoc channel for a meeting - but please update the main #ovirt topic to indicate where the meeting takes place.
Nobody told users that they must/should attend meetings. If they want - they will attend. Why not ovirt-meeting ? I like this name. Sure we need to update the wiki with a new place
#ovirt-devel - will be used for devel discussions only
Have users complained that there are to many technical discussions on #ovirt? I think that it's important to keep the devels near users until devels become a nuisance.
Each discussions should be done in the right place. Maybe devel channel is not relevant for now, but still it will be nice to have it for a future.
#ovirt - general
2. Infra meetings should start with the following topic - New folks introductions (this is a tmp subject) In this topic we will let new folks to introduce themselves.
### Ovirt website ###
1. We should add link to the infra in - http://www.ovirt.org/Community It should be possible to navigate to http://www.ovirt.org/Infra from http://www.ovirt.org/Community . First thing someone that want to join the project will navigate to http://www.ovirt.org/Community , so it is very important to add link there.
2. Update - http://www.ovirt.org/Becoming_an_Infrastructure_team_member
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On Sun, Feb 24, 2013 at 04:42:23AM -0500, Kiril Nesenko wrote:
----- 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.
I think that we need to prepare for the future and do things correctly. I think that this will help the project to grow.
We should add:
#ovirt-meeting - will be used for meetings only, need to add bot that will log the meetings
meeting can generate a lot of temporary noise which can deter people from jumping in, so I would agree to create an ad-hoc channel for a meeting - but please update the main #ovirt topic to indicate where the meeting takes place.
Nobody told users that they must/should attend meetings. If they want - they will attend. Why not ovirt-meeting ? I like this name.
I don't mind the name - I just want the topic of #ovirt to remind me where have everybody's gone to.
Sure we need to update the wiki with a new place
#ovirt-devel - will be used for devel discussions only
Have users complained that there are to many technical discussions on #ovirt? I think that it's important to keep the devels near users until devels become a nuisance.
Each discussions should be done in the right place. Maybe devel channel is not relevant for now, but still it will be nice to have it for a future.
I think that spinning off #ovirt-devel is not "a thing done correctly". We may have to do it in the future, if users are tired of technical java discussions. Until this happens, we need to keep the guys who knows the most about the code near the guys who needs their support, in one happy channel.
#ovirt - general
2. Infra meetings should start with the following topic - New folks introductions (this is a tmp subject) In this topic we will let new folks to introduce themselves.
### Ovirt website ###
1. We should add link to the infra in - http://www.ovirt.org/Community It should be possible to navigate to http://www.ovirt.org/Infra from http://www.ovirt.org/Community . First thing someone that want to join the project will navigate to http://www.ovirt.org/Community , so it is very important to add link there.
2. Update - http://www.ovirt.org/Becoming_an_Infrastructure_team_member
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Kiril Nesenko" <kiril@redhat.com> Cc: infra@ovirt.org Sent: Sunday, February 24, 2013 3:20:01 PM Subject: Re: New ideas to grow the community
On Sun, Feb 24, 2013 at 04:42:23AM -0500, Kiril Nesenko wrote:
----- 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.
I think that we need to prepare for the future and do things correctly. I think that this will help the project to grow.
We should add:
#ovirt-meeting - will be used for meetings only, need to add bot that will log the meetings
meeting can generate a lot of temporary noise which can deter people from jumping in, so I would agree to create an ad-hoc channel for a meeting - but please update the main #ovirt topic to indicate where the meeting takes place.
Nobody told users that they must/should attend meetings. If they want - they will attend. Why not ovirt-meeting ? I like this name.
I don't mind the name - I just want the topic of #ovirt to remind me where have everybody's gone to.
Good idea
Sure we need to update the wiki with a new place
#ovirt-devel - will be used for devel discussions only
Have users complained that there are to many technical discussions on #ovirt? I think that it's important to keep the devels near users until devels become a nuisance.
Each discussions should be done in the right place. Maybe devel channel is not relevant for now, but still it will be nice to have it for a future.
I think that spinning off #ovirt-devel is not "a thing done correctly". We may have to do it in the future, if users are tired of technical java discussions. Until this happens, we need to keep the guys who knows the most about the code near the guys who needs their support, in one happy channel.
Yes I agree with you.
#ovirt - general
2. Infra meetings should start with the following topic - New folks introductions (this is a tmp subject) In this topic we will let new folks to introduce themselves.
### Ovirt website ###
1. We should add link to the infra in - http://www.ovirt.org/Community It should be possible to navigate to http://www.ovirt.org/Infra from http://www.ovirt.org/Community . First thing someone that want to join the project will navigate to http://www.ovirt.org/Community , so it is very important to add link there.
2. Update - http://www.ovirt.org/Becoming_an_Infrastructure_team_member
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 02/24/2013 08:34 AM, Kiril Nesenko wrote:
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Kiril Nesenko" <kiril@redhat.com> Cc: infra@ovirt.org Sent: Sunday, February 24, 2013 3:20:01 PM Subject: Re: New ideas to grow the community
On Sun, Feb 24, 2013 at 04:42:23AM -0500, Kiril Nesenko wrote:
----- 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.
I think that we need to prepare for the future and do things correctly. I think that this will help the project to grow.
We should add:
#ovirt-meeting - will be used for meetings only, need to add bot that will log the meetings
meeting can generate a lot of temporary noise which can deter people from jumping in, so I would agree to create an ad-hoc channel for a meeting - but please update the main #ovirt topic to indicate where the meeting takes place.
Nobody told users that they must/should attend meetings. If they want - they will attend. Why not ovirt-meeting ? I like this name.
I don't mind the name - I just want the topic of #ovirt to remind me where have everybody's gone to.
Good idea
This was discussed very early on -- splitting off and having a -meeting channel. We didn't make the change at that time because there wasn't enough traffic on the channel to warrant having 2 channels. Also, having the meetings in the #ovirt channel can have the side-effect of drawing more people into the meetings that are just lurking in #ovirt. Currently, there are only 3 meetings[1] per week in the #ovirt channel, each lasting 1 hr or less, generally. IMO, moving 3 meetings out is not really going to help.
Sure we need to update the wiki with a new place
#ovirt-devel - will be used for devel discussions only
Have users complained that there are to many technical discussions on #ovirt? I think that it's important to keep the devels near users until devels become a nuisance.
Each discussions should be done in the right place. Maybe devel channel is not relevant for now, but still it will be nice to have it for a future.
I think that spinning off #ovirt-devel is not "a thing done correctly". We may have to do it in the future, if users are tired of technical java discussions. Until this happens, we need to keep the guys who knows the most about the code near the guys who needs their support, in one happy channel.
Yes I agree with you.
I agree, lets not make this split until we have to. Mike
#ovirt - general
2. Infra meetings should start with the following topic - New folks introductions (this is a tmp subject) In this topic we will let new folks to introduce themselves.
### Ovirt website ###
1. We should add link to the infra in - http://www.ovirt.org/Community It should be possible to navigate to http://www.ovirt.org/Infra from http://www.ovirt.org/Community . First thing someone that want to join the project will navigate to http://www.ovirt.org/Community , so it is very important to add link there.
2. Update - http://www.ovirt.org/Becoming_an_Infrastructure_team_member
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[1] infra on Monday, node on Tuesday, Project on Wednesday.
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--
Hi, On 02/25/2013 06:02 PM, Karsten 'quaid' Wade wrote:
### 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.
I think that we need to prepare for the future and do things correctly. I think that this will help the project to grow.
<snip>
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.
I agree with Karsten - we split channels when the old ones get too busy (or do something to manage the busyness). Some of the things which I think, along these lines, would be very positive are: * Consolidating developer lists (arch, vdsm-devel, enginer-devel, node-devel) into one main developer list to ensure that we get away from the "mass CC" phenomenon - I previously proposed updating list descriptions and renaming arch to devel, the difference between vdsm-devel and engine-devel (where developers talk) and arch (where they don't, much) has actually grown since then. * Figuring out how to make the users list more manageable. A few things come to mind: * Opening a forum, so that people don't feel overwhelmed with 50-100 emails a day * Figuring out whether there are questions coming to the users list which really should be FAQs, bugs, or things we can improve in the design/install process to anticipate some of the questions being asked. * Splitting the users list - I do not favour this solution, because there's no clear unconfusing way to split it. Thoughts? Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
On 04/03/2013 12:41, Dave Neary wrote:
* Consolidating developer lists (arch, vdsm-devel, enginer-devel, node-devel) into one main developer list to ensure that we get away from the "mass CC" phenomenon - I previously proposed updating list descriptions and renaming arch to devel, the difference between vdsm-devel and engine-devel (where developers talk) and arch (where they don't, much) has actually grown since then.
i'm for renaming arch to devel and merging engine-devel and vdsm-devel into it. I'll let the node-devel chime in if they think its best to merge it as well or not.
* Figuring out how to make the users list more manageable. A few things come to mind: * Opening a forum, so that people don't feel overwhelmed with 50-100 emails a day
+1 on opening a forum. +2 if it gets sent to a mailing list (could be forum@ rather than user@).
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Dave Neary" <dneary@redhat.com> Cc: infra@ovirt.org Sent: Monday, March 4, 2013 3:28:50 PM Subject: Re: New ideas to grow the community
On 04/03/2013 12:41, Dave Neary wrote:
* Consolidating developer lists (arch, vdsm-devel, enginer-devel, node-devel) into one main developer list to ensure that we get away from the "mass CC" phenomenon - I previously proposed updating list descriptions and renaming arch to devel, the difference between vdsm-devel and engine-devel (where developers talk) and arch (where they don't, much) has actually grown since then.
i'm for renaming arch to devel and merging engine-devel and vdsm-devel into it. I'll let the node-devel chime in if they think its best to merge it as well or not.
* Figuring out how to make the users list more manageable. A few things come to mind: * Opening a forum, so that people don't feel overwhelmed with 50-100 emails a day
+1 on opening a forum. +2 if it gets sent to a mailing list (could be forum@ rather than user@). +3 from me if by sending an E-mail back to forum@ it will automatically post the answer in the forum.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Hi, On 03/04/2013 02:32 PM, Oved Ourfalli wrote:
+1 on opening a forum. +2 if it gets sent to a mailing list (could be forum@ rather than user@). +3 from me if by sending an E-mail back to forum@ it will automatically post the answer in the forum.
How would oVirt feel about being a guinea pig for Discourse? http://www.discourse.org/ Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
On 04/03/2013 15:42, Dave Neary wrote:
Hi, On 03/04/2013 02:32 PM, Oved Ourfalli wrote:
+1 on opening a forum. +2 if it gets sent to a mailing list (could be forum@ rather than user@). +3 from me if by sending an E-mail back to forum@ it will automatically post the answer in the forum.
How would oVirt feel about being a guinea pig for Discourse? http://www.discourse.org/
Cheers, Dave.
that sounds like a question to the users list? i was just using thunderbird support today and it looked good... https://getsatisfaction.com/mozilla_messaging/topics https://support.mozillamessaging.com/en-US/home but i'm guessing it needs a maintainer all of its own
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2XPIBVIKCHLDBNXQJVEMN Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 03/04/2013 05:42 AM, Dave Neary wrote:
Hi, On 03/04/2013 02:32 PM, Oved Ourfalli wrote:
+1 on opening a forum. +2 if it gets sent to a mailing list (could be=
forum@ rather than user@). +3 from me if by sending an E-mail back to forum@ it will automatically post the answer in the forum. =20 How would oVirt feel about being a guinea pig for Discourse? http://www.discourse.org/
I was hoping we'd be able to wait for MailMan 3, but I'm not going to really suggest that as a blocker unless others are behind the idea. Main thing I think about as an infra person is, how hard would it be to migrate content if we switched forums? Regarding Discourse, it looks *great* - they seem to be really thinking through the problems in the right way (not just making it open source but e.g. baking in to the software help for common forum needs.) It definitely tickles my desire to try out something next generation. Not sure off-hand, but perhaps ... well, what if we put out the word to users@ that we were thinking of trying Discourse as a supplement/replacement for an oVirt community support channel, and would anyone from users@ be interested in helping Infra build out and maintain the backend? Also, of course, we might be looking for moderators ... not sure how Discourse handles that. - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 ------enig2XPIBVIKCHLDBNXQJVEMN 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/ iD8DBQFRN+Ok2ZIOBq0ODEERAoaZAJ9+CkLCEflRImjbRrSc2tfOYJ3BPgCfVoBJ uimCqLwjZFGRGBkQv5Mx0oM= =SJvT -----END PGP SIGNATURE----- ------enig2XPIBVIKCHLDBNXQJVEMN--
On 03/04/2013 08:28 AM, Itamar Heim wrote:
On 04/03/2013 12:41, Dave Neary wrote:
* Consolidating developer lists (arch, vdsm-devel, enginer-devel, node-devel) into one main developer list to ensure that we get away from the "mass CC" phenomenon - I previously proposed updating list descriptions and renaming arch to devel, the difference between vdsm-devel and engine-devel (where developers talk) and arch (where they don't, much) has actually grown since then.
i'm for renaming arch to devel and merging engine-devel and vdsm-devel into it. I'll let the node-devel chime in if they think its best to merge it as well or not.
I would prefer not merging node-devel with arch/devel. Node is breaking away from being just an oVirt project, so having a separate devel list is good for us. I'll make sure that we include the general devel mailing list on oVirt related things, but in general, our stuff is much more node specific and not general ovirt related.
* Figuring out how to make the users list more manageable. A few things come to mind: * Opening a forum, so that people don't feel overwhelmed with 50-100 emails a day
+1 on opening a forum. +2 if it gets sent to a mailing list (could be forum@ rather than user@). _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
participants (7)
-
Dan Kenigsberg -
Dave Neary -
Itamar Heim -
Karsten 'quaid' Wade -
Kiril Nesenko -
Mike Burns -
Oved Ourfalli