wren ng thornton w...@freegeek.org writes:
Using a wiki page for each project enables anybody to add comments.[...]
I think this is a great idea.
Because of Duncan's concerns about imposing too much burden on
authors, and because there are many mature projects which already have
wikis etc,
Hello everyone,
Could a new mailing list for patches and/or commentary do the work of
the proposed package Wikis? Similar to the libraries list but separate
so it doesn't pollute the libraries list from its important job of
discussing and refining the core libs.
From my perspective, mails have
Ketil Malde wrote:
wren ng thornton w...@freegeek.org writes:
Using a wiki page for each project enables anybody to add comments.[...]
I think this is a great idea.
Because of Duncan's concerns about imposing too much burden on
authors, and because there are many mature projects which
Excerpts from wren ng thornton's message of Sun Dec 13 13:54:04 +0100 2009:
Ketil Malde wrote:
wren ng thornton w...@freegeek.org writes:
Using a wiki page for each project enables anybody to add comments.[...]
I think this is a great idea.
Because of Duncan's concerns about
wren ng thornton w...@freegeek.org writes:
Ketil Malde wrote:
At least the way I see it, it is primarily *not* for use by
the author, and in fact most useful when the author is not around to
actively support his project.
But if it's a wiki, wouldn't people be able to add changes
2009/12/13 Ketil Malde ke...@malde.org:
wren ng thornton w...@freegeek.org writes:
That's a separate issue isn't it? Why not have an adopt-a-package
program where the community determines which packages are orphaned and
sets up and maintains wikis and other resources for them until a new
On Fri, Dec 11, 2009 at 6:00 PM, Marc Weber marco-owe...@gmx.de wrote:
Hackage is missing one feature:
It is very static. I mean if you have a patch or a question or a comment
you have to lookup the darcs repository, write the patch then contact
the author and wait.. If the author replies
Hi Antoine.
One of the main goals is to have a place to a put information when
you're not the maintainer. Of course I can put everything into *my*
cabal files. I don't want to do this for projects I don't maintain.
I'd like to ask maintainers first. But while this question - reply cycle
is in
What about if during the Checking a Cabal package upload step there
was a check to see if there was a homepage in the cabal file? If there
is no homepage we could have something like:
Your cabal file does not contain a link to a project homepage. You
may want to add a haskell wiki link as your
Marc Weber marco-owe...@gmx.de wrote:
Hackage is missing one feature:
It is very static. I mean if you have a patch or a question or a comment
you have to lookup the darcs repository, write the patch then contact
the author and wait.. If the author replies everything is fine.
If he doesn't you
patch-tag.com has wikis now.
They are some buggy behaviors I still need to address so I haven't blogged
or otherwise drawn attention to it (arrrg) but my hope is that, quite soon,
this will be quite slick and quite useful.
2009/12/11 Marc Weber marco-owe...@gmx.de
hackage is success because:
Hi Wren,
Thank you for taking the time for replying.
Can you reread the wiki section labeled implementation details?
I don't want hackage to be the wiki. I only want hackage to host a link
to the wiki.
There maybe reasons to host the wiki on hackage. Eg hackage does know
when a package get's
hackage is success because:
a) many (most) people do use it (by uploading packages)
b) it is a comprehensive list of availible packages if not the most
comprehensive one
Duncan, can you write about your concerns briefly why some maintainers may
dislike
this idea ?
Hackage is missing one
On Fri, Dec 11, 2009 at 7:00 PM, Marc Weber marco-owe...@gmx.de wrote:
hackage is success because:
a) many (most) people do use it (by uploading packages)
b) it is a comprehensive list of availible packages if not the most
comprehensive one
Duncan, can you write about your concerns
14 matches
Mail list logo
