Add licensing information or a FAQ for license questions to our docs
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by locating the References section on the project websites and review the license files in the GitHub repositories. Decide whether the page should link to those files or provide license information or an FAQ, then confirm that license guidance is accessible from the documentation.
Written by the indexing model from the issue text.
Description
As mentioned by a community member (https://discord.com/channels/1128210118216007792/1460328376882434141), it would be great to not only have the license information in our Github repository but also more accessible from our websites. One idea could be to add a license section under references which either contains license information or a FAQ that answers frequently asked licensing questions. The simplest solution would be to link to the license files in the Github repositories.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 17
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 14
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from restatedev/docs-restate
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
restatedev/docs-restate#422 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
restatedev/docs-restate#410 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
restatedev/docs-restate#385 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
restatedev/docs-restate#123 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
restatedev/docs-restate#99 ·
Maintainers usually reply within 2 days
All issues in restatedev/docs-restate
Similar issues
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ranxianglei/billion-context#4172 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
awslabs/threat-composer#362 ·
Maintainers usually reply within 1 day
-
Area/Cloud Needs Triage Type/Bug
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
wso2/product-integrator#2847 ·
Maintainers usually reply within 1 day