Vendor Forum Rules

The DEVOPSdigest Vendor Forum was established to give vendors of DevOps-related technologies an opportunity to share their views with the IT community in an objective venue. All commentary in Vendor Forum blogs is intended to be objective, vendor-neutral and non-promotional content to educate and enlighten our readers.

All vendors in DevOps-related market spaces are welcome to blog on the Vendor Forum at no cost. To request a blogging account on the Vendor Forum, contact Pete Goldin, Editor and Publisher of DEVOPSdigest.

Signing Up for a Vendor Forum Blogging Account

■ A request for a blogging account on the Vendor Forum must come directly from the individual whose name will be on the blogs, from that individual's corporate email address.

■ Only one representative from each vendor will be allowed to maintain a blogging account for the Vendor Forum at any particular time, if that vendor does not sponsor DEVOPSdigest. Once a company's blogger is established, that same byline must be used for all future blogs from that company. The only time the byline can be changed is if the blogger is no longer with the company; the blogger has moved to a different part of the company and no longer has any involvement with DevOps; or the blogger is no longer blogging and has not posted a blog for a long time. To change the blogger for your company, contact Pete Goldin, Editor and Publisher of DEVOPSdigest.

■ DEVOPSdigest sponsors are allowed multiple blogging accounts on the Vendor Forum. Platinum and Gold Sponsors are eligible for an unlimited number of blogging accounts, and Silver Sponsors are eligible for up to 8 blogging accounts. This sponsor benefit is especially helpful for companies with multiple thought leaders in the industry who would like to claim authorship for their own blogs. Click here to find out how you can sponsor DEVOPSdigest.

■ If a blogger leaves a company, moves to a new company, and continues to blog, all blogs posted by that blogger – past and present – will reference the new company. References to the previous company will be removed from the previous blogs. This would only happen if the blogger remains in the DevOps industry or a related market.

Rules for Blogging on the Vendor Forum

Please observe the following rules when blogging on the Vendor Forum:

■ Do not promote your own company, products or partners in blogs on the Vendor Forum. Topics should be general industry interest. Copy and graphics should be non-promotional and vendor-neutral.

■ One reference to your company in the blog copy is permitted when you are discussing a survey or report conducted or commissioned by your company. A reference to your company's or partner's product is never permitted in the blog copy.

■ If your blog is about a study or survey conducted or commissioned by your company, focus on the results of the survey/study, not why and how the survey/study was conducted.

■ A reference to open source projects is sometimes permitted, as long as the reference is to the open source project or technology itself, and not the company that founded or owns the project. DEVOPSdigest will make a determination on a case by case basis.

■ Do not criticize a company, brand or product in any blogs on the Vendor Forum.

■ Companies that do not sponsor DEVOPSdigest can only include a link to their company home page at the end of the blog – no product pages or any other pages. Even if the product has its own URL separate from the company page, this cannot be included in place of the company home page. The home page link will always be included in the "Related Links" section at the end of the blog, and cannot be substituted with a hyperlink in a marketing message.

■ Only sponsors of DEVOPSdigest can include additional links at the end of the blog, to other pages on their websites, white papers, webinars, articles, blogs, product pages, etc. Click here to find out how you can sponsor DEVOPSdigest.

■ DEVOPSdigest removes old outdated links, but only updates outdated links for current sponsors of the site.

■ Do not place any hyperlinks in the body copy of a blog linking to your company's or any other vendor's web pages or other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making. Hyperlinks in the body copy should only be to support factual points you are making. These hyperlinks can link to a supporting report or article as long as the content is not on your website or your partner's website, is not sponsored or commissioned by your company or partner, and does not promote your company or your partner company in any way. Inclusion of any hyperlinks is at the sole discretion of DEVOPSdigest.

■ Try to keep blogs between 500-1000 words. This is more of a guideline than a rule. You can include more content if you wish, but DEVOPSdigest recommends posting shorter blogs more often. If you have written a 1000+ word blog, consider breaking it into two or more blogs, and post them a couple weeks apart. You could call them Part One and Part Two, if you want.

■ All blogs will be reviewed by DEVOPSdigest prior to publication. DEVOPSdigest reserves the right to edit any content submitted, and the publication of any blog is at the sole discretion of DEVOPSdigest. Vendor Forum blog posts are edited by DEVOPSdigest for spelling, basic grammar and punctuation. Vendor Forum blogs are also edited to ensure they meet DEVOPSdigest guidelines.

■ A Vendor Forum blogger can either log into the DEVOPSdigest system to post their own blogs, or send copy to the editor, who will post the blog under the blogger's name. Once the blogger saves a blog in the system, it does not automatically publish. The system notifies the editor, who will review and publish.

■ The date the blog is actually published will be decided by the editor. DEVOPSdigest may provide you with an estimated date the blog will be posted, but that date cannot be guaranteed, as unforeseen priorities may push the posting date back.

■ DEVOPSdigest sponsors have priority posting. This means that sponsor blogs go to the front of the queue, usually posting within a day or two. The only factors that could delay posting of a sponsor blog would be other sponsor blogs already in the queue, or content that must be posted due to timeliness.

■ Do not save an unfinished blog in the system. The Vendor Forum blogging system does not enable bloggers to go back into a blog and edit it later. Once a blog is saved in the system, it is considered ready to be published, assuming it meets DEVOPSdigest guidelines. So only save blogs in the system when they are ready to be published.

■ If a blogger posts their own blog, and wants to include a graphic with the blog, the graphic must be added by the editor.

■ All Vendor Forum blogs must be original content that has not been published somewhere else. DEVOPSdigest periodically may request to re-post a blog, if the content is particularly valuable to our readers, but please do not re-post your blog on DEVOPSdigest, or pitch DEVOPSdigest to re-post your blog.

■ You can re-post your blogs from the Vendor Forum on your own blogs or websites, as long as you mention that the blog was posted on DEVOPSdigest, and include a link to our site. However, we recommend linking to the blog on DEVOPSdigest.com rather than posting the full blog on your site, to highlight the fact that the content was published by an independent third party. Publication of your blog on a respected industry site provides strong thought leadership credibility for the author and company.

■ Please note that these guidelines are updated periodically to ensure continued alignment with DEVOPSdigest's mission.

Topics for the Vendor Forum

DEVOPSdigest accepts Vendor Forum blogs on topics relating to DevOps, including:

■ DevOps

■ Development Processes

■ Development Technology

■ Development Automation

■ Agile Development

■ Continuous Development

■ API (Application Program Interface)

■ Development Monitoring and Analytics

■ Application Performance and Quality Testing

If you are unsure whether your topic fits DEVOPSdigest, run your idea by Pete Goldin.

The Latest

June 28, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 5, the final installment, covers how Agile improves product quality and the customer experience ...

June 26, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 4 covers how Agile impacts team productivity ...

June 23, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 3 covers how Agile enables you to grow and adapt to change ...

June 21, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 2 is all about speed ...

June 19, 2017

Earlier this year, DEVOPSdigest featured a list of expert opinions on the essential steps to become agile. Now that we have an idea on how to achieve agility, however, we have to consider why. What's the payoff? With this question in mind, DEVOPSdigest asked the experts — including analysts, consultants and vendors — for their opinions on what are the most important advantages of being Agile ...

June 15, 2017

In the development community, creating additional efficiency through improved collaboration has been prevalent for some time. But despite the head start on the rest of the corporate world when it comes to collaboration, many organizations function today as they did 15-20 years ago. Since time is money in the tech world, outdated collaboration is a huge missed opportunity ...

June 14, 2017

Given the efforts we put in these days to deconstructing monolithic applications, and using distributed microservices to make us more agile, the potential for app performance to take a nosedive because of unseen (and unanticipated) network congestion and outages is only getting greater. There is help at hand, though, in the form of new ways to program network awareness directly into your code ...

June 12, 2017

What if you discover a fatal error or an exploit in your app? What if your app is down during a crucial time? As a developer, how you react to a crisis can mean the difference between minor blip and an embarrassing or costly company blunder. Here's a crisis management plan to get things right when they go wrong ...

June 08, 2017

Recently, the results from SmartBear Software's annual survey, the State of Code Review 2017: Trends & Insights into Dev Collaboration were released. One point I found interesting is that it suggests only 66 percent of organizations can get releases out on time. Why are the other 34 percent struggling to get releases out the door? ...

June 06, 2017

Today's app development landscape is competitive and expensive. Thousands of apps are released each month, and user acquisition and retention are costing app developers millions. User abandonment is one of the main battles of every app developer — as every lost user means another wasted investment ...

Share this