Each applicant to The Palisadoes Foundation’s Talawa programs will be assessed using the following criteria
- Contributions to the Talawa repositories
- Communication Skills
- Proposal Quality and End User Impact
- Technical Knowledge & Skill
The above broad criteria will be expanded on below.
Read this carefully.
Contribution evaluation factors include:
- Higher weighting to recent contributions, especially those done during formal evaluation periods as in the GSoC and Calico programs.
- The quality of Issues and Pull Requests (PR)
- We consider the person’s displayed competence in the code base. Consistent meaningful PR contributions show commitment and hence value. You are much better served submitting fewer, higher quality PRs that showcase your abilities.
- Focus on the priorities stated in our
Getting Started - DevelopersYouTube channel playlist.
- Don't submit low quality Issues and PRs. These are ignored when assessing participants. Do not get a reputation for doing this.
- The impact of your merged PRs to our software.
In summary be a conscientious contributor to our long term goals of sustainable software development for the unmet needs of community based organizations.
The quality of the submitted proposals are important.
We value collaboration greatly. Therefore, the value of your participation in the community will be assessed. This includes your:
- Behavior and Attitude toward mentors and other contributors
- Were participants respectful when interacting with others?
- Did participants handle disputes appropriately?
- Did participants perform any malicious actions to gain an unfair advantage for themselves or to deter others?
- Knowledge in using collaboration tools such as GitHub
- Appropriate format for contributions were used when creating issues and PRS
- Accuracy when following contribution guidelines
- Collaboration tools were used appropriately (i.e. Bad practices such as ‘force pushes’ in git were not used)
Our contributors are spread out around the globe from cultures and backgrounds unknown to you. Each repository has a CODE_OF_CONDUCT.md file outlining additional steps you can take to be a better participant.
The End User Perspective
We highly value proposals that consider practicability, long term support, usability, and the perceived value to both the administrator and user. Limiting your solution to only the desired outcome discussion points will not give you an advantage.
Our ideas list gives an outline of what we'd like to see implemented, but do not limit your proposal to this bare minimum. Copying feature functionality from other sources without improving upon them is insufficient, Talawa must always be better. Expand on the possibilities to meet our innovation requirements. We greatly value innovative features and approaches.
When the idea has a focus on the end user always consider new or updated features that will be:
- Likely to be used extensively
- Intuitive to use
- Valuable to the end user
Always evaluate how the feature will make the administrator more likely to try Talawa.
Innovation behind the scenes should cover:
- Ease of management by DevOps teams that may have limited experience.
- Improving performance, scalability and reliability
Talawa is an open source project with mostly documentation as a technical support resource. The ease of use will always need to be considered.
Technical Knowledge and Skill
You should have experience in the technologies we use in the projects. You will not be effective without it. We therefore expect:
- Knowledge of our tech stack (Flutter, NodeJS, Mongo, etc.)
- Experience using our stack
- Previous projects to show affinity with our stack
- Willingness to learn our stack
- Knowledge of deploying systems
- Deploying backend applications to cloud services
- Deploying frontend applications to appropriate mobile stores (Google Play Store & Apple App Store)
- Ability to finish the tasks in a prompt manner and create a productive workflow.
- Ability to independently work on an issue or feature
- High standards of code quality. It must be:
- Maintainable (eg. using widely supported, non EOL, production ready libraries)
- Verifiably testable
We want you to be successful, and these requirements help to ensure this happens.
We need to maintain good code quality therefore we maintain general minimum requirements for any participant that we assess.
We expect that:
- Participants should have at least one properly closed issue and merged PR made on the repository
- Participants should be receptive to any feedback given to them from mentors
- Access to all required hardware and software for development on our project
- Access to a stable internet connection
Without these prerequisites you will not be successful.
These are some general focus areas for our applications by repository.
- Talawa Front End (Web & Mobile)
- UI/UX designs & reviews
- Development of UI
- Development of Features & Functions
- Talawa API Backend
- MERN stack
- Talawa Admin Web Portal
- Deployment of Front and Back End
- CI/CD Pipeline for Front and Back end
NB: Participants will have to work on multiple aspects of the application, but breaking it down will give everyone a more “clear cut” role when they’re deciding what to work on. (i.e. A student won’t be accepted if they're only willing to do UI/UX designs and reviews. If a student would like to work on all areas related to the front end, that would be fine.)
Mentors may at any point decide to hold an interview with any applicant to decide whether they are suitable for selection. This is completely optional, so participants may be accepted without participating in an interview.
Competition for our GSoC slots is tough. We encourage participants to submit multiple proposals. In the past, we noticed people only submitting proposals for the high priority ideas we listed. This was very limiting. To improve the range of useful goals on our product road map, we created the hybrid project idea. This helps people to explore new avenues of innovation where you can differentiate themselves.