Note: The CTO blog content has been integrated into this blog. This post is only still here because we’re picky about these things, and the old permalink need a place to go.
What is the CTO Blog?
The content technology CTO Blog is hosted by the Gilbane Group as a service to the content and information technology community. The purpose of the blog is to facilitate ongoing discussion and debate on technologies, approaches and architectures relevant to enterprise content applications. (Note: Obviously the blog is live, but it won’t be officially launched until late August or Early September.)
Why have we created it?
CTOs have a wealth of critical information about technologies that is not always accessible to enterprise customers. When it is, it is often filtered through marketing or PR staff. CTOs also have demanding jobs, and have limited time available to meet with each other with customers, or with other industry influencers. Some CTOs have their own blogs, but in many cases these are not widely read. This blog is intended to encourage communication both between vendor CTOs and between enterprise customer CTOs and vendor CTOs. We have been asked by multiple CTOs to provide this channel.
Who can contribute?
Any CTO is welcome, and anyone who has an equivalent role. If you are not sure whether it makes sense for you, ask us at: email@example.com. We understand that small companies might have a founding CEO who acts as the CTO (me, for example), and large companies may have multiple senior technology strategists that in effect act as CTOs for divisions. We invite all vendors, enterprise customers, system integrators, and analyst and consulting firms to participate. Anyone may comment on blog postings.
What topics will be covered?
Any topics relevant to enterprise applications and content technologies are welcome. We have set up a starter list of categories at https://gilbane.com/ctoblog/ that suggests the range. Our contributors will help us expand this list. This is a business/technical blog and not intended for personal, political or other types of content.
How can you become an author?
Send an email to firstname.lastname@example.org if you would like to contribute to the blog, or if you have questions about doing so. If you meet our CTO or equivalent criteria you will be set-up as an author and listed as such on the blog. Each author has full posting and commenting permissions, and also will have a direct link to all their own posts (of the form “https://gilbane.com/ctoblog/firstname_lastname.html). If you don’t have a blog, this might be all you need.
What if I already have a blog?
Chances are there will be content that makes sense for your own blog that might not make sense here, and possibly vice versa. In any case, relevant cross-posting is OK.
Are there minimum contribution requirements?
No. Nor are there maximum limits. You can post just once or every day.
- What other rules are there?
Submissions by anyone “representing” approved contributors (for example, PR folks) are not allowed. Anyone is able to comment.
- There will be very little moderating. However no personal attacks, “flaming”, or uncivilized posting will be allowed.
- No pure marketing or sales content is allowed, but it is fine to talk about products and their existing and planned functionality, and even to argue for a particular approach, strategy, or philosophy.
- The CTO Blog has a creative Commons license associated with it that only restricts commercial use, so, for example, re-posting to or from your own or other blogs is fine.
Is this a Gilbane Group platform?
Only physically, in that we host it and moderate it. Our own opinions may be found in comments or on our analyst blog at https://gilbane.com/blog/.