diff options
| -rw-r--r-- | documentation/content/en/articles/contributing/_index.adoc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/content/en/articles/contributing/_index.adoc b/documentation/content/en/articles/contributing/_index.adoc index c19f294c80..53c9a450c7 100644 --- a/documentation/content/en/articles/contributing/_index.adoc +++ b/documentation/content/en/articles/contributing/_index.adoc @@ -342,7 +342,7 @@ If the port has build errors or needs updating, you may wish to include any othe This will help because many committers are less willing to assign maintainership to someone who does not have a known track record with FreeBSD. Submitting PRs that fix build errors or update ports are the best ways to establish one. -File your PR with category `ports` and class `change-request`. +File your PR with Product `Ports & Packages`. A committer will examine your PR, commit the changes, and finally close the PR. Sometimes this process can take a little while (committers are volunteers, too :). @@ -584,7 +584,7 @@ If you can make them feel that their contribution is appreciated (and it should There are some really good places to find a port that needs some attention. You can use the https://bugs.freebsd.org/search[web interface] to the Problem Report database to search through and view unresolved PRs. -The majority of ports PRs are updates, but with a little searching and skimming over synopses you should be able to find something interesting to work on (the `sw-bug` class is a good place to start). +The majority of ports PRs are updates, but with a little searching and skimming over synopses you should be able to find something interesting to work on. https://portsfallout.com/[PortsFallout] shows port issues gathered from the FreeBSD package building. |