[Caml-list] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Caml-list] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Amir Chaudhry]

Dear caml-list,

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.

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).

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.

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 mentioned above.  

3. Over the course of one week, we ask the community to review the new site and report any bugs or problems on the issue tracker [2]. We triage those bugs to identify any blockers and work on those first.  This is the phase we'll be in from *today*.

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 new site to the world.  

During the above, we would not be able to accept any new pull requests on the old site but would be happy to accept them on the new branch.  Hence, restricting the time frame to one week.  

Please note that the above is only intended to merge the *design* and *toolchain* 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.  

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 repository and GitHub's editing and pull request features will allow you to make changes and submit updates, all from within your browser [5].  

There is still work to be done on adding new features but the above changes are already a great improvement to the site and are ready to be reviewed and merged.

[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

Best wishes,
Amir

Re: [Caml-list] [ocaml-infra] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Gabriel Scherer]

I must admit I'm a bit lost in this message that mixes process
discussions with a request for participation.

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.

On Wed, Nov 6, 2013 at 11:31 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
> Dear caml-list,
>
> 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.
>
> 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).
>
> 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.
>
> 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 mentioned above.
>
> 3. Over the course of one week, we ask the community to review the new site and report any bugs or problems on the issue tracker [2]. We triage those bugs to identify any blockers and work on those first.  This is the phase we'll be in from *today*.
>
> 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 new site to the world.
>
> During the above, we would not be able to accept any new pull requests on the old site but would be happy to accept them on the new branch.  Hence, restricting the time frame to one week.
>
> Please note that the above is only intended to merge the *design* and *toolchain* 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.
>
> 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 repository and GitHub's editing and pull request features will allow you to make changes and submit updates, all from within your browser [5].
>
> There is still work to be done on adding new features but the above changes are already a great improvement to the site and are ready to be reviewed and merged.
>
> [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
>
> Best wishes,
> Amir
> _______________________________________________
> Infrastructure mailing list
> Infrastructure@lists.ocaml.org
> http://lists.ocaml.org/listinfo/infrastructure

Re: [Caml-list] [ocaml-infra] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Philippe Wang]

I'd say it thjs way: Your help may consist in reporting bugs (which would be fixed by someone else) or fixing bugs, or fixing the contents (this mainly means "text contents"), etc.
But please concentrate, for the 7 following days, on things that would prevent 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 should lead you to the right file to edit. :)

Cheers,
Philippe


On Nov 6, 2013, at 11:24 AM, Gabriel Scherer <gabriel.scherer@gmail.com> wrote:

> I must admit I'm a bit lost in this message that mixes process
> discussions with a request for participation.
> 
> 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.
> 
> On Wed, Nov 6, 2013 at 11:31 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>> Dear caml-list,
>> 
>> 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.
>> 
>> 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).
>> 
>> 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.
>> 
>> 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 mentioned above.
>> 
>> 3. Over the course of one week, we ask the community to review the new site and report any bugs or problems on the issue tracker [2]. We triage those bugs to identify any blockers and work on those first.  This is the phase we'll be in from *today*.
>> 
>> 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 new site to the world.
>> 
>> During the above, we would not be able to accept any new pull requests on the old site but would be happy to accept them on the new branch.  Hence, restricting the time frame to one week.
>> 
>> Please note that the above is only intended to merge the *design* and *toolchain* 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.
>> 
>> 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 repository and GitHub's editing and pull request features will allow you to make changes and submit updates, all from within your browser [5].
>> 
>> There is still work to be done on adding new features but the above changes are already a great improvement to the site and are ready to be reviewed and merged.
>> 
>> [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
>> 
>> 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

Re: [Caml-list] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Kakadu]

Amir,

Are all bugs related to redesign are marked with `redesign` tag? I
ask, because very small count of opened bugs are tagged with
`redesign`. Can I rely on tagged questions  when I will check is my
bug reported or not?

Kind regards,
Kakadu

On Wed, Nov 6, 2013 at 2:31 PM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
> Dear caml-list,
>
> 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.
>
> 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).
>
> 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.
>
> 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 mentioned above.
>
> 3. Over the course of one week, we ask the community to review the new site and report any bugs or problems on the issue tracker [2]. We triage those bugs to identify any blockers and work on those first.  This is the phase we'll be in from *today*.
>
> 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 new site to the world.
>
> During the above, we would not be able to accept any new pull requests on the old site but would be happy to accept them on the new branch.  Hence, restricting the time frame to one week.
>
> Please note that the above is only intended to merge the *design* and *toolchain* 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.
>
> 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 repository and GitHub's editing and pull request features will allow you to make changes and submit updates, all from within your browser [5].
>
> There is still work to be done on adding new features but the above changes are already a great improvement to the site and are ready to be reviewed and merged.
>
> [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
>
> Best wishes,
> Amir
>
> --
> 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

Re: [Caml-list] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Amir Chaudhry]

Dear Kakadu, 

Yes, they'll be tagged as `redesign` but there may be a delay between submitting an issue and seeing it tagged.  Apologies for that but don't worry about submitting duplicates as we'll cross reference and close any dupes as we triage.

Thanks!
Amir


On 6 Nov 2013, at 13:31, Kakadu <kakadu.hafanana@gmail.com> wrote:

> Amir,
> 
> Are all bugs related to redesign are marked with `redesign` tag? I
> ask, because very small count of opened bugs are tagged with
> `redesign`. Can I rely on tagged questions  when I will check is my
> bug reported or not?
> 
> Kind regards,
> Kakadu
> 
> On Wed, Nov 6, 2013 at 2:31 PM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>> Dear caml-list,
>> 
>> 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.
>> 
>> 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).
>> 
>> 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.
>> 
>> 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 mentioned above.
>> 
>> 3. Over the course of one week, we ask the community to review the new site and report any bugs or problems on the issue tracker [2]. We triage those bugs to identify any blockers and work on those first.  This is the phase we'll be in from *today*.
>> 
>> 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 new site to the world.
>> 
>> During the above, we would not be able to accept any new pull requests on the old site but would be happy to accept them on the new branch.  Hence, restricting the time frame to one week.
>> 
>> Please note that the above is only intended to merge the *design* and *toolchain* 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.
>> 
>> 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 repository and GitHub's editing and pull request features will allow you to make changes and submit updates, all from within your browser [5].
>> 
>> There is still work to be done on adding new features but the above changes are already a great improvement to the site and are ready to be reviewed and merged.
>> 
>> [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
>> 
>> Best wishes,
>> Amir
>> 
>> --
>> 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

Re: [Caml-list] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Yaron Minsky]

Amir, is the live book being kept up to date?  I see lots of commits
and bugs being resolved, but it's not obviously showing up on
preview.ocaml.org.

y

On Wed, Nov 6, 2013 at 5:31 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
> Dear caml-list,
>
> 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.
>
> 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).
>
> 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.
>
> 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 mentioned above.
>
> 3. Over the course of one week, we ask the community to review the new site and report any bugs or problems on the issue tracker [2]. We triage those bugs to identify any blockers and work on those first.  This is the phase we'll be in from *today*.
>
> 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 new site to the world.
>
> During the above, we would not be able to accept any new pull requests on the old site but would be happy to accept them on the new branch.  Hence, restricting the time frame to one week.
>
> Please note that the above is only intended to merge the *design* and *toolchain* 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.
>
> 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 repository and GitHub's editing and pull request features will allow you to make changes and submit updates, all from within your browser [5].
>
> There is still work to be done on adding new features but the above changes are already a great improvement to the site and are ready to be reviewed and merged.
>
> [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
>
> Best wishes,
> Amir
>
> --
> 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

Re: [Caml-list] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org

[Yaron Minsky]

Actually, ignore that.  On further investigation, the patch I was
looking for really has been applied.

Sorry for the noise.

y

On Sat, Nov 9, 2013 at 9:34 PM, Yaron Minsky <yminsky@gmail.com> wrote:
> Amir, is the live book being kept up to date?  I see lots of commits
> and bugs being resolved, but it's not obviously showing up on
> preview.ocaml.org.
>
> y
>
> On Wed, Nov 6, 2013 at 5:31 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>> Dear caml-list,
>>
>> 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.
>>
>> 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).
>>
>> 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.
>>
>> 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 mentioned above.
>>
>> 3. Over the course of one week, we ask the community to review the new site and report any bugs or problems on the issue tracker [2]. We triage those bugs to identify any blockers and work on those first.  This is the phase we'll be in from *today*.
>>
>> 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 new site to the world.
>>
>> During the above, we would not be able to accept any new pull requests on the old site but would be happy to accept them on the new branch.  Hence, restricting the time frame to one week.
>>
>> Please note that the above is only intended to merge the *design* and *toolchain* 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.
>>
>> 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 repository and GitHub's editing and pull request features will allow you to make changes and submit updates, all from within your browser [5].
>>
>> There is still work to be done on adding new features but the above changes are already a great improvement to the site and are ready to be reviewed and merged.
>>
>> [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
>>
>> Best wishes,
>> Amir
>>
>> --
>> 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