forked from psi-im/psi
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.html
123 lines (79 loc) · 10.2 KB
/
README.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
<h1>Psi IM – Qt-based XMPP client</h1>
<p>Stable version: 1.3 <br>
Release date: September 25th, 2017</p>
<p>Website: https://psi-im.org/ <br>
Sources: https://github.com/psi-im</p>
<h2>License</h2>
<p>This program is licensed under the GNU General Public License. See the <a href="https://github.com/psi-im/psi/blob/master/COPYING">COPYING</a> file for more information.</p>
<h2>Description</h2>
<p>Psi IM is a capable XMPP client aimed at experienced users. Its design goals are simplicity and stability. Psi IM is highly portable and runs on MS Windows, GNU/Linux and macOS.</p>
<p>Psi IM is minimal but powerful. There are keybindings for just about everything, Unicode is supported throughout, and contacts are cached offline. Security is also a major consideration, and Psi IM provides it for both client-to-server (TLS) and client-to-client (GnuPG, OTR, OMEMO).</p>
<p>WebKit version of Psi IM has few additional features (in comparing with basic version of Psi): support of animated emoticons, support of (adium) themes in private chats and group chats, support of previewing of images and videos in private chats and group chats, etc. But if you prefer old fashioned plain text chats from era of IRC heyday, then basic version of Psi IM is your obvious choice.</p>
<p>WebEngine version of Psi IM is identical to WebKit version of Psi IM in supporting of extra features, but it has some pros and cons:</p>
<ul>
<li>Better work with embedded video (in chats) in MS Windows.</li>
<li>Worse integration to system. (It does not use system theme in GNU/Linux.)</li>
<li>Support less amount of compilers, systems and CPU architectures.</li>
<li>Stability issues in macOS.</li>
</ul>
<h2>Versions history</h2>
<p>See <a href="https://github.com/psi-im/psi/blob/master/CHANGELOG">CHANGELOG</a> file.</p>
<h2>Installation</h2>
<p>See <a href="https://github.com/psi-im/psi/blob/master/INSTALL">INSTALL</a> file.</p>
<h2>Development</h2>
<p>In 2009 a Psi IM fork named <a href="https://psi-plus.com/">Psi+</a> was started. Project purposes are: implementation of new features, writing of patches and plugins for transferring them to upstream. As of 2017 all active Psi+ developers have become official Psi IM developers, but Psi+ still has a number of unique features. From developers point of view Psi+ is just a development branch of Psi IM which is hosted at separate git repositories and for which rolling release development model is used.</p>
<p>Currently the development model looks like this:</p>
<ul>
<li>Psi IM versions should look like: <code>X.Y</code> (where <code>X</code> and <code>Y</code> are not digits but numbers).</li>
<li>Psi+ versions should look like: <code>X.Y.Z</code> (where <code>X</code>, <code>Y</code> and <code>Z</code> are not digits but numbers).</li>
<li>All development of Psi IM (bug fixes, new features from Psi+ project) are done in <code>master</code> branch of <a href="https://github.com/psi-im/psi">psi</a> repository and its submodules. Each commit to it increases <code>Z</code> part of Psi+ version to one.</li>
<li>At some point of time new release branch is detouched from <code>master</code> branch (for example, <code>release-1.x</code>, <code>release-2.x</code>, etc.). All new releases (git tags) will be done in it. Necessary changes from <code>master</code> branch to stable branches should be cherry-picked or moved manually. Do not forget to <a href="admin/merge_release_to_master.sh">merge release branch</a> into <code>master</code> after adding of new git tags.</li>
<li>All new features are come into master branch of <a href="https://github.com/psi-plus/main">main</a> Psi+ repo. Each commit increases <code>Z</code> part of Psi+ version to one. Sometime later they will be moved to Psi. It may require different amount of time.</li>
<li>All patches in <a href="https://github.com/psi-plus/main">main</a> Psi+ repo should be prepared against <code>master</code> branch of <a href="https://github.com/psi-im/psi">psi</a> repo.</li>
<li>After each new release of Psi IM new git tag with the same version should be created in <a href="https://github.com/psi-plus/main">main</a> Psi+ repo.</li>
<li>Psi IM <a href="https://github.com/psi-im/plugins">plugins</a> are developed separately. Plugin API in <code>master</code> branches of <a href="https://github.com/psi-im/psi">psi</a> and <a href="https://github.com/psi-im/plugins">plugin</a> repos should be in sync.</li>
<li>All <a href="https://github.com/psi-plus/psi-plus-l10n">translations</a> are prepared for <code>master</code> branch of Psi+ and are (semi-automatically) <a href="https://github.com/psi-im/psi-l10n">adapted</a> for Psi.</li>
</ul>
<h2>Developers</h2>
<h3>Lead developers</h3>
<ul>
<li>2017-now, Sergey Ilinykh <<a href="mailto:rion4ik@gmail.com">rion4ik@gmail.com</a>>, Psi IM and Psi+ projects</li>
<li>2010-2017, Sergey Ilinykh <<a href="mailto:rion4ik@gmail.com">rion4ik@gmail.com</a>>, Psi+ project</li>
<li>2009-2010, <a href="http://andbit.net/">Justin Karneges</a> <<a href="mailto:justin@karneges.com">justin@karneges.com</a>>, Psi IM project</li>
<li>2004-2009, <a href="http://doomsong.co.uk/">Kevin Smith</a> <<a href="mailto:kevin@kismith.co.uk">kevin@kismith.co.uk</a>>, Psi IM project</li>
<li>2001-2004, <a href="http://andbit.net/">Justin Karneges</a> <<a href="mailto:justin@karneges.com">justin@karneges.com</a>>, Psi IM project</li>
</ul>
<h3>Other contributors</h3>
<p>There are a lot of people who were involved into Psi IM and Psi+ development. Some of them are listed in license headers in source files, some of them might be found only in the history of commits in our git repositories. Also there are <a href="https://github.com/psi-plus/psi-plus-l10n/blob/master/AUTHORS">translators</a>, makers of graphics and just active users. We are thankful to all them.</p>
<h2>How you can help</h2>
<h3>Bug reports</h3>
<p>If you found a bug please report about it in our <a href="https://github.com/psi-im/psi/issues">Bug Tracker</a>. If you have doubts contact with us in <a href="https://chatlogs.jabber.ru/[email protected]">XMPP Conference</a> <[email protected]> (preferable) or in a <a href="https://groups.google.com/forum/#!forum/psi-users">Mailing List</a>.</p>
<h3>Beta testing</h3>
<p>As we (intentionally) do not have nor beta versions of Psi, nor daily build builds for it, you are invited to use <a href="https://psi-plus.com/">Psi+ program</a> for suggesting and testing of new features, and for reporting about new bugs (if they happen).</p>
<h3>Comments and wishes</h3>
<p>We like constructive comments and wishes to functions of program. You may contact with us in <a href="https://chatlogs.jabber.ru/[email protected]">XMPP Conference</a> <[email protected]> for discussing of your ideas. Some of them will be drawn up as feature requests in our <a href="https://github.com/psi-im/psi/issues">Bug Tracker</a>.</p>
<h3>Translations</h3>
<p>The work of translators is quite routine and boring. People who do it usually lose interests and their translations become incomplete. If you see such situation for translation to your native language, please join to our <a href="https://www.transifex.com/tehnick/psi-plus/">translations team</a>. It is extremely welcome!</p>
<h3>Graphics</h3>
<p>There are many ways to contribute to the Psi IM project, if you think you can do a better job with any of the Psi IM graphics, then go right ahead!</p>
<h3>Programming</h3>
<p>Patches are welcome! Contact to Psi+ team if you are working on them.</p>
<h3>Packaging</h3>
<p>If you want to prepare personal builds of Psi IM and/or Psi+ for MS Windows and macOS systems, it is very welcome! We may distribute them via our official projects on SouceForge.net: <a href="https://sourceforge.net/projects/psi/">psi</a>, <a href="https://sourceforge.net/projects/psiplus/">psiplus</a>. Becoming an official maintaner for these systems is more complicated, but also possible.</p>
<p>For GNU/Linux and *BSD systems the situation is quite clear: just update packages (pkgbuilds, ebuild, etc.) in official repositories of your favorite distributions or make a Personal Package Archive (PPA) with them. We will add links to it into our documentation.</p>
<h3>Donations</h3>
<p>If you want to donate some money for development of Psi IM and Psi+ project, it is possible. See related info at official websites. Thanks!</p>
<h2>Extra links</h2>
<ul>
<li><a href="https://sourceforge.net/projects/psi/files/">Psi IM builds for end users</a> (executables)</li>
<li><a href="https://github.com/psi-im/plugins">Psi IM plugins</a> (sources)</li>
<li><a href="https://github.com/psi-im/psimedia">Psi IM plugin for VoIP and video-calls</a> (sources)</li>
<li><a href="https://github.com/psi-im/psi-l10n">Psi IM translations</a> (sources)</li>
<li><a href="https://psi-plus.com/">Psi+ project</a> (official website)</li>
<li><a href="https://sourceforge.net/projects/psiplus/files/">Psi+ builds for end users</a> (executables)</li>
<li><a href="https://github.com/psi-plus/resources">Psi+ extra resources</a> (iconsets, sounds, skins, themes, etc.)</li>
<li><a href="https://github.com/psi-plus/psi-plus-snapshots">Psi+ snapshots</a> (sources)</li>
<li><a href="https://github.com/psi-plus/psi-plus-l10n">Psi+ translations</a> (sources)</li>
<li><a href="https://github.com/psi-plus/qconf">Qt configuration tool</a> (sources)</li>
</ul>
<p>Have fun!</p>