community: open issues here for any significant old issue from JIRA

[SethTisue]

I closed all open parser combinator tickets in the Scala JIRA bug tracker: scala/bug#9010, https://github.com/scala/bug/issues/8080, scala/bug#7483, https://github.com/scala/bug/issues/6520, https://github.com/scala/bug/issues/6491, scala/bug#6464, scala/bug#6067, https://github.com/scala/bug/issues/4929, https://github.com/scala/bug/issues/4002, scala/bug#3212, https://github.com/scala/bug/issues/2420, https://github.com/scala/bug/issues/1566, scala/bug#1547, https://github.com/scala/bug/issues/1482, scala/bug#1229

many of these ought to become issues here in this repo on GitHub. interested community members are invited to open new issues for them here, with links in both directions

[SethTisue]

closed in the interest of not having an issue that will likely be open forever.

#155 adds a reference from the README, as an alternate (IMO better) means of calling attention to the old issues.

[Philippus]

you can 'strike through' 9010 and 1547 as well I think

[SethTisue]

@Philippus GitHub now permits issues to be relocated from one repo to another within the same organization. shall we do it? (not sure if you have the needed permissions — if not, I could do it)

[Philippus]

I do have the option, but only for a subset of the repos within the scala org, so if you could do it please do!

[SethTisue]

done!

readme change: #326

[SethTisue]

I do have the option, but only for a subset of the repos within the scala org, so if you could do it please do

(fwiw, I didn't see scala-parser-combinators on the list either, and thought something was broken, but then a few minutes later I realized that if I typed the beginning of the repo name ("scala-parse") that made it appear)