We have a number of ways for folks to learn more about InstructLab, communicate with the project maintainers and their fellow users, or subscribe for project updates.
If you need help getting started with using or contributing to InstructLab, the best way to do so is via our project Slack workspace or email lists rather than posts on social media.
To stay up to date on when meetings are added and how to join them, subscribe to the InstructLab project calendar by clicking the button in the bottom right of the calendar view or simply add the InstructLab calendar ics feed URL to your preferred mail app.
The project will host more meetings as it evolves, but those we have already set up are listed here.
We host weekly community meetings each Tuesday at 14:00 UTC. (time zone converter)
Weekly community meetings will feature regular updates on project happenings, including announcements, demos, places to meet with the project maintainers, and more. The second half of the hour will be dedicated to community organization and maintenance.
If you are new to the InstructLab project, the weekly community meeting is a great place to get started!
We host weekly InstructLab CLI meetings each Thursday at 14:00 UTC. (time zone converter)
Weekly InstructLab CLI meetings will feature announcements from the CLI Maintainers team about the CLI project, overviews of the general roadmap the project is taking via our Milestones as well as the Project Board, and dedicated time for discussing the direction of the project.
If you are particularly interested in the CLI aspect of the InstructLab project, we encourage you to join this meeting!
We have two dedicated Office Hours slots each Thursday so we're able to meet with folks across different time zones. See the InstructLab project calendar to select which time works best for you.
We host daily Triage Team stand up meetings at 18:30 UTC. (time zone converter). In this meeting, triagers speak and discuss possible issues or successes with the different PRs put into the https://github.com/instructlab/taxonomy repo.
If you have questions or ideas, we have an open door policy and would love for you to join us.
For real-time chat discussions, please join our InstructLab Slack workspace.
Slack history is deleted after 90 days, so for conversations that should preserved for a longer period use the project mailing lists.
If you want to add feedback or think there is a "large issue" to discuss, a mailing list or a specific repository issue tracker is a good place to have the conversation rather than Slack. If you are unsure of where to comment, users@instructlab.ai is the best place to start.
We use the following email lists for project communications. Subscriptions requires a Google account.
To join a list, click the list name in the table below to visit the list subscription page. If an entry below is noted as an email alias or private to a specific group, you will not be able to join.
| Name | Topic(s) |
|---|---|
| announce | announcements only list for news about releases and other project wide updates; very low traffic |
| coc | email alias for the Code of Conduct Committee, used to report violations privately to the committee |
| community | community discussions, such as sharing a tutorial link or getting help with a meetup talk |
| dev | developer discussions, both front and backend |
| maintainers | maintainer only discussions that must be private, to be used very sparingly |
| PyPI | maintainers only list used for PyPI packaging |
| security | security disclosure notifications |
| security-reporting | email alias to report a possible security vulnerability to project security team |
| users | user feedback on project or help getting started, e.g. "my first PR" |
This table describes who can join each email list, view posts, etc. Some lists, such as the coc and security lists are private so that reporting may be handled with discretion.
| List Name | who can join group | who can view posts | who can post to group | who can post as group |
|---|---|---|---|---|
| announce | anyone | anyone | admins | admins |
| community | anyone | anyone | anyone | admins |
| dev | anyone | anyone | members | noone |
| maintainers | invite only - project maintainers | members | members | admins |
| pypi | invite only - project maintainers | members | members | admins |
| security | anyone | anyone | admins | admins |
| users | anyone | anyone | members | noone |
We are using the GitHub discussion boards in each repo for cases where we need to document things quickly but ephemerally, such as working together as a community to squash a nasty bug. In that case, a link to the appropriate discussion board post will be sent to the relevant project mailing lists so folks can follow along on GitHub. Rather than use the discussion boards to discuss proposals for enhancements or to request help with using InstructLab, please reach out on the project email lists or Slack.
We regularly post model builds on the project's Hugging Face page.
The InstructLab project community maintainers will post regular updates on these social media services. Our project hashtag is #InstructLab.
Follow our LinkedIn page for updates.
Follow us on X for our latest Tweets. Er, Xes. Er, posts of some sort.
Subscribe to the InstructLab YouTube channel for regular updates when we post video tutorials or playlists of talks about InstructLab from conferences and meetups.
Have you made a video tutorial, how to document, or other content that would be helpful to folks involved in the InstructLab community? Thank you!
We would love to help you share it. Please file an issue in the Community Repo or send a note to the community email list to let us know about what you have created.