Repository topics will be changed to reflect the respective project board/team. This includes updating examples in the github-util repository.
t-comm -> senzing-community
t-ast -> senzing-app-server
t-g2-python -> senzing-g2-python
t-gdev -> senzing-gdev
senzing-factory
senzing-garage
Include linking project boards in the repository.
Original ask
The migrated repositories in senzing-garage and senzing-factory are still using the original topics, specifically t-comm.
Should we change this to garage instead of community?
Can we get rid of the t- prefix . Clicking on any of them in the UI shows the topics filter, do we really need to be specifying it is a topic?
Do we want all of the repositories to have a topic that maps to the board they are being tracked on?
By default github shows every github repository with a matching topic (including non senzing repos). For topics that are mostly internal to us (t-comm, t-ast…) do we want to prefix them with senzing so a search on these topics should only return our repositories?
Update 2/28/24
Repository topics will be changed to reflect the respective project board/team. This includes updating examples in the
github-utilrepository.t-comm->senzing-communityt-ast->senzing-app-servert-g2-python->senzing-g2-pythont-gdev->senzing-gdevsenzing-factorysenzing-garageInclude linking project boards in the repository.
Original ask
The migrated repositories in senzing-garage and senzing-factory are still using the original topics, specifically
t-comm.garageinstead of community?t-prefix . Clicking on any of them in the UI shows the topics filter, do we really need to be specifying it is a topic?t-comm,t-ast…) do we want to prefix them withsenzingso a search on these topics should only return our repositories?