Closed roboyoshi closed 5 years ago
See #17 and #19 for the Make
Integration.
Also #29 will showcase one of the 'other' filetrees one might want to download:
plex
branch => datacurator-filetree-[plex]-v0.3.zip
scene
branch => datacurator-filetree-[scene]-v0.3.zip
Meanwhile #11 has already been completed by just using zip files within the structure to offer different "flavours".
master # <- default branch
|- wip # <- "develop" branch
|- user/ # <- User variants
|- roboyoshi # <- personal filetree of mine
|- other/ # <- "feature" branches that focus on specific area/app/etc
|- plex # <- plex-centric
|- kodi # <- kodi-centric
|- scene # <- according to scene rules
chroot
| alt
| other
| section
| feature
| ....?Updated Strategy:
master
branch, which is the release targetchroot/x
branches, which may also receive a release
Makefile
user/x
branches, which are just for ideas/preservation/etc
In order to allow for dynamic builds, I want to update the branching strategy.
Some sections are not going to be the "one way to rule them all" kind of type. Literature can be classified with a few different specifications (e.g. LCC vs UDC) Same for media, some people prefer a more slim approach (e.g. Plex Folder Structure) compared to more complex (e.g. the currently provided).
Overall I want to give users the option to combine some branches and then create a filetree out of it.
IMPORTANT: The "master" branch should still focus on providing 1 unified filetree that most users can agree on. Only reasonable dynamics shall be allowed in the scope of this ticket.
More to be discussed.