https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/

[foolip]

In order for other specs (w3c/mediasession#129) to link to the most up-to-date version of this spec, it would be good if manifest.sysapps.org were on HTTPS. Also update link to https://w3c.github.io/manifest/ in the repo description.

[kenchris]

@marcosc why we do even have this sysapps.org version? SysApps WG is dead, as you know :)

[foolip]

Hmm, https://www.w3.org/TR/appmanifest/ now claims to be a living document. Is that really true, will it never be an out-of-date snapshot?

[marcoscaceres]

On 8 Jun 2016, at 11:20 PM, Philip Jägenstedt notifications@github.com wrote:

Hmm, https://www.w3.org/TR/appmanifest/ now claims to be a living document. Is that really true, will it never be an out-of-date snapshot?

It's true. It's alive.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[marcoscaceres]

On 8 Jun 2016, at 11:11 PM, Kenneth Rohde Christiansen notifications@github.com wrote:

@marcosc why we do even have this sysapps.org version? SysApps WG is dead, as you know :)

Argh... Seems I misconfigured DNS somewhere.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[foolip]

So I guess everything should redirect to https://www.w3.org/TR/appmanifest/

Thanks, we'll link to that, then.

[marcoscaceres]

Fixed DNS, but will take a bit to propagate...

[foolip]

Can you also replace https://w3c.github.io/manifest/ in the repo description and have https://w3c.github.io/manifest/ redirect to https://www.w3.org/TR/appmanifest/?

[RobDolinMS]

@foolip Was your comment from Jun 9 sufficiently resolved?

I see http://www.w3.org/TR/appmanifest/ in the spec and linked from the ReadMe.md file.

[foolip]

The repo description was fixed, but https://w3c.github.io/manifest/ still exists, I'd redirect that so there's no doubt about which is the right one.

[marcoscaceres]

That's a larger change, where we would need to stop using the gh-pages branch (and make master, the master again). I don't mind doing that change, but not right now.

[foolip]

Do you want an issue for it?

[marcoscaceres]

No, I'll do it this week. It's on my todo.

On 15 Aug 2016, at 9:26 PM, Philip Jägenstedt notifications@github.com wrote:

Do you want an issue for it?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.