-
Notifications
You must be signed in to change notification settings - Fork 9
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
Moving GitHub issues that are used to explain process or structure of Marketing Team to Handbook #180
Comments
in my experience, the long explanatory github tickets are confusing because it's not clear how to contribute using that issue and questions/comments are not focused on a single issue. we could also discuss putting these longer explanatory texts on GH pages or the GH wiki instead of the handbook, but i personally think we should make the handbook the single-source of truth. |
I agree. And I think some GitHub issues are confusing not solely because they are long, but because they are not being used as 'tasks' that folks can contribute to. Some are being used to discuss things, share updates and ideas that have been shared on Slack, etc.
If we want to make the Handbook the single source of truth, I think moving the issues/cards you mentioned to the handbook makes sense. But as I said in Slack, I'd try to make this a consistent process and follow the same path for other issues/cards. For example, a few that come to mind are The Month in WordPress or People of WordPress publications. We can also document the process in the Handbook, and then open a card for each edition for contribution. |
Following up on this, I'd be happy to help move the [Ongoing] WordPress Photo Directory Social Campaign - #WPPhotos issue, along with this Contributing Guide to the Marketing Handbook. I suggest proceeding with @sereedmedia's proposal (move those two issues under the "Get Involved" section) and iterating as necessary. |
It seems like there is not a lot of feedback on this proposal from folks one way or another, but I am good to move forward with this restructuring with you @rmartinezduque! Also, I think it would be good to have content in the Handbook restructured prior to the upcoming-at-some-point handbook redesign! |
We worked on this issues during the Marketing team coffee break over zoom on Thursday March 23. @rmartinezduque @eidolonnight, @mark-andrew and yself @sereedmedia were in attendance. Another team member joined briefly and left. We talked through the ticket and made a plan to shift the conten, and began moving pages.
Highlighting these campaigns:
|
Some quick updates here:
|
Per the title, I propose that we move GitHub issues that are used to explain process or structure of the Marketing Team to the Make Marketing Team Handbook: https://make.wordpress.org/marketing/handbook
Specifically, I propose that the following two very useful and long-term tickets would be better served as a new "Social Media" page and subsequent "Social Media Campaigns" subpage(s) in the Handbook, as a new section under "Get Involved"
**WordPress Social Media Amplification (Get Started with WordPress Social Media #7 ) ** (authored by @eidolonnight): I suggest moving this to its own "Social Media" page in the Handbook in the Get Involved section
[Ongoing] WordPress Photo Directory Social Campaign - #WPPhotos ( [Ongoing] WordPress Photo Directory Social Campaign - #WPPhotos #178 )(authored by @rmartinezduque): I suggest moving this to a) its own new subpage of the above proposed Social Media page in the Handbook or b) a section of a new "Social Media Campaigns" subpage that provides similar information for the other campaigns listed in the "Process" section of the Social Media Amplification Card.
As a result of this, the active contribution issues for these campaigns (as referenced in #2 and #3 of the #WPPhotos ticket), can each be their own GitHub issues focused on a specific contributable action, whether that is are ongoing content development, contributor day pushes, or more targeted campaigns (such as creating social content for Learn projects).
The text was updated successfully, but these errors were encountered: