search

Financial-Times / tako

🐙 A GitHub App that provides an API listing the repositories it is installed on.
MIT License
4 stars 0 forks source link

Using Biz Ops as a data source #27

Closed adambraimbridge closed 5 years ago

adambraimbridge commented 5 years ago

  1. We can define ownership of next repositories as the list of repos that next-tako manages

  2. We could also define ownership of next repositories as the list of next repositories from Biz Ops

~We should explain why 1 is better than 2.~

adambraimbridge commented 5 years ago

Related: https://github.com/Financial-Times/next/issues/193#issuecomment-427427561

adambraimbridge commented 5 years ago

Biz-ops is meant to be mostly un-opinionated about the data it stores.

On the other hand, Tako (next-takocat) is meant to be opinionated about how it knows which repositories are Next, how they're grouped (into, e.g, apps / components / other), and so on.

It's unreasonable to code all of that business logic into the biz-ops system.

It's possible that in future next-takocat can push information to biz-ops whenever its repositories change.

lucas42 commented 5 years ago

Who says that biz-ops is meant to be un-opinionated? The data layer is flexible so you should be able to shove as many opinions into it as you want. We don't want to put next-specific business logic into the biz-ops view layer, but there's nothing stopping you from using its data layer as your canonical data source and annotating it with your own custom details.

sjparkinson commented 5 years ago

We don't want to put next-specific business logic into the biz-ops view layer, but there's nothing stopping you from using its data layer as your canonical data source and annotating it with your own custom details.

Okie dokie, the question then is how do we do that? Specific requirement would be to surface the topics of a repository via the API.

I think our rough plan is going to be to continue with this, because then we can agree on a shared schema for our tools, but where this gets its data from can/should change in future.

/cc @lucas42 @wheresrhys

lucas42 commented 5 years ago

Here's a rough stab at getting topics: https://github.com/Financial-Times/github-importer/pull/10

sjparkinson commented 5 years ago

We had a IRL meeting about this, see https://financialtimes.slack.com/archives/CD689QU2K/p1541499781012800.