Skip to content

Commit

Permalink
Merge pull request #2183 from NeoKish/contributing-md-pr
Browse files Browse the repository at this point in the history
Minor fixes to contributing.md
  • Loading branch information
brimoor committed Oct 20, 2022
2 parents b81b573 + 5a32619 commit 395b1bc
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
FiftyOne is open source and community contributions are welcome!

If you have not already, we highly recommend browsing currently
[active projects](https://github.com/voxel51/fiftyone/projects) to get a sense
[active projects](https://github.com/voxel51/fiftyone/projects?type=classic) to get a sense
of what is planned for FiftyOne. Each project is a component of FiftyOne that
we, the maintainers, deem critical to building a world-class ecosystem for
building high quality CV/ML datasets and models.
Expand All @@ -26,7 +26,7 @@ tweaks such as typos or other small improvements do not need to have a
corresponding issue.

FiftyOne maintainers [actively triage](ISSUE_TRIAGE.md) and respond to GitHub
issues. In general, we recommend waiting for feebdack from a FiftyOne
issues. In general, we recommend waiting for feedback from a FiftyOne
maintainer or community member before proceeding to implement a feature or
patch. This is particularly important for
[significant changes](#write-designs-for-significant-changes), and will
Expand All @@ -36,7 +36,7 @@ typically be labeled during triage with `needs design`.

After you have agreed upon an implementation strategy for your feature or patch
with a FiftyOne maintainer, the next step is to introduce your changes (see
[developing changes](#developing-changes-to-fiftyone)) as a pull request
[developer guide](#developer-guide)) as a pull request
against the FiftyOne repository.

Steps to make a pull request:
Expand Down

0 comments on commit 395b1bc

Please sign in to comment.