I HAVE A SOLUTION

for anyone who asks me, I will help manage the "this isn't maintained, i wanna take over maintership" pestering emails that need to happen.

that said, you'll still need to email me to ask me to do that, or pester me on IRC as applicable. (which may take just as much time as "hey i'd like to take over maintainership of X on hackage please" sent to the libraries list)

Point being, if someone finds the prospect of doing the pestering needed to do the process overwhelming, ask me nicely, and i'll try to help push it along (while keeping them in CC and such, though they of course will have to chime in at some point)

should this thread also touch on the the libraries mailing list? ccing it just in case :)


point being, we need to have a responsive, *responsible* way of quickly resolving these things that easy to do.

time for comments: 2 weeks

-Carter 



On Thu, Jan 30, 2014 at 11:53 AM, Ben Gamari <bgamari.foss@gmail.com> wrote:
Clark Gaebel <cgaebel@uwaterloo.ca> writes:

> How does the process of taking over maintenance add latency to your work?
>
> 1) Check out broken version of package.
> 2) Fix locally, bump version number locally.
> 3) cabal sandbox add-source ../fixed-package in any package that needs the
> fixed version.
> 4) Email hackage admins for upload rights.
> 5) Continue working on your actual project.
> 6) Receive upload privileges one day.
> 7) Upload fixed package.
>
> As far as I can tell, the only real latency cost here is that paid to fix
> the broken version.
>
In my experience, step 4 involved several round trips between a number
of different people. Admittedly, this is in part because it's easy to
forget about the broken package after you have fixed it locally.

Cheers,

- Ben


_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe