showcase Academic PBL

[AyushChauhan074]

Discussion Type

Product Feedback

Discussion Content

🏷️ Discussion Type
Question

💬 Feature/Topic Area
Profile / Best Practices

Body
Title: Best way to showcase Academic PBL (Project-Based Learning) projects on a professional GitHub profile?

Hi everyone,

I’m currently in my 6th semester of a B.Tech in Computer Science, and I’m looking to clean up my GitHub profile for upcoming internship applications. I have several academic projects (Project-Based Learning), including an AI Face Recognition Attendance System and a DBMS-based Placement Portal.

I have a few specific questions regarding how to best present these:

Group vs. Individual: For my "TeamSync PBL" project, I worked in a group. Is it better to fork the main team repo to my profile, or should I host my own version with a clear README attributing my teammates?

README Standards: For complex projects like the AI Face Recognition system, should I include a video demo or just architectural diagrams? How much technical detail (like model accuracy or specific libraries used) is "too much" for a recruiter?

Clean-up: I have some older, simpler projects from my 4th semester (like an OS Deadlock Simulator). Should I archive these to keep the focus on my newer, more complex work, or is it better to show the progression of my coding journey?

I’d love to hear how other students or recruiters view "Academic" vs. "Personal" projects on a profile. Any tips on making a profile stand out for CSE internships would be greatly appreciated!

Thanks!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐