-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleaning up the repo of old things #241
Comments
I added the label "old" to everything before 2023 - a temporary label. We should still try and action and close issues from 2023 at the same time, though. |
There is an "Archived" folder which we can move them into: https://github.com/omigroup/gltf-extensions/tree/main/extensions/2.0/Archived |
Sorry, reading back I think this comes across as a little rude, but I have well meaning intentions. I do hope that people come back and finish projects - but if not, then its fair to let others use the workspace now.
cool! well, that would be the place for unfinished projects. Probably safer to preserve it in the same repo too |
I didn't perceive it as rude. We can always un-archive later if somebody shows up with a desire to work on them more. I'd be happy if somebody did that, but in the meantime, I'd prefer to keep the main folder focused on our maintained higher quality extensions that include example files, schemas, implementations, etc. |
Hello,
Lately I am trying to help @aaronfranke tend to this nice garden of gltf extensions, but I see a lot of old stuff around, and I would like to help clean up as they are in the same pile as the current work, so it feels like we should address them and do some sort of spring cleaning.
Instead of just yeeting everything, I would like to meticulously go through the items one by one:
OMI_personality and OMI_link, with the latter possibly being useful one day. I'm not sure if they are going to get any more work, or usage, and seems to be unfinished/abandonded. We can just move them to a
gltf-extensions-archive
or something?all the old issues that have no resolve. lets start a new leaf? some of them can be kept but most of them seem to be from a couple years ago.
any other "old" files, PRs, and content.
The text was updated successfully, but these errors were encountered: