diff options
| -rw-r--r-- | Dockerfile | 2 | ||||
| -rw-r--r-- | LICENSE | 2 | ||||
| -rw-r--r-- | models/attachments.js | 2 | ||||
| -rw-r--r-- | package.json | 6 | ||||
| -rw-r--r-- | sandstorm-pkgdef.capnp | 4 | ||||
| -rw-r--r-- | sandstorm.js | 8 |
6 files changed, 12 insertions, 12 deletions
@@ -1,5 +1,5 @@ FROM meteorhacks/meteord:onbuild -MAINTAINER Maxime Quandalle <maxime@quandalle.com> +MAINTAINER Maxime Quandalle <mquandalle@wekan.io> # Run as you wish! # docker run -d --name wekan-db mongo @@ -1,6 +1,6 @@ The MIT License (MIT) -Copyright (c) 2014-2015 Yasar Icli, Maxime Quandalle +Copyright (c) 2014-2016 The Wekan Team Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/models/attachments.js b/models/attachments.js index 8ef0fef0..d8398816 100644 --- a/models/attachments.js +++ b/models/attachments.js @@ -51,7 +51,7 @@ Attachments.files.before.insert((userId, doc) => { // files that the browser will just execute if we don't serve them with the // appropriate `application/octet-stream` MIME header which can lead to user // data leaks. I imagine other formats (like PDF) can also be attack vectors. - // See https://github.com/libreboard/libreboard/issues/99 + // See https://github.com/wekan/wekan/issues/99 // XXX Should we use `beforeWrite` option of CollectionFS instead of // collection-hooks? if (!file.isImage()) { diff --git a/package.json b/package.json index 77a9fb74..e844c9ec 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { - "name": "wekan", - "version": "1.0.0", + "name": "Wekan", + "version": "0.10.1", "description": "The open-source Trello-like kanban", "private": true, "scripts": { @@ -15,7 +15,7 @@ "bugs": { "url": "https://github.com/wekan/wekan/issues" }, - "homepage": "http://wekan.io", + "homepage": "https://wekan.io", "devDependencies": { "babel-eslint": "4.1.3", "eslint": "1.7.3", diff --git a/sandstorm-pkgdef.capnp b/sandstorm-pkgdef.capnp index 375f1a20..8d692a49 100644 --- a/sandstorm-pkgdef.capnp +++ b/sandstorm-pkgdef.capnp @@ -57,13 +57,13 @@ const pkgdef :Spk.PackageDefinition = ( market = (svg = embed "meta/icons/wekan-150.svg"), ), - website = "http://libreboard.com", + website = "https://wekan.io", codeUrl = "https://github.com/wekan/wekan", license = (openSource = mit), categories = [productivity, office], author = ( - contactEmail = "maxime@quandalle.com", + contactEmail = "mquandalle@wekan.io", pgpSignature = embed "meta/mquandalle-pgp-sig", ), diff --git a/sandstorm.js b/sandstorm.js index 4abe2efb..e7a67f76 100644 --- a/sandstorm.js +++ b/sandstorm.js @@ -126,10 +126,10 @@ if (isSandstorm && Meteor.isServer) { updateUserPermissions(doc._id, doc.services.sandstorm.permissions); }); - // LibreBoard v0.8 didn’t implement the Sandstorm sharing model and instead - // kept the visibility setting (“public” or “private”) in the UI as does the - // main Meteor application. We need to enforce “public” visibility as the - // sharing is now handled by Sandstorm. + // Wekan v0.8 didn’t implement the Sandstorm sharing model and instead kept + // the visibility setting (“public” or “private”) in the UI as does the main + // Meteor application. We need to enforce “public” visibility as the sharing + // is now handled by Sandstorm. // See https://github.com/wekan/wekan/issues/346 Migrations.add('enforce-public-visibility-for-sandstorm', () => { Boards.update('sandstorm', { $set: { permission: 'public' }}); |