389-ds-base

#49678 organiSational vs organiZational spelling in lib389
Closed: wontfix Opened by vashirov.

Closed: wontfix
Reopen Issue

Issue Description

RFC4519 [1] defines organization object class. We should be following RFC spelling in function names and methods, otherwise it is confusing and annoying to remember which one is used where.

[1] https://tools.ietf.org/html/rfc4519#section-3.8

Metadata Update from @vashirov:
- Issue assigned to vashirov

https://pagure.io/389-ds-base/pull-request/49681

Metadata Update from @vashirov:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to review
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @spichugi:
- Custom field reviewstatus adjusted to ack (was: review)

commit c1e022d43f65dedeeed48817f90747006ac5dfd1

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

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/2737

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 (was: fixed)
Metadata
None
None
None
None
None
ack
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.