10:07 a.m.
Hi all,
I'm just wondering how we move forward with the docs and the config
backend. Should we document examples with both, or only slapd.d or
move example config to the appendix and have an appendix for each
format so it doesn't clutter the guide.
My feeling is the last option is best. Thoughts?
Gavin.
--
Sent from my mobile device
http://www.suretecsystems.com/services/openldap/
12:15 p.m.
On Wed, Dec 31, 2008 at 06:07:15PM +0000, Gavin Henry wrote:
I'm just wondering how we move forward with the docs and the
config
backend. Should we document examples with both, or only slapd.d or
move example config to the appendix and have an appendix for each
format so it doesn't clutter the guide.
My feeling is the last option is best. Thoughts?
I would certainly prefer to see just one format used in the body
of the guide. Less duplication, so less chance of error.
The file format is cleaner than the LDIF necessary to express
data for the config backend and there is a simple translation
to the other format, so I would suggest sticking with file-based
examples. Occasional pointers to the section describing the
translation process would be useful.
Andrew
--
-----------------------------------------------------------------------
| From Andrew Findlay, Skills 1st Ltd |
| Consultant in large-scale systems, networks, and directory services |
| http://www.skills-1st.co.uk/ +44 1628 782565 |
-----------------------------------------------------------------------
1:14 a.m.
----- "Andrew Findlay" <andrew.findlay(a)skills-1st.co.uk> wrote:
On Wed, Dec 31, 2008 at 06:07:15PM +0000, Gavin Henry wrote:
> I'm just wondering how we move forward with the docs and the config
> backend. Should we document examples with both, or only slapd.d or
> move example config to the appendix and have an appendix for each
> format so it doesn't clutter the guide.
>
> My feeling is the last option is best. Thoughts?
I would certainly prefer to see just one format used in the body
of the guide. Less duplication, so less chance of error.
The file format is cleaner than the LDIF necessary to express
data for the config backend and there is a simple translation
to the other format, so I would suggest sticking with file-based
examples. Occasional pointers to the section describing the
translation process would be useful.
OK, thanks. Dev team thoughts?
--
Kind Regards,
Gavin Henry.
OpenLDAP Engineering Team.
E ghenry(a)OpenLDAP.org
Community developed LDAP software.
http://www.openldap.org/project/
9:09 a.m.
--On Monday, January 12, 2009 9:14 AM +0000 Gavin Henry
<ghenry(a)OpenLDAP.org> wrote:
OK, thanks. Dev team thoughts?
I found the doc examples using the LDIF format quite useful when
transitioning from the *.conf format to the config format, regardless of
the ability to take a slapd.conf and translate it to LDIF. People who are
starting fresh may never need/desire to have a *.conf file.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
9:44 a.m.
Quanah Gibson-Mount wrote:
--On Monday, January 12, 2009 9:14 AM +0000 Gavin Henry
<ghenry(a)OpenLDAP.org> wrote:
> OK, thanks. Dev team thoughts?
I found the doc examples using the LDIF format quite useful when
transitioning from the *.conf format to the config format, regardless of
the ability to take a slapd.conf and translate it to LDIF. People who are
starting fresh may never need/desire to have a *.conf file.
Along those lines ... we've set a policy that all new code (backends,
overlays) must support cn=config. I think it makes sense to use the same
policy for all newly written documentation. slapd.conf is obsolete.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
2:12 p.m.
----- "Howard Chu" <hyc(a)symas.com> wrote:
Quanah Gibson-Mount wrote:
> --On Monday, January 12, 2009 9:14 AM +0000 Gavin Henry
> <ghenry(a)OpenLDAP.org> wrote:
>
>> OK, thanks. Dev team thoughts?
>
> I found the doc examples using the LDIF format quite useful when
> transitioning from the *.conf format to the config format,
regardless of
> the ability to take a slapd.conf and translate it to LDIF. People
who are
> starting fresh may never need/desire to have a *.conf file.
Along those lines ... we've set a policy that all new code (backends,
overlays) must support cn=config. I think it makes sense to use the
same
policy for all newly written documentation. slapd.conf is obsolete.
Right, done.
Thanks all.
--
Kind Regards,
Gavin Henry.
OpenLDAP Engineering Team.
E ghenry(a)OpenLDAP.org
Community developed LDAP software.
http://www.openldap.org/project/
5375
days inactive
5387
days old
5 comments
5 participants
participants (5)
-
Andrew Findlay -
Gavin Henry -
Gavin Henry -
Howard Chu -
Quanah Gibson-Mount