OpenLitterMap / OpenLitterMap/openlittermap-web
Questions about process for contributing to OLM
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 134
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
HOT and Codeando did community testing on the mobile app two months ago with users and summarised the feedback by adding a list of suggestions on Trello.
There are two specific ones we could potentially work on in supporting the improvement of OpenLitterMap (see below):
https://trello.com/c/L1VRQxlF/212-translation-to-spanish
https://trello.com/c/5H1lSUvU/211-make-an-onboarding-tutorial-inside-the-app
However, before we commit any extra volunteer time to work on this, we need to know:
- Currently the issues are on Trello- should we move them to Github as issues? Or do you prefer Trello? I will be happy to add to Github asap.
- Is this contributing.md the correct one to follow? Fork the repo and then send PRs for you to review?
- What is the expected review time on Pull Requests? @xlcrr are you the only person who can approve and merge PRs or there anyone else who can collaborate with us/ we can tag while you are offline? Especially as we are hoping to contribute and help improve the translation at least by mid-July.
@xlcrr can you provide answers ? Thank you!
Contributor guide
No contributing guide indexed for this repository
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
Start with CONTRIBUTING.md and the two linked Trello cards. Determine whether the cards should become GitHub issues, whether that contribution guide is current, and who reviews and merges pull requests; the work is done when these process and review questions have clear, documented answers.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100