On 05/10/15 10:56, Raphael Hertzog wrote:
> Hi Daniel,
> 
> On Sun, 04 Oct 2015, Daniel Pocock wrote:
>> This patch adds to chapter 11, giving a brief introduction to RTC
>> services on Debian
> 
> We have a section dedicated to XMPP and setting up ejabberd in Chapter
> 13 already:
> https://debian-handbook.info/browse/jessie/ch13s07.html#idm140062055217232
> 
> I think you should put your section there, either by separating XMPP
> from the rest so that you can keep the current section or by merging
> the existing section in an expanded section covering real time
> communication.
> 
> I would need that rather quickly if you want to make it to the
> jessie edition.

I can do some more work on this later today, will that be OK?

Chapter 13 is titled "Workstation", so I had not looked there at all.
Sorry about that.  In any case,

- I'm not sure it is optimal to include server setup stuff in the
Workstation chapter, maybe it should just direct people to the services
chapter (11)?

- only IRC has a focus on IM.  Both XMPP and SIP are doing a lot more:
voice, video, file transfer, pub/sub.  I feel this is a second reason
for not having XMPP servers in chapter 13, as the subheading is "13.7.2
Instant Messaging Systems".

- I ran ejabber for a long time but Prosody is also very popular.  The
official debian.org SIP service (we tested it at DebConf15, it should be
live very soon) is based on Prosody.  There are several DDs actively
involved in the Prosody and module packaging.  Would you be happy if I
put Prosody as the recommended option and ejabberd as an alternative?


Here is what I would do in a revised version of the patch:

ch11:

- at the beginning, I would add an extra paragraph before 11.1, briefly
mentioning that this chapter includes various RTC options and the RTC
Quickstart is worth reading alongside chapter 11

- add 11.8 TURN server, cutting and pasting some content from
     http://rtcquickstart.org/guide/multi/turn.html

- add 11.9 SIP server, cutting and pasting some content from
     http://rtcquickstart.org/guide/multi/sip-proxy-repro.html

- add 11.10 Prosody XMPP server, cutting and pasting some content from
     http://rtcquickstart.org/guide/multi/xmpp-server-prosody.html
    and with a <sidebar> for ejabberd

- add 11.11 PBX server
     briefly mention that Debian has Asterisk packages,
     a full setup is too much to cover though

- and file a wishlist bug for somebody to contribute:
      11.12 IRC server setup

ch13:

- remove section 13.7.2

- create a new section "13.10 Real-time Communications"
    with subsections
     13.10.1 Instant Messaging and Chat
     13.10.2 Voice and Video/webcam
  This new section 13.10 would include:
    - some of the content from section 13.7.2
    - links to the service setup in chapter 11

Does this sound like a reasonable structure?

> 
>> +      <keyword>Prosody</keyword>
> 
> You don't even mention Prosody in your text. You might want to mention it
> as an alternative to ejabberd (in a sidebar possibly?) in the current
> section about IM.
> 
>> +    <para>The Falcot Corp administrators decided that they would use a
>> +    SIP proxy and not a full PBX like Asterisk at the network boundary
>> +    because they wanted to maximize connectivity and stability while also
>> +    having a relatively simple configuration.  They chose the repro SIP 
>> proxy
>> +    from the reSIProcate project because it has been built from the ground 
>> up
> 
> <emphasis>reSIProcate</emphasis>
> 
>> +    to support IPv6 and TLS and it also has support for WebRTC.  In the 
>> future,
>> +    they intend to setup an internal PBX using Asterisk, however, all calls 
>> going
>> +    to the Asterisk server will be routed through the SIP proxy.</para>
>> +
>> +    <para>Comprehensive details of how to plan and install these services
>> +    are available in the Real-Time Communications Quick Start Guide
> 
> <emphasis> around the title
> 
>> +    which includes examples specific to Debian.
>> +    <ulink type="block" url="http://rtcquickstart.org"/></para>
> 
> Otherwise it looks good to me.
> 
> Cheers,
> 

Reply via email to