From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id C9B637EE4E for ; Wed, 6 Nov 2013 12:34:16 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of philippe.wang@cl.cam.ac.uk) identity=pra; client-ip=128.232.25.20; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="philippe.wang@cl.cam.ac.uk"; x-sender="philippe.wang@cl.cam.ac.uk"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of philippe.wang@cl.cam.ac.uk) identity=mailfrom; client-ip=128.232.25.20; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="philippe.wang@cl.cam.ac.uk"; x-sender="philippe.wang@cl.cam.ac.uk"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mta0.cl.cam.ac.uk) identity=helo; client-ip=128.232.25.20; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="philippe.wang@cl.cam.ac.uk"; x-sender="postmaster@mta0.cl.cam.ac.uk"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AggCAOwoelKA6BkUmWdsb2JhbABQCoM/wBCBJRYOAQEBAQEICwsHFCiCJQEBAQMBAQEBNzQLBQsLGC4hBgEvBhMUh1sDCQYNtHANV4kUjGeBLwqBBjMHgyCBEAOVPmODGosjhyCBPoFx X-IPAS-Result: AggCAOwoelKA6BkUmWdsb2JhbABQCoM/wBCBJRYOAQEBAQEICwsHFCiCJQEBAQMBAQEBNzQLBQsLGC4hBgEvBhMUh1sDCQYNtHANV4kUjGeBLwqBBjMHgyCBEAOVPmODGosjhyCBPoFx X-IronPort-AV: E=Sophos;i="4.93,646,1378850400"; d="scan'208";a="41227353" Received: from mta0.cl.cam.ac.uk ([128.232.25.20]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Nov 2013 12:33:30 +0100 Received: from chocolate.mac.cl.cam.ac.uk ([128.232.56.24] helo=[IPv6:::1]) by mta0.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1Ve1N5-0005j4-M9; Wed, 06 Nov 2013 11:34:03 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Philippe Wang In-Reply-To: Date: Wed, 6 Nov 2013 11:34:03 +0000 Cc: Philippe Wang , Amir Chaudhry , caml users , infrastructure Content-Transfer-Encoding: quoted-printable Message-Id: References: <6386BA74-F9BF-4283-A298-ABE30B3A458E@cam.ac.uk> To: Gabriel Scherer X-Mailer: Apple Mail (2.1510) X-Validation-by: philippe.wang@gmail.com Subject: Re: [Caml-list] [ocaml-infra] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org I'd say it thjs way: Your help may consist in reporting bugs (which would b= e fixed by someone else) or fixing bugs, or fixing the contents (this mainl= y means "text contents"), etc. But please concentrate, for the 7 following days, on things that would prev= ent this new site from replacing the current one. (Then, we will work on the rest, i.e., things that need to be fixed but are= not blocking.) For "text contents", the "Edit this page" on the bottom of most pages shoul= d lead you to the right file to edit. :) Cheers, Philippe On Nov 6, 2013, at 11:24 AM, Gabriel Scherer wr= ote: > I must admit I'm a bit lost in this message that mixes process > discussions with a request for participation. >=20 > Would you consider sending a separate mail formulated purely as a call > for participation (focusing on the "please help us this week" part > only), with some details on what you're looking for? If I understand > correctly, this is not about the phoney content of the new website, > but about its look&feel and general user interaction (if this is > correct, you should stress it). Giving a couple of examples of bugs > you've fixed in the past that correspond to what you're looking for > now would be helpful. >=20 > On Wed, Nov 6, 2013 at 11:31 AM, Amir Chaudhry wrote: >> Dear caml-list, >>=20 >> We're close to releasing the new design of ocaml.org but need help from = the community to identify and fix bugs before we switch next week. >>=20 >> Ashish, Christophe, Philippe and I have been discussing how we should go= about this and below is the plan for migration. If you'd like to discuss = any of this, then the infrastructure list is the best place to do so (cced). >>=20 >> 1. We've made a new branch on the main ocaml.org repository [1] with the= redesign. This branch is a fork of the main one and we've simply cleaned = up and replayed our git commits there. >>=20 >> 2. We've built a live version of the new site, which is visible at http:= //preview.ocaml.org - this is rebuilt every few minutes from the branch men= tioned above. >>=20 >> 3. Over the course of one week, we ask the community to review the new s= ite and report any bugs or problems on the issue tracker [2]. We triage tho= se bugs to identify any blockers and work on those first. This is the phas= e we'll be in from *today*. >>=20 >> 4. After one week (7 days), and after blocking bugs have been fixed, we = merge the site into the main branch. This would effectively present the ne= w site to the world. >>=20 >> During the above, we would not be able to accept any new pull requests o= n the old site but would be happy to accept them on the new branch. Hence,= restricting the time frame to one week. >>=20 >> Please note that the above is only intended to merge the *design* and *t= oolchain* for the new site. Specifically, we've created new landing pages,= have new style sheets and have restructured the site's contents as well as= made some new libraries [3, 4]. The new toolchain means people can write = files in markdown, which makes contributing content a lot easier. >>=20 >> Since the files are on GitHub, people don't even need to clone the site = locally to make simple edits (or even add new pages). Just click the 'Edit = this page' link in the footer to be taken to the right file in the reposito= ry and GitHub's editing and pull request features will allow you to make ch= anges and submit updates, all from within your browser [5]. >>=20 >> There is still work to be done on adding new features but the above chan= ges are already a great improvement to the site and are ready to be reviewe= d and merged. >>=20 >> [1] https://github.com/ocaml/ocaml.org/tree/redesign >> [2] https://github.com/ocaml/ocaml.org/issues >> [3] http://pw374.github.io/posts/2013-09-05-22-31-26-about-omd.html >> [4] http://pw374.github.io/posts/2013-10-03-20-39-07-OPAMaging-MPP.html >> [5] https://help.github.com/articles/creating-and-editing-files-in-your-= repository >>=20 >> Best wishes, >> Amir >> _______________________________________________ >> Infrastructure mailing list >> Infrastructure@lists.ocaml.org >> http://lists.ocaml.org/listinfo/infrastructure > _______________________________________________ > Infrastructure mailing list > Infrastructure@lists.ocaml.org > http://lists.ocaml.org/listinfo/infrastructure