jabber.postgresql.org is up
Hello,
The community jabber server is now up. We are using the Wildfire server
from Jive Software, backed to a PostgreSQL database (of course).
Our current enabled features are:
1. Server side storage (for static groups etc..)
-- We currently have a Slaves_to_WWW group for example
2. MUC (basically IRC for jabber)
-- all muc conversations are logged to postgresql and in the long run
will likely be searchable by members of the jabber service.
3. tls or ssl is required
We do not support auto-registration at this time.
-- The idea behind this server is to allow active project members to
communicate without having to use public channels.
We do not support communication with other jabber servers at this time.
-- I don't really see a benefit to this at this time, but it is
something that is easy to set up so it is a consideration in the future.
If you are a project member (Gforge admin, Web team member, commiter
etc...) please let me know if you would like an account.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Sorry, but I don't get it. Why offer a closed forum for an open project?
-M
On Aug 27, 2006, at 24:48 , Joshua D. Drake wrote:
Hello,
The community jabber server is now up. We are using the Wildfire
server from Jive Software, backed to a PostgreSQL database (of
course).
<snip>
-- The idea behind this server is to allow active project members
to communicate without having to use public channels.
<snip>
Show quoted text
If you are a project member (Gforge admin, Web team member,
commiter etc...) please let me know if you would like an account.
AgentM wrote:
Sorry, but I don't get it. Why offer a closed forum for an open project?
Because jabber is a live medium, unlike email. I don't want people
pinging me, out of the blue. It is the whole reason I don't use any of
the public networks. The point is for the people who are actually part
of the project infrastructure to be able to communicate.
In the end it will likely be opened up more, but for now we are taking
baby steps.
SIncerely,
Joshua D. Drake
-M
On Aug 27, 2006, at 24:48 , Joshua D. Drake wrote:
Hello,
The community jabber server is now up. We are using the Wildfire
server from Jive Software, backed to a PostgreSQL database (of course).<snip>
-- The idea behind this server is to allow active project members to
communicate without having to use public channels.<snip>
If you are a project member (Gforge admin, Web team member, commiter
etc...) please let me know if you would like an account.---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
On Sun, Aug 27, 2006 at 08:49:21PM -0700, Joshua D. Drake wrote:
AgentM wrote:
Sorry, but I don't get it. Why offer a closed forum for an open project?
Open source developers already send private emails, private instant
messages, or join private chat rooms.
Because jabber is a live medium, unlike email. I don't want people
pinging me, out of the blue. It is the whole reason I don't use any of
the public networks. The point is for the people who are actually part
of the project infrastructure to be able to communicate.
In the end it will likely be opened up more, but for now we are taking
baby steps.
Assuming the conversations are not secret, and they are being used for an
official purpose, should they not be displayed as a public log, accessible
from a www.postgresl.org?
Baby steps that are away from an open model would serve to discourage
public knowledge or public contribution. I find myself already surprised
about features finding their way into PostgreSQL. Most often the surprise
is pleasant, however, it seems there is a disconnect in the communication
if somebody monitoring the mailing lists cannot determine what will be
included in, say, PostgreSQL 8.2, without asking "what will be in
PostgreSQL 8.2?"
Cheers,
mark
--
mark@mielke.cc / markm@ncf.ca / markm@nortel.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...