As a part of our continuing commitment to highlighting the contributions of Linux Foundation members and projects, we would like to offer our members (and others) the opportunity to partner with us to create original, technical content published on Linux.com. The site receives 1M+ site visitors each month who are highly interested in open source content.
There are three types of content that we are interested in:
1. Technical Content
Example: https://www.linux.com/topic/cloud/docker-volumes-and-networks-compose/
Pick a project you care about and would like to promote. We can help you create project-focused, technical content such as a “how-to” implementation guide, or how to enable certain features, managing a system, and where to get started building and contributing to the community. Technical content receives the most visibility on linux.com from search engines and the community at large.
2. Open Source Strategy
Example: https://www.linux.com/articles/sam-ramjis-3-pillars-growth-strategy-for-datastax/
This would be an essay written by an executive with a strategic focus on the technology or project being discussed. This article would ideally help you promote the vision for what your company is doing in open source and how you engage as part of the community. You’ve made a lot of investments in these communities; it’s good to help others understand why it’s important for them to participate and contribute as well.
3. Question & Answer
Example: https://www.linux.com/news/apache-big-data-preview-qa-ibms-anjul-bhambhri/
We can help you structure an article that presents a few questions you can respond to. This format will likely take less time but may not get as much visibility as the technical content from the open source community.
Interested?
If you are interested in submitting a blog, please contact blogs@linuxfoundation.org
Blogs should target 800 words in length.
We will work with you to review the content of your submission, suggest copy edits, and share suggested edits or copy changes with you for review prior to publication.
Please have all content such as author name and affiliated organization in a single document.