The 4Minitz team proudly announces 4Minitz v1.5
After our first public 1.0 release six month ago we got quite some feedback from small and large companies that introduced 4Minitz. Where applicable we implemented some of their valuable feedback (especially LDAP usage and Docker deployment). Additionally we could realize some shiny new features.
Happy Minuteing! ;-)
Important!!
>>> With Issue #433 we fixed a possible data leak. So, please update!!! <<<
Some 1.5 Stats?
Here you go: 6 month in the making, 8 contributors, >400 hours of work, 15 shiny new features realized, >60 issues solved, >400 commits, >200 files changed, >6000 lines of code added to project.
Dear users, if you now feel like you want to say "Thank you" to our contributors, feel free to add a New "Thank You" issue and ★Star★ our github project, if not yet done so. Also you may tell your business colleagues from other companies to try out 4Minitz. Then, please report problems and improvement ideas in our github issue tracker. And last but not least: if you are familar with JS/HTML/CSS and want to join, feel free to get in contact with us - we will find a great starting point for you! Thank you! ;-)
By the way: 4Minitz 1.0 has been downloaded and used in these 30 countries: Argentina, Australia, Belgium, Brazil, Bulgaria, Canada, Denmark, El Salvador, France, Germany, India, Iraq, Ireland, Italy, Malaysia, Mauritius, Netherlands, New Zealand, Saudi Arabia, Singapore, South Africa, Sweden, Switzerland, Taiwan, Thailand, United Arab Emirates, United Kingdom, United States, Vietnam, Zimbabwe
Then, one last sentence to our admin users: We really appreciate your feedback and your patience in discussing improvement ideas on 4Minitz. Your systems make our IT world run! So, keep up the good work! To make your live easy here comes the second most important question:
How to migrate from 1.0.x to 1.5.x?
General
- Most important news: there should be no extra hazzle in database migration for you - regardless if you used a previous /develop/ or /master/ version. 4Minitz has a built-in database migration framework, that carefully migrates your data, if necessary, to our new DB schema. No animals will be harmed!
- That been said: BACKUP YOUR DATA ANYHOW! (Think of: settings.json, MongoDB, stored attachment files & stored HTML/PDF minutes documents)
- We introduced a few new settings you might want to include in your
settings.json
. This will not happen automatically. We won't overwrite your settings! Though we have quite useful defaults for these new settings (if not specified), you might take a look at ldap.importOnLaunch
, ldap.hideStandardLogin
, ldap.label4Username
, ldap.label4Password
and docGeneration
for PDF & PDF/A protocol file persistence.
Update Docker Instances
- Stop running 4Minitz container (CTRL+C)
- Backup the complete 4minitz_storage directory on the host system
- Consider changes to your settings.json (see above!)
- Pull the newest 4minitz:stable image and spin up a fresh container with your existing 4miniz_storage data directory. Data will be migrated automatically.
Update Non-Docker Instances
- Stop your 4Minitz server
- Perform data backup. See admin guide Backup chapter
- Get the newest code. E.g., via
git pull
- Perform an
npm install
- Rebuild/restart your 4Minitz instance. Some data migration info may fill your console
4Minitz 1.5 - What's new
New Features
- #33 My Action Items shows a list of all my action items from all meeting series where I am invited
- #313 Show a Single Topic from minutes edit on a topic select "Show History", on My Action Items select "Show Topic" to get the finalized context.
- #194 Warn on Concurrent Edits users are now informed with a warning, if a second moderator edits the same topic / item / detail data or the meeting series meta data.
- #351 Quick Item Entry below topics (Click topic background to activate, then press CTRL+ENTER to confirm). Also includes quick adding of details (Press ENTER to add detail lines below).
- #39 PDF & PDF/A protocol file generation. Allows server-side archiving and user file downloads of protocols in long-time archivable PDF/A format. see below: already enabled for docker deployments!
- #345 Finalize Quality Checks now warn e.g., if no participants attendance box is checked; no topics discussed; action item with no responsible, ...
- #398 Docker image now has PDF/A protocol file generation enabled by default (all necessary tools installed & configured the right way!)
==> Hint for Admins that migrate from older docker images: Consider to change the setting
docGeneration.format
to "pdfa"
- #377 Convert ActionItem <=> InfoItem if the item was created in current minutes
- #382 Pinned Global Notes allow moderators to make the global notes text sticky, so it is propagated to the next meeting. E.g. for global meeting rules "No Phones, No Tablets, No Notebooks"
- #428 Participant Counts gives you live stats while marking present people in the room.
- #399 Long readable usernames (e.g. "John Doe") from user profiles are now displayed at various UI places instead of the short login usernames (e.g., "john123")
- #427 & #430 Three new settings in LDAP section to increase user interface of LDAP login:
ldap.hideStandardLogin
, ldap.label4Username
, ldap.label4Password
==> Admins consider adding them to your existing settings.json!
- #315 Automatic
NEW
label for new details allow users to focus on new stuff
- #397 Upload files attachments usability: Area is now expanded by default and shows a "Quick Hint" help
- #432 Admin View with user list allows to filter for "online users" (to determine who is e.g., disturbed by installing a server update)
Fixed Issues
- #433 [!!SECURITY!!] Topic data publishing did not check for user's access rights
- #424 LDAP user import stopped working in Docker deployment
- #435 After change of our schema validator, responsible fields could be null, leading to UI exception
- #425 Informed Users where not included in Minutes EMails / PDF stored protocols
- #426 A fresh docker image crashed in first launch with an empty database (Migration Step#20 was broken)
- #423 #422 The "Standard Login" page had some confusing usability flaws
- #406 & #412 The The official MongoDB driver for Node.js made a breaking API change. So our importUsers.js script was broken.
- #343 Performance of "responsible" select2 box optimized for setups with "thousands" of users
- #395 iOS11 camera photo uploads fixed (Apple changed photo extension from JPG => jpeg)
- #393 Docker deployment: It is now possible to specify a
docker run -e MONGO_URL=...
to use an external MongoDB instance outside of our docker image.
- #339 LDAP auto whitelisting
- #348 LDAP issues (e.g. allow to bind with arbitrary LDAP attributes)
- #348 LDAP auto-import on launch (as the docker image admins can not use the importUsers.js script)
- #354 ROOT_URL broken on docker deployment (Attachment URLs not working)
- #386 IE11 file upload was broken (introduced with v1.1-develop)
- #347 Un-Finalize does not remove all fresh created items from the topics collection
- #292 Non-Moderator can open MS editor by appending "?edit=true" to MS URL
- #350 Fixed some migrations
- #362 Tab "Action Items" did not display labels
- #364 Sort-Order of items now persistent after drag'n'drop re-order
- #374 Migration V18 "lost" some items. So migration V21 fixes this. This was only important for 4Minitz servers that migrated from 1.0-develop to 1.0 final release.
- #379 Edit topic showed wrong "Edited by other user message"
- Fix a bug that crashed minutes finalize (introduced with 1.1-develop)
Changes "Under-the-hood"
- #420 When admins do not switch off
updateCheck
in their instances, then from this version on we are able to send important update notes to their running instance. These update notes are then bundled into the "Admin Update EMail" sent by their own instances.
- #403 We migrated from the stalled kadira:flow-router to the vibrant ostrio:flow-router-extra. Thanx to @Dr-Dimitru from VeliovGroup for keeping the router alive!
- #394 We updated 4Minitz to Meteor.js 1.6.0.1 and then 1.6.1
- #398 Docker image now uses node.js 8
- #346 We added some more E2E security checks
- #349 Finalize performance: Optimise invalidation of the
new
-Flag
- Fixed many ESLint warnings and code duplications reported by CodeClimate
- Carve-out BUILD_DEPLOY.sh from BUILD_DOCKER.sh to prepare "ready to run" node deployments
- Our Docker images now have meta data labels. See here: https://microbadger.com/images/4minitz/4minitz
- private/createTestUsers.js populates user DB with an arbitrary number of users.
- #365 Admin tools: exportMeetingSeries and importMeetingSeries to migrate a specific meeting serieres (with all needed users) to a different server.
- We put quite some effort in hardening our End-2-End tests to ensure quality