Skip to content

Commit 75a63e5

Browse files
authored
Flag that NLTK is in maintenance mode
1 parent 280e2de commit 75a63e5

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

CONTRIBUTING.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,13 @@ Hi! Thanks for your interest in contributing to [NLTK](https://www.nltk.org/).
55
In this document, we'll try to summarize everything that you need to know to
66
do a good job.
77

8+
## Maintenance Mode
9+
10+
NLTK is in maintenance mode. We welcome bugfixes.
11+
We can consider _minor_ enhancements if they are clearly documented in an [NLTK issue](https://github.com/nltk/nltk/issues)
12+
and are supported by a [team member](https://github.com/orgs/nltk/teams/team-nltk) who is willing to review a PR.
13+
(You are welcome to make a case for a _major_ enhancement, but please note we have limited capacity to deal with it.
14+
Please enlist an NLTK team member before doing substantial coding.)
815

916
## Code and Issues
1017

@@ -24,7 +31,7 @@ important are:
2431
- [nltk/nltk_book](https://github.com/nltk/nltk_book), source code for the NLTK
2532
Book.
2633

27-
## Development priorities
34+
## Development priorities (old)
2835

2936
NLTK consists of the functionality that the Python/NLP community is motivated to contribute.
3037
Some priority areas for development are listed in the [NLTK Wiki](https://github.com/nltk/nltk/wiki#development).
@@ -62,9 +69,7 @@ repository [nltk/nltk](https://github.com/nltk/nltk/):
6269

6370
### GitHub Pull requests
6471

65-
We use the famous
66-
[gitflow](https://nvie.com/posts/a-successful-git-branching-model/) to manage our
67-
branches.
72+
We use [gitflow](https://nvie.com/posts/a-successful-git-branching-model/) to manage our branches.
6873

6974
Summary of our git branching model:
7075
- Go to the `develop` branch (`git checkout develop`);

0 commit comments

Comments
 (0)