GitGoals DevLog#2 : Tags
This is a second post in a series of posts which log my journey of building GitGoals. The first devlog is available here.
Before we start here’s the motivation behind 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.
- Ability to comment on those posts.
Work done last week
Last week, added tags to projects. So a project owner can tag the project which relevant tags. The tag list isn’t exhaustive, so added a “suggest tags” feature where the users can suggest tags that can be added to tag list.
This feature helps in,
- finding similar projects
- increase visibility of your project
Challenges faced
Partial search.
Tags are saved as native array values in Postgres. For searching projects with tags, partial search had to be implemented. So had to write a custom postgres function to perform search and return those projects which had the tag being searched.
What’s next
The next task on the list is to design a minimal landing page and write some UI tests.
That’s all folks.
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!