Skip to content
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

Closed
eidolonnight opened this issue Apr 27, 2022 · 13 comments
Closed

Documentation Sprint: Wednesday 25 May 2022 #63

eidolonnight opened this issue Apr 27, 2022 · 13 comments
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@eidolonnight
Copy link
Contributor

eidolonnight commented Apr 27, 2022

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.

@eidolonnight eidolonnight self-assigned this Apr 27, 2022
@eidolonnight eidolonnight changed the title Documentation Sprint: Wednesday 25 April 2022 Apr 27, 2022
@santanainniss
Copy link

@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!

@yvettesonneveld
Copy link

@eidolonnight We're also looking at starting an outline for training for new marketing contributors
How would you like to get input for this? We're chatting about getting new contributors to follow the current training and getting their remaining questions, for instance. Any other thoughts?

@eidolonnight
Copy link
Contributor Author

@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!

If we can pipe the form input to a github issue, that'd be great!

@eidolonnight
Copy link
Contributor Author

@eidolonnight We're also looking at starting an outline for training for new marketing contributors
How would you like to get input for this? We're chatting about getting new contributors to follow the current training and getting their remaining questions, for instance. Any other thoughts?

@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?

@rmartinezduque
Copy link
Contributor

rmartinezduque commented May 18, 2022

Create: Amplification/promotion request template
Possible github issue template? Would need to include link/mission to help people understand what the marketing team can support.

@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:
openverse-example-template

I'm happy to help in any way if we think this could be a good option!

@nalininsbs
Copy link
Contributor

Is there a time for this sprint?

@abhansnuk
Copy link
Contributor

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

@abhansnuk
Copy link
Contributor

On the podcasting task, this is currently in discussion with Learn WP on whether it could sit there. Update on the card

@nalininsbs nalininsbs added this to To do / Status review in Marketing Tasks via automation May 25, 2022
@nalininsbs
Copy link
Contributor

@abhansnuk I could not find this card on the board. Can you please help?

@abhansnuk
Copy link
Contributor

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'.

@abhansnuk abhansnuk moved this from To do / Status review to In progress in Marketing Tasks May 25, 2022
@abhansnuk abhansnuk added the documentation Improvements or additions to documentation label May 25, 2022
@abhansnuk abhansnuk added this to the 25 May 2022 milestone May 25, 2022
@abhansnuk
Copy link
Contributor

abhansnuk commented May 25, 2022

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.
@murillol - for awareness on the extra column and the note above about the task board. Hope they help.

(Updated comment)
Some more of the updates I have done today:
Update on Issue 40 - existing confirmed and reviewed videos which are live on YouTube for onboarding to be added to Learn WP ahead of WCEU, if possible.

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.

@murillol
Copy link

Thanks @abhansnuk , I was creating cards but not adding them to the task board - I will do that from now on.
Just saw the extra column, it definitely helps keep track.

@eidolonnight
Copy link
Contributor Author

eidolonnight commented May 26, 2022

Recap

Big thanks to @jpantani @thetinyl @santanainniss for dropping in to help me out in realtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
7 participants