forked from HumanSignal/label-studio
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Docs/roadmap notes (HumanSignal#842)
* Add roadmap notes (WIP) * Text updates Updating for clarity and language Co-authored-by: nik <[email protected]> Co-authored-by: smoreface <[email protected]>
- Loading branch information
1 parent
4652bb9
commit 4962034
Showing
2 changed files
with
38 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
## Label Studio public roadmap | ||
|
||
We love open source and are inspired by community-driven development. | ||
That's why we made our Label Studio roadmap publicly available. Here is a link: | ||
|
||
[Label Studio Roadmap](https://github.com/orgs/heartexlabs/projects/1) | ||
|
||
If you want to contribute or make a feature request for the next release, please read this guide first. | ||
|
||
## Guide | ||
|
||
The roadmap exposes our development plans for the next few quarters. | ||
|
||
It's structured in columns with the following information: | ||
|
||
**Q2 Apr-Jun** | ||
Describes what is expected to be done in terms of: | ||
- **Focus on** the main goals, | ||
- **Expected release** links | ||
- **Main deliverables** anticipated at the end of the current period. | ||
|
||
Though the roadmap reflects most of the current data annotation community needs, and shows the general direction of Label Studio development, it's not a final "do-or-die" document. The roadmap might change due to unforeseen circumstances or other reasons. | ||
|
||
#### Contribution | ||
|
||
The easiest way to contribute to Label Studio is by creating a [feature request](https://github.com/heartexlabs/label-studio/issues/new?assignees=makseq&labels=&template=feature_request.md&title=), or review the [existing ones](https://github.com/heartexlabs/label-studio/issues) | ||
and leave your comment or vote. | ||
|
||
GitHub issues are processed in the following steps: | ||
|
||
1. Issue is assigned to the [Label Studio Roadmap](https://github.com/orgs/heartexlabs/projects/1) project. This means we're on it and things are going to happen. | ||
2. Issue is assigned to a milestone referring to a specific Label Studio version. This means you can get your feature in a public release by a specific date (the end of the assigned milestone), or even early in a bleeding-edge version (master branch). | ||
|
||
We prioritize all created requests according to the current roadmap. If your feature request or submitted issue is left without any tag or assignment, no worries. Give it some time — we'll include it later, or you can [ping us on Slack](https://join.slack.com/t/label-studio/shared_invite/zt-cr8b7ygm-6L45z7biEBw4HXa5A2b5pw) if you think it's very urgent. |