-
Notifications
You must be signed in to change notification settings - Fork 25
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
Update Five for the Future Documentation to Support Company and Contributor Onboarding and Retention #249
Comments
I have started working on this project, and I have created Google Docs to track each task:
These documents only contain outlines for now, but we'll be adding content to these docs. |
I added the "Onboarding: How to start contributing?" section of the Company Contribution Guide doc. Here's the direct link to the section. |
I'm not sure if we discussed this or not, but we also need a team that will closely communicate with the company management who is supporting the 5FTF program. This team can give feedback about the contribution they made to the WordPress project and can also make them interested on supporting more members/hours for the WordPress project. |
Added the following sections to the Individual Contributor Guide:
Added the following sections to the Company Guide: All sections are in-progress. Feedback and comments are welcome. |
The remarks I often get from smaller companies when I tell them they should join, is: It may even prevent them to have one of their employees to contribute even only 1 hour/week (2.5%) or even for some months 4 hours/week (10%) or more when their employees are for example organizing a WordCamp. The problem they see is that's it's an ongoing and non-fluctuable commitment. If you could clarify this point in the documentation, I think it would help. Another point is to show in the documentation that this is a community project, not an Automattic project, I had a lot of reactions about that confusion. |
My small contribution: we should always be able to check that companies that involve their employees in the 5FTF are not abusing it and using it to get a 'medal on their 5ftf page'. |
Added some comments to the Individual and Company contribution guides |
Big thanks to @naokomc @kafleg @peiraisotta @patriciabt @francescodicandia @estelaris as well as: @angelasjin @kirasong and @poena for their support and contributions! Thanks to y'all's hard work, I'm excited to announce that we now have a V1 of the Five for the Future Handbook that can be accessed here: https://wordpress.org/five-for-the-future/handbook/ This handbook currently contains the following sections:
The following pages are still pending:
We hope to add them in the days to come. |
Hi all, my first little contribution to this nice handbook! |
Thank you for the report, @enrico-sorcinelli This has been fixed. |
Hi all, |
Hi all, |
@enrico-sorcinelli Thank you so much for these excellent suggestions, these are now fixed. I greatly appreciate your diligence and your input! |
@harishankerr I closed this based on your last comment, but realized that the whole issue might not be done, sorry! |
As discussed in the dedicated Five for the Future session at the 2023 Community Summit, and further analyzed in this Make/Project blog post, lack of information on resources on how to go about Five for the Future emerged as a major blocker - both for companies and self-sponsored contributors wanting to pledge their time.
A great way to fix these issues would be to create new documentation in the Five for the Future site that will support both 5ftF organizations and self-sponsored contributors in helping them find their way through their contributor journey.
After some brainstorming, I have arrived at a list of contents that we will need to prepare to update the Five for the Future site, and I'm listing them below:
For now, each checkbox represents a new page (or section) in the Five for the Future website, however the final presentation might differ, after we sync with the website redesign project.
The text was updated successfully, but these errors were encountered: