fixing up links to commits and ghc source on trac wiki/trackers

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

fixing up links to commits and ghc source on trac wiki/trackers

Carter Schonwald
Hey all,

Currently the commit/ source file links on trac wiki and tickets are all
dead, and while thats not a problem for active ghc devs and such, it does
create more friction for new users.

My understanding is the previously the file and commit references would
point at a haskell.org repository, would it be worth having them point at
the github analogues thereof? (and for that matter would that be easy to
do, or take up more of the finite ghc dev time?)

(in my tickets or the like, i'm by hand doing ghc file / commit links to
github to make it easier for myself and others to look up the relevant
info.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20130524/385b7d4a/attachment.htm>

Reply | Threaded
Open this post in threaded view
|

fixing up links to commits and ghc source on trac wiki/trackers

Edward Z. Yang
Hi Carter,

The reason the links are broken is because the Git Trac plugin is currently
disabled for performance reasons.  The easiest thing to do is to get the
plugin updated and re-enable it.

Edward

Excerpts from Carter Schonwald's message of Fri May 24 10:52:44 -0700 2013:

> Hey all,
>
> Currently the commit/ source file links on trac wiki and tickets are all
> dead, and while thats not a problem for active ghc devs and such, it does
> create more friction for new users.
>
> My understanding is the previously the file and commit references would
> point at a haskell.org repository, would it be worth having them point at
> the github analogues thereof? (and for that matter would that be easy to
> do, or take up more of the finite ghc dev time?)
>
> (in my tickets or the like, i'm by hand doing ghc file / commit links to
> github to make it easier for myself and others to look up the relevant
> info.)


Reply | Threaded
Open this post in threaded view
|

fixing up links to commits and ghc source on trac wiki/trackers

Carter Schonwald
ok, and how would that be done?


On Fri, May 24, 2013 at 3:17 PM, Edward Z. Yang <ezyang at mit.edu> wrote:

> Hi Carter,
>
> The reason the links are broken is because the Git Trac plugin is currently
> disabled for performance reasons.  The easiest thing to do is to get the
> plugin updated and re-enable it.
>
> Edward
>
> Excerpts from Carter Schonwald's message of Fri May 24 10:52:44 -0700 2013
> :
> > Hey all,
> >
> > Currently the commit/ source file links on trac wiki and tickets are all
> > dead, and while thats not a problem for active ghc devs and such, it does
> > create more friction for new users.
> >
> > My understanding is the previously the file and commit references would
> > point at a haskell.org repository, would it be worth having them point
> at
> > the github analogues thereof? (and for that matter would that be easy to
> > do, or take up more of the finite ghc dev time?)
> >
> > (in my tickets or the like, i'm by hand doing ghc file / commit links to
> > github to make it easier for myself and others to look up the relevant
> > info.)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20130524/7f590168/attachment.htm>

Reply | Threaded
Open this post in threaded view
|

fixing up links to commits and ghc source on trac wiki/trackers

Austin Seipp-4
The catch is that we don't want to move off of what it's in Debian,
from what I remember. These are obviously slightly dated versions of
Trac. Of course that's a ridiculous understatement because the *real*
problem IMO is that haskell.org is still running Debian 5 (Lenny.)
We're beyond obsolete.

I brought this up to Ian on IRC a week or two ago, and he informed me
that there are some planned infrastructure upgrades for some of the
haskell.org infrastructure. I am not aware of who is in charge here.

Personally, I'd like to see this happen sooner and not later now that
Wheezey is released. A more concerning aspect of this is that we don't
see security updates anymore. An nmap scan (confirming Debian 5 on
lambda.haskell.org) reveals a few services which are quite out of
date; with handfuls of CVEs against all of them at the least (mostly
low priority, but there are several slightly-worrying ones.)

On Fri, May 24, 2013 at 3:56 PM, Carter Schonwald
<carter.schonwald at gmail.com> wrote:

> ok, and how would that be done?
>
>
> On Fri, May 24, 2013 at 3:17 PM, Edward Z. Yang <ezyang at mit.edu> wrote:
>>
>> Hi Carter,
>>
>> The reason the links are broken is because the Git Trac plugin is
>> currently
>> disabled for performance reasons.  The easiest thing to do is to get the
>> plugin updated and re-enable it.
>>
>> Edward
>>
>> Excerpts from Carter Schonwald's message of Fri May 24 10:52:44 -0700
>> 2013:
>> > Hey all,
>> >
>> > Currently the commit/ source file links on trac wiki and tickets are all
>> > dead, and while thats not a problem for active ghc devs and such, it
>> > does
>> > create more friction for new users.
>> >
>> > My understanding is the previously the file and commit references would
>> > point at a haskell.org repository, would it be worth having them point
>> > at
>> > the github analogues thereof? (and for that matter would that be easy to
>> > do, or take up more of the finite ghc dev time?)
>> >
>> > (in my tickets or the like, i'm by hand doing ghc file / commit links to
>> > github to make it easier for myself and others to look up the relevant
>> > info.)
>
>
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
>



--
Regards,
Austin - PGP: 4096R/0x91384671


Reply | Threaded
Open this post in threaded view
|

fixing up links to commits and ghc source on trac wiki/trackers

Herbert Valerio Riedel
On 2013-05-24 23:52:47 +0200, Austin Seipp wrote:
> The catch is that we don't want to move off of what it's in Debian,
> from what I remember. These are obviously slightly dated versions of
> Trac.

Being the author of the original git plugin[1], I feel the need to make
a few comments:

 - The git-plugin version available in lenny is rather ancient and dates
   back to 2008

 - wheezy's git-plugin is basically HEAD of [2], which dates back to
   2011

 - wheezy ships with Trac 0.12.3 (as wheezy decided to ship the
   current 0.12.x LTS branch of Trac)

 - The 0.12.x version of the trac git plugin is not actively maintained
   anymore (by me) and I don't know of anyone else who has taken over
   active maintainance

 - However, the git plugin was merged upstream into Trac project some
   time ago, and is now part of Trac 1.0 and later. This also means the
   git backend is being actively maintained and improved by the Trac
   HQ[3][4]. Moreover, it's even show-cased on trac.edgewall.org [5].

 - Therefore, I'd recommend using Trac 1.0.x even though that version is
   not the one in wheezy (but I expect it to hit wheezy-backports sooner
   or later as it's already in experimental[6]).

> Of course that's a ridiculous understatement because the *real*
> problem IMO is that haskell.org is still running Debian 5 (Lenny.)
> We're beyond obsolete.


cheers,
  hvr

 [1]: http://trac-hacks.org/wiki/GitPlugin
 [2]: https://github.com/hvr/trac-git-plugin/
 [3]: http://trac.edgewall.org/log/branches/1.0-stable/tracopt/versioncontrol/git
 [4]: http://trac.edgewall.org/log/trunk/tracopt/versioncontrol/git
 [5]: http://trac.edgewall.org/log/cboos.git/
 [6]: http://packages.debian.org/experimental/trac


Reply | Threaded
Open this post in threaded view
|

fixing up links to commits and ghc source on trac wiki/trackers

Ian Lynagh-2
In reply to this post by Austin Seipp-4
On Fri, May 24, 2013 at 04:52:47PM -0500, Austin Seipp wrote:
> The catch is that we don't want to move off of what it's in Debian,
> from what I remember. These are obviously slightly dated versions of
> Trac. Of course that's a ridiculous understatement because the *real*
> problem IMO is that haskell.org is still running Debian 5 (Lenny.)
> We're beyond obsolete.
>
> I brought this up to Ian on IRC a week or two ago, and he informed me
> that there are some planned infrastructure upgrades for some of the
> haskell.org infrastructure.

Right, the plan AFAIR is to consolidate lambda+abbot onto a single
new Hetzner machine, with a handful of VMs.

> I am not aware of who is in charge here.
>
> Personally, I'd like to see this happen sooner and not later now that
> Wheezey is released.

Yup, we're just waiting for someone to have time to do it now, AFAIK.
CCing a couple of related lists.


Thanks
Ian