couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Wenk (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2368) Ask Nicely For Permission To Deprecate the Guide
Date Sun, 12 Oct 2014 11:31:33 GMT


Andy Wenk commented on COUCHDB-2368:

The chapter about eventual consistency is already in the docs:

We can do the same with all other "good" chapters 

> Ask Nicely For Permission To Deprecate the Guide
> ------------------------------------------------
>                 Key: COUCHDB-2368
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Documentation
>            Reporter: Javier Candeira
>            Assignee: Javier Candeira
> If the Guide is to be deprecated, we should edit each chapter with a header explaining:

> - The level at which it is deprecated
> - Where the relevant information formerly found in that page is now found
> - Some kind of 307 (temporary redirect) to be sent only to Google (check that this is
legal and doesn't incur penalty first).
> Rationale: newcomers like myself still find the guide through google and other search
engines. We should try to SEO-deprecate it while having good content in the pages both for
humans and for robots who still find it.
> Rationale for 307: I see the 2.0 release as a good opportunity to update the guide, if
the stakeholders still want that to happen. I'm being informed that the Guide is not the project's
property, but Noahs, JCA's and Jan's. Still, it looks almost official and, being hosted at, it somehow "feels" a bit official to people coming from outside.
That's why I dare ask.

This message was sent by Atlassian JIRA

View raw message