Governance section #1504
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| cards: | ||
| - title: "Scala Improvement Process" | ||
| description: "The SIP is the primary mechanism for evolving the Scala language." | ||
| expandText: "Process & People" | ||
| links: | ||
| - name: SIP Committee Members | ||
| url: https://docs.scala-lang.org/sips/process-specification.html#the-sip-committee | ||
| - name: SIP Process Specification | ||
| url: https://docs.scala-lang.org/sips/process-specification.html | ||
julienrf marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| - title: "Scala 3 Maintenance" | ||
|
There was a problem hiding this comment. I think we should cover both Scala 2 and Scala 3. There was a problem hiding this comment. @lrytz can you help us out here? In terms of the maintenance of Scala 2, what resources can we reference for the current process and people involved? There was a problem hiding this comment. There was a problem hiding this comment. Yeah, those are pretty up to date. If you feel anything is missing, let me know. |
||
| description: "Managing the Scala 3 compiler, standard library and documentation." | ||
| expandText: "Process & People" | ||
| links: | ||
| - name: Core Maintainers | ||
| url: https://github.com/lampepfl/dotty/blob/main/MAINTENANCE.md#compiler | ||
| - name: Maintenance Procedures | ||
| url: https://github.com/lampepfl/dotty/blob/main/MAINTENANCE.md | ||
|
Comment on lines
+17
to
+21
There was a problem hiding this comment. Here too, both links point to the same page. Also, that page dives deep into the issue supervisor role without giving an overview of all the organizations (I see at least LAMP and VirtusLab) involved in the maintenance of the compiler and their respective role. Last, the description above mentions the standard library and the documentation, which are not covered by the links. There was a problem hiding this comment. This information should probably be added to the MAINTENANCE.md as a separate PR. |
||
| - title: "Tooling" | ||
| description: "Managing build tools, linters, IDEs, and other tools." | ||
| expandText: "Process & People" | ||
| links: | ||
| - text: "Process and People are TBD, please stay tuned! However you can read below about the Scala Tooling Summit:" | ||
|
There was a problem hiding this comment. I think this section should be filled before we merge the PR. There was a problem hiding this comment. The current status on this is that we've only conducted one Tooling Summit during which no process was adopted. Changing this might be the goal for the next Summit in September. There was a problem hiding this comment. Even if there is no “process”, I would expect the Governance section to give more understanding to the readers about which organizations do exist and actively work on the tooling ecosystem. I think we should mention at least VirtusLab with Scala CLI and Metals, and Jetbrains with IntelliJ. |
||
| - name: "Scala Tooling Summit of March 2023" | ||
| url: https://www.scala-lang.org/blog/2023/04/11/march-2023-scala-tooling-summit.html | ||
| - title: "Moderation" | ||
| description: "Learn about how is the Scala community moderated." | ||
anatoliykmetyuk marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| expandText: "Process & People" | ||
| links: | ||
| - name: "Moderation Team" | ||
| url: https://www.scala-lang.org/conduct/#contact | ||
| - name: Code of Conduct | ||
| url: https://www.scala-lang.org/conduct/ | ||
| - name: "Inclusive Language Guide" | ||
| url: https://docs.scala-lang.org/contribute/inclusive-language-guide.html | ||
| - name: "Communication Channels" | ||
| url: https://docs.scala-lang.org/community/ | ||
| - title: "Update Frequency" | ||
| description: "This page is updated every 6 months by the Scala Center." | ||
| dontExpand: true | ||
| links: [] | ||
bishabosha marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
| // GOVERNANCE | ||
| //------------------------------------------------ | ||
| //------------------------------------------------ | ||
|
|
||
| .governance { | ||
| // background: $gray-nutshell; | ||
|
|
||
| .vertical-buttons-list { | ||
| @include display(flex); | ||
| @include flex-direction(column); | ||
| @include justify-content(space-between); | ||
| padding: 15px 0; | ||
| li { | ||
| margin-bottom: 10px; | ||
| } | ||
| // @include align-items(center); | ||
| // @include justify-content(flex-start); | ||
| } | ||
|
|
||
| .button-expand { | ||
| text-align: center; | ||
| display: block; | ||
| } | ||
|
|
||
| .button-more { | ||
| font-size: $font-size-small; | ||
| padding: 5px; | ||
| cursor: pointer; | ||
| } | ||
|
|
||
| .scala-items-list { | ||
| .items-menu { | ||
| .scala-item { | ||
| @include span-columns(4); | ||
| @include omega(3n); | ||
|
|
||
| @include display(flex); | ||
| @include flex-direction(column); | ||
| // @include align-items(center); | ||
| @include justify-content(space-between); | ||
| padding: 15px 10px; | ||
| text-align: center; | ||
| transition: $base-transition; | ||
| // border: 1px solid $gray-light; | ||
| margin-top: 15px; | ||
| @include bp(large) { | ||
| @include span-columns(12); | ||
| } | ||
|
|
||
| min-height: 150px; | ||
|
|
||
| h4 { | ||
| font-size: $font-size-h3; | ||
| color: #000; | ||
| text-transform: uppercase; | ||
| font-family: $base-font-family; | ||
| margin-bottom: 10px; | ||
| } | ||
|
|
||
| p { | ||
| font-size: $font-size-medium; | ||
| } | ||
|
|
||
| &.active { | ||
| background: $gray-light; | ||
| } | ||
| } | ||
|
|
||
| .items-content { | ||
| background: $gray-light; | ||
| transition: $base-transition; | ||
|
|
||
| .items-code { | ||
| display: none; | ||
| padding: 5px 0; | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be good to expand a little bit the description. What about the following?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, but this will take many lines of text, is it ok to go in the expanded section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally, I find the current
descriptiontoo short: it does not really provides anything in addition to the title. Is it a problem to make descriptions a bit longer?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the context of being the top of the community page, it adds a lot of vertical space, also the other boxes don't have a similar amount of text, so leading to empty space