Welcome to data-research-analysis-platform Discussions!

[mustafaneguib]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[preettrank53]

Hi team,

I recently worked on issue #284, and the PR was merged successfully. While working on it, I spent time understanding the codebase, project structure, and current development flow.

I’m interested in contributing more consistently and taking ownership of specific areas of the project instead of one-off fixes.

Some areas I can actively work on:

• Picking up open issues and closing them end-to-end
• Improving code structure and maintainability where needed
• Adding missing tests and improving existing test coverage
• Helping with small feature iterations and bug fixes

Before proceeding, I wanted to start this discussion to understand:

• Current priorities for the project
• Areas where help would be most valuable
• Whether long-term contributions in this repo would be useful

Happy to align with the project’s direction and take responsibility where needed.

Thanks.

[mustafaneguib]

Hi Preet,

First off, huge thanks for the work on #284. The quality of the PR was excellent, and it’s great to have you in the codebase.

To answer your questions directly: Yes, long-term contributions will always be incredibly valuable and we are excited for you to join and help us make this platform better.

We are currently in our "Private Beta" stage and are in the process of acquiring new marketing companies as customers, so our current focus is to integrate the tools that marketing executives and teams use in their marketing related activities as data sources.

We are adding to the issues/features request list what we want implemented as soon as possible and new issues are being added as we speak that align with the vision of this platform.

Here is how we can align your interest with our current project direction:

1. Even though we have backend tests implemented we still need to test the platform end to end and create detailed Github issues for the bugs that are found so that we can fix them as soon as possible.

2. You can access the tickets based on the priority from the following:
   high priority
   medium priority
   low priority

   The high priority issues are to be tackled first and then move on to medium issues. If a new high priority issue comes then that is to be tackled first. This is extremely important.

3. We need to ensure the reliability of the data source connectors and have to ensure that whatever has been implemented is working and is reliable.

4. Areas for Ownership Since you mentioned maintainability and test coverage, I’d love for you to take point on "The Stability Layer." This includes:

Test Suite Stewardship: We need to increase our coverage to ensure new features don't break old ones. You can have a look at the already implemented backend unit tests.

Refactoring for Scale: As we add more users, we need to ensure our data processing isn't creating its own "Technical Bottleneck."

5. Long-term Vision While we are building this in the open, our ultimate goal is to solve the "Data Drudgery" for non-technical users. Your work on the "back-end" allows them to have that "Conversational AI" experience on the front-end.

Next Steps: I’ve tagged a few issues with "Priority: High" and "Status: Help Wanted." Why don't you take a look at #287? If you can close 10-15 of these, I'd be happy to discuss a more formal "Core Contributor" role where you can help review other PRs and steward specific modules.

We are also planning a formal "Contributor Recognition" section in our README soon—your name should definitely be at the top of that list.

Welcome to the team!

[preettrank53]

@mustafaneguib Thank you for the detailed context and the trust - I really appreciate it.
I understand the current priorities and the importance of stability, especially during the Private Beta phase. I’m happy to take ownership of the Stability Layer as outlined.
I’ll start with issue #287 and focus on high-priority issues first, ensuring clear bug reports, reproducible test cases, and fixes where applicable. I’ll also look into improving end-to-end test coverage alongside existing backend tests.
I’ll keep updates focused and actionable.
Looking forward to contributing.

[mustafaneguib]

@preettrank53 i appreciate your trust in us as well, welcome to the team, and I thank you again for helping us make Data Research Analysis better. I have assigned #287 to you.