From: Ashish Agarwal <agarwal1975@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
Philippe Wang <mail@philippewang.info>,
OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] latest version
Date: Sat, 14 May 2016 19:03:11 -0400 [thread overview]
Message-ID: <CAMu2m2JcUFC-c87Auv1M7QNQWtirgLfhMfc5dLu0NcMfz1wMyw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1605141501560.2075@localhost6.localdomain6>
[-- Attachment #1: Type: text/plain, Size: 3412 bytes --]
I'll work on Issue #701 <https://github.com/ocaml/ocaml.org/issues/701>.
Unfortunately even seemingly small issues sometimes end up taking hours,
which is often more than the volunteers have.
> a clear description of the process to follow to edit ocaml.org on the event
of an OCaml release.
Currently I port the page from caml.inria.fr, which I feel is a duplication
of work. It would certainly be better if the release page could be made
directly on ocaml.org. The relevant directory in the repo is site/releases,
and one simply has to copy a previous page to start, and update the text
and links as appropriate.
On Sat, May 14, 2016 at 9:02 AM, Julia Lawall <julia.lawall@lip6.fr> wrote:
>
>
> On Sat, 14 May 2016, Gabriel Scherer wrote:
>
> > We discussed how to give more visibility to OCaml releases last
> September:
> >
> http://lists.ocaml.org/pipermail/infrastructure/2015-September/000537.html
> > https://github.com/ocaml/ocaml.org/issues/701
> >
> > The feature request #701 did not result in a change, but the
> > discussions were about more invasive change than just adding some
> > content on one of the pages, so I'm not sure it's reasonable to expect
> > an external contributor to lead it.
> >
> > From an "upstream OCaml" point of view, what I would like to have is a
> > clear description of the process to follow to edit ocaml.org on the
> > event of an OCaml release. I think the people that know ocaml.org best
> > should decide on that, and then I'd try to get it done on each
> > release.
>
> Thanks, I didn't really want to become responsible for this...
>
> julia
>
> >
> > On Sat, May 14, 2016 at 7:58 AM, Philippe Wang <mail@philippewang.info>
> wrote:
> > > Hi, perhaps you could make a pull request by editing the concerned
> > > page on ocaml.org? :)
> > > There's an edit button on each page (the pencil on the top right
> corner). :)
> > > Cheers,
> > >
> > >
> > > On Sat, May 14, 2016 at 9:12 AM, Julia Lawall <julia.lawall@lip6.fr>
> wrote:
> > >> On ocaml.org, it could be more ovious what is the latest version of
> ocaml.
> > >> This information could at least be at the top of the "Install OCaml"
> > >> page. Instead, one has to scroll down to the bottom to find "From
> Source"
> > >> and click on "Download the source for your preferred OCaml release".
> > >>
> > >> julia
> > >>
> > >>
> > >> --
> > >> Caml-list mailing list. Subscription management and archives:
> > >> https://sympa.inria.fr/sympa/arc/caml-list
> > >> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > >> Bug reports: http://caml.inria.fr/bin/caml-bugs
> > >
> > >
> > >
> > > --
> > > Philippe Wang
> > > mail@philippewang.info
> > >
> > > --
> > > Caml-list mailing list. Subscription management and archives:
> > > https://sympa.inria.fr/sympa/arc/caml-list
> > > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > > Bug reports: http://caml.inria.fr/bin/caml-bugs
> >
> > --
> > Caml-list mailing list. Subscription management and archives:
> > https://sympa.inria.fr/sympa/arc/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
> >
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 6484 bytes --]
prev parent reply other threads:[~2016-05-14 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 7:12 Julia Lawall
2016-05-14 11:58 ` Philippe Wang
2016-05-14 12:46 ` Gabriel Scherer
2016-05-14 13:02 ` Julia Lawall
2016-05-14 23:03 ` Ashish Agarwal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMu2m2JcUFC-c87Auv1M7QNQWtirgLfhMfc5dLu0NcMfz1wMyw@mail.gmail.com \
--to=agarwal1975@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=mail@philippewang.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).