diff options
| author | Juuso Lapinlampi <wub@partyvan.eu> | 2016-05-07 19:13:46 +0200 |
|---|---|---|
| committer | Juuso Lapinlampi <wub@partyvan.eu> | 2016-05-08 06:13:25 +0200 |
| commit | 617c4409e76b4a86316c81b50ff1edca70b329e2 (patch) | |
| tree | d773b38b67c6a1de6f5b6069a8dceba4c8fb2b8e /README.md | |
| parent | f8b21e6f2f237ea16184f1ac5f17c20a4481864c (diff) | |
README: Add #pomf on Partyvan to getting help
It turns out that moving to Rizon's IRC network was a bad idea after
all. One or more developers (myself included) are unable to connect to
Rizon for using Tor or operating Tor exits.
Now there's this split: Users and Pomf site maintainers are on #pomfret
on Rizon (where I don't have frequent access) and development has moved
back to #pomf on Partyvan (where there's also #/g/hostingtalk).
Given how I personally play such a big role in leading Pomf development,
it has no longer been practical to continue development communication on
an IRC network I can't access. There was no interest to finish setting
up a mailing list for Pomf development because IRC was considered more
important.
Thus, the stagnation and stalled development of pantsu/pomf between
2016-01-31 and 2016-04-30 as seen in commit logs.
There used to be an IRC channel called #pantsucat on Partyvan's IRC
network, before development moved to Rizon. That channel is no longer
active.
See: pantsu/pomf@5846ba7ccb1aa6af2850b3fcf34c6bd396995161
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -75,7 +75,8 @@ configuration file. The Pomf community gathers on IRC. You can also email the maintainer for help. -- IRC: `#pomfret` on Rizon (`irc.rizon.net`) +- IRC (users): `#pomfret` on Rizon (`irc.rizon.net`) +- IRC (developers): `#pomf` on Partyvan (`irc.partyvan.eu`) - Email: <hostmaster@pantsu.cat> ## Contributing |