Top 4 open source alternatives to Slack for team collaboration and Chat

Off course Slack is market leader in terms team collaboration and Chat but here are the list of 4 open source alternatives to Slack for team collaboration and Chat.
Slack offers a lot of IRC-like features: persistent chat rooms (channels) organized by topic, as well as private groups and direct messaging (again, historically based on IRC).[14] All content inside Slack is searchable, including files, conversations, and people. Slack integrates with a large number of third-party services and supports community-built integrations. Major integrations include services such as Google Drive, Trello, Dropbox, Box, Heroku, Crashlytics, GitHub, Runscope and Zendesk. In December 2015, Slack announced their app directory, consisting of over 150 integrations that users can install.[21] Users can add emoji buttons to their messages, which other users can then click on to express their reactions to messages.
More info –
Internet Relay Chat, or IRC, is a protocol which dates back to the late 1980s. Since it’s been around so long, there are numerous open source implementations on both the client and the server side.
Coming with its age, however, are numerous drawbacks. It lacks many features one might expect in a modern chat client, from security to identity management to even just being able to easily transmit non-text components, like images, files, or emoticons (the latter might be seen as a plus to some, however). Some features have been implemented after-the-fact through bot services, including nickname management, logging, and other features, but these vary from server to server.
IRC does still have some things going for it, though. It’s nearly universal, and clients are available for basically every platform out there. Though the command-driven interface isn’t necessarily intuitive for beginners, many clients re-implement commands through a GUI. And if you’re doing upstream open source development, there’s a good chance you’re already hanging out in IRC anyway, so adding a team server might be a path of least resistance.
Let’s Chat
Let’s Chat is a persistent messaging application that runs on Node.js and MongoDB. It’s designed to be easily deployable and fits well with small, intimate teams.
It’s free (MIT licensed) and ships with killer features such as LDAP/Kerberos authentication, a REST-like API and XMPP support.
Let’s Chat is a side-project of the development team at Security Compass. (A real life 10% time project!)
More –
As an alternative to proprietary SaaS messaging, Mattermost brings all your team communication into one place, making it searchable and accessible anywhere. It’s written in Golang and React and runs as a production-ready Linux binary under an MIT license with either MySQL or Postgres.
Rocket.Chat is an incredible product because we have an incredible developer community.
Over 200 contributors have made our platform a dynamic and innovative toolkit, from group messages and video calls to helpdesk killer features.
Our contributors are the reason we’re the best cross-platform open source chat solution available today.
Tagged : / / / / / / / / / / / / / / / / /

Maven CLI Options Reference – Command Line | Maven Command Line Cheatsheet


Maven CLI Options Reference

Options Description
-am,--also-make If project list is specified, also build projects required by the list
-amd,--also-make-dependents If project list is specified, also build projects that depend on projects on the list
B,–batch-mode Run in non-interactive (batch) mode
-C,--strict-checksums Fail the build if checksums don’t match
-c,--lax-checksums Warn if checksums don’t match
-cpu,--check-plugin-updates Ineffective, only kept for backward compatibility
-D,--define <arg> Define a system property
-e,--errors Produce execution error messages
-emp,--encrypt-master-password <arg> Encrypt master security password
-ep,--encrypt-password <arg> Encrypt server password
-f,--file <arg> Force the use of an alternate POM file (or directory with pom.xml).
-fae,--fail-at-end Only fail the build afterwards; allow all non-impacted builds to continue
-ff,--fail-fast Stop at first failure in reactorized builds
-fn,--fail-never NEVER fail the build, regardless of project result
-gs,--global-settings <arg> Alternate path for the global settings file
-h,--help Display help information
-l,--log-file <arg> Log file to where all build output will go.
-llr,--legacy-local-repository Use Maven 2 Legacy Local Repository behaviour, ie no use of _maven.repositories. Can also be activated by using -Dmaven.legacyLocalRepo=true
-N,--non-recursive Do not recurse into sub-projects
-npr,--no-plugin-registry Ineffective, only kept for backward compatibility
-npu,--no-plugin-updates Ineffective, only kept for backward compatibility
-nsu,--no-snapshot-updates Suppress SNAPSHOT updates
-o,--offline Work offline
-P,--activate-profiles <arg> Comma-delimited list of profiles to activate
-pl,--projects <arg> Comma-delimited list of specified reactor projects to build instead of all projects. A project can be specified by [groupId]:artifactId or by its relative path.
-q,--quiet Quiet output – only show errors
-rf,--resume-from <arg> Resume reactor from specified project
-s,--settings <arg> Alternate path for the user settings file
-T,--threads <arg> Thread count, for instance 2.0C where C is core multiplied
-t,--toolchains <arg> Alternate path for the user toolchains file
-U,--update-snapshots Forces a check for updated releases and snapshots on remote repositories
-up,--update-plugins Ineffective, only kept for backward compatibility
-V,--show-version Display version information WITHOUT stopping build
-v,--version Display version information
-X,--debug Produce execution debug output
Tagged : / / / / / / / / / / / / / / / / / /