Config migration: typed config, VisualizationConfig, and bootstrap command

[aboydnw]

Summary

Keeps all config in a single config.toml (repositories + contributors inline) while adding typed data models.

• Adds ContributorType enum, ContributorEntry model, VisualizationConfig for typed config access
• Adds core_contributors / community_contributors properties (first group = core, rest = community)
• Adds contributor-network bootstrap <infile> command to generate config.toml from a repos file or contributors CSV
• Adds GITHUB_TOKEN to CI build step
• Updates README with "Creating your own contributor network" section

Value

Enables typed config access and the bootstrap workflow without breaking the existing single-file config format.

[aboydnw]

@gadomski this splits out the config.toml file into two files, one for contributors and one for repositories. I think this will help set up #59 #60 and #61 by making the lists more clearly separated.

[gadomski]

Is this idea here that forks will want to use the same contributor list, but change the repositories?

I don't get why we couldn't do that from the same config.toml?

[aboydnw]

Hm good point @gadomski

The next feature is intended to make it so that a person can either bring a list of repositories as the starting point OR a list of contributors. So maybe I just made this change to make it make more sense to me, but I am not sure it's actually needed. If you think it's safer to keep as config.toml then I'm down to keep it.

[gadomski]

The next feature is intended to make it so that a person can either bring a list of repositories as the starting point OR a list of contributors. So maybe I just made this change to make it make more sense to me, but I am not sure it's actually needed. If you think it's safer to keep as config.toml then I'm down to keep it.

Yeah, let's keep it as a single config.toml. For the "i want to bring a list of contributors and build the respoitories" or vice-versa, let's add a contributor-network bootstrap <infile> command that builds a config.toml from a file's contents.

[aboydnw]

@gadomski okay good call. I think this is ready for review again. And it's a nice addition to this workflow for somebody to standup a new visual.

[gadomski]

I tried "bootstrap" locally w/ a list of repos, and my subsequent discover command errored with:

$ contributor-network discover
Discovering repos for 0 core contributors...
Known repos: 4

============================================================
DISCOVERED REPOSITORIES (min 2 core contributors)
============================================================

No repos found with 2+ core contributors.
Try lowering --min-contributors or check GitHub token permissions.

I think that's because the discover command won't work w/o contributors:

contributor-network/python/contributor_network/cli.py

Line 226 in 4d09508

for username, name in contributors.items():

For the flow suggested by this PR to work, we'll need to refactor the discover command to work with an empty contributors list and a empty repo list.