IRC Meetings RFC


#1

Hi guys! As I mentioned in the blog post I wrote a few days back, we should
start having regular developer meetings in IRC. The following pull request
is my stab at how we should hold those meetings, and a proposed standing
agenda (that I expect will change dramatically as we evolve.)

Note that I do not expect the first meeting to follow the standard agenda.

When I get 3 thumbsups, I’m going to merge it.

Feedback super welcomed.

Adam


Opscode, Inc.
Adam Jacob, Chief Dev Officer
T: (206) 619-7151 E: adam@opscode.com


#2

Adam,

This is great, thanks for opening this up.

  • Is the goal of this to have Chef Inc developers join in on the “where is
    Chef (the product) going” discussion, and open it to interested,
    non-Chef-employed parties?

  • You reference moderators, voicers and de-voicing. Will the IRC room turn
    into Voice-only for the duration of the meeting? Who will be given voice
    for that?

Thanks for taking the time!
-M

On Mon, Jul 7, 2014 at 5:59 PM, Adam Jacob adam@opscode.com wrote:

Hi guys! As I mentioned in the blog post I wrote a few days back, we
should start having regular developer meetings in IRC. The following pull
request is my stab at how we should hold those meetings, and a proposed
standing agenda (that I expect will change dramatically as we evolve.)

Note that I do not expect the first meeting to follow the standard agenda.

https://github.com/opscode/chef-rfc/pull/14

When I get 3 thumbsups, I’m going to merge it.

Feedback super welcomed.

Adam


Opscode, Inc.
Adam Jacob, Chief Dev Officer
T: (206) 619-7151 E: adam@opscode.com


#3

The goal is to start a discussion on how to structure Chef as an open
source project - and ultimately decide, document, and live by that
structure. That starts with a lot of Chef Software employees, because we
are the maintainers currently. As we build the rules for maintainers, ever
more people will have increased authority (and responsibilities) for
various parts of the project. For sure that involves roadmap.

Unless we just can’t function without it, the rooms will be open and no
restrictions placed. Feel free to send a clarifying PR.

Adam
On Jul 7, 2014 4:07 PM, “Mike” miketheman@gmail.com wrote:

Adam,

This is great, thanks for opening this up.

  • Is the goal of this to have Chef Inc developers join in on the “where is
    Chef (the product) going” discussion, and open it to interested,
    non-Chef-employed parties?

  • You reference moderators, voicers and de-voicing. Will the IRC room turn
    into Voice-only for the duration of the meeting? Who will be given voice
    for that?

Thanks for taking the time!
-M

On Mon, Jul 7, 2014 at 5:59 PM, Adam Jacob adam@opscode.com wrote:

Hi guys! As I mentioned in the blog post I wrote a few days back, we
should start having regular developer meetings in IRC. The following pull
request is my stab at how we should hold those meetings, and a proposed
standing agenda (that I expect will change dramatically as we evolve.)

Note that I do not expect the first meeting to follow the standard agenda.

https://github.com/opscode/chef-rfc/pull/14

When I get 3 thumbsups, I’m going to merge it.

Feedback super welcomed.

Adam


Opscode, Inc.
Adam Jacob, Chief Dev Officer
T: (206) 619-7151 E: adam@opscode.com


#4

On Jul 7, 2014, at 2:59 PM, Adam Jacob adam@opscode.com wrote:

Hi guys! As I mentioned in the blog post I wrote a few days back, we should start having regular developer meetings in IRC. The following pull request is my stab at how we should hold those meetings, and a proposed standing agenda (that I expect will change dramatically as we evolve.)

Note that I do not expect the first meeting to follow the standard agenda.

https://github.com/opscode/chef-rfc/pull/14

When I get 3 thumbsups, I’m going to merge it.

Feedback super welcomed.

I think the idea looks good overall. My only concern is that the standing agenda reads very much like this being “ChefInc broadcasts updates” and less of a participatory discussion. I don’t think it would actually work out like that, but I would like to see it reflected at least a little if things are going to be codified like this.

–Noah


#5

It’s a good idea. Just do it. I am sure a lot of us would find the discussions both interesting and productive
-g

On Jul 7, 2014, at 8:48 PM, Adam Jacob adam@opscode.com wrote:

The goal is to start a discussion on how to structure Chef as an open source project - and ultimately decide, document, and live by that structure. That starts with a lot of Chef Software employees, because we are the maintainers currently. As we build the rules for maintainers, ever more people will have increased authority (and responsibilities) for various parts of the project. For sure that involves roadmap.

Unless we just can’t function without it, the rooms will be open and no restrictions placed. Feel free to send a clarifying PR.

Adam

On Jul 7, 2014 4:07 PM, “Mike” miketheman@gmail.com wrote:
Adam,

This is great, thanks for opening this up.

  • Is the goal of this to have Chef Inc developers join in on the “where is Chef (the product) going” discussion, and open it to interested, non-Chef-employed parties?

  • You reference moderators, voicers and de-voicing. Will the IRC room turn into Voice-only for the duration of the meeting? Who will be given voice for that?

Thanks for taking the time!
-M

On Mon, Jul 7, 2014 at 5:59 PM, Adam Jacob adam@opscode.com wrote:
Hi guys! As I mentioned in the blog post I wrote a few days back, we should start having regular developer meetings in IRC. The following pull request is my stab at how we should hold those meetings, and a proposed standing agenda (that I expect will change dramatically as we evolve.)

Note that I do not expect the first meeting to follow the standard agenda.

https://github.com/opscode/chef-rfc/pull/14

When I get 3 thumbsups, I’m going to merge it.

Feedback super welcomed.

Adam


Opscode, Inc.
Adam Jacob, Chief Dev Officer
T: (206) 619-7151 E: adam@opscode.com


#6

I like it. At the very least, it’s a good place to start things off.

Cheers,

Jon

On 8 Jul 2014, at 06:54, Girish girishp@gmail.com wrote:

It’s a good idea. Just do it. I am sure a lot of us would find the discussions both interesting and productive
-g

On Jul 7, 2014, at 8:48 PM, Adam Jacob adam@opscode.com wrote:

The goal is to start a discussion on how to structure Chef as an open source project - and ultimately decide, document, and live by that structure. That starts with a lot of Chef Software employees, because we are the maintainers currently. As we build the rules for maintainers, ever more people will have increased authority (and responsibilities) for various parts of the project. For sure that involves roadmap.

Unless we just can’t function without it, the rooms will be open and no restrictions placed. Feel free to send a clarifying PR.

Adam

On Jul 7, 2014 4:07 PM, “Mike” miketheman@gmail.com wrote:
Adam,

This is great, thanks for opening this up.

  • Is the goal of this to have Chef Inc developers join in on the “where is Chef (the product) going” discussion, and open it to interested, non-Chef-employed parties?

  • You reference moderators, voicers and de-voicing. Will the IRC room turn into Voice-only for the duration of the meeting? Who will be given voice for that?

Thanks for taking the time!
-M

On Mon, Jul 7, 2014 at 5:59 PM, Adam Jacob adam@opscode.com wrote:
Hi guys! As I mentioned in the blog post I wrote a few days back, we should start having regular developer meetings in IRC. The following pull request is my stab at how we should hold those meetings, and a proposed standing agenda (that I expect will change dramatically as we evolve.)

Note that I do not expect the first meeting to follow the standard agenda.

https://github.com/opscode/chef-rfc/pull/14

When I get 3 thumbsups, I’m going to merge it.

Feedback super welcomed.

Adam


Opscode, Inc.
Adam Jacob, Chief Dev Officer
T: (206) 619-7151 E: adam@opscode.com


#7

That reflection in the standing agenda is due to the current shape of who
maintains the bulk of the project. I expect it will change quite a bit as
we change how the process works. Given the standing agenda is a backstop
rather than fixed (the first meeting agenda won’t be the standing one) -
I’m not worried about it.

Adam
On Jul 7, 2014 10:44 PM, “Noah Kantrowitz” noah@coderanger.net wrote:

On Jul 7, 2014, at 2:59 PM, Adam Jacob adam@opscode.com wrote:

Hi guys! As I mentioned in the blog post I wrote a few days back, we
should start having regular developer meetings in IRC. The following pull
request is my stab at how we should hold those meetings, and a proposed
standing agenda (that I expect will change dramatically as we evolve.)

Note that I do not expect the first meeting to follow the standard
agenda.

https://github.com/opscode/chef-rfc/pull/14

When I get 3 thumbsups, I’m going to merge it.

Feedback super welcomed.

I think the idea looks good overall. My only concern is that the standing
agenda reads very much like this being “ChefInc broadcasts updates” and
less of a participatory discussion. I don’t think it would actually work
out like that, but I would like to see it reflected at least a little if
things are going to be codified like this.

–Noah