[ocaml-infra] Fwd: [opam-repository] Add ocaml-markdown 0.1.1 (#863)

[Sylvain Le Gall]

2013/7/3 Anil Madhavapeddy <anil at recoil.org>:
> On 3 Jul 2013, at 16:44, Sylvain Le Gall <sylvain+ocaml at le-gall.net> wrote:
>
>> 2013/7/3 Ashish Agarwal <agarwal1975 at gmail.com>:
>>>> anyone else's thoughts on how to organise the github.com/ocaml org
>>>
>>> I think the following criteria make sense:
>>>
>>> * The project should be mature.
>>>
>>> * The project should somehow relate to ocaml itself or the ocaml community
>>> in general.
>>>
>>> * There should be reasonable consensus that the above two criteria hold.
>>>
>>
>> Maturity of a project is hard to define.
>>
>> I think it is not a big deal to put there "non-toy" project. E.g. I
>> will not put here my sekred or dirvish-stats repositories, because I
>> don't expect anyone in the OCaml community to be interested in it.
>> However there could be a couple of libraries that will made sense to
>> be there -- even not mature one.
>
> The problem with this particular one is that there are a number of Markdown
> libraries, so this one clearly isn't "the one".  Unlike, say, ocaml-re,
> which is generally what people pick as a regular expression library.
>

Not entirely true, e.g. I am using more pcre-ocaml, just because it
exists in Debian Stable (and Old Stable, which is the ultimate
"mature" criteria). I would say so I don't think we should consider
any "the one" or "mature" libraries, I like to have choices and I
don't feel in position to judge.

>> My criteria would be:
>> * Project where you expect more than one contributor from the OCaml
>> community (including original author)
>> * No strong ownership of the code (i.e. expect that someone wants to
>> rewrite half of the code)
>> * OSI license
>
> This all sounds good.  One other criteria that is loosely enforced is that
> we only put libraries up here that are used by ocaml.org infrastructure.
> This includes ocaml-re, oasis and of course the website repos themselves.
> There will eventually be a Markdown library here too, but we should give
> it some time to figure out which one that is (Philippe is investigating
> the options).

I like the idea to set the goal: "used by ocaml.org infrastructure".
It is a summary of:
- this runs in production
- this is a choice made by a group of people (follow it if you want)

>
>> Although if you start outside of ocaml/ what happens when you'll want
>> to push your personnal project to ocaml/. How can you say to github:
>> from now my project is a fork of these other newly created repository
>> ?
>
> That's a good question -- we just mail Github support to do the switch
> at the moment.
>
>> But if Anil wants me to remove the library, I am fine.
>
> I'd prefer you remove it and move it to wherever you prefer rather than
> me deleting other people's repositories!
>

I'll move it, I was not asking you to do it ;-)

Although, may I ask a delay. Maybe it will be the choice of Philippe
and I don't want to move it 3 times in a week. (forge -> github/ocaml
-> github/gildor478 and maybe back to ocaml/ pending decision of
Philippe). Just tell Philippe to notify to do the move.

> -anil
>
>
>>
>>>
>>> On Wed, Jul 3, 2013 at 6:28 AM, Anil Madhavapeddy <anil at recoil.org> wrote:
>>>>
>>>> Hi Sylvain,
>>>>
>>>> Thanks for uploading the code to Github; that's very useful.
>>>>
>>>> Could you not put this in the ocaml organisation yet, and just keep
>>>> it in your personal repository?  We haven't really worked out which
>>>> libraries
>>>> to put in the "official" repository -- some, like oasis, should be there
>>>> without
>>>> a doubt, but the more work-in-progress efforts like markdown should
>>>> probably
>>>> be given some more thought before being put there.
>>>>
>>>> (anyone else's thoughts on how to organise the github.com/ocaml org are
>>>> welcome, of course -- it's probably best to be cautious before putting
>>>> stuff
>>>> up there though, since it's difficult to move repositories once they're
>>>> established and linked to).
>>>>
>>>> cheers,
>>>> Anil
>>>>
>>>> On 2 Jul 2013, at 21:50, Sylvain Le Gall <sylvain+ocaml at le-gall.net>
>>>> wrote:
>>>>
>>>>> As Christophe suggested, I have migrated the ocaml-markdown source
>>>>> code to github:
>>>>> https://github.com/ocaml/ocaml-markdown
>>>>>
>>>>> The builder is here (but not working due to broken tyxml on godi):
>>>>> http://deci.ovh.le-gall.net:8080/job/ocaml-markdown/
>>>>>
>>>>> Trackers and file distributions remains on:
>>>>> https://forge.ocamlcore.org/projects/ocaml-markdown/
>>>>>
>>>>> Pull request are welcome if you want to add anything to make this
>>>>> project even better suited to your needs.
>>>>>
>>>>> Regards
>>>>> Sylvain
>>>>>
>>>>> 2013/7/2 Sylvain Le Gall <sylvain+ocaml at le-gall.net>:
>>>>>> 2013/7/2 Thomas Gazagnaire <thomas at gazagnaire.org>:
>>>>>>>> Mauricio Fernandez wrote a basic Markdown parser which might fit
>>>>>>>> your needs well.  Have you looked at it yet?
>>>>>>
>>>>>> ocaml-markdown is the one written by Mauricio Fernandez. See the
>>>>>> copyright:
>>>>>>
>>>>>> http://darcs.ocamlcore.org/cgi-bin/darcsweb.cgi?r=ocaml-markdown/ocaml-markdown;a=headblob;f=/src/Markdown.ml
>>>>>>
>>>>>> Well I have extracted it from its initial proejct, but we were in sync
>>>>>> to do it.
>>>>>>
>>>>>>>
>>>>>>> Yup, we are using it in ocaml-cow[1,2] (and we have adapted it to
>>>>>>> (almost) read Github Markdown as well).
>>>>>>>
>>>>>>> Thomas
>>>>>>>
>>>>>>> [1] https://github.com/mirage/ocaml-cow/blob/master/lib/markdown.ml
>>>>>>> [2]
>>>>>>> https://github.com/mirage/ocaml-cow/blob/master/lib/markdown_github.ml
>>>>>>> _______________________________________________
>>>>>>> Infrastructure mailing list
>>>>>>> Infrastructure at lists.ocaml.org
>>>>>>> http://lists.ocaml.org/listinfo/infrastructure
>>>>> _______________________________________________
>>>>> Infrastructure mailing list
>>>>> Infrastructure at lists.ocaml.org
>>>>> http://lists.ocaml.org/listinfo/infrastructure
>>>>>
>>>>
>>>> _______________________________________________
>>>> Infrastructure mailing list
>>>> Infrastructure at lists.ocaml.org
>>>> http://lists.ocaml.org/listinfo/infrastructure
>>>
>>>
>>
>