get rid of humandate

[eseiver]

In the index.html file, either:

1. create a more meaningful variable name/desc to make clear humandate = "human-readable" date
2. do away with humandate entirely and infer from the machine readable entry.

[rgaiacs]

Thanks for the feedback. @gvwilson Could you provide some information about the design choices here?

[gvwilson]

Sure - the problem is that if the startdate is 2015-01-01 and the
enddate is 2015-01-04, the workshop could be:

• one day on 2015-01-01 and one day on 2015-01-04
• half a day on each of those four days
• a four-day workshop

and we can't infer te right answer from the calendar interval. The
"right" solution is to allow people to insert a blob of iCal or
something like that, but that would be horribly unusable.

We also have language issues: @r-gaia-cs is keen to add a 'language: xx'
header so that we can signal the human language used in the workshop.
The human-readable date might then need to be in Portuguese or Korean
rather than English, and I don't think we can go there.

But I agree, 'humandate' is a lousy name...

[wking]

On Thu, Jan 08, 2015 at 03:33:39PM -0800, Greg Wilson wrote:

We also have language issues: @r-gaia-cs is keen to add a 'language:
xx' header so that we can signal the human language used in the
workshop. The human-readable date might then need to be in
Portuguese or Korean rather than English, and I don't think we can
go there.

Why not? Presumably only folks who spoke the target language would be
interested in the finer details of the human-readable field. The rest
of us could get the general idea from the machine-readable fields.

How about ‘date-notes’ or some YAML-y version thereof?