1
0
mirror of https://github.com/profanity-im/profanity.git synced 2024-11-03 19:37:16 -05:00
Go to file
Michael Vetter 3b3a6b7a75 Remove /python sourcepath
I feel like this mostly is confusing people.
Also don't see much value for it.

To me it looks like a regular workflow is like:
```
/plugin install ~/src/profanity-plugins/my.py
```

The whole thing with sourcepath, install (which also loads without
having that described anywhere), load etc is confusing.
Also each plugin file that is present in
`.local/share/profanity/plugins` will then be auto loaded. Which means
after installation.
2021-09-29 15:49:05 +02:00
.builds Upgrade OpenBSD to 6.8 2020-11-19 13:33:59 +01:00
.github gh: fix typo in issue template 2021-06-10 13:52:24 +02:00
apidocs Trim excess whitespace 2021-08-26 01:18:10 +00:00
docs Start new cycle 2021-09-28 19:53:05 +02:00
icons better, final icons 2016-03-09 12:55:57 +01:00
src Remove /python sourcepath 2021-09-29 15:49:05 +02:00
tests Trim excess whitespace 2021-08-26 01:18:10 +00:00
themes Trim excess whitespace 2021-08-26 01:18:10 +00:00
.clang-format clang-format: Dont sort includes 2020-07-07 14:18:37 +02:00
.gitignore Add I/O error handling and use filenames instead of file descriptors 2020-11-16 21:58:09 +01:00
bootstrap.sh Add Travis CI tests for Arch, Debian and OSX/macOS 2019-06-06 13:58:26 +02:00
Brewfile Switch from Travis CI to GitHub Actions 2020-12-17 15:09:25 +01:00
CHANGELOG Release 0.11.1 2021-09-28 19:48:42 +02:00
ci-build.sh Print logs on error in CI 2020-12-21 16:07:58 +01:00
configure-debug debug build: build without -fsanitize=address 2021-03-24 17:20:54 +01:00
configure-plugins Trim excess whitespace 2021-08-26 01:18:10 +00:00
configure.ac Start new cycle 2021-09-28 19:53:05 +02:00
CONTRIBUTING.md Add filetype check to pre hook example 2020-07-15 11:36:39 +02:00
COPYING License: use upstream license file 2021-08-26 00:30:55 +00:00
Dockerfile.arch Change to .tar.zst archives that latest Arch devtools uses 2020-07-20 10:52:12 +02:00
Dockerfile.debian Add sqlite to CI dependencies 2020-04-06 10:50:20 +02:00
Dockerfile.fedora Add Fedora travis CI 2020-04-17 15:46:55 +02:00
Dockerfile.tumbleweed travis: add libstrophe to tw 2020-10-09 09:38:47 +02:00
Dockerfile.ubuntu Ubuntu Latest (20.04 currently) in CI 2020-07-10 14:14:04 +02:00
LICENSE.txt Update copyright years 2019-04-24 01:08:38 +02:00
Makefile.am Merge pull request #1375 from wstrm/feature/omemo-sendfile 2020-12-09 08:09:09 +01:00
prof.supp Dirty fix libgcrypt memleak 2019-07-11 14:25:42 +02:00
profanity.spec Trim excess whitespace 2021-08-26 01:18:10 +00:00
profrc.example XEP-0392: config: add "color.nick" bool option 2019-12-03 21:10:39 +01:00
README.md Trim excess whitespace 2021-08-26 01:18:10 +00:00
RELEASE_GUIDE.md Fix spelling 2021-08-26 01:17:42 +00:00
SPONSORS.md sponsors: Add Matteo Bini 2021-05-12 16:50:45 +02:00
theme_template Make 'scrolled' themeable 2020-05-21 09:16:18 +02:00

Profanity

Build Status builds.sr.ht status Chat Packaging status GitHub contributors

Profanity is a console based XMPP client inspired by Irssi.

If you like Profanity consider becoming a sponsor or donate some money.

alt tag

See the User Guide for information on installing and using Profanity.

Project

This project is about freedom, privacy and choice. We want to enable people to chat with one another in a safe way. Thus supporting encryption (OTR, PGP, OMEMO, OX) and being decentralized, meaning everyone can run their own server. We believe XMPP is a great proven protocol with an excellent community serving this purpose well.

Feel free to follow us on twitter, join our mailing list and/or MUC.

Installation

Our user guide contains an install section and a section for building from source yourself.

Donations

We would highly appreciate it if you support us via GitHub Sponsors. Especially if you make feature requests or need help using Profanity. Sponsoring enables us to spend time on Profanity.

GitHub matches every donation in the first year.

An alternative way to support us would be via Patreon or ask for our IBAN.

Issues backed by a sponsor will be tagged with the sponsored label. Feature requests that we consider out of scope, either because of interest or because of time needed to implement them, will be marked with the unfunded label.

Another way to sponsor us or get an issue solved is to create a bug bounty. Here one sets a bounty on a certain task and once the task is completed you send the money to the person who did the work.

Tasks from our sponsors will be tackled first.

Thank you! <3

How to contribute

We tried to sum things up on our helpout page. Additionally you can check out our blog where we have articles like: How to get a backtrace and Contributing a Patch via GitHub. For more technical details check out our CONTRIBUTING.md file.

Getting help

To get help, first read our User Guide then check out the FAQ. If you have are having a problem then first search the issue tracker. If you don't find anything there either come to our MUC or create a new issue depending on what your problem is.

Website

URL: https://profanity-im.github.io

Repo: https://github.com/profanity-im/profanity-im.github.io

Blog

URL: https://profanity-im.github.io/blog

Repo: https://github.com/profanity-im/blog

Mailinglist

Mailing List: https://lists.notraces.net/mailman/listinfo/profanity

Chatroom

MUC: profanity@rooms.dismail.de

Plugins

Plugins repository: https://github.com/profanity-im/profanity-plugins