Skip to content

Commit 8ffd0bc

Browse files
committedMay 14, 2024··
Add decommission note
1 parent b86c493 commit 8ffd0bc

File tree

2 files changed

+34
-71
lines changed

2 files changed

+34
-71
lines changed
 

‎README.md

+34-71
Original file line numberDiff line numberDiff line change
@@ -1,71 +1,34 @@
1-
# LDAPjs
2-
3-
[![Build Status](https://github.com/ldapjs/node-ldapjs/workflows/Lint%20And%20Test/badge.svg)](https://github.com/ldapjs/node-ldapjs/actions)
4-
[![Coverage Status](https://coveralls.io/repos/github/ldapjs/node-ldapjs/badge.svg)](https://coveralls.io/github/ldapjs/node-ldapjs/)
5-
6-
LDAPjs makes the LDAP protocol a first class citizen in Node.js.
7-
8-
## Usage
9-
10-
For full docs, head on over to <http://ldapjs.org>.
11-
12-
```javascript
13-
var ldap = require('ldapjs');
14-
15-
var server = ldap.createServer();
16-
17-
server.search('dc=example', function(req, res, next) {
18-
var obj = {
19-
dn: req.dn.toString(),
20-
attributes: {
21-
objectclass: ['organization', 'top'],
22-
o: 'example'
23-
}
24-
};
25-
26-
if (req.filter.matches(obj.attributes))
27-
res.send(obj);
28-
29-
res.end();
30-
});
31-
32-
server.listen(1389, function() {
33-
console.log('ldapjs listening at ' + server.url);
34-
});
35-
```
36-
37-
To run that, assuming you've got the [OpenLDAP](http://www.openldap.org/)
38-
client on your system:
39-
40-
ldapsearch -H ldap://localhost:1389 -x -b dc=example objectclass=*
41-
42-
## Installation
43-
44-
npm install ldapjs
45-
46-
## Node.js Version Support
47-
48-
As of `ldapjs@3` we only support the active Node.js LTS releases.
49-
See [https://github.com/nodejs/release#release-schedule][schedule] for the LTS
50-
release schedule.
51-
52-
For a definitive list of Node.js version we support, see the version matrix
53-
we test against in our [CI configuration][ci-config].
54-
55-
Note: given the release date of `ldapjs@3`, and the short window of time that
56-
Node.js v14 had remaining on its LTS window, we opted to not support Node.js
57-
v14 with `ldapjs@3` (we released late February 2023 and v14 goes into
58-
maintenance in late April 2023). Also, Node.js v14 will be end-of-life (EOL) on
59-
September 11, 2023; this is a very shortened EOL timeline and makes it even
60-
more reasonable to not support it at this point.
61-
62-
[schedule]: https://github.com/nodejs/release#release-schedule
63-
[ci-config]: https://github.com/ldapjs/node-ldapjs/blob/master/.github/workflows/main.yml
64-
65-
## License
66-
67-
MIT.
68-
69-
## Bugs
70-
71-
See <https://github.com/ldapjs/node-ldapjs/issues>.
1+
# Project Decomissioned
2+
3+
This project has been decomissioned. I, James Sumners, took it on when it was
4+
languishing without any maintenance as it filled a need in the ecosystem and
5+
I had built things at a prior organization that depended upon this project.
6+
I spent a lot of time triaging issues and reworking things toward a path
7+
that could be more easily maintained by a community of volunteers. But I have
8+
not had the time to dedicate to this project in quite a while. There are
9+
outstanding issues that would take me at least a week of dedicated development
10+
time to solve, and I cannot afford to take time off of work to do that.
11+
Particularly considering that the aforementioned organization was two
12+
jobs ago, and it is extremely unlikely that I will transition to a role again
13+
that will need this project.
14+
15+
So, why am I just now deciding to decomission this project? Because today,
16+
2024-05-14, I received the following email:
17+
18+
![Abusive email](dt.png)
19+
20+
I will not tolerate abuse, and I especially will not tolerate tacit death
21+
threats, over a hobby. You can thank the author of that email for the
22+
decomissioning on this project.
23+
24+
My recommendation to you in regard to LDAP operations: write a gateway in a
25+
language that is more suited to these types of operations. I'd suggest
26+
[Go](https://go.dev).
27+
28+
👋
29+
30+
P.S.: if I ever do need this project again, I might revive it. But I'd fight
31+
hard for my suggestion above. Also, I will consider turning it over to an
32+
interested party, but I will require at least one recommendation from a
33+
Node.js core contributor that I can vet with the people that I know on that
34+
team.

‎dt.png

155 KB
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.