Change History (5)

comment:1 Changed 5 years ago by https://id.mayfirst.org/dskallman

  • Keywords f2f support added
  • Owner set to https://id.mayfirst.org/ross
  • Status changed from new to assigned

This too would be something to discuss at the next face to face support team session.

comment:2 follow-up: Changed 5 years ago by https://id.mayfirst.org/ross

Hi Jeremy,

The general request from dkg when someone asks for a trac plugin is that they package the plugin for debian, which seems generally like a good idea. Is that something you'd be interested in doing and/or something you're capable of doing with relative ease?

~/ross

comment:3 in reply to: ↑ 2 Changed 5 years ago by https://launchpad.net/~jeremyb

Replying to https://id.mayfirst.org/ross:

The general request from dkg when someone asks for a trac plugin is that they package the plugin for debian, which seems generally like a good idea.

Ok, don't know much about trac (and some people that agree with that in general do not support that for webapps. see e.g. http://notes.pault.ag/debian-python/ )

I personally don't have much experience running packaged webapps. (and again no trac experience)

Is that something you'd be interested in doing and/or something you're capable of doing with relative ease?

Yeah. dkg has done this before and would be able to help me?

comment:4 follow-up: Changed 5 years ago by https://id.mayfirst.org/dkg

i don't have time to work on that right now, nor to evaluate the consequences of setting up something like this (the caveats about redirect loops in ServerSideRedirectPlugin sound worrisome to me at least).

Ross maintains a trac module for debian, maybe he can help out if this is desired.

I personally don't think that asking users who've landed on the wrong page to click through to a different page is particularly onerous, or worth the hassle of maintaining extra code. One other concern i have about being able to force redirects is what it does to the history of the page. If I can place a redirect on a given page, it is important that that action shouldn't make it more difficult for users reviewing the site to see the history of the original page.

We've worked hard to make sure that this wiki history is transparent and visible, so losing that for the sake of a quick redirect on a handful of pages seems like a dubious tradeoff to me.

Anyway, i'm happy to be convinced otherwise, if folks feel strongly.

comment:5 in reply to: ↑ 4 Changed 5 years ago by https://launchpad.net/~jeremyb

Replying to https://id.mayfirst.org/dkg:

Ross maintains a trac module for debian, maybe he can help out if this is desired.

Ok.

I personally don't think that asking users who've landed on the wrong page to click through to a different page is particularly onerous, or worth the hassle of maintaining extra code. One other concern i have about being able to force redirects is what it does to the history of the page. If I can place a redirect on a given page, it is important that that action shouldn't make it more difficult for users reviewing the site to see the history of the original page.

We've worked hard to make sure that this wiki history is transparent and visible, so losing that for the sake of a quick redirect on a handful of pages seems like a dubious tradeoff to me.

Anyway, i'm happy to be convinced otherwise, if folks feel strongly.

Well I brought it up to begin with because I'm missing that feature when compared to MediaWiki.

compare https://en.wikipedia.org/wiki/Barack_Obama vs. https://en.wikipedia.org/wiki/Barack_obama

See immediately under "From Wikipedia, the free encyclopedia" (which is under <h1>). There's a link to https://en.wikipedia.org/w/index.php?title=Barack_obama&redirect=no

I'll let others judge what the optimal UX is here, was just a suggestion.

Last edited 5 years ago by https://launchpad.net/~jeremyb (previous) (diff)

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.