couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Javier Candeira (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-2368) Ask Nicely For Permission To Deprecate the Guide
Date Thu, 09 Oct 2014 11:55:44 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Javier Candeira updated COUCHDB-2368:
-------------------------------------
    Description: 
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 somehow "feels"
a bit official to people coming from outside. That's why I dare.

  was:
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 somehow "feels"
a bit official to people coming from outside. So I dare to move this proposal as part of the



> Ask Nicely For Permission To Deprecate the Guide
> ------------------------------------------------
>
>                 Key: COUCHDB-2368
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2368
>             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 somehow "feels"
a bit official to people coming from outside. That's why I dare.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message