scalacenter / sprees Goto Github PK

well, this is daunting. there are 1,967 open issues at https://github.com/scala/bug

499 of them are labeled "quickfix": https://github.com/scala/bug/issues?q=is%3Aopen+is%3Aissue+label%3Aquickfix

help is needed even doing the triaging. the label may have been inappropriately applied in some cases, there are may be duplicates, etc. the number 499 seems suspiciously high to me. I looked at https://github.com/adriaanm/bbj/blob/master/src/main/scala/bbj/JiraExport.scala just now and it looks like all issues that had priority of "Minor" or "Trivial" are now labeled quick fix, in addition to all the issues that had the "low-hanging-fruit" tag.

the "Trivial" priority is probably usually correct, and I think the "low-hanging-fruit" tag was usually correct, too, but I think lots of "Minor" tickets were given that priority not because they were easy, but because someone thought they were of lesser importance.

under the circumstances, at present the easiest way to find eligible tickets is to search JIRA, actually 😢

• 72 JIRA issues labeled "low-hanging-fruit": https://issues.scala-lang.org/issues/?jql=labels%20%3D%20low-hanging-fruit
• 119 JIRA issues labeled "trivial": https://issues.scala-lang.org/issues/?jql=priority%20%3D%20Trivial

well, that's still a lot.

but anyway, once you find a JIRA issue with a URL such as https://issues.scala-lang.org/browse/SI-1234, the URL for the corresponding issue on GitHub is scala/bug#1234

I need to collect all the links to the PRs that were done (many).

I don't have sufficient permissions to do this myself. @anatoliykmetyuk ?

done, just now, and readme updated in 84a585c

Write small document explaining:

• Organization of the hackathon. Duration, pace, steps.
• Steps to add a project to a Scala Center hackathon.
• Suggestions on how to be a good maintainer.
• Suggestions on how to write good issues.
• Suggestions on how to guide first-time contributors.

I will use my experience running hackathons to write those guidelines.

There have been some changes that I merged and make the README a little bit inconsistent, since it mixes details from both Scala IO and Lambda World.

Tomorrow morning I will work on adding only Lambda World details and putting all Scala io spree details in another document, with a link to it from the README. @julienrf

/cc @Duhemm Any chance we can add scala-native to the project list? It would be awesome to have some spree tickets there.