diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js index dc0ed585b..a3407f09e 100644 --- a/docs/.vuepress/config.js +++ b/docs/.vuepress/config.js @@ -5,6 +5,8 @@ const redirects = { "/Election2022.html": "/foundation/elections/2022.html", "/election2023.html": "/foundation/elections/2023.html", "/Election2025.html": "/foundation/elections/2025.html", + "/sigs/Marketing.html": "/sigs/Promo.html", + "/sigs/marketing/indico.html": "/sigs/promo/indico.html", }; module.exports = { @@ -372,14 +374,14 @@ module.exports = { children: ["/sigs/infrastructure/almapeople"], }, "/sigs/LiveMedia", - { - title: "Marketing SIG", - path: "/sigs/Marketing", - children: ["/sigs/marketing/indico"], - }, "/sigs/MediaAndEntertainmentSIG", "/sigs/Migration", "/sigs/ProcessForCreatingNewSIG", + { + title: "Promo SIG", + path: "/sigs/Promo", + children: ["/sigs/promo/indico"], + }, ], }, { diff --git a/docs/Contribute.md b/docs/Contribute.md index 088a814b1..5ceef9892 100644 --- a/docs/Contribute.md +++ b/docs/Contribute.md @@ -34,7 +34,7 @@ If any of those sound interesting to you, then take a look at the list of [SIGs] - [Infrastructure](https://chat.almalinux.org/almalinux/channels/infrastructure) - [Security](https://chat.almalinux.org/almalinux/channels/security) - [Documentation](https://chat.almalinux.org/almalinux/channels/sigdocumentation) -- [Marketing](https://chat.almalinux.org/almalinux/channels/marketing) +- [Promo SIG](https://chat.almalinux.org/almalinux/channels/marketing) - [Web presence](https://chat.almalinux.org/almalinux/channels/www) ## Help with reporting bugs and making fixes @@ -72,7 +72,7 @@ We want AlmaLinux to reach its users as fast as possible through a robust mirror ### 4. Promotion, blog posts, translations, and more! -If you are looking to flex skills not directly involved in development, we are always looking for guest blog posts, help with translations of our website, folks to staff events, and much more! Reach out in the [Marketing](https://chat.almalinux.org/almalinux/channels/marketing) channel for more info! +If you are looking to flex skills not directly involved in development, we are always looking for guest blog posts, help with translations of our website, folks to staff events, and much more! Reach out in the [Promo SIG](https://chat.almalinux.org/almalinux/channels/marketing) channel for more info! ### 5. More ways to help for DevOps & Programmers diff --git a/docs/Help-translating-site.md b/docs/Help-translating-site.md index 08adf9965..0ed888487 100644 --- a/docs/Help-translating-site.md +++ b/docs/Help-translating-site.md @@ -8,7 +8,7 @@ The content of [almalinux.org](https://almalinux.org/) is localized and translat # Help translating the site -The translations that get submitted through Weblate are automatically submitted to the [almalinux.org repo](https://github.com/AlmaLinux/almalinux.org) as a pull request from Weblate. Pull requests from Weblate are reviewed by a member of the marketing SIG or another team lead, and merged as appropriate. +The translations that get submitted through Weblate are automatically submitted to the [almalinux.org repo](https://github.com/AlmaLinux/almalinux.org) as a pull request from Weblate. Pull requests from Weblate are reviewed by a member of the Promo SIG or another team lead, and merged as appropriate. If you would like to help contribute to translations, you can do so by following the directions below! @@ -32,7 +32,7 @@ Then choose the language you want to translate to. For this example, I'll choose ![image](/images/weblate-send-translations.webp) -After translating from English to your chosen language (.e.g Hebrew) press on "Save and continue" and your translation will be sent eventually as a PR to the [almalinux.org repo](https://github.com/AlmaLinux/almalinux.org) and reviewed by a member of the marketing SIG or another team lead, then merged as appropriate. +After translating from English to your chosen language (.e.g Hebrew) press on "Save and continue" and your translation will be sent eventually as a PR to the [almalinux.org repo](https://github.com/AlmaLinux/almalinux.org) and reviewed by a member of the Promo SIG or another team lead, then merged as appropriate. ## Request new languages diff --git a/docs/Transparency.md b/docs/Transparency.md index 4f7c94013..692dec2d1 100644 --- a/docs/Transparency.md +++ b/docs/Transparency.md @@ -47,16 +47,16 @@ All the trademarks and assets are owned by AlmaLinux OS Foundation. Some assets were initially owned by CloudLinux, Inc, but were transferred from CloudLinux to the AlmaLinux OS Foundation. -| asset | What needs to be done | Status | -| :-------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------- | -| almalinux.org domain | Assign the rights to AlmaLinux, in theory, we can leave the control over it to the CloudLinux IT folks, same as over the rest AlmaLinux infrastructure | DONE as of May 24, 2021 | -| AlmaLinux OS trademark sublicense | Request CloudLinux Foundation to re-assign AlmaLinux OS from CL to AlmaLinux OS Foundation | DONE, Sublicense ID number 20210506-0001 | -| social media accounts | Reassign them to AlmaLinux OS Foundation. | [In Progress](/Marketing.html#social-media-accounts) | -| github almalinux account | Already open-sourced, nothing needs to be done | DONE | -| Build/Test system | Work has started to open source it, but it will require some time. ETA - end of Q2 or Q3 | [DONE](https://github.com/AlmaLinux/build-system) | -| RPM signing keys | Need to be "assigned" as belonging to AlmaLinux OS Foundation, need to come up with signing ceremony, who controls it | Q3 2023: Need to come up with rules for holding keys | -| EV certificate for Secure Boot | We've been on an AlmaLinux owned cert since 8.8/9.2 | DONE | -| Logo License for the foundation | Transfer documents, and initial acquisition document uploaded into a Logo Transfer folder, transfer document signed | DONE - all assets in the Google drive | +| asset | What needs to be done | Status | +| :-------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------- | +| almalinux.org domain | Assign the rights to AlmaLinux, in theory, we can leave the control over it to the CloudLinux IT folks, same as over the rest AlmaLinux infrastructure | DONE as of May 24, 2021 | +| AlmaLinux OS trademark sublicense | Request CloudLinux Foundation to re-assign AlmaLinux OS from CL to AlmaLinux OS Foundation | DONE, Sublicense ID number 20210506-0001 | +| social media accounts | Reassign them to AlmaLinux OS Foundation. | [In Progress](/sigs/Promo.html#social-media-accounts) | +| github almalinux account | Already open-sourced, nothing needs to be done | DONE | +| Build/Test system | Work has started to open source it, but it will require some time. ETA - end of Q2 or Q3 | [DONE](https://github.com/AlmaLinux/build-system) | +| RPM signing keys | Need to be "assigned" as belonging to AlmaLinux OS Foundation, need to come up with signing ceremony, who controls it | Q3 2023: Need to come up with rules for holding keys | +| EV certificate for Secure Boot | We've been on an AlmaLinux owned cert since 8.8/9.2 | DONE | +| Logo License for the foundation | Transfer documents, and initial acquisition document uploaded into a Logo Transfer folder, transfer document signed | DONE - all assets in the Google drive | ## Minutes of AlmaLinux OS Foundation Board Meetings diff --git a/docs/sigs/ProcessForCreatingNewSIG.md b/docs/sigs/ProcessForCreatingNewSIG.md index fdae65f05..041b41521 100644 --- a/docs/sigs/ProcessForCreatingNewSIG.md +++ b/docs/sigs/ProcessForCreatingNewSIG.md @@ -45,7 +45,7 @@ Though we hope to have provided all of the feedback ahead of time, if the board ### 4. Approval and Announcement -Once the proposal has been reviewed and deemed acceptable, the board will formally approve the creation of the new SIG, and the pull request will be merged into the wiki. The approval will be announced by the marketing SIG through appropriate communication channels, such as mailing lists, forums, and social media. The announcement will include: +Once the proposal has been reviewed and deemed acceptable, the board will formally approve the creation of the new SIG, and the pull request will be merged into the wiki. The approval will be announced by the Promo SIG through appropriate communication channels, such as mailing lists, forums, and social media. The announcement will include:
  1. The title and objectives of the new SIG.
    2. diff --git a/docs/sigs/Marketing.md b/docs/sigs/Promo.md similarity index 77% rename from docs/sigs/Marketing.md rename to docs/sigs/Promo.md index a27aa6d17..511e6ca01 100644 --- a/docs/sigs/Marketing.md +++ b/docs/sigs/Promo.md @@ -1,10 +1,10 @@ --- -title: "Marketing SIG" +title: "Promo SIG" --- -# Marketing SIG +# Promo SIG -The Marketing team is responsible for AlmaLinux branding consistency, marketing and outreach efforts, and overall public presence. Marketing is often an overlooked or eschewed term in open source, but without marketing efforts it's a whole lot harder for your audience to find you. We try to make it easy for the users who need a free enterprise Linux distribution to find us. +The Promo SIG (formerly the Marketing SIG) is responsible for AlmaLinux branding consistency, promotion and outreach efforts, and overall public presence. We try to make it easy for the users who need a free enterprise Linux distribution to find us. You can read more about the name change in [The Marketing SIG is now the Promo SIG](https://almalinux.org/blog/2026-10-15-the-marketing-sig-is-now-the-promo-sig/). ## How to Join @@ -12,11 +12,11 @@ Joining is easy! You can show up to a meeting, pick up an issue from the list by **Where we chat** -We use the [~Marketing](https://chat.almalinux.org/almalinux/channels/marketing) channel for communication on the AlmaLinux mattermost server. +We use the [Promo SIG](https://chat.almalinux.org/almalinux/channels/marketing) channel for communication on the AlmaLinux Mattermost server. You can also reach us by email at [promo-sig@almalinux.org](mailto:promo-sig@almalinux.org). **Where/how we meet** -Meetings are every other Thursday on Google Meet at 9pm UTC. Join the Marketing channel on [chat.almalinux.org](https://chat.almalinux.org/almalinux/channels/marketing) and ask benny for the meeting invite! Our meeting notes are kept in [Google drive](https://docs.google.com/document/d/1OK8mQSU-EucCT-VdFVOd87BECmVSXIKXkG7uhLubs9o/edit#heading=h.9ynhotw081jk). +Meetings are every other Thursday on Google Meet at 9pm UTC. Join the Promo SIG channel on [chat.almalinux.org](https://chat.almalinux.org/almalinux/channels/marketing) and ask benny for the meeting invite! Our meeting notes are kept in [Google drive](https://docs.google.com/document/d/1OK8mQSU-EucCT-VdFVOd87BECmVSXIKXkG7uhLubs9o/edit#heading=h.9ynhotw081jk). ## Activities, projects, and deliverables @@ -58,13 +58,13 @@ These members share responsibilities between and among each other. We also have a variety of folks who help us with PR, social media, and website maintenance through submissions to chat or just PRs to the [website repo](https://github.com/AlmaLinux/almalinux.org). -We also contract with a Publice Relations team who joins the Marketing SIG meetings +We also contract with a Public Relations team who joins the Promo SIG meetings. -# Marketing accounts +# Promo SIG accounts -Here is where we track the different accounts that marketing uses, and who has admin rights for them. +Here is where we track the different accounts that the Promo SIG uses, and who has admin rights for them. -### Various marketing-adjacent accounts +### Other accounts - [Canva](https://canva.com) - we have a non-profit Pro teams account - benny has admin/owner rights @@ -80,7 +80,7 @@ These accounts are actively monitored, updated, and managed by the SIG on a regu - [Twitter (x)](https://twitter.com/almalinux) - password in Vaultwarden - [LinkedIn](https://www.linkedin.com/company/almalinuxos/) - benny and Jack have 'owner' rights - [BlueSky](bsky.app/almalinux) - password in Vaultwarden -- [Youtube](https://www.youtube.com/@AlmaLinuxOS) - benny and Jack have 'owner' rights - others (in and outside the marketing SIG) have "content manager" rights +- [Youtube](https://www.youtube.com/@AlmaLinuxOS) - benny and Jack have 'owner' rights - others (in and outside the Promo SIG) have "content manager" rights - [Instagram](https://www.instagram.com/almalinuxos/) - password in Vaultwarden #### Inactive (placeholder) accounts diff --git a/docs/sigs/README.md b/docs/sigs/README.md index a9b62cc17..8f86eb9cf 100644 --- a/docs/sigs/README.md +++ b/docs/sigs/README.md @@ -17,9 +17,9 @@ The following SIGs are already established: - [HPC and AI](/sigs/HPCandAI) - The AlmaLinux High performance computing and AI SIG. - [Infrastructure](/sigs/Infrastructure) - The AlmaLinux OS infrastructure team. - [Live Media](/sigs/LiveMedia) - The AlmaLinux OS Live Media maintainers. -- [Marketing](/sigs/Marketing) - The AlmaLinux OS Marketing SIG. - [Media and Entertainment](/sigs/MediaAndEntertainmentSIG) - The AlmaLinux OS Media and Entertainment SIG. - [Migration](/sigs/Migration) - The AlmaLinux OS Migration maintainers. +- [Promo](/sigs/Promo) - The AlmaLinux OS Promo SIG (formerly the Marketing SIG). # Additional Resources diff --git a/docs/sigs/marketing/indico.md b/docs/sigs/promo/indico.md similarity index 94% rename from docs/sigs/marketing/indico.md rename to docs/sigs/promo/indico.md index 6617d5cee..676f7d19e 100644 --- a/docs/sigs/marketing/indico.md +++ b/docs/sigs/promo/indico.md @@ -4,13 +4,13 @@ title: "Managing events.almalinux.org" # Managing events.almalinux.org -Our events are managed using [Indico](https://getindico.io/), the open source software created and developed at CERN. Our install, at [events.almalinux.org](https://events.almalinux.org) (documentation at [learn.getindico.io](https://learn.getindico.io/)), is kept up to date by the AlmaLinux Infra SIG, but events on it are managed by the marketing SIG. This document helps us consistently create new events to the community. +Our events are managed using [Indico](https://getindico.io/), the open source software created and developed at CERN. Our install, at [events.almalinux.org](https://events.almalinux.org) (documentation at [learn.getindico.io](https://learn.getindico.io/)), is kept up to date by the AlmaLinux Infra SIG, but events on it are managed by the Promo SIG. This document helps us consistently create new events to the community. # Creating different events When creating different types of events, it's important that you follow the directions below so that our community can count on events being presented in a consistent way. -All events should start as unlisted events to be published after they're reviewed by the marketing SIG chair. +All events should start as unlisted events to be published after they're reviewed by the Promo SIG chair. ## Webinars @@ -31,7 +31,7 @@ After it's created, there are some more adjustments to make: ## SIG meetings 1. Navigate to to the [SIGs category](https://events.almalinux.org/category/1/manage/), and choose the appropriate category there for the specific SIG. -1. Create a **meeting** event, naming it appropriately for the SIG using [$freqency - $signame meeting] as the pattern (for example, Bi-weekly Marketing SIG meeting). +1. Create a **meeting** event, naming it appropriately for the SIG using [$freqency - $signame meeting] as the pattern (for example, Bi-weekly Promo SIG meeting). 1. Once created, on the default settings page update the **Contact title** and **Email** to match the SIG in question's contact details. 1. Under \*_Timetable_ click _Add new_ and _Contribution_ 1. use the same title as for the full event, in the description add details about the event (general agenda, where they meet, and where to get the meeting link at least).