From 5a32619fa28aae4d1d617ea266c7fb087e6260aa Mon Sep 17 00:00:00 2001 From: Kishan Savant Date: Wed, 19 Oct 2022 22:27:55 +0530 Subject: [PATCH] Minor fixes to contributing.md --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6c46101350..a78c448941 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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. @@ -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 @@ -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: