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.

Sign up for GitHub

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

Jump to bottom

add marketing blog guidelines #4459

Merged
merged 3 commits into from
Jan 31, 2020
Merged

add marketing blog guidelines #4459

merged 3 commits into from
Jan 31, 2020

Conversation

boluisa
Copy link
Contributor

@boluisa boluisa commented Jan 29, 2020

This PR adds a blog guideline for the marketing team.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 29, 2020
@k8s-ci-robot
Copy link
Contributor

Welcome @boluisa!

It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/community has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @boluisa. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/community-management sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. labels Jan 29, 2020
@boluisa
Copy link
Contributor Author

boluisa commented Jan 29, 2020

/assign castrojo

@parispittman
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 29, 2020
@parispittman parispittman added area/contributor-comms Issues or PRs related to the upstream marketing team and removed area/community-management labels Jan 29, 2020
@parispittman
Copy link
Contributor

/hold for comments from other marketing team folks

thanks for kicking this off, tunde

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 29, 2020
@boluisa
Copy link
Contributor Author

boluisa commented Jan 30, 2020

@parispittman I fixed the markdown format.

@parispittman parispittman mentioned this pull request Jan 30, 2020
Closed
jonasrosland
jonasrosland reviewed Jan 31, 2020
View reviewed changes
communication/marketing-team/contributor-blogging.md Outdated
1. Active bloggers should write one blog a quarter. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue.
2. Adhere to the code of conduct, values, and principles of the project.
3. Bloggers are expected to attend at least one upstream marketing team meeting a month or check-in to remain active.
4. If you receive a request to write about someone or a group of people from your employer, ask another blogger to write it.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably include something like "a project from your employer". Otherwise looks really good!

@parispittman
Copy link
Contributor

Add that blogs should also be reviewed by the people being mentioned in the piece

@onlydole
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 31, 2020
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 31, 2020
@chris-short
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 31, 2020
@parispittman
Copy link
Contributor

/approve

@parispittman parispittman removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 31, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: boluisa, parispittman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2020
@k8s-ci-robot k8s-ci-robot merged commit f4c07ee into kubernetes:master Jan 31, 2020
@boluisa boluisa mentioned this pull request Feb 3, 2020
Closed
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jonasrosland jonasrosland jonasrosland left review comments

@mrbobbytables mrbobbytables Awaiting requested review from mrbobbytables

@parispittman parispittman Awaiting requested review from parispittman

Assignees

@onlydole onlydole

@castrojo castrojo

@chris-short chris-short

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/community-management area/contributor-comms Issues or PRs related to the upstream marketing team cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@boluisa @k8s-ci-robot @parispittman @onlydole @chris-short @jonasrosland @castrojo