Async meetings

[Qard]

Async meetings

[Qard]

Our first meeting seems to have worked well. After seeing how the conversation went, I'm thinking we should try a meeting issue every 2 weeks and keep it open for 48 hours.

Drop some 👍 or 👎 on this and if the group seems to agree, I'll get another issue up on Monday the 23rd.

[sam-github]

I'm OK with trying anything, and we can iterate on the fly, so +1 for me.

I thought the meetings were for discussion though, not voting. Node uses a consensus forming strategy, not a ************ of the majority, so I would hope voting would be rare.

Then again, discussion can happen in github.

How would an "async meeting issue" work?

[Qard]

Mostly I don't see voting happening. Just thinking for the occasional thing, like the decision we made to do guides/topics stuff back when we started this.

I mainly imagine the async meeting issue being used to coordinate larger tasks, like centralizing the guides/topics location, and to determine what areas to focus on going forward. There's lots of topics and guides that could be written, so we should try to think about what we can do now to make progress there.

[Qard]

Also, it could be a good place to just drop suggestions for docs that'd be useful but perhaps the person who thinks of it doesn't have the time or expertise to write it themselves.

[Qard]

Not much reaction other than a couple thumbs up. I'll try posting a first meeting issue on Monday and we can try it out. If you have any topics you want to discuss, feel free to post suggestions in advance here.

[evanlucas]

It would be cool if we could come up with a solid plan for where we want the guides to live. If we could get that together before Wednesday, I'd be happy to bring it up during the CTC meeting.