openstack team mailing list archive

[Anne Gentle <anne@xxxxxxxxxxxxx>]

Hi Ori -
Great question. Comments on /trunk are purposely disabled because Disqus
uses the URL to maintain the thread for comments. So if we enabled comments
on /trunk, which exists at all times, comment threads would be meaningless
as they'd be about 2 years old now.

So, with each release of the documentation for a grouped release of
OpenStack, I go through this process
http://wiki.openstack.org/Documentation/Release to create new discussion
threads. Would like to find a way to automatically close the Disqus threads
for 2 releases old (such as /diablo) but haven't worked on a solution with
the Disqus API yet.

Ideally we'll release the /folsom docs site when we are confident the
highest-priority doc bugs are addressed. I'd like to do that after the
Summit.

Thanks for asking -
Anne

Anne Gentle
Content Stacker
anne@xxxxxxxxxxxxx


On Oct 16, 2012, at 1:30 PM, Ori Tzoran <ori.tzoran@xxxxxxxxxx> wrote:

hi Anne,

On the bottom of each page in Essex's
doc<http://docs.openstack.org/essex/openstack-compute/admin/content/ch_getting-started-with-openstack.html>comments
were welcome. This feature is suppressed
now<http://docs.openstack.org/trunk/openstack-compute/admin/content/ch_getting-started-with-openstack.html>
.
is this intentional? can you please explain?

thanx
Ori