New repository proposal: sdg - #63

@russellb Can we add a bit about creating a new SDG Triager/Maintainer team, in line with the scheme we have for the CLI teams? These team will be responsible for triaging, maintenance, releases, etc.

Alternatively this can be a proposal to the community repo CONTRIBUTORING_ROLES.md doc once the new repo is created.

I wonder if anyone can come up with a less cryptic name than SDG, but I don't have a good suggestion (data-gen or synth-data... etc don't thrill me)

Dumb question - why don't we just call it synthetic-data-generation? It does what it says on the tin.

Honestly I'm not opposed to @lhawthorn's suggestion or something like synthetic-datagen

I would prefer a rough mapping to the Python package included in the repo. This proposal was instructlab/sdg for the instructlab-sdg package. For the other name suggestions, a PyPI check to see if it can also be the Python package name would be good. It would also be helpful to know if the name suggestions are brainstorming or a “-1” for the proposed name.

Naming is hard.

Nice proposal, thanks @russellb.

One thing should we also include the basic implementation (which is a modified version of self-instruct (https://arxiv.org/abs/2212.10560)) currently in the CLI to be moved to the repository also? That way we extract all SDG implementation from the CLI and we have the community supported implementations in 1 repository.

Yes, I envisioned that we would move the current implementation in instructlab/instructlab repo over there. It's probably the fastest way to bootstrap the new repo, actually. Then we can enhance it from there.

We should also note that the sdg code is also a consumer of the schema since it much be able to understand taxonomy qna.yaml files.

I wonder if it time to have the schema repo publish instructlab-schema to PyPI so that ilab, sdg, taxonomy can all have a python dependency on the schema rather than more repos submoduling the schema repo. Using submodules was useful before we started publishing to PyPI, but perhaps now is is time to change from submodules.

We should also note that the sdg code is also a consumer of the schema since it much be able to understand taxonomy qna.yaml files.

I wonder if it time to have the schema repo publish instructlab-schema to PyPI so that ilab, sdg, taxonomy can all have a python dependency on the schema rather than more repos submoduling the schema repo. Using submodules was useful before we started publishing to PyPI, but perhaps now is is time to change from submodules.

big +1 to moving away from git submodules for the schema - a package on pypi makes sense to me

We should also note that the sdg code is also a consumer of the schema since it much be able to understand taxonomy qna.yaml files.
I wonder if it time to have the schema repo publish instructlab-schema to PyPI so that ilab, sdg, taxonomy can all have a python dependency on the schema rather than more repos submoduling the schema repo. Using submodules was useful before we started publishing to PyPI, but perhaps now is is time to change from submodules.

big +1 to moving away from git submodules for the schema - a package on pypi makes sense to me

+1 to this as well

big +1 to moving away from git submodules for the schema - a package on pypi makes sense to me

+1 to this as well

OK, I'll start some work towards this end.

https://github.com/instructlab/sdg