<Travis> gregwhitworth: I think I just made you an Op...
yep, you did - thanks!!
<Travis> Now, to de-op myself...
can you send me how you did that
<Travis> Nice. Locked myself out :)
lol
start the meeting
<scribe> meeting: March 27 Open UI Sync
<scribe> scribenick: gregwhitworth
ack q+
"/me"
Hey everyone, if you haven't joined the DL for Open UI please do so as that is where I'll be sending corresponance to from now on including the minutes from today's call. As we gain momentum, me keeping a manual list of folks on who to invite is scalable. Here's the link: https://lists.w3.org/Archives/Public/public-open-ui/
If you have begun to work in the Open UI or plan to contribute, even if only in the meetings but not in editing please join the WICG here: https://www.w3.org/community/wicg/
As you'll see in the agenda we have quite a bit of things to cover and I expect that to only grow as we begin to need consensus on decisions. I'd like to propose a bi-weekly 30 meeting sync or a 1 hour monthly sync. I prefer the bi-weekly sync as it helps keeps things moving rather than waiting a month. Thoughts?
Levi: once per month would be my
vote
... bi-weekly would be ok I suppose
<chrisdholt> I'm good with bi-weekly for 30 minutes.
<nicholasrice> Good with bi-weekly
<Levi> bi-weekly it is
Proposed Resolution: Bi-weekly 30 minute syncs to keep momentum
RESOLUTION: Bi-weekly 30 minute syncs
Finally, we're beginning to function as a community group and I figured we mine as well make it official. I've proposed the community group but need five others to agree to that. Can you all please go and give your approval. In the next sync we'll resolve on chairs and charter. https://www.w3.org/community/groups/proposed/
PR #51: Review and resolve on initial template for component specifications: https://github.com/WICG/open-ui/pull/51
Levi: I have not had a chance to
review it lately, nicholasrice and I were just discussing
... *sharing screen*
... There is a PR up that organizes the research page a bit
more
... we're considering the way of linking key concepts
over
... it allows you to take the specifies what the proposed open
ui name but then what the other potential names are
... *goes over proposal of process*
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) WARNING: Replacing list of attendees. Old list: (no_one) New list: Levi Thomason Nick Rice Chris Holt Default Present: Levi, Thomason, Nick, Rice, Chris, Holt Present: Levi Thomason Nick Rice Chris Holt Found ScribeNick: gregwhitworth Inferring Scribes: gregwhitworth WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]