Open elray1 opened 9 months ago
No super strong feelings on my part about either of these things. I think doing option 2 feels a bit more convoluted, but also, as long as it's well documented, perhaps the best option.
Both sound like good solutions to me.
Can you say more about who the users are for this?
After in-person discussion, Becky votes for keeping stuff in the same repo, maybe in one high level folder called _internal_data
, with documentation in readme that this is not intended to be part of the hub structure.
After chatting with @elray1, here's my understanding of the "audience" question below:
The sample data repo has two audiences:
[this doesn't really answer Evan's original question, just surfacing the convo in case anyone else out there is trying to solidify their understanding of the problem space]
Can you say more about who the users are for this?
1. Internal Hubverse developers who want to publish sample data and make it available for packaging in other hubverse libraries? 2. People standing up their own hubs want want to produce their own sample data? 3. Both?
I am realizing that the original data and code for this is currently just sitting on my laptop, which is bad.
I see two options here:
data-raw
, that contains the original data files and processing code.data-raw
folder. This could be confusing.example-simple-forecast-hub-source
(open to other naming ideas), that contains this code. maybe there's an expectation that the two repos would be cloned into the same folder on the developer's computer so that relative paths can be used inexample-simple-forecast-hub-source
to put the data files in the right place inexample-simple-forecast-hub
I'm leaning toward option 2 but soliciting input.