Skip to content
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.

Docs WG Meeting #3 - 2016-02-03 @ 10:00AM PST #72

Closed
chrisdickinson opened this issue Jan 29, 2016 · 14 comments
Closed

Docs WG Meeting #3 - 2016-02-03 @ 10:00AM PST #72

chrisdickinson opened this issue Jan 29, 2016 · 14 comments

Comments

@chrisdickinson
Copy link
Contributor

This meeting is scheduled for 2016-02-03 @ 10:00AM PST, and will be a public-viewable Google Hangout on the Air.

I will place the Google Hangouts link for participants in the Docs WG Slack, and link the public URL in this issue.

Minutes will be recorded in a Slack Document that will be shared in the channel, then committed back to this repo after the meeting.

We will be revisiting the time of subsequent meetings to make sure everyone invited can attend.

Invited

Docs WG Meeting #3 2016-02-02

Present

In-meeting

In-chat

Agenda

  • Doctool: Remark plugins #61
  • Add first draft of ROADMAP.md #70
  • Discuss open PRs on Core (time permitting) issue tracker
@evanlucas
Copy link

How will we get around the max user limit on hangouts?

@rdodev
Copy link

rdodev commented Jan 30, 2016

Hangouts "on air" don't have a user limit. Granted most of us will be
"listeners" and can interact via text chat with each other.

On Fri, Jan 29, 2016 at 6:26 PM, Evan Lucas notifications@github.com
wrote:

How will we get around the max user limit on hangouts?


Reply to this email directly or view it on GitHub
#72 (comment).

@Knighton910
Copy link

LGTM 💯

@techjeffharris
Copy link

I work evenings 7 days/week until April, so I'm a bit nocturnal these days, but I should be able to wake up and get some coffee in me by then.. ;)

@ashleygwilliams
Copy link

hey @chrisdickinson there should probably be a policy for who will be an observer vs participant in the call.

additionally: is someone creating an agenda?

@chrisdickinson
Copy link
Contributor Author

@thefourtheye Yep! Thanks — I'll add that to the issue text.

@ashleygwilliams I'll be putting together the agenda from issues labeled wg-agenda next week on Tuesday morning PST. Any Docs WG member can label any issue or PR with wg-agenda, and if it's labeled before that time, it'll go on the agenda. I'll also do a call for agenda items on Tuesday in the team Slack. Before that point the agenda is mutable. If nothing is added before Tuesday the meeting will be canceled. At the moment, the only issue labeled wg-agenda is the roadmap PR — I'll add that to the issue text now.

Re: the observer/participant policy — I totally agree, but am not quite sure of the best way to go forward. Ideally everyone invited in the list above would be a participant, but Hangouts introduces an artificial constraint. The CTC & TSC meetings use Uberconference to get around the participant limit, and I'm looking into getting that set up for us. If we can't get Uberconference before then, I'll ask the team Slack if anyone has business that they'd like to introduce at the meeting and have those folks participate, while I (or another person) voice comments from the observer chat. That said, I am totally up to suggestions on this — how does the policy work for the Inclusivity WG?

@a0viedo
Copy link
Member

a0viedo commented Feb 2, 2016

Maybe we could grab the open issues with the doc label (in reverse chronological order) and see what's holding them back since there are many valuable additions.

@chrisdickinson
Copy link
Contributor Author

@a0viedo that would be great — would you be available to do that?

@Knighton910
Copy link

👍 @a0viedo

@a0viedo
Copy link
Member

a0viedo commented Feb 2, 2016

@chrisdickinson sure, I'll take a look. to add labels to issues should I just ping you or the team? I don't have those permissions at the moment

@chrisdickinson
Copy link
Contributor Author

OK, a link to the chat & minutes doc has been put in Slack.

@benjamingr
Copy link
Member

Sorry, I'm at a conference and won't be able to attend.

@eljefedelrodeodeljefe
Copy link
Contributor

Closing. Meeting was done. New meeting imminent.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants