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

Wed Jul 3 19:12:28 BST 2013

There are also practical points that haven't been raised yet.  

At the moment there are only 4 people who can create new repos and payment for the ocaml account is running though my credit card (hence, I'm one of those 4 people - it's ultimately being covered by OCaml Labs).  I think it's unwise to add a large number of 'owners' to this account and I hope the reasons are self-evident.  Therefore, I'd say that the existing 4 people are in a rather privileged position and should be disciplined about what repos they create.

I agree with Ashish's comment that the github/ocaml organisation should only be for "semi-official ocaml stuff".  Discovery of new libs should happen through OPAM so I'd encourage authors to make releases early and often there (and link back to their homepages).  Even if someone else wanted to rewrite half the code of something, it would still involve negotiation between the maintainer and submitter (being under github/ocaml makes almost no practical difference here).  

Given the above, I'd be even more stringent with the criteria and turn it around.  I would only make repos under github/ocaml if it *didn't* make sense to do (or continue) anywhere else.

my 2cents,
Amir

On 3 Jul 2013, at 17:18, Anil Madhavapeddy <anil at recoil.org> wrote:

> 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.
> 
>> 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).
> 
>> 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! 
> 
> -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
>>> 
>>> 
>> 
> 
> _______________________________________________
> Infrastructure mailing list
> Infrastructure at lists.ocaml.org
> http://lists.ocaml.org/listinfo/infrastructure