Orange-OpenSource / Orange-OpenSource/ouds-android
Eco design - Explain why a component does not rely on the native implementation
Open
Nobody has claimed this yet.
📖 documentation
🧰 library
- Dominant language
- Kotlin
- Stars
- 22
- Forks
- 5
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 30
Description
Here is an eco design requirement coming from Maria Jose Presso.
When a component does not rely on the native implementation, add a section in its technical documentation that explain why this is the case.
Contributor guide
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.
Research direction
Review the technical documentation for the library's components and identify those that do not rely on native implementations. Add a section to each affected component's documentation explaining why, then verify that the documentation remains complete and consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- documentation, mobile
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100