Skip to content

Update README #87

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

Merged
merged 1 commit into from
May 20, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
81 changes: 42 additions & 39 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
# PowerShell Community Blog Repository

This repository is for submissions for posts to the [PowerShell Community Blog](https://devblogs.microsoft.com/powershell-community).
We welcome submissions to the blog from anyone in the community.
This repository is for submissions for posts to the
[PowerShell Community Blog](https://devblogs.microsoft.com/powershell-community). We welcome
submissions to the blog from anyone in the community.

Submissions for articles on this blog are governed by the
[Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) or the
Expand All @@ -10,53 +11,55 @@ information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/code

## The Purpose of This Blog

The intended purpose of the PowerShell Community Blog is to provide a platform for the PowerShell Community to show off
the great things you can do with PowerShell and Windows PowerShell.
Each article should provide a set of (relatively!) simple steps to take, with
PowerShell, to achieve some task. Blog posts can cover either Windows PowerShell, or the open source
PowerShell 7.
While we welcome deep, deep posts, most posts are likely to be at the 200-300 level.
Posts should make clear the problem the article helps the reader to solve.
In other words, great practical advice on how to solve real-world IT professional problems, with a
side-helping of technical depth. This blog welcomes submissions to the blog both from internal
Microsoft teams and external people.
The intended purpose of the PowerShell Community Blog is to provide a platform for the PowerShell
Community to show off the great things you can do with PowerShell and Windows PowerShell. Each
article should provide a set of (relatively!) simple steps to take, with PowerShell, to achieve some
task. Blog posts can cover either Windows PowerShell, or the open source PowerShell 7. While we
welcome deep, deep posts, most posts are likely to be at the 200-300 level. Posts should make clear
the problem the article helps the reader to solve. In other words, great practical advice on how to
solve real-world IT professional problems, with a side-helping of technical depth. This blog
welcomes submissions to the blog both from internal Microsoft teams and external people.

Posts to the blog can discuss products and technologies that are not part of the core PowerShell
product or even made by Microsoft, as long as the post's content is relevant to PowerShell users and
is not marketing those products.

The published language for the PowerShell community is English, and mainly American Ennglish, although posts other variations of English are acceptable.
The article review process focuses on the language and structure of each article as well as the specific details.
If English is not your first language, or even if it is, the review process can help to iron out any problems.
The published language for the PowerShell community is English, and mainly American Ennglish,
although posts other variations of English are acceptable. The article review process focuses on the
language and structure of each article as well as the specific details. If English is not your first
language, or even if it is, the review process can help to iron out any problems.

## How to Interact

There are several ways you can interact, depending on your needs and levels of enthusiasm.

1. The entry-level, so to speak, is to read the blog and enjoy the content. You can come
[to the PowerShell Community BLog directly](https://devblogs.microsoft.com/powershell-community) or use a blog aggregation
mechanism to view the content. Over time, we hope and expect the major search engines to index
these posts, making it easy for IT Pros to find and use the information contained.

1. You can also comment on any of blog posts directly on the blog. This blog uses WordPress, so in order to add comments,
you need to create and then login to a WordPress account. Once you logon successfully to the blog,
WordPress allows you to add comments to the posts here. See our
[Coimmunity Blog Wiki pages](https://github.com/PowerShell/Community-Blog/wiki) for detailed instructions. We
welcome comments - but keep them civil and constructive.
We prefer comments in English. Feel free to use [Bing Translator](https://www.bing.com/translator) or [Google Translate](https://translate.google.com/) if English is not your first language.

1. You may want to contribute to the development of blog posts. You are welcome to create new posts,
file issues on any article (or proposed article), or help review content submissions. And should you find an error, feel free to
[file an issue on GitHub](https://github.com/PowerShell/Community-Blog/issues). If there is a
specific question you feel might make a good blog post, also file an issue.

If you want to either create new blog posts or participate in the creation and review of new posts,
then you need to head to [this blog's GitHub repository home](https://github.com/PowerShell/Community-Blog).
[to the PowerShell Community Blog directly](https://devblogs.microsoft.com/powershell-community)
or use a blog aggregation mechanism to view the content. Over time, we hope and expect the major
search engines to index these posts, making it easy for IT Pros to find and use the information
contained.

1. You can also comment on any of blog posts directly on the blog. This blog uses WordPress, so in
order to add comments, you need to create and then login to a WordPress account. Once you logon
successfully to the blog, WordPress allows you to add comments to the posts here.

See our [Community Blog Wiki pages](https://github.com/PowerShell/Community-Blog/wiki) for
detailed instructions. We welcome comments and prefer them in English. You can use an online
translator like [Bing Translator](https://www.bing.com/translator) if English is not your first
language.

1. You may want to contribute to the development of blog posts. You can create new posts, file
issues on any article (or proposed article), or help review content submissions. If you find an
error, feel free to
[file an issue on GitHub](https://github.com/PowerShell/Community-Blog/issues). You can also file
an issue to suggest a specific topic you feel might make a good blog post.

You need a GitHub account to be able to submit anything to the blog's GitHub repository. You can
sign up for a GitHub account at
[GitHub's new account sign up page](https://github.com/join?source=login).
And, you need to be able to use GitHub and, most likely, git on your workstation.
sign up for GitHub at [GitHub's new account sign up page](https://github.com/join?source=login).
And, you need to be able to use GitHub and, most likely, git on your workstation.

Acceptance of any blog post is done at the sole discretion of the Blog administrators. Before we can accept
any blog post submission, you must sign the Contributor License Agreement (CLA). This is a one-time
event.
> [!NOTE]
> Acceptance of any blog post is done at the sole discretion of the Blog administrators. Once you
> submit a PR, the build automation adds a comment to the PR asking you to sign the CLA. The comment
> contains a link to take you to the CLA signing page. Before we can accept any blog post
> submission, you must sign the Contributor License Agreement (CLA). This is a one-time event.