Public IRC meeting about 1.0-beta, today at 5pm CEST

Hi all,

A few of us are trying to get remoteStorage.js 1.0 polished enough to finally release a 1.0-beta version and switch the current GitHub default branch from the legacy stable back to master.

This includes, among many other things, a whole new documentation site, which aims to considerably improve the onboarding experience for both app developers and library contributors. Any help with that, even if it’s just proofreading and giving feedback, would definitely go a long way!

@galfert and I would like to invite anyone who’s interested to an IRC meeting today at 5pm CEST in #remotestorage on Freenode. We’ll try to decide on all issues to be moved to the 1.0 milestone and divide some tasks among us. We might also have a quick look at the TODO comments in the source code and create some more issues from those.

See you there!


We decided to release remoteStorage.js 1.0.0-rc1 (release candidate) next Friday. Yes, Friday the 13th. YOLO. :wink:

We tried to find all remaining issues and tasks and put them all in the RC milestone: 1.0.0-rc1 Milestone · GitHub

This release candidate for 1.0.0 aims to replace the current stable 0.14 for new app developers as well as existing ones wanting to upgrade.


  • Public API shouldn’t break after this release (until the next major version).
  • It should be as stable as 0.14.x.
  • Dropbox and GDrive should work reasonably well and not change things like base directory, but minor bugs can stay and be fixed in upcoming patch releases.
  • Documentation should be ready for both app developers as well as library contributors to jump in and not run against walls

So, if nothing goes considerably wrong, sometime by the end of next week, 1.0 will become the default recommended version for everyone, and there should be enough documentation to easily learn how everything works.

Any and all help is most welcome, of course! Just grab an issue in the milestone, or over in the widget repo, and/or do whatever else you think could be useful.

If you don’t want to or cannot touch code (yet), then reviewing the docs and giving feedback on those, or improving them yourself, is a great way to help the whole community and any future developers: