You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2017/11/27 20:02:17 UTC
housekeeping - uima website docs/
The docs/ in the uima website has a large amount of folders/files from older
releases.
I'm thinking of moving these to another svn project under
https://svn.apache.org/repos/asf/uima, say
https://svn.apache.org/repos/asf/uima/website-archive
This could be done using the svn move style - so no "space" for the data would
be consumed.
The advantage: svn operations on the uima-website would proceed faster because
there would be many less files to check.
----------------
Alternative: do an svn delete of the older folders/files in docs/. This is
more-or-less the same as above, except it becomes more difficult to find the
older files (you have to go thru history, etc).
----------------
Opinions? I'm leaning toward an explicit website-archive "project".
-Marshall
Re: housekeeping - uima website docs/
Posted by Marshall Schor <ms...@schor.com>.
The apache docs on httpd for htaccess
https://httpd.apache.org/docs/current/howto/htaccess.html seem to suggest using
these is a bad idea. The response I got from infra also seems to suggest I can
just post a "pull" request against a github thing. Here's part of what they said:
Sure thing! If you take a look at our Puppet config for the
webservers: https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/themis.apache.org.yaml#L453
and https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/tlp-eu-west.apache.org.yaml
, one example is how we are redirectingmod_* docs for HTTPD to their
site. Feel free to make a PR against both those .yaml files if you
are comfortable otherwise let us know in a JIRA ticket what you'd like
done and we can do it
So, I'm guessing they want to manage these this way...
I'll wait a day or 2 to see if there's any other comments about this, and then
if no objections, I'll create the svn copies and ask they do the redirects.
-Marshall
On 11/28/2017 1:54 PM, Richard Eckart de Castilho wrote:
> Sounds good. It might be possible to set up redirects using .htaccess files
> if infra allows that. In that way we could change the configs when necessary without the need to involve them.
>
> https://mediatemple.net/community/products/grid/204643080/how-do-i-redirect-my-site-using-a-htaccess-file
>
> -- Richard
>
>> On 28.11.2017, at 19:51, Marshall Schor <ms...@schor.com> wrote:
>>
>> I asked on the infra list and they say that there's a simple way to configure
>> this (which they have to do - one-liners (per migrated top-level directory
>> item), to automatically redirect things.
>>
>> The lines in their scripts look like this:
>>
>> Redirect permanent /travel/application http://tac-apply.apache.org
>> RedirectMatch permanent ^/LICENSE.* http://www.apache.org/licenses/
>> RedirectMatch permanent /flyers(.*)
>> http://www.apache.org/foundation/contributing.html
>>
>> So, I think we can do this without much difficulty, in a way which preserves
>> "old links".
>>
>> So the next thing to do is to decide **what** to do.
>> Here's a start:
>> create a .../uima/site/trunk/uima-website-archive next to
>> .../uima/site/trunk/uima-website (existing)
>>
>> svn copy .../uima-website/docs/d/
>> all the older versions (except the current one) of
>> ruta, uima-as, uima-ducc, uimafit, uimaj-2x uimaj-3x
>>
>> That's the vast bulk of what needs to be archived.
>> Because of our naming conventions, I suspect some pattern might be usable for
>> the redirect matching.
>>
>> After we copy these, and get the redirects working, then we can svn delete
>> these, and the redirects will continue to work.
>>
>> Does that sound about right?
>
Re: housekeeping - uima website docs/
Posted by Richard Eckart de Castilho <re...@apache.org>.
Sounds good. It might be possible to set up redirects using .htaccess files
if infra allows that. In that way we could change the configs when necessary without the need to involve them.
https://mediatemple.net/community/products/grid/204643080/how-do-i-redirect-my-site-using-a-htaccess-file
-- Richard
> On 28.11.2017, at 19:51, Marshall Schor <ms...@schor.com> wrote:
>
> I asked on the infra list and they say that there's a simple way to configure
> this (which they have to do - one-liners (per migrated top-level directory
> item), to automatically redirect things.
>
> The lines in their scripts look like this:
>
> Redirect permanent /travel/application http://tac-apply.apache.org
> RedirectMatch permanent ^/LICENSE.* http://www.apache.org/licenses/
> RedirectMatch permanent /flyers(.*)
> http://www.apache.org/foundation/contributing.html
>
> So, I think we can do this without much difficulty, in a way which preserves
> "old links".
>
> So the next thing to do is to decide **what** to do.
> Here's a start:
> create a .../uima/site/trunk/uima-website-archive next to
> .../uima/site/trunk/uima-website (existing)
>
> svn copy .../uima-website/docs/d/
> all the older versions (except the current one) of
> ruta, uima-as, uima-ducc, uimafit, uimaj-2x uimaj-3x
>
> That's the vast bulk of what needs to be archived.
> Because of our naming conventions, I suspect some pattern might be usable for
> the redirect matching.
>
> After we copy these, and get the redirects working, then we can svn delete
> these, and the redirects will continue to work.
>
> Does that sound about right?
Re: housekeeping - uima website docs/
Posted by Marshall Schor <ms...@schor.com>.
I asked on the infra list and they say that there's a simple way to configure
this (which they have to do - one-liners (per migrated top-level directory
item), to automatically redirect things.
The lines in their scripts look like this:
Redirect permanent /travel/application http://tac-apply.apache.org
RedirectMatch permanent ^/LICENSE.* http://www.apache.org/licenses/
RedirectMatch permanent /flyers(.*)
http://www.apache.org/foundation/contributing.html
So, I think we can do this without much difficulty, in a way which preserves
"old links".
So the next thing to do is to decide **what** to do.
Here's a start:
create a .../uima/site/trunk/uima-website-archive next to
.../uima/site/trunk/uima-website (existing)
svn copy .../uima-website/docs/d/
all the older versions (except the current one) of
ruta, uima-as, uima-ducc, uimafit, uimaj-2x uimaj-3x
That's the vast bulk of what needs to be archived.
Because of our naming conventions, I suspect some pattern might be usable for
the redirect matching.
After we copy these, and get the redirects working, then we can svn delete
these, and the redirects will continue to work.
Does that sound about right?
-Marshall
On 11/28/2017 8:03 AM, Richard Eckart de Castilho wrote:
> Any links on third-party websites or papers etc. referring to the old documentation
> would also break. Would it be worth trying to add some custom 404 page which would
> tell people where to find the current documentation?
>
> -- Richard
>
>> On 27.11.2017, at 21:02, Marshall Schor <ms...@schor.com> wrote:
>>
>> The docs/ in the uima website has a large amount of folders/files from older
>> releases.
>>
>> I'm thinking of moving these to another svn project under
>> https://svn.apache.org/repos/asf/uima, say
>> https://svn.apache.org/repos/asf/uima/website-archive
>>
>> This could be done using the svn move style - so no "space" for the data would
>> be consumed.
>>
>> The advantage: svn operations on the uima-website would proceed faster because
>> there would be many less files to check.
>>
>> ----------------
>>
>> Alternative: do an svn delete of the older folders/files in docs/. This is
>> more-or-less the same as above, except it becomes more difficult to find the
>> older files (you have to go thru history, etc).
>>
>> ----------------
>>
>> Opinions? I'm leaning toward an explicit website-archive "project".
>>
>> -Marshall
>
Re: housekeeping - uima website docs/
Posted by Marshall Schor <ms...@schor.com>.
One can put a forwarding pointer that automatically redirects particular pages.
This might not be feasible for things like old javadocs - which have a very
large number of pages...
Is there a technique that can redirect a set of web url addresses starting with
a common prefix?
-Marshall
On 11/28/2017 8:03 AM, Richard Eckart de Castilho wrote:
> Any links on third-party websites or papers etc. referring to the old documentation
> would also break. Would it be worth trying to add some custom 404 page which would
> tell people where to find the current documentation?
>
> -- Richard
>
>> On 27.11.2017, at 21:02, Marshall Schor <ms...@schor.com> wrote:
>>
>> The docs/ in the uima website has a large amount of folders/files from older
>> releases.
>>
>> I'm thinking of moving these to another svn project under
>> https://svn.apache.org/repos/asf/uima, say
>> https://svn.apache.org/repos/asf/uima/website-archive
>>
>> This could be done using the svn move style - so no "space" for the data would
>> be consumed.
>>
>> The advantage: svn operations on the uima-website would proceed faster because
>> there would be many less files to check.
>>
>> ----------------
>>
>> Alternative: do an svn delete of the older folders/files in docs/. This is
>> more-or-less the same as above, except it becomes more difficult to find the
>> older files (you have to go thru history, etc).
>>
>> ----------------
>>
>> Opinions? I'm leaning toward an explicit website-archive "project".
>>
>> -Marshall
>
Re: housekeeping - uima website docs/
Posted by Richard Eckart de Castilho <re...@apache.org>.
Any links on third-party websites or papers etc. referring to the old documentation
would also break. Would it be worth trying to add some custom 404 page which would
tell people where to find the current documentation?
-- Richard
> On 27.11.2017, at 21:02, Marshall Schor <ms...@schor.com> wrote:
>
> The docs/ in the uima website has a large amount of folders/files from older
> releases.
>
> I'm thinking of moving these to another svn project under
> https://svn.apache.org/repos/asf/uima, say
> https://svn.apache.org/repos/asf/uima/website-archive
>
> This could be done using the svn move style - so no "space" for the data would
> be consumed.
>
> The advantage: svn operations on the uima-website would proceed faster because
> there would be many less files to check.
>
> ----------------
>
> Alternative: do an svn delete of the older folders/files in docs/. This is
> more-or-less the same as above, except it becomes more difficult to find the
> older files (you have to go thru history, etc).
>
> ----------------
>
> Opinions? I'm leaning toward an explicit website-archive "project".
>
> -Marshall
Re: housekeeping - uima website docs/
Posted by Peter Klügl <pe...@averbis.com>.
I have no strong opinion on this.
Just a guess: how likely will someone need the history of the old docs?
I assume code changes are more relevant.
Peter
Am 27.11.2017 um 21:02 schrieb Marshall Schor:
> The docs/ in the uima website has a large amount of folders/files from older
> releases.
>
> I'm thinking of moving these to another svn project under
> https://svn.apache.org/repos/asf/uima, say
> https://svn.apache.org/repos/asf/uima/website-archive
>
> This could be done using the svn move style - so no "space" for the data would
> be consumed.
>
> The advantage: svn operations on the uima-website would proceed faster because
> there would be many less files to check.
>
> ----------------
>
> Alternative: do an svn delete of the older folders/files in docs/. This is
> more-or-less the same as above, except it becomes more difficult to find the
> older files (you have to go thru history, etc).
>
> ----------------
>
> Opinions? I'm leaning toward an explicit website-archive "project".
>
> -Marshall
>