GSoC Ideas

Change Policy

These ideas are subject to change at any time prior to us submitting our GSoC Organization application. Ideas may be added, removed or updated up to this time.

1. If we are accepted, there may be additions and minor modifications.
2. Mentor assignments may be adjusted throughout the evaluation period

Introduction

Welcome to our GSoC ideas page!

Tip

These are the minimum requirements. We encourage you to expand on them.

Repository Languages and Skills

Here is a list of basic skills that will be required for each repository.

1. Talawa: Flutter / Dart, GraphQL
   1. Work will be applied to the develop-postgres GitHub branch
2. Talawa-API: Typescript, GraphQL, PostgreSQL with the Drizzle ORM
   1. Work will be applied to the develop-postgres GitHub branch
3. Talawa-Admin Portal: TypeScript
   1. Work will be applied to the develop-postgres GitHub branch
4. SwitchMap-NG: Python
   1. Work will be applied to the develop GitHub branch

There are others, but these are the primary ones that will guide your contributions.

Impact Definition

We have categorized the various ideas according to the degree of impact they will have to the project. Use these definitions to understand how each idea will affect our overall project goals.

1. Low-hanging fruit: These projects require minimal familiarity with the codebase and basic technical knowledge. They are relatively short, with clear goals.
2. Risky/Exploratory: These projects push the scope boundaries of our development efforts. They might require expertise in an area not covered by our current development team. They might take advantage of a new technology. There is a reasonable chance that the project might be less successful, but the potential rewards make it worth the attempt.
3. Fun/Peripheral: These projects might not be related to the current core development focus, but create new innovations and new perspective for our project.
4. Core development: These projects derive from the ongoing work from the core of our development team. The list of features and bugs is never-ending, and help is always welcome.
5. Infrastructure/Automation: These projects are the code that our organization uses to get our development work done; for example, projects that improve the automation of releases, regression tests and automated builds. This is a category in which a contributor can be really helpful, doing work that the development team has been putting off while they focus on core development.

Difficulty

Most of our project ideas require knowledge of two or more programming languages. Meaningful PRs that prove your understanding of the repos will always be beneficial. We have created testing issues specifically for this purpose.

1. Hard: Requires dominion of the language used by the repo most affected by the project. A good working knowledge of the languages used by other affected repositories will be needed.
2. Medium: A good working knowledge of the languages used by affected repositories will be needed.
3. Easy: A beginner's level knowledge of the languages is sufficient.

Project Areas

info

Ideas will be posted on the next GSoC Organization application deadline date.