Hackathon: Namespaces & Organizations

[gabor-boros]

Hey everyone! 👋

Since several people have been helping Elemo recently, I would love to organize a hackathon focusing on the “Namespaces” and “Organizations” related functionalities. This would be a great opportunity for those who already contributed and new contributors as well to collaborate and shape the future of the project and a great community.

🗓️ Timeline

September 8–14: Kickoff, ideas, and team formation

• Ideation
• Find teammates or work solo.
• Align on what you'd like to build.

September 15–28: Implementation sprint

• Build, test, and document your contributions.
• Open PRs and show progress.

September 29-30: Summarizing results

• Summarizing results
• Sharing results publicly

🎯 Hackathon Focus

Namespaces and organizations are the next big step for Elemo. Some ideas to be explored:

• Namespace creation and management. (Implement namespaces #130)
• Organization creation and management. (Implement organizations #318)
• Invitations to organizations. (Invite users into organizations #150)
• Anything else that makes namespaces and orgs more powerful in Elemo

(These are suggestions; feel free to bring your own spin on what namespace + org features could look like!)

🤝 How to Participate

1. Comment below with your interest, idea(s), or if you’re looking for teammates.
2. Join forces with others, or go solo.
3. Start hacking once kickoff begins on September 8.

🏆 Outcomes

• Pull requests merged into Elemo 🎉
• Shared learning and collaboration
• The foundation of Elemo's namespace & organization features
• Public summary of the results

🤖 Notes on AI

Yes, you may use AI assistance. However, please be mindful about it and keep the following:

• Do not commit AI slop.
• Always review the code generated by AI.
• Try to use AI for assisting you, not to generate a full blown things; that rarely ends with good results.

---

All participants who contributes to the hackathon in the categories below will receive a public recognition and credit:

• Creating (accepted) GitHub issues for bug reports, new features, or helps with triaging new issues.
• Creating (merged) Pull Requests for bug fixes, new features, or tasks.
• Creates, fixes or reviews documentation.
• Helps the community several times with answering questions on Discord, Slack or GitHub Issues/Discussions.

If you would like to collaborate with someone who is not part of the community yet, encourage them to join and make some great contributions together!

[gabor-boros]

Hey @zyfy29, @tecoholic, @shujamukhtar-ops, @Sachinbhanu7, and @fajremvp you may be interested in this 😊

[fajremvp]

Thanks for tagging me! I’d be glad to join the hackathon. I’ll do my best to contribute, whether through testing, documentation, or smaller code contributions.

[Sachinbhanu7]

Excited for the hackathon..Thanks for tagging 🙌

[shravankumar8]

Excited

[zyfy29]

That's great, I'm willing to join.

[tecoholic]

Cool. I am game :)

[gabor-boros]

Thanks everyone for showing interest! If we have 2-3 more people, we may want to include something else into the scope to have enough things to work on 😅 😄

[utawasthi]

I would also love to join it ....!!!

[fajremvp]

Welcome!

[gabor-boros]

Awesome! 🎉 Looks like we’ve got everyone excited to join the Hackathon! Let’s figure out who prefers working solo vs. in a team, and what areas they’d like to focus on, so we don’t overlap too much.

Organizations and Namespaces are separate features, but related. I’ll be helping out with both tracks wherever needed. To get things rolling, I’ll start with issue #293.

Quick question for everyone: who’s interested in working on frontend, backend, or both?

PS: I'm going to provide design as we go on or we can do best effort.

[tecoholic]

I am planning to work on both. However, with no go experience, I will be limited on the backend side.