Previously @mquandalle took care of packaging Wekan for Sandstorm, so
he was listed as the sole author of the SPK. Since I'm now taking over
packaging, this commit moves @mquandalle into the `upstreamAuthor`
slot and adds me as the SPK author by using my email address for
`contactEmail` and adding a pgp-signed statement that I am now an author.
It also adds my public key to the `keyring` file.
This one is a pretty strange chain of events:
* fetching /.sandstorm-login via accounts-sandstorm's rendezvous protocol
causes a user to be created in the users collection
* models/users.js has hooks to create a board and lists when a user is created
* models/activities.js has a hook to create activity entries when a list is
created
* this hook does not handle not having no boardId, which results in attempting
to run the hook with boardId: 'false'. 'false' does not have a title
attribute, which causes the whole method call to throw an exception.
* This makes the initial login fail.
While there may be other bugs, the simple fix is to not create the board and
lists when running under Sandstorm, where you only have one board anyway.
We add the SANDSTORM=1 environment variable to sandstorm-pkgdef.capnp so that
accounts-sandstorm will ensure that it's the only loaded accounts package when
running under Sandstorm.
The member is only set to inactive, so we could not test for $pull.
Instead we have to look into the $set modified and check whether the
member was deactivated.
As suggested in #604 there might be some language unnecessary redundancy, for
instance between 'es' (Spanish) and 'es-ES' (Spain's Spanish), but we'll figure
that out during the release candidate phase.
I've just discovered that the reason NPM outputs a giant "npm ERR!" message
asking to contact the author of the library and suggesting that it’s most likely
“not a problem with npm itself” when I run "npm run lint" and I forgot a
semicolon is because the return code of an NPM script has to be 0. So this
commit adds "exit 0;" at the end of the NPM commands.
