https://github.com/act-rules/act-rules.github.io/pull/555 needs to be updated again, needs to go into final call again.

AGENDA ITEM, Reviewers wanted https://github.com/act-rules/act-rules.github.io/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+review%3Arequired+;

Objective / Unambiguous metadata in definitions? (revisit) https://github.com/act-rules/act-rules.github.io/issues/1003;

group seems in agreement, adding to the frontmatter of definitions is helpful. This information does not need to be in the rules themselves.

emma: it would be good to have a guide for writing definitions

Wilco & Kasper working on guidance for this.

Jey & Jean-Yves will work on adding this metadata to the frontmatter

AGENDA ITEM, Reviewers wanted https://github.com/act-rules/act-rules.github.io/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+review%3Arequired+;

Examples descriptions lang rules https://github.com/act-rules/act-rules.github.io/pull/1073;

https://github.com/act-rules/act-rules.github.io/issues/834

talked about using "should" syntax, group decided against this.

going to go forward with the PR as is, going to open more PRs / update PRs with this new format for example descriptions

Change the time for our second call? https://github.com/act-rules/act-rules.github.io/issues/1048;

Wilco is going to e-mail the list, see if anyone feels strongly about moving the second call, and remind folks that they are welcome to participate in either or both calls.

Shepherding rules to the ACT Task Force https://github.com/act-rules/act-rules.github.io/issues/1076;

1. chair will keep a list of rules ready for TF

2. open an issue as soon as rule is shared with TF, where feedback can be tracked

3. Once feedback is in, chair will meet with rule author to discuss how/when feedback will be resolved

4. rule author updates the rule

5. chair send updated rule back to TF

Descriptive page title: another example for consideration (c4a8a4) https://github.com/act-rules/act-rules.github.io/issues/1006;

trackbot, end meeting

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)

Default Present: Wilco_, Jean-Yves, Jey
Present: Wilco_ Jean-Yves Jey
No ScribeNick specified.  Guessing ScribeNick: Wilco_
Inferring Scribes: Wilco_

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 12 Dec 2019
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.)