Skip to main content

GSoC Ideas


Welcome to our GSoC ideas page! Get familiar with our general philosophy by reading this section. The ideas follow afterwards.

General Considerations

This is not an exhaustive list of ideas, but they broadly classify the types of features on which we'd like to focus our attentions.

You are open to propose your own solutions.

  1. We encourage candidates to think laterally.
  2. Take the initiative and consider something hybrid taking thoughts from various ideas posted here or something totally new.

We want ideas that will have a material impact on the project

Remember, the ideas list is just a guide for what we feel could be achieved, and not a strict list of requirements. Think of the overall goal of making a better product. Picking a subset of suggestions and expanding them beyond our expectations shows your initiative.

NOTE: If you feel the project ideas will take too much time as stated, then:

  1. Add that to your proposal
  2. Include what you think a reasonable scope should be.

We need your ideas to be completed on time with 100% test cases with each PR.

  1. Brittle code that breaks easily does not help the project
  2. Incomplete functionality is not acceptable unless specifically stated.

If there are any dependencies on other project ideas, then state it. Also include additional or alternative things that you would do if the dependencies are not completed in your desired time frame

The project is so much in its infancy that we'll accept any good idea that users will want or will facilitate that they could want. They must significantly advance our goal of having an MVP within the year.

We also welcome any other ideas that we could use. Please review the "Desired Features" section of this website for even more ideas and further necessary information.

Internship Participants

Many of you reading this page are interested in participating in our various internship programs (eg. Google Summer of Code, GitHub Externship, Google Summer of Docs, Outreachy, etc.).

  1. Make sure to read the relevant Introduction and Application Guide/ Contribution Process pages first.
    1. GSoC Introduction.
    2. GSoC Application Guide.
  2. Review the Selection Criteria to ensure you meet all the requirements for a good proposal.
  3. Use the Application Template as a guide to formatting your application. The tips on this page are very important.

Good luck!


We need to reduce the learning curve of contributors and sysadmins alike. Project work needs to be well documented in our code so that tools can eventually automatically add it to our documentation websites.


All code submitted must be tested. We are working towards getting to 100% test code coverage on all Talawa repositories. This will mean that you will have to write tests for new code you write or modify.

The test percent code coverage requirement will incrementally rise with each pull request. In some cases you may have to write a few extra tests for code you may not have updated. We hope this will be rare.

Write code that will work in the long term. Eliminate brittle code that will easily break.

Repository Languages and Skills

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

  1. Talawa: Flutter / Dart, GraphQL
  2. Talawa-API: Typescript, GraphQL, MongoDB
  3. Talawa-Admin Portal: TypeScript

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.


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.


Talawa is a suite of applications that are aimed at managing the memberships of community based organizations. This concept may be new to you, and we suggest you research church, temple and/or synagogue management software as a starting point. Talawa needs to have a broader reach and your additions to our ideas will make the difference. We have included links to YouTube videos on this page that will be useful in improving your understanding.

Your solution should ideally consider the:

  1. ability of typical small community organizations with limited resources to:
    1. get tech support to maintain the application
    2. have tech-savvy users
    3. afford long term costs
    4. need all membership information completely under their control
    5. manage services outside the applications
  2. impact of using third party services
  3. performance / usability trade-offs
  4. potential data residency law requirements


We will not support administrative functions in the mobile app.

Idea Areas

This section outlines the primary features we'd like to implement in the coming months with impacts on all the applications.

Please read the Research section of this document for background information

Improved File Uploads and Security

  1. Description: We need a better solution for handling files uploaded from Talawa clients. GraphQL is unsuitable for file access and, storing files in the code tree with only a .gitignore file as protection is risky.
  2. Expected Outcomes:
    1. Objects must be:
      1. Stored in a location outside the code tree
      2. Accessed using industry best practices and libraries that are unlikely to be deprecated or abandoned.
      3. Deduplicated.
      4. Encrypted whenever and wherever possible.
      5. Stored in the same way independent of their size, type or other characteristics.
      6. Screened for malicious content.
    2. Other
      1. By default, storage must be accessible via the system's locally accessible filesystem as a configurable parameter(s).
      2. The use of cloud storage services is discouraged at this time.
  3. References: There have been extensive discussions about this which should help in evaluating options.
  4. Repos to update: Talawa, Talawa-API, Talawa-Admin
  5. Skills Required: Code stacks related to repos above. See introduction section.
  6. Depends on Project: N/A
  7. Project Size: 350 hours (Large)
  8. Possible Mentors:
    1. Aashima Wadhwa - @aashimawadhwa (Primary)
    2. Tasneem Koushar - @tasneemkoushar (Secondary)
  9. Difficulty: Medium
  10. Impact Definition: Core development

Self Hosted Chat and Notifications

  1. Description: The Talawa apps are closely coupled with cloud services which creates operational concerns.
    1. This greatly complicates setup as each new service requires new externally controlled configuration parameters.
    2. It also adds greater troubleshooting and billing complexity for organizations that will not be tech-savvy.
    3. Small organizations may also find it difficult to comply with new data residency laws when using international services.
      For this idea there must be no dependency on any third party cloud service providers, all the code must run on the API server.
  2. Expected Outcomes:
    1. Chat : A key component of the Talawa application suite is chat. Though some endpoints have been created, the feature has not been fully activated and deployed. Chat must be:
      1. Hosted on the API server. We expect the typical Talawa deployment to be small and hosted by communities with limited funding that may not be able to afford cloud additional services.
      2. Available as 1 to 1 and 1 to many group chat options
      3. Automatically available to registered attendees of events as a dedicated group chat instance.
      4. Encrypted whenever and wherever possible
      5. Capable of allowing users to reply to any historical comment.
      6. Allow administrators to respond in various ways to complaints about chats.
      7. Have the ability for older chats to be purged from the system
      8. Assume that most communities using the chat system will be small. Research typical community sizes, seating and event attendance for various community based organizations in designing your solution. Consider easy to implement scalability if required.
    2. Notifications
      1. Identify an acceptable way to have notifications handled on the local server
  3. Repos to update: Talawa, Talawa-API, Talawa-Admin
  4. Skills Required: Code stacks related to repos above. See introduction section.
  5. Depends on Project: N/A
  6. Project Size: 350 hours (Large)
  7. Possible Mentors:
    1. Dominic Mills - @DMills27 (Primary)
    2. Kevonia Tomlinson - @Kevoniat (Secondary)
  8. Difficulty: Medium
  9. Impact Definition: Core development, Risky/Exploratory

AI Powered Improvements to Community Health

  1. Description: We want to enhance community interaction and moderation with AI. Implement various features that leverage AI to create more nuanced community interactions that anticipate user interactions, receive collaborative recommendations, and streamline task management with data-driven insights. Selected participants will integrate these key features in the Talawa Mobile App, to improve user experience and facilitate efficient moderation.
  2. Expected Outcomes: Consider ways to:
    1. Integrate sentiment analysis to gauge the emotional tone of discussions, helping to identify and address potential issues within the community.
    2. Use AI-powered summarization techniques to generate concise summaries of lengthy discussions or documents, making it easier for users to grasp key points.
    3. Use natural language processing (NLP) algorithms to automate content moderation, identifying and flagging inappropriate or spammy content.
    4. Utilize machine learning models to predict user engagement patterns, helping community organizers understand when to schedule events or post important updates for maximum impact.
    5. Implement collaborative filtering algorithms to suggest groups, subgroups, or content based on what similar users with shared interests are engaging with.
    6. Implement predictive analytics to help users and groups estimate the time needed to complete tasks and identify potential bottlenecks in project timelines.
  3. Reference:
    1. An Admin must not rely exclusively on AI for the features you suggest as they may not choose to activate AI.
    2. Non-profit organizations that we expect to use Talawa are often underfunded and will not have budgets to purchase powerful computing resources. As they often have small memberships, they will not have sufficient numbers of users to generate adequate data sets to train models. You will need to consider ways to use external sources that require minimum to no configuration requirements and cost. Open source solutions would be preferred.
  4. Repos to update: Talawa, Talawa-API, Talawa-Admin
  5. Skills Required: Code stacks related to repos above. See introduction section.
  6. Depends on Project: N/A
  7. Project Size: 350 hours (Large)
  8. Possible Mentors:
    1. Dominic Mills - @DMills27 (Primary)
    2. Shannika Jackson - @bonnie-23 (Secondary)
  9. Difficulty: Medium
  10. Impact Definition: Risky/Exploratory

AI Powered Automated Testing

  1. Description: This project idea aims to implement AI-powered testing automation for both Talawa-Admin and Talawa-API, encompassing test case generation, dynamic test suite optimization, and production environment testing. By leveraging artificial intelligence, the goal is to enhance the efficiency, accuracy, and adaptability of the testing process, ensuring robust and reliable performance.
  2. Expected Outcomes:
    1. Test Case Generation:
      1. Identify and integrate AI tools or frameworks capable of generating test cases based on code changes and requirements.
      2. Utilize AI algorithms to comprehend code modifications and automatically generate relevant test scenarios.
      3. Explore tools for AI-assisted test case generation.
    2. Dynamic Test Suite Optimization:
      1. Implement an AI-driven solution to dynamically optimize the test suite based on code changes.
      2. Utilize machine learning models to identify test cases that need prioritization or skipping based on the impact of code modifications.
      3. Ensure efficient resource utilization by dynamically adjusting the test suite.
    3. Production Environment Testing:
      1. Develop an automated testing pipeline tailored for the production environment.
      2. Leverage AI to simulate real-world scenarios and user interactions, ensuring a production-like testing environment.
      3. Implement AI algorithms to identify and prioritize critical test cases for the production environment.
    4. End to End Testing:
      1. We need a way to test the applications end to end for the correct functionality. Our merged PRs often cause functionality to break in ways not dectectable by our unit testsing.
  3. Reference:
    1. Non-profit organizations using Talawa may have budget constraints and limited computing resources. Consider open-source solutions and external sources that require minimal configuration and cost for AI-powered testing. It is essential to design the solution keeping in mind the resource limitations of the target user base.
    2. We have been investigating products such as:
      1. Diffblue Cover
      2. Parasoft
      3. TestPilot
  4. Repos to Update: Talawa-API, Talawa-Admin
  5. Skills Required: Code stacks related to repos above. See introduction section.
  6. Depends on Project: N/A
  7. Project Size: 350 hours (Large)
  8. Possible Mentors:
    1. Tasneem Koushar - @tasneemkoushar (Primary)
    2. Md Noman Khan - @noman2002 (Secondary)
    3. Kukade Siddhesh Bhupendra - @SiddheshKukade (Scondary)
  9. Difficulty: Medium
  10. Impact Definition: Risky/Exploratory

Event Attendance - Talawa Admin

  1. Description: Administrators will need features to improve the management of, and reporting on, event attendance. For this to be most effective, event attendance will need to be accessed from either from:
    1. A member's profile (Member Profile) view.
    2. An event's detail page (Event Detail) views.
  2. Expected Outcomes: This project idea is more prescriptive than others in the list because we need to get the basic structure correct as it will have a long term impact on our repositories. There will be lots of ways for you transform this foundation into an impressive result.
    1. Member Profile: We need additional functionality to the member profile screen to achieve this goal.
      1. Attendance: A button or menu item should be presented (Admins only) on each member's profile. When selected, this should display an attendance view.
        1. Attendance View: This should display a list of events that the member has attended and any upcoming events the member is registered to attend.
          1. If the member has neither attended a past event nor is registered for an upcoming event options should be presented to the admin user to;
            1. Invite the selected member to upcoming events.
          2. If the member has attended past events or is registered for upcoming events, display the following attributes for each event in the list.
            1. Event Name: The name of the event
            2. Date of Event: The scheduled start date for the event
            3. Recurring Flag: A flag indicating if the event ids a recurring event
            4. Task Flag: A flag indicating that the member has been assigned one or multiple tasks for the event
          3. The admin user must have the ability to toggle between a list of past events attended by the selected member and upcoming events they are registered for.
          4. The admin user must have the ability to interact with the list of events being displayed. (S)he must be able to:
            1. Search: Search the displayed event list for an event by event name.
            2. Sort: Sort the displayed event list by event name or by event date.
            3. Filter: Filter the displayed event list by a date range based on event date or by one or multiple event tags.
          5. The admin user must be able to select an event in the list and navigate to the event detail view.
    2. Event Detail
      1. Event Attendance Management: The user (Admins only) must be presented with a button or menu item for Attendance. When this item is selected the admin user must be navigated to a list of attendees to the selected event.
        1. For each item in the list of Attendees display the following attributes;
          1. Member Name: Name of registered member that attended the event
          2. Member Status: The status of the member in the organization
          3. Number of Events Attended: The number of events attended by the member;
            1. This month
            2. This year
        2. If the selected event is a past event or future event, display the list of attendees and/or invitees for the event where relevant.
        3. Flag attendees that performed a role or was assigned to an Action Item for the event
        4. If the event is part of a recurring event, the admin user must be presented with options to;
          1. View a list of past events in the series
          2. Edit all events in the series
          3. Edit the current event and future occurrences of the event
        5. The Admin user must be able to Check-In a member to the event.
          1. If people turn up at the door, and they are not in the system, it must be possible to add them as part of the check-in process (USERS and NON_USERs alike).
          2. Events requiring registration must only be able to check-in people who have registered. It must also be possible to add, register and check-in people at the door as an exception if the venue has the space.
      2. Event Attendance Reporting
        1. Reporting and data visualization is also required for events. The following charts and measures must be displayed;
          1. Total number attendees for the event
          2. For recurring events, historical attendance must be reported on;
            1. Attendance Trend; Charting
              1. 6 months
              2. 12 months
              3. 24 months
            2. Attendance Frequency; the number of persons attending the selected event for the;
              1. First time
              2. Second time
              3. Third time
              4. Fourth time
              5. Greater than 5 times
            3. The admin should be able to view the list of attendees in each frequency bucket
          3. Attendance Demography; the number of attendants grouped by;
            1. Gender
            2. Member Status
            3. Age Group
          4. Think of novel ways of tabulating historical attendance for recurring events
    3. NOTE: These are ongoing efforts in which API and Admin CRUD work has been happening for months. You will need to integrate these efforts into your project, and make improvements. We feel the other needs of this project will require a majority of your time.
      1. Making recurring meetings flawless
      2. Adding improved attendance tracking
      3. Improving user profile management
    4. Other:
      1. Think of the many ways in which you could improve this outline.
      2. You will need to write valid tests for this work
      3. You may want to add features to one or more repositories to facilitate your idea.
      4. The challenge will be in creating an intuitive UI/UX to make these features desirable. The UI/UX must conform with our design guide and Figma files found here:
      5. Support for this feature was added to Talawa API in the past year. We welcome GitHub issues to verify and rectify the expected functionality of this API support during the GSoC evaluation period.
  3. Repos to update: Talawa-API, Talawa-Admin
  4. Skills Required: Code stacks related to repos above. See introduction section.
  5. Depends on Project: N/A
  6. Project Size: 350 hours (Large)
  7. Possible Mentors:
    1. Shannika Jackson - @bonnie-23 (Primary)
    2. Dominic Mills - @DMills27 (Secondary)
    3. Aashima Wadhwa - @aashimawadhwa (Secondary)
  8. Difficulty: Medium
  9. Impact Definition: Core development

User Tag Management - Talawa Admin

  1. Description: We need a comprehensive user tag management system for Talawa Admin to address current limitations and enhance community organisation. This system will introduce both automatic and manual tag allotment, hierarchical tag structures, and CRUD operations.
    1. The current lack of a robust tag management system hinders effective organisation and communication within the Talawa community. The proposed system aims to streamline user categorization, facilitating targeted communication and enhancing community engagement.
    2. This should not be confused with hashtags or tagging someone in a chat. This is for applying a label/category to User and Event objects
    3. Support for this feature was added to Talawa API in the past year. We welcome GitHub issues to verify and rectify the expected functionality of this API support during the GSoC evaluation period.
  2. Expected Outcomes:
    1. Automatic tag allotment based on predefined criteria.
    2. Manual tag allotment by Admins and/or Super Admins.
    3. Hierarchical tag structures with parent and nested sub-tags.
    4. CRUD operations for tags (Create, Read, Update, Delete).
    5. Grouping of users based on tags.
    6. Broadcasting emails/messages to a group of users with certain tags.
    7. Filtering of users based on tags for targeted communication.
  3. Repos to Update: Talawa, Talawa-API, Talawa-Admin
  4. Skills Required: Code stacks related to the mentioned repositories.
  5. Depends on Project: N/A
  6. Project Size: 350 hours (Large)
  7. Possible Mentors:
    1. Rishav Jha - @rishav-jha-mech (Primary)
    2. Nitya Pasrija - @Nitya-Pasrija (Secondary)
    3. Noble Mittal - @beingnoble03 (Secondary)
  8. Difficulty: Medium
  9. Impact Definition: Core development

Event Parity - Talawa Mobile

  1. Description: We have recently added many new features to the API to that enhance event management. These are not reflected in our mobile app. 2. Expected Outcomes:
    1. Requirements: Your proposal must meet the guidelines below. It must:
      1. Provide user feature parity with the Talawa Admin User Portal for event management.
      2. Not add any Admin or Super Admin features. These must remain solely in the Talawa-Admin web app.
    2. Other:
      1. The challenge will be in creating an intuitive UI/UX to make these features desirable. The UI/UX must conform with our design guide and Figma files found here:
      2. Significant updates to this feature were added to Talawa API in the past year. We welcome GitHub issues to verify and rectify the expected functionality of this API support during the GSoC evaluation period.
      3. Implemet fundraising campaigns.
      4. Implement tags in the mobile app.
  2. Repos to update: Talawa, Talawa-API
  3. Skills Required: Code stacks related to repos above. See introduction section.
  4. Depends on Project: User Tag Management
  5. Project Size: 350 hours (Large)
  6. Possible Mentors:
    1. Md Noman Khan - @noman2002 (Primary)
    2. Mikey Lue - @JamaicanFriedChicken (Secondary)
  7. Difficulty: Medium
  8. Impact Definition: Core development

Offline Capability Enhancement - Talawa Mobile

  1. Description: Talawa's mobile application currently lacks robust offline capabilities, unlike many other social media apps. This compromises the app's stability and reliability. Additionally, the absence of a proper app state caching mechanism leads to performance issues and unnecessary network usage overhead.
  2. Expected Outcomes:
    1. Your proposal should focus on enhancing Talawa Mobile's offline capabilities to achieve feature parity with other social media platforms.
    2. The solution should include:
      1. Implementing offline functionality that gracefully handles offline situations, allowing users to seamlessly interact with the app and cache their actions and app state locally.
      2. Synchronizing user actions and app state with the server once the app regains connectivity.
      3. Implementing a robust caching mechanism throughout the app to enhance user experience, reduce internet usage overhead, and improve performance.
    3. Integrate chat in the mobile app.
  3. Other Considerations:
    1. Creating an intuitive UI/UX to make the offline features desirable is a significant challenge. The UI/UX must align with Talawa's design guide and Figma files, which can be found here.
    2. Note: Ensure that the proposed features do not include any Admin or Super Admin functionalities, which should remain exclusive to the Talawa-Admin web app.
  4. Repos to Update: Talawa, Talawa-API
  5. Skills Required: Proficiency in the code stacks related to the Talawa and Talawa-API repositories. Refer to the introduction section for more details.
  6. Depends on Project: Self Hosted Chat and Notifications
  7. Project Size: 350 hours (Large)
  8. Possible Mentors:
    1. Md Noman Khan - @noman2002 (Primary)
    2. Ayush Chaudhary - @Ayush0Chaudhary (Secondary)
  9. Difficulty: Medium
  10. Impact Definition: Risky/Exploratory

Hybrid: Hybrid Innovation

  1. Description: Do the ideas need something more? What completely new thoughts could be applied to the existing ideas? If you have answers to these questions then this section is for you.
  2. Expected Outcomes: Your proposal must meet the guidelines below. It must:
    1. Not depend on other participants. There should be minimal impact by other participants disappearing or doing a very bad or very good job.
    2. Add completely new features not previously stated in ideas.
    3. Create features that users will want or facilitate new features that will be the groundwork for features that they would want.
    4. Be suitable for use by most non-profit organization.
      1. We are not interested in membership subscriptions and any related financial management at this time.
    5. Justify 350 hours of work.
  3. Repos to update: Talawa, Talawa-API, Talawa-Admin
  4. Skills Required: Code stacks related to repos above. See introduction section.
  5. Depends on Project: N/A
  6. Project Size: 350 hours (Large)
  7. Possible Mentors:
    1. Tyrone Taylor - @ttaylor92 (Primary)
    2. Ayush Chaudhary - @Ayush0Chaudhary (Secondary)
  8. Difficulty: Medium
  9. Impact Definition: Risky/Exploratory