Hii @armanalam03 Thanks for the above details. I want to ask what do we really want to implement for this section Side-by-side comparison for discussions and articles.. do we need to compare articles ? do we need different page for this or should we implement this inside gmail like interface ? one more question is what kind of improvements do we need for this Improved comment system with threading. we have already implemented threading in comment system.
Thanks.
Hi, we donât need side by side comparison and yes threading system is implemented.
I added it by mistake from previous draft feature list. I have removed it from the list now.
Thanks
I am preparing my GSoC proposal for the project âSciCommons: A Social-Web Tool for Scientific Discussion, Interaction, Rating, and Peer-Reviewâ and would like to have it reviewed by the mentors. Could you please guide me on how to proceed?
Please use the INCF GSoC template, and when it is ready, send it to me and Armaan via DM. @Irfanulhak_Shaikh
To increase your chances, it is highly recommended that you actually engage with the codebase first and demonstrate a level of understanding by successfully attempting a few tasks or finding bugs etc.
@ arnab1896, @armanalam03 , @jbPoline , @suresh.krishna
hii everyone,
My name is Aryan Yadav, and I am currently in my 3rd year of Computer Science. I am a student of Sigma 4.0 Batch at Apna College, actively working on MERN stack and Next.js projects.
I am very interested in contributing to SciCommons in GSoC 2025, particularly in frontend development with Next.js, Radix UI/ShadCN UI, and TanStack Query. My experience aligns well with this project as I have:
I would love to learn more about the current challenges and discuss how I can contribute. Please find my portfolio and GitHub links below:
Portfolio: [Your Portfolio Link]
GitHub: [Your GitHub Link]
LinkedIn: [Your LinkedIn Link]
Looking forward to your guidance and an opportunity to contribute!
Best regards,
Aryan Yadav
Hello everyone. As @suresh.krishna sir said, lets engage more into the project and the feature list we provided. Only proposal wonât help us decide how well you understand the project and will you be a good fit or not. So lets iterate more over some ideas you have based on the feature list. Parallelly, I would also recommend you to start building a solid proposal mentioning all of your contributions and ideas you discussed with us.
Few important points:
Efficient API calls and caching in frontend into the feature list. this is one of the important requirement for us as we are using tanstack query, we want to make the api calls and caching data much efficient and easy to handle.Hi, @armanalam03 can you please review my proposal. I have send you on you Mail. I will continue to edit it.
Thanks.
Hi @armanalam03 @suresh.krishna Tanstack query is already implemented in SciCommon. what improvements we need to do in that. Can you please tell me in brief.
Right now, weâre using Tanstack Query, but weâre not really making the most of it. One big issue is that weâre not properly maintaining query keys for caching, and the cache TTL (time-to-live) isnât well set either.
Example scenario:
Letâs say I add a new review for an article. When I submit the review, the frontend makes an API call to submit it, and then another API call to fetch all the updated reviews. The problem? Fetching all reviews again might take some time, which means for a short period, the frontend could be showing stale data.
How we can improve this:
Instead of waiting for the API response and triggering a refetch, we can optimistically update the existing reviews list in the cache. Basically, as soon as the user submits a review, we update the UI instantly using the same query key we used for fetching reviews. This way, the frontend feels snappier because the new review appears immediately.
Of course, we canât just blindly assume everything will go fine. If adding a review fails (network issue, validation error, etc.), we need to handle that properlyâlike showing an error message or rolling back the UI update so the user knows the submission didnât go through.
By setting up proper query keys and leveraging optimistic updates, we can make the experience a lot smoother while keeping the data in sync without unnecessary refetches.
Hello everyone. I request you all to please again send me your proposals for reviews. I was quite busy last week so I didnât get much time to review it. Thanks.
@shreyamali01 @yadavaryan17 @abhishek2634 @Irfanulhak_Shaikh
As proposal submission deadline is near, I request you all to draft the final proposal and get it reviewed from @suresh.krishna sir and me. Its crucial to add all the work you have done and your proposed ideas.
You can find proposal template here:
https://www.incf.org/sites/default/files/files/INCF_GSoC_2022_Application_template.pdf
Alright @armanalam03 I have send you my proposal. please review it and suggest me how can i improve it. Thanks.
@armanalam03 @suresh.krishna
I have mailed my proposal to both of you.
Could you please review it and let me know if there are any improvements or missing aspects that I should work on? Your guidance would be really helpful in refining my proposal further.
@armanalam03
I have messaged you my proposal to your LinkedIn. Please review it and let me know if there is anything to improve.
Dear Mentors and INCF Community,
I hope this message finds you well. My name is Madhurya Veera, and I am currently a third-year Computer Science and Engineering student at Aditya College of Engineering and Technology, India.
I am writing to express my sincere interest in the GSoC 2025 project titled âSciCommons: A social-web tool for scientific discussion, interaction, rating, and peer-review.â
With a solid background in Python programming, data science, and web development, I am excited by the opportunity to contribute to a platform that aims to democratize scientific discourse and enhance scholarly communication.
As part of my preparation:
I have started exploring the SciCommons portal and reviewing its core goals and structure.
I am brushing up on relevant technologies such as Next.js, modular front-end patterns, and open-source NLP tools and LLMs.
I am particularly interested in contributing to the NLP side of the project, where I can help build and integrate intelligent tools for literature filtering and scientific content analysis.
I would be grateful for any guidance you could provide to help me further align with the projectâs current roadmapâsuch as recommended resources, starter issues, or areas where I can begin contributing. Iâm looking forward to connecting with you and becoming a part of the SciCommons journey.
Thank you for your time and consideration!
Best regards,
Madhurya Veera
Third-Year Student, Computer Science and Engineering
Aditya College of Engineering and Technology
madhurya3112@gmail.com
+91 9652329479
MANAGED BY INCF
