Meeting minutes 15 Feb [was Re: Meeting minutes 8 Feb]

Nicola Nye nicolan at fastmail.com
Mon Feb 15 22:19:20 EST 2016


AFAIK, cyrus-sasl has its own tree for library distribution, which
includes its internal documentation such as saslauthd.8 (This is
generated out of saslauthd.mdoc via a "make install" target).

I haven't even looked at cyrus-sasl from a documentation perspective.
(There's a separate mailing list for all things sasl-y)

You are right in that there is some SASL user-facing documentation in
the cyrus-docs repository, brought over as a result of moving the old
mediawiki content into version control under git with RST.

It would make sense if we move cyrus-docs back into cyrus-imap, to split
off the cyrus-sasl documentation and move it into cyrus-sasl, so that
each project can maintain their docs along with their source. We can
manage the tooling from the website perspective to pull both doc trees
and integrate to build cyrusimap.org, I'm sure.

I'll have to see if I can contact some active cyrus-sasl folks and see
what they think and ideally find someone who can take ownership of the
sasl docs.

What a tangled web we weave!

Nicola


On Tue, Feb 16, 2016, at 12:25 PM, Nic Bernstein via Cyrus-devel wrote:
> Oops!  My bad!  I was looking at the cyrus-sasl repo, which has it's
    own doc branch, and took that to be the cyrus-sasl
    documentation. Upon further review, that seems to be mostly the
    supporting RFC data.
>
>
    My apologies for the snap-answer.  I've spent so much time buried in
    cyrus-docs, I somehow managed to miss this.
>
    -nic
>
>
> On 02/15/2016 07:14 PM, ellie timoney
      via Cyrus-devel wrote:
>> But the cyrus-docs repository appears (at a superficial
        glance) to contain SASL docs?  So merging it wholesale into the
        cyrus-imapd repository, especially in a way that obsoletes or
        removes the cyrus-docs repository, could have ramifications
>>
>> On Tue, Feb 16, 2016, at 12:08 PM, Nic Bernstein via
        Cyrus-devel wrote:
>>> The cyrus-sasl[1]
          software and documentation is in a wholly separate repository,
          and should not be in any way affected by what happens with the
          cyrus-docs[2] and cyrus-imapd[3] repositories.
>>> -nic
>>>
>>> On 02/15/2016 06:53 PM, ellie timoney via Cyrus-devel
          wrote:
>>>> Hmm.  I don't know if/how this will affect SASL.

On Tue, Feb 16, 2016, at 11:44 AM, Jan Parcel via Cyrus-devel wrote:
>>>>
>>>>> As a consumer, I'd like to say a couple of things.

1.  I really REALLY don't want to see it become difficult, on my end, to
    get the right versions of the libsasl2 docs on download. Apparently
    quite a few pages disappeared between 1.5.28 and 2.1.26, but those
    pages still appear in other places (including Solaris, possibly-
    corrected for
2.N.N)  I don't view them as "part of" imap.

2.  I've got some severe formatting problems displaying saslauthd(8) ,
    which I hope is unique to that file and not a trend.  saslauthd.8
    appears to be pre-roff'd, it looks like the others are not.
>>>>>
>>>
>>> --
Nic Bernstein                             nic at onlight.com Onlight Inc.
www.onlight.com6525 W Bluemound Rd., Ste 24             v. 414.272.4477
Milwaukee, Wisconsin  53213-4073          f. 414.290.0335
>>>
>>
>
> --
Nic Bernstein                             nic at onlight.com Onlight Inc.
www.onlight.com6525 W Bluemound Rd., Ste 24             v. 414.272.4477
Milwaukee, Wisconsin  53213-4073          f. 414.290.0335
>



Links:

  1. https://git.cyrus.foundation/diffusion/S/
  2. https://git.cyrus.foundation/diffusion/D/
  3. https://git.cyrus.foundation/diffusion/I/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.andrew.cmu.edu/pipermail/cyrus-devel/attachments/20160216/810afa85/attachment-0001.html>


More information about the Cyrus-devel mailing list