[Meta] Proposal status page

I got sidetracked today and mocked up a proposal "status page":

    Swift Evolution

This moves the proposal status info (currently in README.md) into a
separate "source of truth":

    https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using XSLT.
Unfortunately, in order to get this working on GitHub Pages, I had to load
the files using JavaScript (otherwise the browser blocks the cross-origin
requests):
https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

If we wanted to adopt this for the official swift-evolution repo, the steps
would be:

    1. push the XML and XSL files to master

    2. push a gh-pages branch with the status page

    3. update README.md on master to point to the status page, rather than
duplicating all the information.

Thoughts? Tweaks? Insults?

Jacob

It occurs to me that moving swift-evolution to use *only* a gh-pages
branch, like swift-internals does, would allow this to work without JS.

···

On Thu, Jul 14, 2016 at 1:30 AM, Jacob Bandes-Storch <jtbandes@gmail.com> wrote:

I got sidetracked today and mocked up a proposal "status page":

    Swift Evolution

This moves the proposal status info (currently in README.md) into a
separate "source of truth":

    https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using XSLT.
Unfortunately, in order to get this working on GitHub Pages, I had to load
the files using JavaScript (otherwise the browser blocks the cross-origin
requests):
https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

If we wanted to adopt this for the official swift-evolution repo, the
steps would be:

    1. push the XML and XSL files to master

    2. push a gh-pages branch with the status page

    3. update README.md on master to point to the status page, rather than
duplicating all the information.

Thoughts? Tweaks? Insults?

Jacob

Cool! Looks great!

-Thorsten

···

Am 14.07.2016 um 10:30 schrieb Jacob Bandes-Storch via swift-evolution <swift-evolution@swift.org>:

I got sidetracked today and mocked up a proposal "status page":

    Swift Evolution

This moves the proposal status info (currently in README.md) into a separate "source of truth":

    https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using XSLT. Unfortunately, in order to get this working on GitHub Pages, I had to load the files using JavaScript (otherwise the browser blocks the cross-origin requests): https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

If we wanted to adopt this for the official swift-evolution repo, the steps would be:

    1. push the XML and XSL files to master

    2. push a gh-pages branch with the status page

    3. update README.md on master to point to the status page, rather than duplicating all the information.

Thoughts? Tweaks? Insults?

Jacob
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

This new feature was added to GitHub Pages a few weeks ago:

<Simpler GitHub Pages publishing - The GitHub Blog;

You might be able to publish from the `master` branch, without using JavaScript:

<https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/&gt;

-- Ben

···

On 14 Jul 2016, at 09:30, Jacob Bandes-Storch wrote:

I got sidetracked today and mocked up a proposal "status page":

    Swift Evolution

This moves the proposal status info (currently in README.md) into a separate "source of truth":

    https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using XSLT. Unfortunately, in order to get this working on GitHub Pages, I had to load the files using JavaScript (otherwise the browser blocks the cross-origin requests): https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

Only talking about the page and its content, since I didn't review the
code and how it works: I love it! I think it would be great to have this
in the official repo.

···

On Thu, Jul 14, 2016, at 11:46, Jacob Bandes-Storch via swift-evolution wrote:

It occurs to me that moving swift-evolution to use *only* a gh-
pages branch, like swift-internals does, would allow this to work
without JS.

On Thu, Jul 14, 2016 at 1:30 AM, Jacob Bandes-Storch > <jtbandes@gmail.com> wrote:

I got sidetracked today and mocked up a proposal "status page":

Swift Evolution

This moves the proposal status info (currently in README.md) into a
separate "source of truth":

https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using
XSLT. Unfortunately, in order to get this working on GitHub Pages, I
had to load the files using JavaScript (otherwise the browser blocks
the cross-origin requests):
https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

If we wanted to adopt this for the official swift-evolution repo, the
steps would be:

    1. push the XML and XSL files to master

    2. push a gh-pages branch with the status page

    3. update README.md on master to point to the status page, rather
       than duplicating all the information.

Thoughts? Tweaks? Insults?

Jacob

_________________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

This is now live: http://apple.github.io/swift-evolution/

···

On Fri, Jul 15, 2016 at 8:08 AM, Thorsten Seitz <tseitz42@icloud.com> wrote:

Cool! Looks great!

-Thorsten

Am 14.07.2016 um 10:30 schrieb Jacob Bandes-Storch via swift-evolution < > swift-evolution@swift.org>:

I got sidetracked today and mocked up a proposal "status page":

    Swift Evolution

This moves the proposal status info (currently in README.md) into a
separate "source of truth":

    https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using XSLT.
Unfortunately, in order to get this working on GitHub Pages, I had to load
the files using JavaScript (otherwise the browser blocks the cross-origin
requests):
https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

If we wanted to adopt this for the official swift-evolution repo, the
steps would be:

    1. push the XML and XSL files to master

    2. push a gh-pages branch with the status page

    3. update README.md on master to point to the status page, rather than
duplicating all the information.

Thoughts? Tweaks? Insults?

Jacob

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

This is now live: http://apple.github.io/swift-evolution/

Very very nice!

I wonder if we should do something to avoid the 404 here though: http://apple.github.io <http://apple.github.io/&gt;

Perhaps a redirect to GitHub - apple/swift: The Swift Programming Language or maybe directly to https://github.com/apple/swift/blob/master/README.md? <https://github.com/apple/swift/blob/master/README.md?&gt;

Mark

···

On Jul 18, 2016, at 4:44 PM, Jacob Bandes-Storch via swift-evolution <swift-evolution@swift.org> wrote:

On Fri, Jul 15, 2016 at 8:08 AM, Thorsten Seitz <tseitz42@icloud.com <mailto:tseitz42@icloud.com>> wrote:
Cool! Looks great!

-Thorsten

Am 14.07.2016 um 10:30 schrieb Jacob Bandes-Storch via swift-evolution <swift-evolution@swift.org <mailto:swift-evolution@swift.org>>:

I got sidetracked today and mocked up a proposal "status page":

    Swift Evolution

This moves the proposal status info (currently in README.md) into a separate "source of truth":

    https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using XSLT. Unfortunately, in order to get this working on GitHub Pages, I had to load the files using JavaScript (otherwise the browser blocks the cross-origin requests): https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

If we wanted to adopt this for the official swift-evolution repo, the steps would be:

    1. push the XML and XSL files to master

    2. push a gh-pages branch with the status page

    3. update README.md on master to point to the status page, rather than duplicating all the information.

Thoughts? Tweaks? Insults?

Jacob
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org <mailto:swift-evolution@swift.org>
https://lists.swift.org/mailman/listinfo/swift-evolution

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

I'm not sure whether it's possible to have both an "organization page" and
a "project page" (used for both swift-evolution and swift-internals).
Someone could certainly try it out.

Jacob

···

On Mon, Jul 18, 2016 at 4:57 PM, Mark Lacey <mark.lacey@apple.com> wrote:

On Jul 18, 2016, at 4:44 PM, Jacob Bandes-Storch via swift-evolution < > swift-evolution@swift.org> wrote:

This is now live: http://apple.github.io/swift-evolution/

Very very nice!

I wonder if we should do something to avoid the 404 here though:
http://apple.github.io

Perhaps a redirect to GitHub - apple/swift: The Swift Programming Language or maybe directly to
https://github.com/apple/swift/blob/master/README.md?

Mark

On Fri, Jul 15, 2016 at 8:08 AM, Thorsten Seitz <tseitz42@icloud.com> > wrote:

Cool! Looks great!

-Thorsten

Am 14.07.2016 um 10:30 schrieb Jacob Bandes-Storch via swift-evolution < >> swift-evolution@swift.org>:

I got sidetracked today and mocked up a proposal "status page":

    Swift Evolution

This moves the proposal status info (currently in README.md) into a
separate "source of truth":

    https://github.com/jtbandes/swift-evolution/blob/master/proposals.xml

The status page is then generated from the source of truth using XSLT.
Unfortunately, in order to get this working on GitHub Pages, I had to load
the files using JavaScript (otherwise the browser blocks the cross-origin
requests):
https://github.com/jtbandes/swift-evolution/blob/gh-pages/index.html\.

If we wanted to adopt this for the official swift-evolution repo, the
steps would be:

    1. push the XML and XSL files to master

    2. push a gh-pages branch with the status page

    3. update README.md on master to point to the status page, rather
than duplicating all the information.

Thoughts? Tweaks? Insults?

Jacob

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

The Swift Open Source project isn’t the only project under github.com/apple. Any landing page here would have to come from Apple PR.

Jordan

···

On Jul 18, 2016, at 16:57, Mark Lacey via swift-evolution <swift-evolution@swift.org> wrote:

On Jul 18, 2016, at 4:44 PM, Jacob Bandes-Storch via swift-evolution <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:

This is now live: http://apple.github.io/swift-evolution/

Very very nice!

I wonder if we should do something to avoid the 404 here though: http://apple.github.io <http://apple.github.io/&gt;

Perhaps a redirect to GitHub - apple/swift: The Swift Programming Language or maybe directly to https://github.com/apple/swift/blob/master/README.md? <https://github.com/apple/swift/blob/master/README.md?&gt;

You could add a simple <https://github.com/apple/apple.github.io/blob/master/404.html&gt; file:

  <!DOCTYPE html>
  <meta charset="UTF-8" />
  <meta http-equiv="Refresh" content="0; URL=Apple Open Source; />
  <title>404 Not Found</title>

That will redirect to the URL which also appears at the top of the <https://github.com/apple/&gt; page.

-- Ben

···

On 21 Jul 2016, at 19:10, Jordan Rose wrote:

On Jul 18, 2016, at 16:57, Mark Lacey wrote:

On Jul 18, 2016, at 4:44 PM, Jacob Bandes-Storch wrote:

This is now live: http://apple.github.io/swift-evolution/

Very very nice!

I wonder if we should do something to avoid the 404 here though: http://apple.github.io

Perhaps a redirect to GitHub - apple/swift: The Swift Programming Language or maybe directly to https://github.com/apple/swift/blob/master/README.md?

The Swift Open Source project isn’t the only project under github.com/apple. Any landing page here would have to come from Apple PR.

Is it possible to have a repo named apple.github.io, and still allow
individual repos having their own pages (like
apple.github.io/swift-evolution)?

Jacob

···

On Mon, Sep 5, 2016 at 7:05 AM, Ben Rimmington via swift-evolution < swift-evolution@swift.org> wrote:

> On 21 Jul 2016, at 19:10, Jordan Rose wrote:
>
>> On Jul 18, 2016, at 16:57, Mark Lacey wrote:
>>
>>> On Jul 18, 2016, at 4:44 PM, Jacob Bandes-Storch wrote:
>>>
>>> This is now live: http://apple.github.io/swift-evolution/
>>
>> Very very nice!
>>
>> I wonder if we should do something to avoid the 404 here though:
http://apple.github.io
>>
>> Perhaps a redirect to GitHub - apple/swift: The Swift Programming Language or maybe directly
to https://github.com/apple/swift/blob/master/README.md?
>
> The Swift Open Source project isn’t the only project under
github.com/apple. Any landing page here would have to come from Apple PR.

You could add a simple <Apple · GitHub
apple.github.io/blob/master/404.html> file:

        <!DOCTYPE html>
        <meta charset="UTF-8" />
        <meta http-equiv="Refresh" content="0; URL=
Apple Open Source; />
        <title>404 Not Found</title>

That will redirect to the URL which also appears at the top of the <
https://github.com/apple/&gt; page.

-- Ben

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

It is, read here: domain - Publishing more than one site on GitHub Pages - Web Applications Stack Exchange

···

--
Adrian Zubarev
Sent with Airmail

Am 6. September 2016 um 08:12:36, Jacob Bandes-Storch via swift-evolution (swift-evolution@swift.org) schrieb:

Is it possible to have a repo named apple.github.io, and still allow individual repos having their own pages (like apple.github.io/swift-evolution)?

Jacob

On Mon, Sep 5, 2016 at 7:05 AM, Ben Rimmington via swift-evolution <swift-evolution@swift.org> wrote:

On 21 Jul 2016, at 19:10, Jordan Rose wrote:

On Jul 18, 2016, at 16:57, Mark Lacey wrote:

On Jul 18, 2016, at 4:44 PM, Jacob Bandes-Storch wrote:

This is now live: http://apple.github.io/swift-evolution/

Very very nice!

I wonder if we should do something to avoid the 404 here though: http://apple.github.io

Perhaps a redirect to GitHub - apple/swift: The Swift Programming Language or maybe directly to https://github.com/apple/swift/blob/master/README.md?

The Swift Open Source project isn’t the only project under github.com/apple. Any landing page here would have to come from Apple PR.

You could add a simple <https://github.com/apple/apple.github.io/blob/master/404.html&gt; file:

    &lt;\!DOCTYPE html&gt;
    &lt;meta charset=&quot;UTF\-8&quot; /&gt;
    &lt;meta http\-equiv=&quot;Refresh&quot; content=&quot;0; URL=https://developer.apple.com/opensource/&quot; /&gt;
    &lt;title&gt;404 Not Found&lt;/title&gt;

That will redirect to the URL which also appears at the top of the <https://github.com/apple/&gt; page.

-- Ben

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

The `username.github.io` and `username.github.io/projectname` combination works for me.

The `orgname.github.io` and `orgname.github.io/projectname` combination should also work (but I haven't tried it).

<https://help.github.com/articles/user-organization-and-project-pages/&gt;

-- Ben

···

On 6 Sep 2016, at 07:11, Jacob Bandes-Storch <jtbandes@gmail.com> wrote:

Is it possible to have a repo named apple.github.io, and still allow individual repos having their own pages (like apple.github.io/swift-evolution)?

Thanks for the suggestion, Ben. After a bit of discussion we’ve put in a redirect to github.com/apple/, which is definitely better than just 404ing.

Jordan

···

On Sep 6, 2016, at 05:47, Ben Rimmington via swift-evolution <swift-evolution@swift.org> wrote:

On 6 Sep 2016, at 07:11, Jacob Bandes-Storch <jtbandes@gmail.com> wrote:

Is it possible to have a repo named apple.github.io, and still allow individual repos having their own pages (like apple.github.io/swift-evolution)?

The `username.github.io` and `username.github.io/projectname` combination works for me.

The `orgname.github.io` and `orgname.github.io/projectname` combination should also work (but I haven't tried it).

<https://help.github.com/articles/user-organization-and-project-pages/&gt;

— Ben

It'd be great to see swift.org as just another repo on github.com/apple via
GitHub Pages ;-)

Jacob

···

On Tue, Sep 6, 2016 at 8:45 PM, Jordan Rose <jordan_rose@apple.com> wrote:

> On Sep 6, 2016, at 05:47, Ben Rimmington via swift-evolution < > swift-evolution@swift.org> wrote:
>
>
>
>> On 6 Sep 2016, at 07:11, Jacob Bandes-Storch <jtbandes@gmail.com> > wrote:
>>
>> Is it possible to have a repo named apple.github.io, and still allow
individual repos having their own pages (like apple.github.io/swift-
evolution)?
>
> The `username.github.io` and `username.github.io/projectname`
combination works for me.
>
> The `orgname.github.io` and `orgname.github.io/projectname` combination
should also work (but I haven't tried it).
>
> <https://help.github.com/articles/user-organization-and-project-pages/&gt;
>
> — Ben

Thanks for the suggestion, Ben. After a bit of discussion we’ve put in a
redirect to github.com/apple/, which is definitely better than just
404ing.

Jordan