Initial repo setup

[SethTisue]

• Push initial skeleton with license and such
• Disable unwanted GitHub features such as wiki
• Grant access to appropriate teams and/or individuals
• Add it to readme at https://github.com/scala/sbt-scala-module
• Add build.sbt with sbt-scala-module (add build #6)
• Make sure Travis-CI works (https://travis-ci.org/scala/scala-library-next)
• Add it to the Scala 2.13 community build (add scala-library-next community-build#1264)
• Add it to scala-steward (add scala/scala-library-next scala-steward-org/repos#468)
• Add publishing secrets to Travis-CI config, following sbt-ci-release instructions
• Try out publishing to make sure it works
  • but drop the staging repos so nothing actually publishes
• Write a proper README (add a proper README #11)
• Set up labels for use on issues
• Reference it from the scala/scala README (mention scala-library-next in readme scala#9273)

[NthPortal]

Be clear about where discussions on additions should take place

where should discussions on additions take place?

[lrytz]

* Add `build.sbt` with `sbt-scala-module`

Please use scala-xml as template, it's the most up to date. In particular, I still have to push scala/scala-xml#417 through all the other module repos.

[SethTisue]

update on timing:

a few things cut in front of this in my queue:

• scala-collection-compat release (now done)
• scala-xml release for Dotty (now done)

and still in progress is:

• scala-parallel-collections 1.0 release — harder than expected because we should make sure Dotty support is in place before going 1.0

if the scala-parallel-collections stuff gets too hairy, I might decide to tackle this repo first.

but also, I'm on vacation next week.

so: this is currently on hold, but not for much longer, I'm optimistic I'll get to it before October.

in the meantime, it's fine to start discussions on issues.

[NthPortal]

I just realised we didn't determine where discussions on additions should take place yesterday

[SethTisue]

Here seems good? (And as with the other issue trackers, if something seems important and/or contentious enough, we call attention it on a Discourse thread, and/or on Twitter, etc.)

Anywhere but scala/bug!

What are the other choices, if any?

[NthPortal]

could ask people to open a discourse thread? that seems to be what scala/bug suggests.

I think it's easiest to put them here personally

[SethTisue]

I did a round of work on this today. Build is in place, publishing is in place. (See checkboxes above.) More soon.

[NthPortal]

I will be migrating some issues from scala/bug over.

Transferred: #7, #8, #9

[SethTisue]

have at it, everybody!

[SethTisue]

I will be migrating some issues from scala/bug over.

I opened #12 on this

[SethTisue]

I made a milestone (0.1.0)