GitGoals DevLog #1 : Comments
This is the first article in a series of articles in which I will document my journey building GitGoals.
A bit about GitGoals
Open Source Software thrives on a healthy community. A healthy community helps project maintainers by giving
- feedback
- monetary support via Patreon or Github Sponsor
- by solving issues and implementing feature requests
GitGoals will provide a channel for the developers and maintainers to interact efficiently with their community via posting project updates, setting goals for the next update and making them public for the community to see and critique.
GitGoals is exclusively for Open Source Software. It’s a place to build and grow a community for your OSS.
Progress so far
GitGoals is certainly months away from a MVP. So far the following things have been achieved.
- Federated Login via Firebase (currently only support Github Login, Gitlab is certainly on the roadmap)
- Creating Project against your public repos.
- Posting updates on your project page.
Work done last week
Last week, added comments to posts. So now a logged in user can post comments on a project update.
Some screenshots
Challenges faced
Identifying a resource owner
Identifying who owns a post or a comment was something that I had never done before. So for me it was a challenge. I went through a couple of sites which deal with the same problem and looked at their code. Got a fair idea and implemented a similar solution.
Identification was important because only the owner can update or delete his/her post or comment.
What’s next
The next thing that I will be working on Tags. Tags are great for searching related projects.
That’s it folks.
See you next week and if you are interested in trying out GitGoals early, you can reach out to me on Twitter where i tweet about my projects and also some useful resources.
Have a great week!