<r12a> ACT

Action items

<r12a> https://www.w3.org/International/groups/hebrew-layout/track/

<r12a> ACTION: richard to Send out commands for IRC and rrsagent etc [recorded in http://www.w3.org/2017/07/18-hlreq-minutes.html#action04]

<trackbot> Created ACTION-2 - Send out commands for irc and rrsagent etc [on Richard Ishida - due 2017-07-25].

<r12a> https://www.w3.org/International/groups/hebrew-layout/track/actions/open

Identify editors for Hebrew Layout Requirements document

<r12a> https://github.com/w3c/hlreq

r12: each member should have a github id
... there are some guidelines
... info about contributing, editing, etc.
... editors should read very carefully

<r12a> https://w3c.github.io/hlreq/

r12: working with the markup - important
... who's familiar with github?

<aharoni> my github id is amire80

Lina: who wants to be an editor?

Amir: can be an editor

<aharoni> I can volunteer to be an editor.

Lina: I am also

<r12a> ACTION: Richard to set up Amir and Lina with edit access for the hlreq doc [recorded in http://www.w3.org/2017/07/18-hlreq-minutes.html#action05]

<trackbot> Created ACTION-3 - Set up amir and lina with edit access for the hlreq doc [on Richard Ishida - due 2017-07-25].

r12: the best way to get text into a doc
... alhreq using wiki
... whether editors commit directly or thru pull request
... need to decide the above
... editing tool which doesn't ruin souce text
... to reformat stuff recommendation to use pull request

<aharoni> BlueGriffon, DreamWeaver

<aharoni> these are WYSIWYG editors for HTML

<r12a> check whether Blue Griffin reformats source, DW is ok

<aharoni> I mostly use Atom as a plain-text editor.

aharoni: core content in English, Hebrew for samples etc only

<mati> There is IBM's HomePage, very old and probably not supported, but is simple to use.

<r12a> https://w3c.github.io/type-samples/

there is a separate repo for samples

<r12a> https://github.com/w3c/type-samples

<r12a> https://w3c.github.io/clreq/

aharoni: what is the target audience for the layout reqs?

r12: Scope of the document
... not technology specific at all
... but focused on how Hebrew works in terms article book etc
... eg underlining: this is how Hebrew uses underlining (general req) not technology specific implementation

Identify topics relevant to Hebrew http://w3c.github.io/typography/

Divide work on the topics.

Lina: let's work through these offline, and discuss proposals during next week's telecon

r12a: i suggest also using this URL, which is specifically intended to help layout TF folks brainstorm what to put in their docs, and give ideas on how to structure the information

<r12a> http://w3c.github.io/typography/checklist

<r12a> http://w3c.github.io/typography/

r12: points to information and issues
... we try not to use mailing lists but github issues
... key point keeping ppl on track
... mailing lists much more difficult to control

public-hlreq-admin

<r12a> https://w3c.github.io/i18n-activity/hlreq/

<r12a> public-i18n-hebrew

r12: daily digest of issues changes goes to the list