Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homepage link broken #22

Closed
Profpatsch opened this issue Jan 11, 2015 · 5 comments
Closed

Homepage link broken #22

Profpatsch opened this issue Jan 11, 2015 · 5 comments

Comments

@Profpatsch
Copy link

Another thing:

http://legacy.cs.uu.nl/daan/parsec.html

@gbaz
Copy link
Contributor

gbaz commented Mar 6, 2015

It would actually be very good if we could also pull the documentation from the homepage (as hosted by web.archive.org: http://web.archive.org/web/20140329210442/http://legacy.cs.uu.nl/daan/download/parsec/parsec.html) and ported the parts that aren't just haddocks into a new parsec documentation module or the like, and put some very simple "getting started" bits from them at the top of the main Text.Parsec module. (having updated them to work with the latest parsec).

Additionally there should be some top level documentation in the package indicating that that is the main entry point, and also which modules only remain for compatibility...

@aslatter
Copy link
Collaborator

The first comment has been fixed on Hackage but not the second, so I'm leaving this issue open for now.

I haven't heard from Daan Leijen that it would be okay to copy his text verbatim elsewhere, so anything pulled in to the package description or module documentation would need to be new text.

@gbaz
Copy link
Contributor

gbaz commented Mar 22, 2015

did he just not reply to your email? did you try with a relatively recent address such as that in this paper (http://research.microsoft.com/pubs/210640/paper.pdf) ?

I hope we can get in touch with him, because it would be much easier to do things that way, and I can't imagine he would object, even if it is slow to get a response and get his approval...

@aslatter
Copy link
Collaborator

Yeah, that's the email I tried. It was a ways back.

@aslatter
Copy link
Collaborator

aslatter commented Apr 5, 2015

Closing this ticket, and moving the discussion of the old documentation to #33.

@aslatter aslatter closed this as completed Apr 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants