created the become a partner page #260
Conversation
There was a problem hiding this comment.
@susanodii This is good, well done. We just have some vale suggestions that needs to be fixed. Please let me know when you do that. Did you use Gitpod? if you did, in the docs directory you can run
Vale filepath - filepath is a placeholder change to the docs file path
|
|
||
| It's required that all Community Partners are financially supporting the growth of the Mautic community as a :xref:`Corporate Member of Mautic`. Members pay for all memberships annually, and via our :xref:`Open Collective`. Prior to v2 of the Mautic governance model which came into effect on ``12th December 2023``, companies who sponsored Mautic at $100 per month or more were also eligible. Companies who were already sponsoring at this tier when the new governance model came into effect and continue to do so are 'grandfathered' in, providing that their sponsorship continues at this tier, for a period of 12 months. This gives them until ``12th December 2024`` to transition to becoming a Corporate Member in order to maintain their status as a Mautic Partner. | ||
|
|
||
| Practical Contribution |
There was a problem hiding this comment.
| Practical Contribution | |
| Practical contribution |
sentence-style capitalization
|
|
||
| Practical Contribution | ||
| ---------------------- | ||
| Of course money is not everything, and in fact contributing to Mautic in practical ways, whether that might be through code contributions, leading a team, organizing official events or meetups, contributing to the Documentation resources that we have or working on tasks in one of our five Community Teams are all vital to the growth of our community. |
There was a problem hiding this comment.
| Of course money is not everything, and in fact contributing to Mautic in practical ways, whether that might be through code contributions, leading a team, organizing official events or meetups, contributing to the Documentation resources that we have or working on tasks in one of our five Community Teams are all vital to the growth of our community. | |
| Of course, money isn't everything. Contributing to Mautic in practical ways, whether through code contributions, leading a team, organizing events or meetups, improving documentation, or working on tasks within the Community Teams, is essential to the growth of our community. |
More vale fixes
There was a problem hiding this comment.
@fakela @RCheesley I have made all the changes. Looking forward to your review
|
@RCheesley Please this needs to be merged. Thank you 🙏 |
There was a problem hiding this comment.
Thanks @susanodii for the PR - please don't use ..vale off and .. vale on unless there's a really good reason to do so - it should be used sparingly and only as a last resort.
I've suggested a bunch of Vale fixes and ways to improve the text, see what you think!
docs/links/open_collective.py
Outdated
| link_text = "Open Collective" | ||
| link_url = "https://opencollective.com" | ||
| link_url = "https://opencollective.com/mautic" |
There was a problem hiding this comment.
Please do not rename existing link files. These are already used elsewhere.
If you need to make a new link to a different url, it's super easy:
- Type
make linkin the terminal of your Gitpod or local VSCode window - Follow the steps requested
- It will generate a new link file, and tell you the XREF to copy to use in the text.
There was a problem hiding this comment.
cc @fakela @favour-chibueze in case you weren't aware of this.
| The Mautic Community Partners Program showcases organizations that are contributing to Mautic - both financially and practically - so that members of the community can find service providers who are :xref:`Makers rather than takers` to work with. These organizations represent the ideals of providing ongoing contributions that open source software rely upon. | ||
|
|
||
| How do organizations become a partner? | ||
| ====================================== |
There was a problem hiding this comment.
Please ensure that you are using the correct link nesting strategy.
H1: ###
H2: ***
H3: ===
H4: ---
H5: ~~~
This should be a H2, not a H3 heading.
| There are two elements to consider when reviewing an application to join the Partners Programme, both relate to whether the organization is supporting the community. | ||
|
|
||
| Financial contribution | ||
| ---------------------- |
There was a problem hiding this comment.
As above with the heading nesting :)
Co-authored-by: Ruth Cheesley <ruth@ruthcheesley.co.uk>
Co-authored-by: Ruth Cheesley <ruth@ruthcheesley.co.uk>
Co-authored-by: Ruth Cheesley <ruth@ruthcheesley.co.uk>
Co-authored-by: Ruth Cheesley <ruth@ruthcheesley.co.uk>
Co-authored-by: Ruth Cheesley <ruth@ruthcheesley.co.uk>
Co-authored-by: Ruth Cheesley <ruth@ruthcheesley.co.uk>
Co-authored-by: Ruth Cheesley <ruth@ruthcheesley.co.uk>
|
@RCheesley We went through the changes together on a call to check the headers and links. |
There was a problem hiding this comment.
Hi @susanodii thanks for your work on this! Only a couple of small things then we should be good to go!
docs/links/mautic_open_collective.py
Outdated
There was a problem hiding this comment.
This seems to be an invalid link file, and I'm not sure why it's needed? It looks like perhaps it's a duplicate of the docs/links/mautic_open_source_collective.py link?
I would recommend using this one, because it's a shorter and more relevant filename, adding the missing line:
link.xref_links.update({link_name: (link_text, link_url)})
Then removing the docs/links/mautic_open_source_collective.py file.
Please always use the make link command, it avoids making mistakes like this.
No description provided.