-
Notifications
You must be signed in to change notification settings - Fork 8
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
Documentation Sprint: Wednesday 25 May 2022 #63
Comments
@eidolonnight Looking at the amplification template line item above, must this be in GitHub? Or would a Google form template work? @yvettesonneveld, Reyes and I are discussing this for the Yoast contributor day as a good issue! |
@eidolonnight We're also looking at starting an outline for training for new marketing contributors |
If we can pipe the form input to a github issue, that'd be great! |
@yvettesonneveld I heard that the Training team is working on general contributor training too, so IMO we should sync up with them before creating any of our own training. Our training can then be specific to the Marketing team rather than covering the universal basics of Slack, Make blogs, etc. If we do that, then I think the first thing to do would be to fire up a dedicated github issue and start outlining the training? |
@eidolonnight I'm not sure if it will be very complicated to implement, but an issue form could also work for the amplification/promotion requests. Here's an example of a template that Openverse has for suggesting new sources: I'm happy to help in any way if we think this could be a good option! |
Is there a time for this sprint? |
I am not available after the meeting today. I have added comments and summary of the work that is going on the glossary (and linked to work between docs and Learn WP during 6.0) and related contributor materials coming together on Learn WordPress #39 |
On the podcasting task, this is currently in discussion with Learn WP on whether it could sit there. Update on the card |
@abhansnuk I could not find this card on the board. Can you please help? |
Hello. It is because the card is not assigned to a board. I will add this for you and add a documentation label. @eidolonnight when you add a card in the repo, you also have to allocate it to a board. In this case the 'Marketing Tasks board'. You can do this under 'projects'. This will then appear on the board and you can either move it along the columns for progression or it can auto move, for example, when you mark an item with a different status or you close an issue, it will go into 'done'. |
I have added updates and reviews to as many cards as I could for now. I have created a new column for where items need to be available until they physically migrate to another team's GitHub so that it is clearer. Need to get back to work. Have fun in the rest of the sprint. (Updated comment) Update on Issue 14 - GitHub labels and tags consolidation Update on Issue 37 - Promote call to translating hosting pages. Moved to other teams migration column. Note this is also set to be reviewed post WCEU by Polyglots, who will advise marketing if they need assistance with promoting a call. The issue has been closed for now with agreement from polyglots. Update on Issue 35 - Trac Ticket commenting - moved to column for migration to another team's board. Note: if this is found to be needed prior to WCEU, it may need to be reopened. |
Thanks @abhansnuk , I was creating cards but not adding them to the task board - I will do that from now on. |
Recap
Big thanks to @jpantani @thetinyl @santanainniss for dropping in to help me out in realtime. |
Once a month, I spend a day focused on writing and documentation. For this sprint, I'm I'll be looking at the following items:
If you would like to join in, contribute, or share a request, please comment on this issue. Whatever doesn't get done in this sprint will get revisited next month.
The text was updated successfully, but these errors were encountered: