Adds Slack info to various docs

Signed-off-by: Steven <[email protected]>

Author: stevsmit

CONTRIBUTING.md

@@ -27,7 +27,7 @@ Participating in the InstructLab project can come by contributing to any one of
 
 Help on open source projects is always welcome and there is always something that can be improved. For example, documentation (like the text you are reading now) can always use improvement, code can always be clarified, variables or functions can always be renamed or commented on, and there is always a need for more test coverage. If you see something that you think should be fixed, take ownership!
 
-To contribute code or documentation, please submit a pull request to the relevant repository. Note that contribution to any repository has its own set of requirements and expectations, and users should familiar themselves with those expectations before contributing.
+To contribute code or documentation, please submit a pull request to the relevant repository. Note that contribution to any repository has its own set of requirements and expectations, and users should familiarize themselves with those expectations before contributing.
 
 ### ilab command-line interface (CLI) tool repository
 

InstructLabSlackModerationGuide.md

@@ -5,13 +5,13 @@ abuse in the Slack workspace and to provide space administrators with an easy to
 
 # Reporting Abuse
 
-Should any community members using the InstructLab Slack workspace feel that they have experienced behavior that violates our [project code of conduct](https://github.com/instructlab/community/blob/main/CODE_OF_CONDUCT.md), they are welcome and encouraged to contact the members of the [Code of Conduct Committee](https://github.com/instructlab/community/blob/main/COCC.md) for help. Mentioning <code>@cocc</code> will page all members of the committee so that they can assist you.
+Should any community members using the InstructLab Slack workspace feel that they have experienced behavior that violates our [project Code of Conduct](https://github.com/instruct-lab/community/blob/main/CODE_OF_CONDUCT.md), they are welcome and encouraged to contact the members of the [Code of Conduct Committee](https://github.com/instruct-lab/community/blob/main/COCC.md) for help. Mentioning <code>@cocc</code> will page all members of the committee so that they can assist you.
 
 In the event that you do not receive help within a timely fashion - and we will do our very best to respond right away - you can ask for help from the workspace admins by either joining channel <code>#admin</code> or mentioning <code>@admins</code>.
 
 # Moderation Guide
 
-Moderation activities can only be performed by users who are designated as workspace adminstrators.
+Moderation activities can only be performed by users who are designated as workspace administrators.
 
 ## Workspace Administrators
 
@@ -41,9 +41,9 @@ At time of writing, our workspace adminstrators/moderators are as follows:
 ## How We Moderate
 
 ## Deleting Inappropriate Comments 
-Upon report of abuse to the [Code of Conduct Committee](https://github.com/instructlab/community/blob/main/COCC.md) or, alternatively if needed to the workspace adminstrators due to a coverage gap, the appropriate parties will assess the situation.
+Upon report of abuse to the [Code of Conduct Committee](https://github.com/instruct-lab/community/blob/main/COCC.md) or, alternatively if needed to the workspace administrators due to a coverage gap, the appropriate parties will assess the situation.
 
-The first step will be to remind folks to abide by the [project code of conduct](https://github.com/instructlab/community/blob/main/CODE_OF_CONDUCT.md).  
+The first step will be to remind folks to abide by the [project Code of Conduct](https://github.com/instruct-lab/community/blob/main/CODE_OF_CONDUCT.md).  
 
 Inappropriate or offensive messages [will be deleted](https://slack.com/help/articles/202395258-Edit-or-delete-messages#delete-a-message).
 

README.md

@@ -29,15 +29,15 @@ The following documentation shows you an overview of the workflow, and the resou
 
 The `ilab` tool allows you to interact with the IBM AI model `Merlinite`, contribute your own information, and train the model locally. 
 
-> **Note:** Before proceeding, it might be beneficial to check out the [Contributing](https://github.com/instructlab/community/blob/main/CONTRIBUTING.md) guide for an overview of contributing practices and expectations.
+> **Note:** Before proceeding, it might be beneficial to check out the [Contributing](https://github.com/instruct-lab/community/blob/main/CONTRIBUTING.md) guide for an overview of contributing practices and expectations. Additionally, you should consider joining the [InstructLab community Slack channel](https://github.com/instructlab/community/blob/main/InstructLabSlackGuide.md).
 
 1. Navigate to the `ilab` CLI repository and follow the instructions in the [README.md](https://github.com/instructlab/cli/blob/main/README.md). The README.md instructs you on how to perform the following: 
 
     a. In the [Getting started](https://github.com/instructlab/cli/blob/main/README.md#-getting-started) section of the README.md file, you can install the `ilab` tool, set up your local environment, and download the IBM `Merlinite` AI model.
 
-    b. You can then create your own data sets to feed into and train the model. In the taxonomy project, there are two types of data you can serve to the model: skills and knowledge. There are a few different types of skills and knowledge you can create. For more detailed information on the types, see the Taxonomy [README.md](https://github.com/instructlab/taxonomy/blob/main/README.md#getting-started-with-skill-contributions). 
+    b. You can then create your own data sets to feed into and train the model. In the taxonomy project, there are two types of data you can serve to the model: skills and knowledge. There are a few different types of skills and knowledge you can create. For more detailed information on the types, see the Taxonomy [README.md](https://github.com/instructlab/taxonomy/blob/main/README.md#welcome-to-the-instructlab-taxonomy). 
 
-    c. In your local taxonomy repository, generated after the [Initialize lab](https://github.com/instructlab/cli/blob/main/README.md#%EF%B8%8F-initialize-lab) step, navigate to the path that you want to add information to. You can see a flow chart of the paths in this file [taxonomy_diagram](https://github.com/instructlab/taxonomy/blob/main/docs/taxonomy_diagram.png). Create a `qna.yaml` file in that path with your contributions. 
+    c. In your local taxonomy repository, generated after the [Initialize lab](https://github.com/instructlab/instructlab/blob/main/README.md#-installing-ilab) step, navigate to the path that you want to add information to. You can see a flow chart of the paths in this file [taxonomy_diagram](https://github.com/instruct-lab/taxonomy/blob/main/docs/taxonomy_diagram.png). Create a `qna.yaml` file in that path with your contributions. 
 
     d. [Serve and train the model](https://github.com/instructlab/cli/blob/main/README.md#-train-the-model) with your contributions to see if the model can answer questions more accurately. 
 
@@ -106,14 +106,17 @@ SPDX-License-Identifier: [Apache-2.0](https://spdx.org/licenses/Apache-2.0)
 
 If you would like to see the detailed LICENSE click [here](LICENSE).
 
-## Information resources
+## Contact resources
 
-- [InstructLab Slack]() FORTHCOMING
+- [InstructLab Slack](https://instruct-lab.slack.com). See the InstuctLab Slack Guide for directions on how to join.
+- [InstructLab Slack Guide](https://github.com/instruct-lab/community/blob/main/InstructLabSlackGuide.md)
+- [InstructLab Slack Moderation Guide](https://github.com/instruct-lab/community/blob/main/InstructLabSlackModerationGuide.md)
 - [InstructLab Mailing lists]() FORTHCOMING
-- In the meantime, feel free to start a [discussion](https://github.com/orgs/instructlab/discussions).
+- [Discussion](https://github.com/orgs/instruct-lab/discussions).
 
 ## Quick Links
 
+# [FAQ](FAQ.md)
 * [LICENSE](LICENSE)
 * [README](README.md)
 * [CONTRIBUTING](CONTRIBUTING.md)

docs/README.md

@@ -61,5 +61,5 @@ We received so many at the beginning, and with jokes being "in the eye of the be
 
 ## Works Cited on this Page
 * [Christianity in Nepal](https://en.wikipedia.org/wiki/Christianity_in_Nepal), Wikipedia, Wikimedia Foundation, 24 April 2024.
-* [Concepts of Biology - 1st Canadian Edition](https://opentextbc.ca/biology/), Chapter 11.3 _Circulatory and Respiratory Systems_. Copyright 2015 by Charles Molnar and Jane Gair, licensed under a [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/). No modications were made to the text.
-* [World History, volume 2: from 1400](https://openstax.org/details/books/world-history-volume-2), Chapter 6.3 _Capitalism and the First Industrial Revolution_. Copyright 2022 Rice University, licensed under a [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/). No modications were made to the text.
+* [Concepts of Biology - 1st Canadian Edition](https://opentextbc.ca/biology/), Chapter 11.3 _Circulatory and Respiratory Systems_. Copyright 2015 by Charles Molnar and Jane Gair, licensed under a [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/). No modifications were made to the text.
+* [World History, volume 2: from 1400](https://openstax.org/details/books/world-history-volume-2), Chapter 6.3 _Capitalism and the First Industrial Revolution_. Copyright 2022 Rice University, licensed under a [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/). No modifications were made to the text.

governance.md

@@ -17,7 +17,7 @@ At launch, the InstructLab Project will not have an Oversight Committee to avoid
 
 Except where otherwise noted, decisions should always start at the most local level of project governance. For example, decisions that affect only one project, such as the taxonomy repository and not the `ilab` CLI tool, can  happen within that project. While communication between the different project teams is important as they are all interconnected, minor decisions do not need organization-wide consensus and can be moved forward at the project level.
 
-Changes in maintainership and other governance are announced on the **TODO: InstructLab mailing list**.
+Changes in maintainership and other governance are currently announced on the InstructLab community Slack channel. Directions to join the Slack channel can be found [here](https://github.com/instructlab/community/blob/main/InstructLabSlackGuide.md). In the future, a mailing list will be established. 
 
 ## Project Maintainers overview
 
@@ -66,7 +66,7 @@ The election will proceed according to the following process:
 
 1. The nomination period will be three weeks. This period starts from the day after an organization Maintainer opening becomes available.
 
-1. The nomination must be made by the **TODO: InstructLab mailing list**.
+1. The nomination must be made on the InstructLab community Slack channel. Directions to join the Slack channel can be found [here](https://github.com/instructlab/community/blob/main/InstructLabSlackGuide.md). In the future, a mailing list will be established for nominations.
 
 1. After a nominated individual(s) agrees to be a candidate for the Oversight Committee, project Maintainers will vote. The voting period will be open for a minimum of three business days. It will remain open until a [supermajority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) of project Maintainers has voted. Only current Maintainers of active projects are eligible to vote.
 
@@ -78,7 +78,7 @@ The election will proceed according to the following process:
 
 Project Maintainers or Oversight Committee members may resign or could be expelled as follows: 
 
-* Maintainers or an Oversight Committee member may step down through email. Within 7 calendar days, organization contributors and Maintainers will be notified of the change through an email from **TODO: InstructLab mailing list**.
+* Maintainers or an Oversight Committee member may step down through email. Within 7 calendar days, organization contributors and Maintainers will be notified on the InstructLab community Slack channel. Directions to join the Slack channel can be found [here](https://github.com/instructlab/community/blob/main/InstructLabSlackGuide.md). In the future, a mailing list will be established. 
 
 * After an Oversight Committee member steps down, they become an emeritus Maintainer.
 
@@ -105,7 +105,7 @@ The secondary decision making process is done by voting. The following items mus
 * Licensing and intellectual property changes such as new logos or wordmarks (simple majority)
 * Adding, archiving, or removing projects (simple majority)
 
-Other decisions may, but do not need to be, called out and put up for decision on the **TODO: InstructLab mailing list**. This can be done by anyone at any time. By default, any decisions called to a vote will be for a _simple majority_ vote.
+Other decisions may, but do not need to be, called out and put up for decision  on the InstructLab community Slack channel. Directions to join the Slack channel can be found [here](https://github.com/instructlab/community/blob/main/InstructLabSlackGuide.md). In the future, a mailing list will be established. This can be done by anyone at any time. By default, any decisions called to a vote will be for a _simple majority_ vote.
 
 ## Code of Conduct
 
@@ -115,7 +115,7 @@ The CoCC is responsible for investigating, evaluating, and recommending remedies
 
 Current CoCC members can be found on the [Code of Conduct Committee](https://github.com/instructlab/community/blob/main/COCC.md) page.
 
-Possible Code of Conduct violations should be reported to the Code of Conduct Committee at **TODO: Private CoC mailing list**.
+Possible Code of Conduct violations should be reported to the Code of Conduct Committee on the InstructLab community Slack channel. Directions to join the Slack channel can be found [here](https://github.com/instructlab/community/blob/main/InstructLabSlackGuide.md). In the future, a mailing list will be established.
 
 ## Developer Certificate of Origin (DCO) and Licenses