Google Summer of Code 2015

Google Summer of Code 2015

[Raniere Silva]

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

Hi all,

I became a heavy user of Pandoc when one project that I contribute, Software
Carpentry, starting using it at their software stack and since them I report a
few bugs to Pandoc.

I know that John already published a suggestion for Google Summer of Code,
https://github.com/jgm/pandoc/issues/1852, but I want to ask for tips of how
learn Haskell and starting contributing to Pandoc so that I can apply for Google
Summer of Code.

Thanks in advance,
Raniere

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20150116023632.GZ19197%40buriti.rgaiacs.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Google Summer of Code 2015

[Matthew Pickering]

Hi Raniere,

Pandoc is a great first project to get your hands dirty with Haskell.
The structure is very simple and doesn't use very many language
extensions.

This is one of the most commonly referred to tutorials:
https://github.com/bitemyapp/learnhaskell

It eventually boils down to recommending this course:
http://www.seas.upenn.edu/~cis194/spring13/index.html

Having looked at the syllabus, it seems that after understanding
everything there it should be possible to understand most of pandoc's
code.

There are lots of open issues on the issue tracker. I've tried to tag
them all appropriately; you can read more about the classification
here.

https://github.com/jgm/pandoc/blob/master/CONTRIBUTING.md

Of course, any questions, feel free to ping me or post on the mailing list.

Matt

On Fri, Jan 16, 2015 at 2:36 AM, Raniere Silva <raniere-Xhq86aZylhRTIXuwt5Zssw@public.gmane.org> wrote:
> Hi all,
>
> I became a heavy user of Pandoc when one project that I contribute, Software
> Carpentry, starting using it at their software stack and since them I report a
> few bugs to Pandoc.
>
> I know that John already published a suggestion for Google Summer of Code,
> https://github.com/jgm/pandoc/issues/1852, but I want to ask for tips of how
> learn Haskell and starting contributing to Pandoc so that I can apply for Google
> Summer of Code.
>
> Thanks in advance,
> Raniere
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20150116023632.GZ19197%40buriti.rgaiacs.com.
> For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2015

[Matthew Pickering]

[-- Attachment #1: Type: text/plain, Size: 3764 bytes --]

Thanks for your feedback John.

I think it's an interesting, attainable project so hopefully someone picks
it up.

On Sun, Feb 22, 2015 at 7:06 AM, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:

> +++ Ivan Lazar Miljenovic [Feb 22 15 14:12 ]:
>
>  On 22 February 2015 at 10:27, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
>>
>>> +++ John MacFarlane [Feb 21 15 15:15 ]:
>>>
>>>>
>>>> +++ Matthew Pickering [Feb 20 15 21:45 ]:
>>>>
>>>>>
>>>>> Dear list,
>>>>>
>>>>> I have created a ticket on the Haskell.org GSoC idea list for one of
>>>>> the
>>>>> ideas which John suggested[1] would be suitable. It is important that
>>>>> that
>>>>> projects are fairly freestanding (not requiring intimate knowledge of
>>>>> the
>>>>> architecture) and are selected based on utility to the Haskell
>>>>> community
>>>>> as
>>>>> a whole.
>>>>>
>>>>> If anyone has any comments, feel free to edit the proposal or reply
>>>>> here
>>>>> and I will make the changes.
>>>>>
>>>>> https://ghc.haskell.org/trac/summer-of-code/ticket/1660#ticket
>>>>>
>>>>
>>>>
>>>> It's a good proposal.  Some further motivation:  pandoc's current
>>>> Markdown parser is not very efficient.  It even goes exponential on some
>>>> inputs, which is not good for web use.
>>>>
>>>> I've already developed algorithms for parsing CommonMark efficiently,
>>>> without backtracking.  They are so much more efficient than what pandoc
>>>> currently does that even the JavaScript implementation of commonmark is
>>>> 3-4 times faster than pandoc, and the C implementation is 30-40 times
>>>> faster.
>>>>
>>>> So I'd hope for a 10X speedup with a rewrite.
>>>>
>>>
>>>
>>> Further thoughts on this.
>>>
>>> The best GSOC projects benefit the whole community (infrastructure).
>>>
>>> So, it might make more sense to write a standalone CommonMark parser
>>> library with a liberal (BSD) license, that could be used in other
>>> Haskell projects (e.g., potentially, in some future version of Haddock).
>>>
>>> If this is made extensible, pandoc could simply use this library.
>>> But the library would also be available for other purposes.
>>>
>>> Pandoc itself won't ever be relicensed.  But I think it would be a good
>>> idea, if contributors will agree, to dual license pandoc-types BSD3/GPL.
>>> (There are only a few commits by people other than me, so this is
>>> feasible.)
>>>
>>
>> If pandoc-types is licensed BSD3, is there any real need for it to
>> also be licensed GPL (especially since Cabal doesn't really understand
>> dual-licensing)?
>>
>
> Probably not.
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/pandoc-discuss/20150222070657.GB42783%40localhost.hsd1.ca.comcast.
> net.
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CALuQ0m9j-jWK6LLuQZirKMvwBQZ%2BPDSOS15WUypUH_TRzXe8%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 5653 bytes --]

Re: Google Summer of Code 2015

[John MacFarlane]

+++ Ivan Lazar Miljenovic [Feb 22 15 14:12 ]:
>On 22 February 2015 at 10:27, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
>> +++ John MacFarlane [Feb 21 15 15:15 ]:
>>>
>>> +++ Matthew Pickering [Feb 20 15 21:45 ]:
>>>>
>>>> Dear list,
>>>>
>>>> I have created a ticket on the Haskell.org GSoC idea list for one of the
>>>> ideas which John suggested[1] would be suitable. It is important that
>>>> that
>>>> projects are fairly freestanding (not requiring intimate knowledge of the
>>>> architecture) and are selected based on utility to the Haskell community
>>>> as
>>>> a whole.
>>>>
>>>> If anyone has any comments, feel free to edit the proposal or reply here
>>>> and I will make the changes.
>>>>
>>>> https://ghc.haskell.org/trac/summer-of-code/ticket/1660#ticket
>>>
>>>
>>> It's a good proposal.  Some further motivation:  pandoc's current
>>> Markdown parser is not very efficient.  It even goes exponential on some
>>> inputs, which is not good for web use.
>>>
>>> I've already developed algorithms for parsing CommonMark efficiently,
>>> without backtracking.  They are so much more efficient than what pandoc
>>> currently does that even the JavaScript implementation of commonmark is
>>> 3-4 times faster than pandoc, and the C implementation is 30-40 times
>>> faster.
>>>
>>> So I'd hope for a 10X speedup with a rewrite.
>>
>>
>> Further thoughts on this.
>>
>> The best GSOC projects benefit the whole community (infrastructure).
>>
>> So, it might make more sense to write a standalone CommonMark parser
>> library with a liberal (BSD) license, that could be used in other
>> Haskell projects (e.g., potentially, in some future version of Haddock).
>>
>> If this is made extensible, pandoc could simply use this library.
>> But the library would also be available for other purposes.
>>
>> Pandoc itself won't ever be relicensed.  But I think it would be a good
>> idea, if contributors will agree, to dual license pandoc-types BSD3/GPL.
>> (There are only a few commits by people other than me, so this is
>> feasible.)
>
>If pandoc-types is licensed BSD3, is there any real need for it to
>also be licensed GPL (especially since Cabal doesn't really understand
>dual-licensing)?

Probably not.

Re: Google Summer of Code 2015

[Ivan Lazar Miljenovic]

On 22 February 2015 at 10:27, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
> +++ John MacFarlane [Feb 21 15 15:15 ]:
>>
>> +++ Matthew Pickering [Feb 20 15 21:45 ]:
>>>
>>> Dear list,
>>>
>>> I have created a ticket on the Haskell.org GSoC idea list for one of the
>>> ideas which John suggested[1] would be suitable. It is important that
>>> that
>>> projects are fairly freestanding (not requiring intimate knowledge of the
>>> architecture) and are selected based on utility to the Haskell community
>>> as
>>> a whole.
>>>
>>> If anyone has any comments, feel free to edit the proposal or reply here
>>> and I will make the changes.
>>>
>>> https://ghc.haskell.org/trac/summer-of-code/ticket/1660#ticket
>>
>>
>> It's a good proposal.  Some further motivation:  pandoc's current
>> Markdown parser is not very efficient.  It even goes exponential on some
>> inputs, which is not good for web use.
>>
>> I've already developed algorithms for parsing CommonMark efficiently,
>> without backtracking.  They are so much more efficient than what pandoc
>> currently does that even the JavaScript implementation of commonmark is
>> 3-4 times faster than pandoc, and the C implementation is 30-40 times
>> faster.
>>
>> So I'd hope for a 10X speedup with a rewrite.
>
>
> Further thoughts on this.
>
> The best GSOC projects benefit the whole community (infrastructure).
>
> So, it might make more sense to write a standalone CommonMark parser
> library with a liberal (BSD) license, that could be used in other
> Haskell projects (e.g., potentially, in some future version of Haddock).
>
> If this is made extensible, pandoc could simply use this library.
> But the library would also be available for other purposes.
>
> Pandoc itself won't ever be relicensed.  But I think it would be a good
> idea, if contributors will agree, to dual license pandoc-types BSD3/GPL.
> (There are only a few commits by people other than me, so this is
> feasible.)

If pandoc-types is licensed BSD3, is there any real need for it to
also be licensed GPL (especially since Cabal doesn't really understand
dual-licensing)?

>
> This would allow authors of more liberally licensed libraries to
> include a nice "handle" or interface with pandoc.  For example, a
> BSD licensed CommonMark parsing library could provide an option
> to parse to a Pandoc structure, which could then be consumed by
> any of the pandoc writers.
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/20150221232739.GA42324%40localhost.hsd1.ca.comcast.net.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Ivan Lazar Miljenovic
Ivan.Miljenovic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
http://IvanMiljenovic.wordpress.com

Re: Google Summer of Code 2015

[John MacFarlane]

+++ John MacFarlane [Feb 21 15 15:15 ]:
>+++ Matthew Pickering [Feb 20 15 21:45 ]:
>>Dear list,
>>
>>I have created a ticket on the Haskell.org GSoC idea list for one of the
>>ideas which John suggested[1] would be suitable. It is important that that
>>projects are fairly freestanding (not requiring intimate knowledge of the
>>architecture) and are selected based on utility to the Haskell community as
>>a whole.
>>
>>If anyone has any comments, feel free to edit the proposal or reply here
>>and I will make the changes.
>>
>>https://ghc.haskell.org/trac/summer-of-code/ticket/1660#ticket
>
>It's a good proposal.  Some further motivation:  pandoc's current
>Markdown parser is not very efficient.  It even goes exponential on some
>inputs, which is not good for web use.
>
>I've already developed algorithms for parsing CommonMark efficiently,
>without backtracking.  They are so much more efficient than what pandoc
>currently does that even the JavaScript implementation of commonmark is
>3-4 times faster than pandoc, and the C implementation is 30-40 times
>faster.
>
>So I'd hope for a 10X speedup with a rewrite.

Further thoughts on this.

The best GSOC projects benefit the whole community (infrastructure).

So, it might make more sense to write a standalone CommonMark parser
library with a liberal (BSD) license, that could be used in other
Haskell projects (e.g., potentially, in some future version of Haddock).

If this is made extensible, pandoc could simply use this library.
But the library would also be available for other purposes.

Pandoc itself won't ever be relicensed.  But I think it would be a good
idea, if contributors will agree, to dual license pandoc-types BSD3/GPL.
(There are only a few commits by people other than me, so this is
feasible.)

This would allow authors of more liberally licensed libraries to
include a nice "handle" or interface with pandoc.  For example, a
BSD licensed CommonMark parsing library could provide an option
to parse to a Pandoc structure, which could then be consumed by
any of the pandoc writers.

Re: Google Summer of Code 2015

[John MacFarlane]

+++ Matthew Pickering [Feb 20 15 21:45 ]:
>Dear list,
>
>I have created a ticket on the Haskell.org GSoC idea list for one of the
>ideas which John suggested[1] would be suitable. It is important that that
>projects are fairly freestanding (not requiring intimate knowledge of the
>architecture) and are selected based on utility to the Haskell community as
>a whole.
>
>If anyone has any comments, feel free to edit the proposal or reply here
>and I will make the changes.
>
>https://ghc.haskell.org/trac/summer-of-code/ticket/1660#ticket

It's a good proposal.  Some further motivation:  pandoc's current
Markdown parser is not very efficient.  It even goes exponential on some
inputs, which is not good for web use.

I've already developed algorithms for parsing CommonMark efficiently,
without backtracking.  They are so much more efficient than what pandoc
currently does that even the JavaScript implementation of commonmark is
3-4 times faster than pandoc, and the C implementation is 30-40 times
faster.

So I'd hope for a 10X speedup with a rewrite.

Google Summer of Code 2015

[Matthew Pickering]

[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]

Dear list,

I have created a ticket on the Haskell.org GSoC idea list for one of the
ideas which John suggested[1] would be suitable. It is important that that
projects are fairly freestanding (not requiring intimate knowledge of the
architecture) and are selected based on utility to the Haskell community as
a whole.

If anyone has any comments, feel free to edit the proposal or reply here
and I will make the changes.

https://ghc.haskell.org/trac/summer-of-code/ticket/1660#ticket

If there are any other projects that people feel would be beneficial and
suitable for a summer's work then please let me know and I can submit
further ideas to the list.

PS. Please note that I do not intend to apply this year, this is to
facilitate another interested party.

Matt

[1]: https://github.com/jgm/pandoc/issues/1852

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CALuQ0m8oGFfhneJtng%3DvRtRbfZ%2B3Kip6x_rUDc%2Byxqfv_6Abpw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 2149 bytes --]