Open-source KVM software
Go to file
walker0643 3d245c7255
Create README.md
2018-01-25 17:05:55 -05:00
.github Ask for logs in issue template 2016-12-05 11:01:53 +00:00
cmake Move version number handling out of main CMake file 2017-05-27 14:01:49 +01:00
debian QtQuick isn't a required dependency 2017-05-11 21:18:29 +01:00
dist Update Qt version 2017-11-26 20:09:57 +00:00
doc Merge branch 'beefnog-mac-directions' of https://github.com/beefnog/synergy into beefnog-beefnog-mac-directions 2016-12-07 17:13:47 +00:00
ext Update OpenSSL to v1.0.2l 2017-05-26 22:10:15 +01:00
res Update 16px icon 2017-05-25 14:09:55 +01:00
src #6116 Change log level for unknown quartz event type to DEBUG3 2017-08-09 19:59:44 +01:00
.gitignore Unzip GTest and GMock and remove zip handling code 2017-02-07 01:24:32 +00:00
Build.properties Move version number handling out of main CMake file 2017-05-27 14:01:49 +01:00
CMakeLists.txt Move version number handling out of main CMake file 2017-05-27 14:01:49 +01:00
ChangeLog Make ready v1.9.0-rc3 2017-05-10 15:29:48 +01:00
LICENSE Delete old build system and cruft 2017-02-07 01:27:15 +00:00
README.md Create README.md 2018-01-25 17:05:55 -05:00

README.md

Barrier

KVM software forked from Symless's synergy 1.9 codebase.

What's different?

Whereas synergy has moved beyond its goals from the 1.x era, barrier aims to maintain that simplicity. Barrier will let you use your keyboard and mouse from machine A to control machine B (or more). That's it.

Project goals

Hassle-free reliability. We are users, too. Barrier was created so that we could solve the issues we had with synergy and then share these fixes with other users.

Compatibility. We use more than one operating system and you probably do, too. Windows, OSX, Linux, FreeBSD... Barrier should "just work". We will also have our eye on Wayland when the time comes.

Communication. Everything we do is in the open. Our issue tracker will let you see if others are having the same problem you're having and will allow you to add additional information. You will also be able to see when progress is made and how the issue gets resolved.

Contact & support

Please be aware that the only way to draw our attention to a bug is to create a new PR in the issue tracker. Write a clear, concise, detailed report and you will get a clear, concise, detailed response. Priority is always give to issues that affect a wider range of users.

For short and simple questions or to just say hello find us on the Freenode IRC network in the #barrier channel.