Open Hour 2020-SEP-10

January 23, 2021 - slangadmin

Agenda

Salt News and Updates

Community Manager Cassandra Faris

  • We’re always looking for suggested Open Hour topics. If there’s something you’d like to discuss in an Open Hour, contact Cassandra so she can put it on the agenda. We also encourage people to speak up via chat or verbally during the Open Hours.
  • Triage Tuesdays continue on Twitch along with R&D, Test Clinic, and Open Hour. All events are on the Salt Community Events which anyone can subscribe to.
  • Core Team Focus for the week
    • Development: Continued work on tech debt, ZeroMQ work, label and potential SEP discussions. The dev done date for Magnesium is scheduled for September 22.
    • Community: Continued work on the new contributor greeting and orientation tools, Docs Jam planning.
  • New feature: greeting bot
    • When someone makes their first contribution to the Salt project, they’ll get an automatic response that thanks them for their contribution and provides helpful information. This includes links to the Contributor Guide, Slack, Calendar, Wiki, and other resources.
    • When someone’s first merge occurs, they’ll now get an automatic response congratulating them.
    • Over time, the bot will probably have more automatic responses for common situations. We hope this will give people a better understanding of their contribution statuses and help them find information they may need.
  • Save the dates:
    • The Docs Jam is scheduled for October 7. This will be a time for community members to work together and improve documentation. Before the event, we’ll host a Docs Clinic to help prepare attendees. The Clinic will be September 30.
    • SaltConf 20 is scheduled for October 29. Registration will open in the coming weeks. We’re looking for speakers. If you’re interested in giving a talk, submit your proposal via the Call for Speakers form.

Community Advisory Board

Salt Community and Core Team
Discussion begins at 6:44 on the video

  • We are in the early stages of planning a Community Advisory Board that will do things such as monitor SEPs, influence technical direction and decisions, and help manage Working Groups. There are still a lot of things to define. We’ll iterate on board creation and logistics.
  • An Advisory Board exists to help lead and guide an organization. It’s a volunteer group that gives advice and support to a group. They’re specific with set guidelines and goals. It represents community members and, in this case, would work with both the community and the Core Team.
  • We’re looking for feedback on what this Advisory Board could do for the community and want to know how community members would like to be represented. Since we’re building this from scratch, we have options and flexibility in how to give the community a voice.
  • Advisory Board suggestions from contributors:
    • Better documentation.
    • Good communication that is clear and accessible in a timely manner. Communication should be focused on issue and PR status and changes that are relevant to the community.
    • Create and share consistent and informative meeting notes.
  • If you’re interested in joining the Advisory Board and taking on a leadership role in the Salt Community, contact Cassandra. We’re still working on the member selection process and board size. It would be a commitment of a few hours per month and would require meeting attendance and some light documentation.

SEP 26: Package Salt with Tiamat

SaltStack Engineers Bryce Larson and David Murphy
Discussion begins at 18:58 on the video

  • Motivation
    • When we make a new release, because all dependencies we package along with Salt, thre are so many that any time requirements change, it takes a lot of time to find source RPMs, etc. This holds us back from releasing more quickly.
    • The native Python environment for native minions is limited.
    • With Mac and Windows, we package dependencies all in one bundle and can create them within a couple hours. This makes us package Linux and other operating systems as easily. Then at release, users can simply tag and the PR is ready to go.
  • In use, it’s making it quicker and easier to build Salt on non-Windows and non-Mac operating systems. It’s being used successfully with Arista currently. Previously, we had to support and backport a cumbersome amount of packages making maintenance more difficult.
  • Regular packages will contain Py files that can be modified. There will also be a single binary available that people can run for testing use (but not production use).
  • Packages are built more quickly when using Tiamat.
  • Potential downsides
    • We have to keep up on CVEs in the dependencies that we use. However, this is now quicker to turn around and we can address CVEs more quickly.
    • Packages without many dependencies will now be architecture-dependent when being installed.

Open Community Discussion and Questions

Salt Community and Core Team

  • There were no general questions.