28 Nov
2012
28 Nov
'12
1:30 p.m.
On 11/28/2012 03:16 AM, Vincent Massol wrote:
On Nov 28, 2012, at 1:07 AM, Sergiu Dumitriu <sergiu(a)xwiki.org> wrote:
PURL is a really neat idea, there are multiple PURL servers and as I
understand it a URL is gossuped around similar to how PGP keyservers work
making it highly stable, decentralized and disaster resistant.
That said, in this case we're using it as a tinyurl clone and the average
viewer of a release tweet doesn't know what it is and of course twitter
insists on shortening everything with t.co so they can spy on people so
it's just another layer of indirection and an extra 250ms of wait time.
+1 to remove it from the tweet and the release process since it's extra
work and it doesn't even showcase the great technology that PURL is.
Thanks,
Caleb
On 11/27/2012 04:28 PM, Vincent Massol wrote:
Yes PURLs could be a good solution for specific important pages like the one you mention
but they are adhoc and I don't believe those are required for temporary resources such
as Release notes.
Or you really need to make it transparent so that it doesn't cost more when doing
releases. I spent 15 minutes trying to create a PURL when I did the release 2 days ago and
in the end I didn't do it since it was too complex and I couldn't understand how
to do it.
Hi Sergiu,
On Nov 27, 2012, at 10:01 PM, Sergiu Dumitriu <sergiu(a)xwiki.org> wrote:
Again, this is not about tweeter. PURLs aren't about length, they're
about finding something in a reliable place, and involve maintenance
work. There should be no broken PURL. I created a few other PURLs a long
time ago, like purl.org/xwiki/repo/, purl.org/xwiki/ml/ and
purl.org/xwiki/ml/archive, purl.org/xwiki/ci/ (which used to point to
hudson). On 11/27/2012 09:18 AM, Vincent Massol wrote:
> Hi devs,
>
> Here are some notes I took while releasing XWiki 4.3 on how to improve the release
process:
>
> * We need to automate the generation of the CLIRR report. This is what takes the
longest when releasing (not overall time but manual time required). IMO this can be done
relatively easily by creating a patch for the CLIRR maven plugin itself to:
> ** Add support for wildcards in the new <difference> syntax
> ** Ensure that their report generation takes into account the <justification>
element
> ** Possibly add a text report generation that we'll be able to copy paste in our
RN
+1.
> * Remove PURL generation for Tweets
> ** Tweets are ephemeral so no need to have permanent URLs
> ** Tweet clients already do URL shortening
> (It's complex to use the PURL UI too)
-1. The PURL is not just about twits, it's about having some permanent
links to our release notes. I really don't like that our URLs are so
damn long
(http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki44RC1
is 71 chars long), so I like to have something shorter.
You don't need PURL for that…. As i mentioned the tweet clients already shorten URLs…
Check my tweet, you'll see it's not 71 chars long:
https://twitter.com/xwikiorg/status/273180659521028096 (I didn't do anything specific
to shorten the URL). [snip]
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs