Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

Deprecate L20n in favor of Fluent #17

Open
1 of 13 tasks
stasm opened this issue Jan 3, 2018 · 0 comments
Open
1 of 13 tasks

Deprecate L20n in favor of Fluent #17

stasm opened this issue Jan 3, 2018 · 0 comments

Comments

@stasm
Copy link
Contributor

stasm commented Jan 3, 2018

Project Fluent has been around for almost a year now.

Let's make sure L20n is sunset properly and responsibly.

To do:

  • Edit the description of the L20n org on GitHub.
  • Put a deprecation notice in this repo's README.
  • Put a deprecation notice in l20n/l20n.js.
  • Put a deprecation notice in l20n/python-l20n.
  • Put a deprecation notice in l20n/l20n.org.
  • Put a deprecation notice in l20n/tinker.
  • Put a deprecation notice in l20n/builds.
  • Put a deprecation notice in l20n/demo.
  • Put a deprecation notice in l20n/preso.
  • Put a deprecation notice in l20n/l20n-syntax-fixtures.
  • Deploy a placeholder redirecting to http://projectfluent.org at http://l20n.org.
  • Deploy a placeholder redirecting to http://projectfluent.org/play at http://l20n.github.io/tinker.
  • Deprecate the l20n package on npm.

On 2018-11-26 we will let the l20n.org domain registration expire.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant