#50613 Improve lib389 documentation
Closed: wontfix 3 years ago by spichugi. Opened 4 years ago by spichugi.

Issue Description

We should get our lib389 API documentation revisited.
For that we should go though the existing docstrings of non-depricated modules and get them in order.
Also, we should add more examples which can coordinate the newcomers better.


@vashirov @aadhikari @bsmejkal @aborah @tbordaz @lkrispen and other team members who are interested - please, share which lib389 usage scenarios you want me to cover.

Metadata Update from @spichugi:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

4 years ago

Metadata Update from @spichugi:
- Issue assigned to spichugi

4 years ago

@spichugi we should finish the "Work in progress" section as soon as possible .

@spichugi we should finish the "Work in progress" section as soon as possible .

I'll probably reorganize the thing anyway. But first I need a better understanding of the requirements and demands

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.2

4 years ago

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4 backlog (was: 1.4.2)

4 years ago

Metadata Update from @spichugi:
- Assignee reset

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2665

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata