<Helen> so what is the password?

<Carmen> Hey

<Carmen> Do I need to ask here for a password?

<Carmen> hi btw

<Sameera> Hi! Looking for password to join the Act call

<scribe> scribe: Jean-Yves

<Sameera> thanks

PRESENTATION: Carmen Burghardt working to redesign the website

Carmen: I am redesigning ACT rules web site. First focusing on potential users and their need/goal when reaching the site. Interview with representatives of these personas. Entry barrier in the way site is high. Rules are very abstract and hard to understand. Comparing with other sites that are known for good documentation. Prototyping interaction design. Sharing screen of prototype.
... will share link to demo.

Shadi: there is a lot more doc about this redesign. We should create survey with the full doc and prioritise what we implement now.

Helen: can we look at the prototype?

Shadi: yes. Will share in survey. Remember it's mockup and probably not 100% accessible.

<EmmaJPR> +present

<EmmaJPR> thank you

Final call https://github.com/act-rules/act-rules.github.io/issues/461

Wilco: 2 one week FC. No two weeks ones.

Rules ready for W3C publication https://github.com/act-rules/act-rules.github.io/issues/1120

Wilco: nothing new in accepted ones.

Jey: gonna work on mine.

Wilco: trying to put in FC next week.
... there's a bunch at the W3C currently. Some backlog at the TF.

Jey: running tests on iframe.

Wilco: I have too much on my plate. Can somebody help?

Aron: I can take the autocomplete one.

Jean-Yves: i can look at "required context role"

Link to related rules in the background https://github.com/act-rules/act-rules.github.io/issues/1402

Wilco: this follows a suggestion form TF. Make connection between rules clearer.

<Jey> +1 for the idea

Emma: is it like composite rules?

Wilco: no. That's same topic rules. Composite need result from other rules. Here it's not needing results, but checking similar or related stuff.

Emma: should it be a "related content" section, rather than background?

Jey: Maybe we can automate for rules checking SC.

Wilco: not sure it always make sense. Some SC are very broad.

Emma: automated would be good.

Jey: manual make it hard to fill, especially for newcomers.

Wilco: I think f you try and write a rule without already knowing related ones, you're going into troubles anyway.

Adil: can we define some criteria for what it mean to e related?

Wilco: same type of elements and some type of SC.
... if we introduce categories/label, this can be used to automate grouping.
... this needs more thought.

Emma: would it be about adding some metadata keywords?

Wilco: yes, for example.
... I'll try and come up with a more fleshed out proposal.
... Final Thoughts.

Shadi: exited about website.

Daniel: same.

Aron: searching for rules is needed.

Adil: good discussion and proposal.

Emma: Nice to see new names.

Helen: lot to swallow. Can help with metadata.

Jean-Yves: hard to scribe.

Jey: happy to see work on website.

Sameera: learning a lot. good discussions.

This is scribe.perl Revision of Date 
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: Adil, Wilco, Jean-Yves, Helen, Jey, Daniel, present, Emma
Present: Adil Wilco Jean-Yves Helen Jey Daniel present Emma
Found Scribe: Jean-Yves
Inferring ScribeNick: Jean-Yves

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: 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.)