[pkg-lua-devel] Intent to upload prosody_0.8.2-1~bpo60+1, dh-lua_13~bpo60+1 and lua-ldap_1.1.0-1-geeac494-3~bpo60+1

[Luca Capello]

Hi there!

Still Cc:ing people, please let me know if you prefer replies to the
list only (obviously, if you are subscribed to pkg-lua-devel@).

On Tue, 08 May 2012 22:33:42 +0200, Matthew Wild wrote:
> Glad to hear things are going well for you with Prosody!

Thank you for the software ;-)

> On 8 May 2012 20:49, Luca Capello <luca at pca.it> wrote:
>> Hi Antoine!
>>
>> On Tue, 08 May 2012 17:46:10 +0200, Antoine Beaupré wrote:
>>> This seems reasonable. Will you upload the lua-ldap-plugins too?
>>
>> The idea would be to have them in the prosody package or, if not
>> possible, in a full or some-module package from prosody-modules:
>>
>>  <http://code.google.com/p/prosody-modules/>
>>
>> Anyway, I *need* the LDAP authentication for myself, so in some way or
>> another that will end up in a package, official or not.
>
> I'd rather not bundle anything unofficial into the Prosody package
> that isn't included upstream.

This is why I wrote 'if not possible', because nothing will be done if
upstream does not agree.  And, BTW, I do not want to end up maintaining
prosody in unstable as well ;-)

> We definitely plan to include LDAP auth
> and storage with Prosody in a future version, but the ones you linked
> to (most recent and seemingly most complete) are not even in
> prosody-modules yet. We would rather they went through the usual path
> to inclusion with Prosody to make sure they've had the right amount of
> testing and review.

Fully agree.

> Another reason not to include them is that we work hard to keep
> Prosody upgrades trivial. A config file from ~0.2 (Dec 2008) will
> still work in Prosody 0.9 (coming) without change.

May I play the devil here?  This is not true for Cyrus SASL
authentication, there are changes between 0.7 and 0.8:

  <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670549#35>

OK, just kidding, the above is *documented* upstream (which is what is
important to me), so everything is fine:

  <http://prosody.im/doc/cyrus_sasl>

> Our upgrade-safety
> includes things in prosody-modules. Having a significant portion of
> users running code outside our control would make us cry.

The problem I see here is that there *are* already users running code
outside of your control:

1) prosody-modules' mod_auth_ldap.lua does not work out of the box
   because it is missing LDAP's scope:

     <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670549#40>

2) Stefan Hepp's mod_auth_ldap.lua is waiting for reviews for more than
   a year now and even the prosody-modules' mod_auth_ldap.lua page
   advertises it:

     <https://groups.google.com/forum/?fromgroups&hl=en#!topic/prosody-dev/KC6HYRauQXc>
     <http://code.google.com/p/prosody-modules/wiki/mod_auth_ldap>

3) Rob Hoelz's LDAP-based modules (authentication, storage, vCard and
   groups) is quite new, but it seems other users already jumped in:

     <https://groups.google.com/forum/?fromgroups&hl=en#!topic/prosody-dev/ZwGQjeTdUu4>

As I see it, if Debian provides an official package (let me say only in
experimental), then your code is less outside your control, not the
other way around.

Please note that I wanted to contact prosody-dev before any other email,
while merging Stefan's and Rob's work into my local prosody-modules,
minimizing the changes and also providing tests (which I did anyway,
extensively if I may).  The fact that prosody-dev is on Google Groups
and it seems it requires a Google account simply refrained me to do that
(no Google here, sorry).  The new plan was to use prosody-user via
Gmane:

  <http://dir.gmane.org/gmane.network.jabber.prosody.user>

BTW, is there any reason why prosody-dev is not available through Gmane
as well?

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-lua-devel/attachments/20120509/957574ac/attachment-0001.pgp>