Re: github isses

While I think the core spec will be a priority, I expect that there will be
parallel conversations about other topics such as disambiguation of syntax
for accessibility, "blanks", and indicating insertion points/selections,
and I'm sure several other topics. I think a single repo with labels is the
appropriate way to deal with issues for the group.

My two cents,

    Neil


On Tue, Feb 19, 2019 at 8:29 AM David Carlisle <davidc@nag.co.uk> wrote:

> On 19/02/2019 15:51, Daniel Marques wrote:
> > HI everybody,
> >
> > We are currently creating issues at both
> > https://github.com/mathml-refresh/mathml-core/issues
> > and
> > https://github.com/mathml-refresh/mathml/issues
> > But I'm not sure whether it make sense at all.
> >
> > I do not see much of the difference. Most of the things we plan for
> > mathml4 are because of the mathml implementation in the web
> > (mathml-core). Thus, most of the issues of mathml could be also valid in
> > mathml-core.
> >
> > Should we create all issues in the same place and just use Projects,
> > Labels or whatever solution github provides?
> >
> > Dani
>
> I'd suggest that mostly we use mathml-core as I think that the main item
> of business should be to get that specified, then once that is clearer
> we can look at what to say about the remaining parts of mathml (some
> bits will need to be removed, some bits deprecated, and some bits just
> marked as "not in core")
>
> Note that github has a beta feature that means that issues can be
> transferred between repositories in the same organisation, so if we
> decide that some existing issues should be moved, we can move them from
> mathml-core to mathml or in the other direction.
>
> David
>
>
> *Disclaimer*
>
> The Numerical Algorithms Group Ltd is a company registered in England and
> Wales with company number 1249803. The registered office is: Wilkinson
> House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. Please see our Privacy
> Notice <https://www.nag.co.uk/content/privacy-notice> for information on
> how we process personal data and for details of how to stop or limit
> communications from us.
>
> This e-mail has been scanned for all viruses and malware, and may have
> been automatically archived by Mimecast Ltd, an innovator in Software as a
> Service (SaaS) for business.
>