Write/Speak/Code 2019
Last updated
Last updated
This page was originally a ticket https://github.com/ushahidi/platform/issues/3659 and was migrated here for historical reasons.
Date: August 18, 2019.
Credits to for adding a new description in the Ushahidi settings page, making it much more clear what the user is going to achieve by making a deployment private. <3
******
****
@rowasc (that's me!) will be available for support in the W/S/C slack, in the channel #oss-ushahidi which you can join
@Erioldoesdesign will join us for design and product related questions later in the day (Thanks, Eriol 💯 ! )
@Angamanga is going to be supporting me the day before the event with preparation (Thanks Anna! ❤️ )
Our code of conduct
Tickets tagged wsc2019 are here to ensure there were some pre-selected issues that most folxs will be able to get started on quickly, but if you find an issue that you want to contribute and isn't tagged for the conference feel free to grab it (just leave a comment on it so other folks avoid picking the same issue, and tag @rowasc if you need some help ) :)
🤝 Please add a comment when you work on a ticket so others know it's already in progress
The full documentation to get started with coding in Ushahidi can be found here. We recommend to follow the local setup instructions and reach out to me with any blockers or issues you might find (we are revamping our docs, and migrating to gitbooks, so we appreciate all your feedback)
Hi! We are excited to be a part of the open source day with Write Speak Code this year! If you are new to Ushahidi, you can learn more about our work and our team here .
Report Code of Conduct violations: romina [at] ushahidi.com or angela [at] ushahidi.com
New to OSS? Tickets tagged are great to get started if you are new to open source development. We reserve those to make sure people who haven't contributed before can have a chance to fix small issues that make our platform better.
Tickets tagged will be prioritized for the participants of this open-source day. All tickets tagged for the event will have the secondary tag , , , so you can get a good idea of what they will involve.
Tickets tagged (even if the wsc2019 tag isn't present) are fair game for anyone who is looking to help verify that issues are still happening, or to folks interested in helping write descriptions and categorize the types of changes needed for them. Please do make sure to tag @rowasc or @Erioldoesdesign when you work on them so we can support you.
If you are planning to work on the frontend application, you only need one part of the codebase, the . We will provide (through slack) a demo deployment hosted in our QA servers for anyone looking to test their client work against the API, doing triage, documentation, or testing issues.
We are working on a new installation experience at the moment, and you can help us make it better 🎉 In you can find instructions if that's something you'd like to work on. We would love to get all your feedback and use it to improve the tools
