-
Notifications
You must be signed in to change notification settings - Fork 16
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
Move artwork to a dedicated repository #35
Comments
Also select files from: |
@ranolfi can you clarify please - are we (re)moving from the stated directories or just copying so they exist in both places? |
@mattjbrent - from my POV doing an actual copy is good enough for now, just for the sake of having one "true source of truth" so to speak in terms of creative/brand assets, while still kickstarting this issue. In the long term, I would recommend the git submodules approach (from annotated tags, ideally marked as releases btw) which can be "shallowly-cloned" or/and "sparse-checked out" to address concerns about history size (to be expected given a repo composed largely of binary content) and number of unrelated assets across parts of other projects, respectively. This would be the "more complicated setup" I mentioned in the issue description. You can consult with other project members, particularly @kieranirving and JustinM (frontend group leader and devops leader, respectively) - but certainly with others too, to make a decision. |
This is so right, thanks. |
No further question? -> can remove label status: information needed Not a good first issue because requires creating a new repository, to be linked as submodule. Else (the repository exists) consider adding explaining which one is (could be https://github.com/codidact/artwork? but is empty yet). |
Brought up a few times on Discord, met with no disagreement - artwork should be moved*
from: https://github.com/codidact/landing-page/tree/master/dist/assets/img and https://github.com/codidact/landing-page/tree/master/src/img
to: https://github.com/codidact/artwork
(*) For the sake of simplicity, I see no problem in maintaining an actual copy here instead of performing a strict "move" which would require a more complicated setup at this moment.
The text was updated successfully, but these errors were encountered: