add Who can Contribute FAQ

Author: bishabosha

_config.yml

@@ -148,7 +148,7 @@ defaults:
       path: "_overviews/contribute"
     values:
       partof: scala-contribution
-      overview-name: Contributing to Scala
+      overview-name: Contributing to Scala's OSS Ecosystem
       layout: multipage-overview
       permalink: "/contribute/:title.html"
   -

_includes/sidebar-toc-multipage-overview.html

@@ -1,7 +1,7 @@
 {% assign pagetype = page.type %}
 <div class="content-nav">
   <div class="inner-box sidebar-toc-wrapper {% if pagetype %}book{% endif %}" style="">
-		<h5 class="contents">Contents</h5>
+    <h5 class="contents">Contents</h5>
       {% if pagetype %}
         <div class="inner-toc book" id="sidebar-toc">
       {% else %}
@@ -10,28 +10,32 @@ <h5 class="contents">Contents</h5>
       <ul>
         {% assign sorted = site[page.collection] | sort: 'num' %}
         {% for pg in sorted %}
-					{% if pg.num == page.num %}
-						{% capture toc %}
-						<div id="toc"></div>
-						{% endcapture %}
-					{% endif %}
+          <!-- Do not show the a page with sidebarState == "hidden" -->
+          {% if pg.sidebarState != "hidden" %}
+            {% capture toc %}
+              {% if pg.num == page.num %}
+                <div id="toc"></div>
+              {% endif %}
+            {% endcapture %}
 
-          {% if pg.num and (page.partof == pg.partof) %}
-            {% if page.language %} <!-- if page is a translation, get the translated title -->
-              {% assign prefix = page.language | prepend: '/' %}
-              {% assign localizedId = pg.id | prepend: prefix %}
-              {% for lpg in site.[page.language] %}
-                {% if lpg.id == localizedId %}
-                  <li><a {% if page.title == lpg.title %}class="active"{% endif %} href="/{{ site.baseurl }}{{ page.language }}{{ pg.url }}">{{ lpg.title }}</a>
-									{{ toc }}</li>
-                {% endif %}
-              {% endfor %}
-            {% else %} <!-- this must be English, so get the other documents' titles -->
 
-              {% if pg.type %} <!-- if a type is set in a document, we add it as a class. Used in Scala book to diff between chapter and section -->
-                <li class="type-{{ pg.type }}"><a {% if page.num == pg.num %}class="active"{% endif %} href="{{ site.baseurl }}{{ pg.url }}">{{ pg.title }}</a>{{toc}}</li>
-              {% else %}
-                <li><a {% if page.num == pg.num %}class="active"{% endif %} href="{{ site.baseurl }}{{ pg.url }}">{{ pg.title }}</a>{{toc}}</li>
+            {% if pg.num and (page.partof == pg.partof) %}
+              {% if page.language %} <!-- if page is a translation, get the translated title -->
+                {% assign prefix = page.language | prepend: '/' %}
+                {% assign localizedId = pg.id | prepend: prefix %}
+                {% for lpg in site.[page.language] %}
+                  {% if lpg.id == localizedId %}
+                    <li><a {% if page.title == lpg.title %}class="active"{% endif %} href="/{{ site.baseurl }}{{ page.language }}{{ pg.url }}">{{ lpg.title }}</a>
+                    {{ toc }}</li>
+                  {% endif %}
+                {% endfor %}
+              {% else %} <!-- this must be English, so get the other documents' titles -->
+
+                {% if pg.type %} <!-- if a type is set in a document, we add it as a class. Used in Scala book to diff between chapter and section -->
+                  <li class="type-{{ pg.type }}"><a {% if page.num == pg.num %}class="active"{% endif %} href="{{ site.baseurl }}{{ pg.url }}">{{ pg.title }}</a>{{toc}}</li>
+                {% else %}
+                  <li><a {% if page.num == pg.num %}class="active"{% endif %} href="{{ site.baseurl }}{{ pg.url }}">{{ pg.title }}</a>{{toc}}</li>
+                {% endif %}
               {% endif %}
             {% endif %}
           {% endif %}
@@ -44,8 +48,8 @@ <h5 class="contents">Contents</h5>
           {% for l in page.languages %}
             {% capture intermediate %}{{ page.url }}{% endcapture %}
             {% capture rootTutorialURL %}{{ intermediate | remove_first: '/' }}{% endcapture %}
-      			{% assign lang = site.data.languages[l] %}
-      			<li><a href="{{ site.baseurl }}/{{ l }}/{{ rootTutorialURL }}" class="lang">{{ lang.name }}</a></li>
+            {% assign lang = site.data.languages[l] %}
+            <li><a href="{{ site.baseurl }}/{{ l }}/{{ rootTutorialURL }}" class="lang">{{ lang.name }}</a></li>
           {% endfor %}
         </ul>
       {% elsif page.language %}
@@ -59,8 +63,8 @@ <h5 class="contents">Contents</h5>
           {% endfor %}
         </ul>
       {% endif %}
-		</div>
-		<hr>
-		<div class="help-us"><a href="https://github.com/scala/docs.scala-lang/blob/main/{% if page.collection %}{{ page.relative_path }}{% else %}{{ page.path }}{% endif %}"><i class="fa fa-pencil" aria-hidden="true"></i> Problem with this page?<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Please help us fix it!</a></div>
-	</div>
+    </div>
+    <hr>
+    <div class="help-us"><a href="https://github.com/scala/docs.scala-lang/blob/main/{% if page.collection %}{{ page.relative_path }}{% else %}{{ page.path }}{% endif %}"><i class="fa fa-pencil" aria-hidden="true"></i> Problem with this page?<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Please help us fix it!</a></div>
+  </div>
 </div>

_overviews/contribute/become-contributor.md

@@ -1,34 +1,95 @@
 ---
 title: Contribution FAQ
 num: 2
+sidebarState: hidden # hide from sidebar
 ---
 
-## Why contribute?
-Open Source Software (OSS) libraries are the flesh on top of the bone structure of the core language itself. They power vast majority of the commercial and non-commercial projects out there alike.
+{% capture backButton %}
+<p>
+  <a href="index.html#newcomers-faq">
+    <i class="fa-solid fa-angle-left"></i>
+    <span> back</span>
+  </a>
+</p>
+{% endcapture %}
 
-Contributing is a great way to strengthen your CV. It's also good from the community standpoint: if you do it consistently, with time, you get to know people, and people get to know you. Such a networking can lead to all sorts of opportunities.
+## Who Can Contribute To Open Source?
+{{backButton}}
+- **Everyone:** No matter your skills or background, non-technical or otherwise, there is always
+  [some way](#how-can-i-contribute-to-open-source) you can contribute to a project.
+- **Community organisers:** Communities often form around open source projects, perhaps you would like to help grow a
+  community.
+- **Scala learners:** If you are at the start of your Scala journey, once you have a basic understanding of everyday
+  Scala programming, becoming familiar with open source code will show you new techniques, helping you to improve
+  your expertise.
+- **Got a cool idea?** Perhaps you have gained confidence in your skills and are looking to give back to the community,
+  start a new project that fills that perfect niche, or maybe is the life-changing tool everyone never knew they needed.
+{{backButton}}
 
-Contributing to open source libraries is a great way to learn Scala. A standard practice in open source software is code review – which means you are going to get expert feedback about your code. Learning together with feedback from competent people is much faster than making all the mistakes and figuring them out alone.
-
-Finally, by contributing you improve the projects you are using yourself. Being a part of a maintainer team can be a source of personal satisfaction, and working on an innovative library can be a lot of fun.
+## Why Should I Contribute to Open Source?
+{{backButton}}
+- **The world is built on OSS:**
+  Open Source Software (OSS) libraries are the flesh on top of the bone structure of the core language itself.
+  They power vast majority of the commercial and non-commercial projects out there alike.
+- **Become more visible:**
+  Contributing is a great way to strengthen your CV. It's also good from the community standpoint: if you do it
+  consistently, with time, you get to know people, and people get to know you. Such a networking can lead to all
+  sorts of opportunities.
+- **Learn by doing something practical:** Contributing to open source libraries is a great way to learn Scala.
+  A standard practice in open source software is code review – which means you are going to get expert feedback
+  about your code. Learning together with feedback from competent people is much faster than making all the
+  mistakes and figuring them out alone.
+- **Have fun and help out:** Finally, by contributing you improve the projects you are using yourself. Being a part of
+  a maintainer team can be a source of personal satisfaction, and working on an innovative library can be a lot of fun.
 
 The above benefits are something good to achieve regardless of your level of experience.
+{{backButton}}
 
-## Ways to contribute
-Often, when people are talking about contributing to OSS, they think of fixing issues or implementing new features. While a valuable help, these are far from the only ways you can contribute. Following are some other ways you should consider:
-
-- **Documentation**. Often it is outdated, incomplete, erroneous. If you see a way to improve a documentation for a project you are using, you should consider finding out if the the documentation is hosted on github in which case you can submit a pull request to fix it.
-- **Issue minimization**. Many of the reported issues found on a project's issue tracker are hard to reproduce and the reproduction involves a lot of code. However, it is very frequently the case that only a tiny fraction of the reported setup and code is necessary to reproduce the issue. More reproduction code means more work for the maintainer to fix an issue. You can help them considerably by investigating already reported issues in an attempt to make their reproduction as small as possible.
-- **Issue reproduction**. Some reported issues lack reproduction instructions at all! If a maintainer can't reproduce it, they won't be able to fix it. Pinning down exact conditions that make an issue manifest is another way to contribute.
-- **Open-source your own project**. Do you have a pet project you are working on? Is there anything you're working on at work parts of which are generic enough that you can share them online? Open-sourcing your work is a way to solve a problem for other programmers who may also have it. If you are interested in going open-source, here is an excellent guide on how to get started: [https://docs.scala-lang.org/overviews/contributors/index.html](https://docs.scala-lang.org/overviews/contributors/index.html).
-
-## Choosing Where to Contribute
-The best project to contribute to is the one that you are using yourself. Take an inventory of your work and hobby projects: what OSS libraries do they use? Have you ever encountered bugs in them? Or have you ever wanted a certain feature implemented? Pick a bug and a feature and commit to fixing or implementing it. Clone the project you are trying to improve, figure out how the tests are written and run there. Write a test for your feature or bug.
-
-While implementing or fixing the feature, it is important to ask for help early when you feel stuck. Even if your code doesn't work, don't hesitate to submit a pull request while stating clearly that you need help. More information about the guidelines of good contribution you can find in the [talk by Seth Tisue](https://youtu.be/DTUpSTrnI-0) on how to be a good contributor.
-
-If you can't immediately see a bug or feature that you personally would like to use, a good idea is to learn a new Scala library, push it to its limits and see where it can be improved. You can find popular Scala libraries on [Scaladex](https://index.scala-lang.org/awesome). It's not a good idea to just pick a random library from the list and try fixing random bugs in it: you need to really spend the time with it to start seeing what's important and how to improve it right. So if you are passionate about contributing but don't see any immediate contribution options that would attract you, this should be your cue that it is time to expand your horizons and learn something new.
-
-There is also an option to contribute to the Scala 3 compiler itself. The Scala Center runs the Compiler Academy project to onboard and educate new people in the Scala 3 compiler. One of the Compiler Academy projects is an Issue Spree – an event that takes place every 3 weeks where people fix Scala 3 compiler issues in pair programming sessions while learning the compiler together. You can apply for the Spree participation by [filling the form](https://forms.gle/DfoSuHFm3T6MA3L59).
+## How Can I Contribute to Open Source?
+{{backButton}}
+- **Documentation:** Often it is outdated, incomplete, or with mistakes. If you see a way to improve the
+  documentation for a project you are using, you should consider if the project is accepting contributions,
+  in which case you can submit a pull request to include your changes.
+- **Building community:** All projects have users, and users come together to form communities. Managing and growing
+  communities takes coordination and effort.
+- **Issue minimization:** Many of the reported issues found on a project's issue tracker are hard to reproduce and the
+  reproduction involves a lot of code. However, it is very frequently the case that only a tiny fraction of the
+  reported setup and code is necessary to reproduce the issue. More reproduction code means more work for the
+  maintainer to fix an issue. You can help them considerably by investigating already reported issues in an attempt
+  to make their reproduction as small as possible.
+- **Issue reproduction:** Some reported issues lack reproduction instructions at all! If a maintainer can't
+  reproduce it, they won't be able to fix it. Pinning down exact conditions that make an issue manifest is another
+  way to contribute.
+- **Fixing a bug:** If you are comfortable with reproducing an issue, perhaps you would like to trace its
+  origin in code, and even try to build a solution that prevents the issue from occurring.
+- **Adding a feature:** Sometimes projects maintain lists of planned or requested features, and you could assist
+  in bringing those ideas to reality. Although please beware - you should only do this if the core maintainers
+  have already approved the idea for the feature, they are not obligated to accept your additions!
+- **Feel free to ask for help:** While implementing or fixing the feature, it is important to ask for help early
+  when you feel stuck. Even if your code doesn't work, don't hesitate to submit a pull request while stating clearly
+  that you need help. More information about the guidelines of good contribution you can find in the
+  [talk by Seth Tisue](https://youtu.be/DTUpSTrnI-0) on how to be a good contributor.
+- **Open-source your own project:** Do you have a pet project you are working on? Is there anything you're working
+  on at work parts of which are generic enough that you can share them online? Open-sourcing your work is a way to
+  solve a problem for other programmers who may also have it. If you are interested in going open-source, the
+  [Library Author's Guide](https://docs.scala-lang.org/overviews/contributors/index.html) is an
+  excellent resource on how to get started.
+{{backButton}}
 
-You may want to keep an eye on the Scala Center [LinkedIn](https://www.linkedin.com/company/scala-center/) and [Twitter](https://twitter.com/scala_lang) to stay up-to-date with the possible contribution opportunities. For example, every year, the Scala Center participates in the Google Summer of Code program where you are paid to work on open source Scala projects over the course of summer.
+## How Do I Choose Where To Contribute?
+{{backButton}}
+- **Ask yourself, what am I using?** The best project to contribute to is the one that you are using yourself.
+  Take an inventory of your work and hobby projects: what OSS libraries do they use? Have you ever encountered bugs in
+  them? Or have you ever wanted a certain feature implemented? Pick a bug and a feature and commit to fixing or
+  implementing it. Clone the project you are trying to improve, figure out how the tests are written and run there.
+  Write a test for your feature or bug.
+- **Try out an awesome library:** [Scaladex](https://index.scala-lang.org/awesome) is a great place to find new
+  libraries. If you are passionate about contributing but don't see any attractive opportunities to contribute
+  to projects you are already using, try learning a new Scala library, push it to its limits and see where it can
+  be improved. For best results, spend a lot of time with the library to get a feel of what's important
+  and what can improve.
+- **Lookout for announcements:** You may want to keep an eye on the Scala Center
+  [LinkedIn](https://www.linkedin.com/company/scala-center/) and [Twitter](https://twitter.com/scala_lang) to stay up-to-date with the possible contribution opportunities. For example, every year, the Scala Center participates
+  in the Google Summer of Code program where you are paid to work on open source Scala projects over the course
+  of summer.
+{{backButton}}

_overviews/contribute/bin-old-content.md

@@ -0,0 +1,68 @@
+---
+title: Grab Bag of Stuff
+num: 15
+---
+
+### Why You Should Contribute To Scala
+The Scala programming language is an open source project with a very
+diverse community, where people from all over the world contribute their work,
+with everyone benefiting from friendly help and advice, and
+kindly helping others in return. So why not join the Scala community and help
+everyone make things better?
+
+**What Can I Do?**
+That depends on what you want to contribute. Below are some getting started resources for different contribution domains. Please read all the documentation and follow all the links from the topic pages below before attempting to contribute, as many of the questions you have will already be answered.
+
+### Reporting bugs
+
+See our [bug reporting guide][bug-reporting-guide] to learn
+how to efficiently report a bug.
+
+### Contribute
+
+Coordination of contribution efforts takes place on
+[Scala Contributors](https://contributors.scala-lang.org/).
+
+{% include column-list-of-items.html collection=site.contribute_resources %}
+
+### Guidelines
+
+When contributing, please follow:
+
+* The [Scala Code of Conduct](https://scala-lang.org/conduct/)
+* The [Inclusive Language Guide][inclusive-language-guide]
+
+### Community Tickets
+
+All issues can be found in the [Scala bug tracker](https://github.com/scala/bug), or the [Scala 3 issue tracker](https://github.com/lampepfl/dotty/issues). Most issues are labeled
+to make it easier to find issues you are interested in.
+
+### Tools and Libraries
+
+The Scala ecosystem includes a great many diverse open-source projects
+with their own maintainers and community of contributors.  Helping out
+one of these projects is another way to help Scala.  Consider lending
+on a hand on a project you're already using.  Or, to find out about
+other projects, see the
+[Libraries and Tools section](https://scala-lang.org/community/#community-libraries-and-tools)
+on our Community page.
+
+### Scala Community Build
+
+The Scala community build enables the Scala compiler team
+to build and test a corpus of
+Scala open source projects
+against development versions of the Scala compiler and standard
+library in order to discover regressions prior to releases.
+The build uses Lightbend's
+[dbuild](https://github.com/typesafehub/dbuild) tool,
+which leverages [sbt](https://www.scala-sbt.org).
+
+If you're the maintainer -- or just an interested user! -- of an
+open-source Scala library or tool, please visit the
+[community build documentation](https://github.com/scala/community-build/wiki)
+for guidelines on what projects are suitable for the community build
+and how projects can be added.
+
+[bug-reporting-guide]: {% link _overviews/contribute/bug-reporting-guide.md %}
+[inclusive-language-guide]: {% link _overviews/contribute/inclusive-language-guide.md %}