Technical communities · SINGAPORE
Start with the question you need to answer. Each guide explains what to look for in an event and links to Boardzip’s free search. Individual events have their own prices and participation terms.
Search upcoming events →Showing 1–8 of 8 guides
Developers making a first open-source contribution
Compare a social coding night, competitive build and supported project contribution, then prepare one agreed task with the setup, evidence and review route it needs.
First-time contributors responding to an unaccepted patch
Turn the actual review into a bounded next action, distinguishing a repair request, a declined scope and an unanswered proposal before spending another coding session on it.
First-time contributors whose approved patch cannot be merged
Check the project’s completion step instead of treating an approved patch as a merged release.
Contributor with an unrequested patch
Turn a large change already started into a bounded proposal with alternatives, then identify the project decision still needed before doing more implementation.
Contributor writing deployment notes
Turn an installation that worked on your machine into a scoped documentation contribution that another reader can assess and reproduce.
Contributor checking translated messages
Prepare a message card with its inserted information, actual rendering state and expected meaning, then record language and interface observations at the cases you checked.
Contributor finding untranslated interface text
Record one unchanged interface message, distinguish an observed rendering path from a suspected key, and prepare the smallest project-scoped question before editing more files.
Contributor with a security-related question
Choose the project’s actual reporting route for a possible finding, and prepare a separate public learning question whose scope does not expose the live observation.