Improving Code Ownership: GitHub Account Types for Developers and Non-Developers

[centraldave]

Select Topic Area

Product Feedback

Body

As GitHub becomes increasingly essential for both developers and businesses, facilitating code exchanges between entities, the platform has to continue evolving for everyone - not just devs. The amount of information displayed is still primarily for developers in th current context where more and more individuals and businesses wish to fully own their code while contracting development services - and on their own, not asking access but giving them. It becomes a necessity to include them in a new account type.

The Issue

In today's context, it makes less and less sense for developers to retain ownership of the code they develop for clients. Instead, individuals or businesses commissioning the development must maintain ownership of their repositories, including their history, from start to finish. So non-technical people must create their own account to give access to devs, right?

However, GitHub's current interface and account setup are heavily developer-centric, which creates barriers for non-technical individuals or businesses. These users often lack the technical knowledge required to confidently manage repositories, assign access, or navigate GitHub's developer-focused terminology and features. We must display fewer stuff for them!

Proposed Solution

Introduce two distinct account types on GitHub:

1. Developer Account:

   • Full access to GitHub's traditional features.
   • Advanced interface tailored for technical users.
   • Designed for those writing and managing code.

2. Non-Developer Account (Businesses/Individuals):

   • Simplified interface with minimal technical jargon.
   • Easy tools to manage repository ownership and access.
   • Focused on ensuring code ownership, with features to:
     • Temporarily grant developers access to repositories.
     • Add or remove collaborators with a few clicks.
     • Ensure all repository history remains under the owner's account.

Why This Matters?

This feature would completely reassure non-technical people on ownership and will:

• 👥Make them confidently use GitHub without extensive development knowledge (more people!)
• 💰Boost the developers market by giving more people the confidence to hire developers (you're the boss)
• 🤝Make a better collaboration between non-technical clients and developers (less confusion)
• 🙌Make a more inclusive platform that serves not just developers but also their clients (everybody's happy)

Call to Action

GitHub can support the growth of the development industry and make it more accessible to non-technical users. I even believe this shift aligns with GitHub's mission of being the platform for everyone to build software. So let's discuss it and maybe make it happen!

🆙Now, would you support this feature?🆙

[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. ⭐