scalacenter / advisoryboard

Scala Center Advisory Board planning

The Scala Center Advisory Board

Purpose

This repository documents the process and activities of the Scala Center Advisory Board, the body which makes recommendations on the activities of the Scala Center, under the provisions of the Scala Industry Affiliates Program

Proposals for Recommendation

Proposals for recommendation may be submitted to the Advisory Board for consideration only by

• The Scala Center,
• advisory board members,
• affiliate members, or
• community members through the community representatives,

and should be made via a pull-request adding a new Markdown file to the proposals directory. The proposal should be assigned the next available Scala Center Proposal (SCP) number in sequence, and the file should be named nnn-<description>.md, where nnn is the SCP number, padded with zeroes, and <description> is a concise, lower-case, dash-separated description of the proposal.

Proposals should follow the format and sections laid out in the template proposal, and should be concise enough to fit on a single side of paper if printed out.

Proposals status

To see the up-to-date status of a proposal see the proposals/README which holds whether or not the proposal has been accepted, a summary of updates and the current status of all proposals. Once a proposal has been accepted by the board it becomes a "recommendation".

NOTE: This proposals/README.md file is auto-generated, so if you need to add an update or change the status of a proposal make sure to do so in the heading of the proposal file. The possible headings are:

date: date proposed
accepted: true, yes, false, no
updates:
  - postponed until next meeting
  - accepted after discussion
  - Updates found at https://www.scala-lang.org/blog/
status: completed, postponed, active, etc

The proposals/README.md will be updated in CI when merged into main, but you can also manually regenerate it with scala-cli run bin/ from the root of this project.

Invitations

For reference, invitations sent to each Advisory Board representative are included in the invitations directory.

Agendas

Agendas for each Advisory Board meeting shall be made available online at least five days before the meeting takes place, and shall reside in the agendas directory, under the filename xxx-yyyy-qz.md, where xxx represents the meeting number, yyyy represents the year and z represents the quarter (1, 2, 3 or 4).

Minutes

The minutes of the Scala Center shall be written up by the secretary after each meeting, and made available shortly afterwards on the Scala Center website.

Contributions

Contributions may be made to this repository, however the documents here represent a record of the proceedings of Advisory Board meetings, so only immaterial changes such as spelling corrections and reformatting will be accepted.

advisoryboard's Issues

Add a “status” field to each proposal

It is hard to track what’s the status of each proposal: has it been completed, or is there a work in progress, or has the proposal be withdrawn, or is it on our todo list, etc.

I propose that we add a header containing this information, at the top of each proposal:

# Status

Completed, see [this thing](http://www.some.thing)

SCP-005 is missing

This proposal was discussed in the first meeting, and accepted, but no proposal exists in the repository.

SCP-004 is missing

This proposal (Center to coordinate SIP/SLIP process) was discussed in the first meeting, and accepted, but there's no text for it.

post minutes from 9 May 2016 meeting

The minutes of the Scala Center shall be written up by the secretary after each meeting, and made available shortly afterwards in the minutes directory

yup, sure thing. might be a few days this time around because of Scala Days hecticness

move all the old minutes to scala.epfl.ch repo

like #33, but retroactive

The current "status" of proposals

While looking through the various proposals today I realized that there are quite a few that the "status" in the proposals readme hasn't been updated in quite some time. I think it'd be a good idea to do a quick review of these and to update the status in the relevant places. I'll provide a table down below of the existing proposals that "remains active" after quite some time. If need be we can discuss this during the next AB meeting, but if we're able to just take care of it this way, then no need.

Proposal	Current Status	Notes
002-dotty-migration-path	Remains active Updated to "completed"	There have been tools like scala3-migrate and a migration guide. Do we feel this sufficient to mark this as "completed"?
004-sip-and-slip-coordiation	Remains active	It says @darja is the SIP coordinator. Is this still active as intended?
005-continuity-of-scala-js	Remains active Updated to "completed"	I'm assuming this is still correctly marked as "active".
008-websites	Remains active Updated to "completed"	I'm actually not 100% sure if this is the case or not?
017-lsp-stp-wg-support	Remains active Updated to "completed"	While maybe fluid in its definition, I suppose the continue support of Metals means this is correctly "active"?
021-zinc-improvements	Remains active	The initial timescales outline in here are far exceeded. So what would we like to do with this?
022-jsr-45	Remains active	From looking on GitHub, abandoned pr in Scala 2 and draft pr in Scala 3.
024-diversity	Remains active	I believe this is still a WIP.
025-inclusive-language	Remains active	The inclusive language guide has been published, but I still see that a fair amount of repos: dotty, scalajs-bundler, and sbt-missinglink just to name a few under epfl/Scala Center that aren't actually following their own guidance with branch naming etc. Is there a reason for this? After the last AB meeting there needs to be a blog post published about this before being marked as completed
026-solidify-getting-started-with-coursier	Remains active Update to completed	There are some updates in here and some prs to address issues, but nothing is in a stable release yet in Coursier or available via coursier/apps, so I'm assuming this is still "active".

@sjrd @darjutak and/or @julienrf, I assume the three of you would know the most about the status of many of these, but anyone else that has info, please let me know and I can update accordingly.

Meeting minutes from 2018?

Have any meetings been held in 2018?

If so, where are the minutes?

If not, it would be good to add some note as to why as its been 6 months.

Updated members list

I hadn't seen the announcement that a community member spot on the Advisory Board had been filled. The most recent minutes only mention invitations had been sent, and the attendees.md file in this repo is stale. It would be helpful to have a reference of who is currently on the board, particularly for community members who wish to raise concerns.

Rename `master` branch to `main`

I do not have sufficient access in this repository to rename it.

@sjrd could you either do it yourself, or grant me the needed access?

GitHub has nice instructions at https://github.com/github/renaming

"invitations" and "recommendations" directories need updating

I have some more pressing updates I'm making first, but noticed these in the process, opening an issue so I don't forget to come back to it

SCP-008: Maintain scala-lang, docs.scala-lang, scala.epfl.ch websites

See the proposal for details.

• Fix changes to Getting Started tutorial series
• Update Getting Started page
• Look at Google Analytics to figure out which pages are getting the most hits. Use this to design a website structure.
• Simplify the docs page using the new 47 degrees template
• Merge docs.scala-lang.org into scala-lang.org/documentation
• Write an explanation of backends: use cases, performance, stability, etc
• Update list of recommended books
• Link to Scastie
• Copy templates from scala/scala-lang over to scala/scala.github.com so the style is consistent across the site
• Create a new Guides landing page
• Create a new Reference page
• Link to "All About Scala" http://allaboutscala.com/
• Fix downloads page: Update links, fix HTML beneath IntelliJ so the links are in the right order
• Link from scala-lang.org to scala.epfl.ch and be clear about what the Scala Center does
• Link to contributing page from community page
• Merge templates designed by 47 degrees into scala-lang
• Update the text on scala.epfl.ch with current information
• Add photos of team members to scala.epfl.ch
• Add a link to make changes to docs pages so it's very easy for readers to suggest quick edits
• Investigate what can be done to speed up docs site builds
• Give @travissarles Admin rights to merge non-contentious pull requests
• Develop a procedure to match contributors with issues and PRs
• Find an alternative to Disqus
• Add link to navigate from news post back to list

Find a venue for first Advisory Board meeting

add proposals for the May 2016 meeting to the proposals directory

@propensive we discussed an SCP-002 and so on at the recent advisory board meeting, but the proposals directory stops at SCP-001. can you add the proposals? we'll need this before we can send out the minutes, since the minutes will refer to the proposals.