Welcome to Dodo for Mastodon1
This is a free and open Mastodon client and lives from contributions of the community.
There are many ways to contribute:
- 📣 Spread the project or its apps to the world
- ✍️ Writing tutorials and blog posts
- 📝 Create or update the documentation
- 🐛 Submit bug reports
- 💡 Adding ideas and feature requests to Discussions
- 👩🎨 Create designs or UX flows
- 🧑💻 Contribute code or review PRs
A community like this should be open, considerate and respectful.
Behaviours that reinforce these values contribute to a positive environment, and include:
- Being open. Members of the community are open to collaboration, whether it's on PEPs, patches, problems, or otherwise.
- Focusing on what is best for the community. We're respectful of the processes set forth in the community, and we work within them.
- Acknowledging time and effort. We're respectful of the volunteer efforts that permeate the Python community. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community.
- Being respectful of differing viewpoints and experiences. We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts.
- Showing empathy towards other community members. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.
- Being considerate. Members of the community are considerate of their peers -- other Python users.
- Being respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts.
- Gracefully accepting constructive criticism. When we disagree, we are courteous in raising our issues.
- Using welcoming and inclusive language. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference.
- Ensure cross-platform compatibility for every change that's accepted. Windows, Mac, Debian & Ubuntu Linux.
- Ensure that code that goes into the repository meets all requirements
- Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
- Don't add any classes to the codebase unless absolutely needed. Err on the side of using functions.
- Be welcoming to newcomers and encourage diverse new contributors from all backgrounds.
To contribute code to the repository, you don't need any permissions. First start by forking the repository, clone and checkout your clone and start coding. When you're happy with your changes, create Atomic commits on a new feature branch and push it to your fork.
Atomic commits will make it easier to track down regressions. Also, it enables the ability to cherry-pick or revert a change if needed.
- Fork it (https://github.com/AndroidDev-social/DodoForMastodon/fork)
- Install pre-commit hooks (
git config core.hooksPath .githooks
) - Create a new feature branch (
git checkout -b feature/fooBar
) - Commit your changes (
git commit -am 'Add some fooBar'
) - Push to the branch (
git push origin feature/fooBar
) - Create a new Pull Request
If you find a security vulnerability, do NOT open an issue. Email [[email protected]] instead.
- Open the issues tab on github
- Click on New issue
- Choose the bug report 🐛 template and fill out all required fields
Check open issues and ongoing discussions for a list of proposed features.
If your suggestion can not be found already, see if it is already covered by our Roadmap.
Otherwise, start a new Discussion and see what other users and contributors think.
There is also a Slack to join to get in touch with the community.
Also, sometimes it makes it easier to discuss topics
The project is currently build based on the Compose Multiplatform port from jetbrains, to re-use different parts on multiple platforms supporting Android, iOS and Desktop.
Underneath it is using these frameworks:
- Ktor - Kotlin async web framework
- SQLDelight - For SQL statements
The project is structured in layers with tree-structured feature modules
flowchart TD
android[app-android]
desktop[app-desktop]
ios[app-ios]
android --> ui
desktop --> ui
ios --> ui
ui-timeline --> domain-timeline
select-server --> domain-authentication
subgraph ui
ui-root
ui-signedIn
ui-signedOut
ui-timeline
ui-profile
ui-notifications
landing
select-server
oauth/sign-up/log-in
end
ui-root --> ui-signedIn
ui-root --> ui-signedOut
ui-signedOut --> landing
ui-signedOut --> select-server
ui-signedOut --> oauth/sign-up/log-in
ui-signedIn --> ui-timeline
ui-signedIn --> ui-profile
ui-signedIn --> ui-notifications
subgraph domain
domain-timeline
domain-authentication
end
domain --> data
subgraph data
data-repository
data-network
data-persistence
end
data-repository <--> data-network
data-repository <--> data-persistence[fa:fa-database data-persistence]
data-network <--> Y[fa:fa-cloud MastodonAPI]
To build the different apps, checkout the repository and run one of the following commands on your local machine
To build and run the desktop app
$ ./gradlew :app-desktop:run
To build and run the android app (emulator or real android device is needed)
$ ./gradlew :app-android:installDebug
To verify checks, run the following commands on your local machine
Run all configured checks for the project
$ ./gradlew check
For code analysis and enforcing code guidelines
- Run for whole project:
$ ./gradlew detekt
- Run for specific module:
$ ./gradlew module:detekt
Footnotes
-
This is just the working title for now. ↩