Re: Explainers

This would be useful for the requirements that have a deep background or
wide solution space; however, it is overkill for others that are neither
deep or wide. In the latter case, the issue in tt-reqs should suffice.


On Thu, Feb 7, 2019 at 5:26 AM Nigel Megitt <nigel.megitt@bbc.co.uk> wrote:

> All,
>
> Now that we’re beginning to move from requirements gathering into solution
> design, it would be worth generating short documents explaining the
> problems and planned solutions in a little more depth. Looking ahead, at
> some point we will need to take the proposals to horizontal review
> including to TAG.
>
> Helpfully, TAG has an explainer for writing explainers, at
> https://w3ctag.github.io/explainers
>
> It would be very helpful to start to organise our thoughts in that sort of
> document framework to make it easier to communicate both amongst ourselves
> and with those horizontal review groups.
>
> Explainers are supposed to be short, and can change, so this should not be
> an onerous task.
>
> Perhaps we could aim to have first draft explainers ready by the middle of
> March?
>
> Kind regards,
>
> Nigel
>
>
>
> ----------------------------
>
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain personal
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
>
> ---------------------
>