-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create 2025.md #111
base: main
Are you sure you want to change the base?
Create 2025.md #111
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @RCheesley,
I left reviews here.
Feel free to commit those you'd like, and ignore that you find not applicable. 😊
Thanks!
Co-authored-by: Ayu Adiati <[email protected]>
Co-authored-by: Ayu Adiati <[email protected]>
Co-authored-by: Ayu Adiati <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the great review @adiati98 - I'll commit those suggestions now!
Co-authored-by: Ayu Adiati <[email protected]>
Think we're good to go - @adiati98 would you mind doing the final review to make sure I didn't miss anything? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @RCheesley,
I've dropped the final reviews here.
I think other than these, there is no more issue. ✨
- [Why Low- and No-Code Contributions Matter](#why-low-and-no-code-contributions-matter) | ||
- [Ways to Contribute](#ways-to-contribute) | ||
- [1. **Documentation**](#1-documentation) | ||
- [2. **Translations**](#2-translations) | ||
- [3. **Community Engagement**](#3-community-engagement) | ||
- [4. **Design and User Experience (UX)**](#4-design-and-user-experience-ux) | ||
- [5. **Marketing**](#5-marketing) | ||
- [6. **Knowledgebase**](#6-knowledgebase) | ||
- [How to Get Started](#how-to-get-started) | ||
- [Useful Resources](#useful-resources) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: Do we want to include the section headers in line 133-147 in the TOC?
suggestion: Because Mautic uses "sentence' style for titles, let's fix the capitalization here, too. :)
- [Why Low- and No-Code Contributions Matter](#why-low-and-no-code-contributions-matter) | |
- [Ways to Contribute](#ways-to-contribute) | |
- [1. **Documentation**](#1-documentation) | |
- [2. **Translations**](#2-translations) | |
- [3. **Community Engagement**](#3-community-engagement) | |
- [4. **Design and User Experience (UX)**](#4-design-and-user-experience-ux) | |
- [5. **Marketing**](#5-marketing) | |
- [6. **Knowledgebase**](#6-knowledgebase) | |
- [How to Get Started](#how-to-get-started) | |
- [Useful Resources](#useful-resources) | |
- [Why low- and no-code contributions matter](#why-low-and-no-code-contributions-matter) | |
- [Ways to contribute](#ways-to-contribute) | |
- [1. **Documentation**](#1-documentation) | |
- [2. **Translations**](#2-translations) | |
- [3. **Community engagement**](#3-community-engagement) | |
- [4. **Design and user experience (UX)**](#4-design-and-user-experience-ux) | |
- [5. **Marketing**](#5-marketing) | |
- [6. **Knowledgebase**](#6-knowledgebase) | |
- [How to get started](#how-to-get-started) | |
- [Useful resources](#useful-resources) |
|
||
Open source projects thrive not only from code contributions but also from the community's efforts in other areas. Low- and no-code contributions help Mautic grow and improve through better documentation, translations, community support, and more. If you're not a developer but want to contribute to open source, there are plenty of ways to get involved! | ||
|
||
## Ways to Contribute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Ways to Contribute | |
## Ways to contribute |
- **Contribute to Mautic’s Knowledgebase**: Write helpful articles, how-to guides, or troubleshoot common issues in the [Mautic Knowledgebase](https://kb.mautic.org/). | ||
- **Update existing articles**: Review and update articles to ensure they reflect the latest Mautic features and best practices. | ||
|
||
## How to Get Started |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## How to Get Started | |
## How to get started |
|
||
Browse through the **[Mautic Low- and No-Code Issues](https://github.com/orgs/mautic/projects/21/)**. There are specific tags like `documentation`, `design`, or `translation` to help you find no-code contribution opportunities. Use the tabs to navigate between the types of tasks. | ||
|
||
6. **Make Your Contribution** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: We might want to fix the capitalization here for consistency.
6. **Make Your Contribution** | |
6. **Make your contribution** |
- **Translations**: Get involved by translating at [Mautic Translations](https://www.transifex.com/mautic/mautic/). | ||
- **Community**: Help in the forums or join conversations on Mautic’s social media platforms. | ||
|
||
7. **Submit Your Contribution** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
7. **Submit Your Contribution** | |
7. **Submit your contribution** |
|
||
For documentation, submit your work via a pull request on GitHub. If you're contributing in October, make sure to reference Hacktoberfest in your contribution notes so that the team know to add the `hacktoberfest-accepted` label. For other tasks like translations or writing on the knowledgebase, follow the submission process on Transifex or the knowledgebase and then follow the steps below to have your contribution validated and counted. | ||
|
||
For low- and no-code contributions where there is no pull request to make (e.g. marketing, design etc.), we've created a file in this repository (named YYYY.md, for example 2025.md) where we will maintain an activity log, which will allow you to submit a pull request (so that it counts for Hacktoberfest and as a Mautic contribution) each time you complete a task. **Please note:** Some teams work on Jira, and the issues there are automatically counted as a contribution when they are completed and assigned to a person. If you work with issues on Jira, you don't need to make a PR here for those tasks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestions: I see around (also on GitHub docs) that file names are commonly wrapped in backticks. It's your call whether to wrap the file names here in backticks or not.
For low- and no-code contributions where there is no pull request to make (e.g. marketing, design etc.), we've created a file in this repository (named YYYY.md, for example 2025.md) where we will maintain an activity log, which will allow you to submit a pull request (so that it counts for Hacktoberfest and as a Mautic contribution) each time you complete a task. **Please note:** Some teams work on Jira, and the issues there are automatically counted as a contribution when they are completed and assigned to a person. If you work with issues on Jira, you don't need to make a PR here for those tasks. | |
For low- and no-code contributions where there is no pull request to make (e.g. marketing, design etc.), we've created a file in this repository (named `YYYY.md`, for example `2025.md`) where we will maintain an activity log, which will allow you to submit a pull request (so that it counts for Hacktoberfest and as a Mautic contribution) each time you complete a task. **Please note:** Some teams work on Jira, and the issues there are automatically counted as a contribution when they are completed and assigned to a person. If you work with issues on Jira, you don't need to make a PR here for those tasks. |
To make a PR to have your contribution counted, follow these steps: | ||
|
||
1. Log in to GitHub with your GitHub account | ||
2. Click the Fork button at the top right of this repository | ||
3. Edit the relevant file for the current year, and add your contribution and a link to the issue at the bottom of the list. Follow any instructions that are written as to the formatting to use | ||
4. Click the button to commit your changes, and make a new branch (ideally call it something relevant to this contribution, so you know what each one is) | ||
5. Go back to the [Mautic low and no-code](https://github.com/mautic/low-no-code) repository | ||
6. Click the button at the top of the page to make a new pull request | ||
7. Add the details about your contribution, and submit the pull request for the team to review | ||
8. Celebrate! 🥳 | ||
|
||
Please follow this process for each contribution, so that it counts for Hacktoberfest or Mautic's contributions. The team will add the label `hacktoberfest-accepted` for relevant contributions, which will allow you to have your contributions counted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestions: (Sorry I totally missed this!)
Because these are part of number 7, we want to give indentation. However, there is one problem. The list for the steps will be in roman numerals because they are nested. Another way is to use unordered list here if you'd like.
To make a PR to have your contribution counted, follow these steps: | |
1. Log in to GitHub with your GitHub account | |
2. Click the Fork button at the top right of this repository | |
3. Edit the relevant file for the current year, and add your contribution and a link to the issue at the bottom of the list. Follow any instructions that are written as to the formatting to use | |
4. Click the button to commit your changes, and make a new branch (ideally call it something relevant to this contribution, so you know what each one is) | |
5. Go back to the [Mautic low and no-code](https://github.com/mautic/low-no-code) repository | |
6. Click the button at the top of the page to make a new pull request | |
7. Add the details about your contribution, and submit the pull request for the team to review | |
8. Celebrate! 🥳 | |
Please follow this process for each contribution, so that it counts for Hacktoberfest or Mautic's contributions. The team will add the label `hacktoberfest-accepted` for relevant contributions, which will allow you to have your contributions counted. | |
To make a PR to have your contribution counted, follow these steps: | |
1. Log in to GitHub with your GitHub account | |
2. Click the Fork button at the top right of this repository | |
3. Edit the relevant file for the current year, and add your contribution and a link to the issue at the bottom of the list. Follow any instructions that are written as to the formatting to use | |
4. Click the button to commit your changes, and make a new branch (ideally call it something relevant to this contribution, so you know what each one is) | |
5. Go back to the [Mautic low and no-code](https://github.com/mautic/low-no-code) repository | |
6. Click the button at the top of the page to make a new pull request | |
7. Add the details about your contribution, and submit the pull request for the team to review | |
8. Celebrate! 🥳 | |
Please follow this process for each contribution, so that it counts for Hacktoberfest or Mautic's contributions. The team will add the label `hacktoberfest-accepted` for relevant contributions, which will allow you to have your contributions counted. |
|
||
Please follow this process for each contribution, so that it counts for Hacktoberfest or Mautic's contributions. The team will add the label `hacktoberfest-accepted` for relevant contributions, which will allow you to have your contributions counted. | ||
|
||
8. **Get Your Rewards** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
8. **Get Your Rewards** | |
8. **Get your rewards** |
This PR creates the 2025.md file for the new year's low/no code contribution recognition.
I've added a line for the hacktoberfest table and for the ongoing contributions just so it's clear how to write the contributions.