include pad.lv short urls in pages

[Martin Pool]

It would be nice if Launchpad included a link to the pad.lv short url for a page, on those pages that have one. All of them can be easily mechnically generated..

[Adolfo Jayme Barrientos (fitojb)]

It also would be nice if that pad.lv ULRs become implemented in automated translations credits strings (those handled by Launchpad). :)

[Martin Pool (mbp)]

Could you explain that more, or give an example?

[Adolfo Jayme Barrientos (fitojb)]

Many times, the small “About → Credits → Translated by” windows become too cluttered of long translators’ names and its URLs.

The current approach is:
...
Launchpad Contributions:
  Fitoschido https://launchpad.net/~fitoschido
  Foobar https://launchpad.net/~foobar
...

It sucks because of large font size by default and the small space to show all this text at the same time. Think on real and long names!

I propose to follow a design like this:
...
Contributors in Launchpad:

* Fitoschido
   <http://pad.lv/~fitoschido>
* Another display name
   <http://pad.lv/~lpnickname>
...

By using line wraps and short pad.lv URLs, the credits will look much nicer and easy to read.

[Martin Pool (mbp)]

OK, I see, that makes sense.
Martin

[Jonathan Lange (jml)]

I don't think we should do this before pad.lv is hosted, deployed etc by Canonical Launchpad & LOSA teams. Otherwise will end up with version skew, differing uptimes, no @launchpadstatus updates etc. Alternatively we could somehow clearly mark the pad.lv link as being external. Or someone could come up with a client-side solution (e.g. GreaseMonkey)

[Martin Pool (mbp)]

On 7 June 2011 21:27, Jonathan Lange <email address hidden> wrote:
> I don't think we should do this before pad.lv is hosted, deployed etc by
> Canonical Launchpad & LOSA teams. Otherwise will end up with version
> skew, differing uptimes, no @launchpadstatus updates etc. Alternatively
> we could somehow clearly mark the pad.lv link as being external. Or
> someone could come up with a client-side solution (e.g. GreaseMonkey)

I agree with all that.

I'm happy to transition this to being run by Canonical IS; though that
will probably somewhat slow down the ability to change it and create
more work for them. So, maybe not yet.