-
Notifications
You must be signed in to change notification settings - Fork 71
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
Inventory sub-projects, and potential version #182
Comments
One argument to start pulling the one repo to rule them all apart; we need to release artifacts for Java repos. |
|
Based on the above:
We'll need to talk this out a lot, and should not rush any of it. I'll put this on the next few tech calls. But, it would be really good to have @daniel-dgi's input, and I don't think we'll get that until around July. |
Version schema; everything non-Drupal is semantic. |
@whikloj makes a good point. I completely forgot the sprint-002 branch, which means I forgot the microservices. |
I'll write up a proposal of how to proceed, as per today's CLAW call discussion. |
Organize Thyself;A CLAW GitHub Restructuring ProposalIslandora-CLAW/CLAW Remains as the canonical repository for the project. This includes ticketing (issues, milestones), wiki, and documentation. This repository would largely consist of git submodules. Core releases for the project would be done here. Each sub-project can have its own release, and we will follow semantic versioning where possible. Documentation would be in the main CLAW repo
Structure would include all related sub-projects that would be apart of a release. Sub-projects
Ok! @Islandora-CLAW/7-x-2-x-committers + @nigelgbanks, @manez, @edf, @br2490, @dltj, I'd love your feedback on this. Tear it apart if need be 😄 editing as needed with feedback |
dromedary instead of chameau? Might this be a good time to deprecate the CLAW part of the name, at least for repositories? Was there an intentional decision to move away from Confluence for user documentation? |
No. Islandora CLAW is the name the project, as agreed to by the Roadmap Committee.
Yes. We control the namespace, look and feel, and the documentation lives with the code. |
Also throwing some tags here for @MarcusBarnes and @mark-cooper as sometimes CLAWdians. CLAWdiators? CLAWnadians? |
CLAWnadians |
Seems fine to me, a repo per artifact. My only thought is when extracting into separate repos, avoid reusing existing project names like islandora-claw/drupal, as if someone wants to fork it, and they already got a fork of drupal/drupal, then it gets odd names like drupal-1 in the users account, so something like islandora-claw/claw-drupal would work better. |
Also doc's probably doesn't need to be a sub project, could still live on where it currently does (it'll be simpler to update that way). |
@nigelgbanks good stuff. I'll ammend the proposal to put docs back into the main repo. That does seem like the best place for it. |
Suggestions on what we should call the "Drupal" repo? "claw-drupal" make sense? Or something else since the intention would be this is what goes on Drupal.org. |
Will that repo contain all the various Drupal modules? Because I think Drupal.org only cares about the actual module names, no? |
Yeah. My proposal is to only have one Drupal module, and that module would have all the sub-modules. Kinda like Islandora Scholar. Then, we would only have on module on Drupal.org. |
Will research on this for Drupal 8.
|
I have a name(s) for the php microservices; crawfish, crawdads, freshwater lobsters, or mudbugs. Little lobsters! |
My options: crawfish (which sounds like crowd...and i like it!) + mudbugs also! |
'crayfish' would be the Canadian version. It's also the colloquial name for the little shrimp-looking critters that crowd around to see if you're dead if you swim at the beaches around here, so I'm fond of it 😄 |
@DiegoPino @whikloj: Here is a proof-of-concept for moving everything out, and keeping the history of just those files: https://github.com/ruebot/crayfish. |
Crayfish looks already good! Thanks @ruebot. I would just add composer as dependency and make sure people type "composer install" or "composer update" on the clone's root before trying to run the services. |
👍 to crayfish |
Crawfish is done. I'll create a pull request for yank services from the CLAW repo here shortly, and get Crayfish setup on Packagist. |
Alpaca is done: https://github.com/Islandora-CLAW/Alpaca |
Islandora is done: https://github.com/Islandora-CLAW/islandora |
@whikloj @DiegoPino @daniel-dgi : https://github.com/Islandora-CLAW/Alpaca/tree/master/commands We should talk about that. That should get moved out of Alpaca. |
nvm, I think we have to leave it in there: https://github.com/Islandora-CLAW/Alpaca/search?utf8=%E2%9C%93&q=islandora.php |
Partially resolved with 2c602c1 |
Partially resolved with f3637fb |
Partially resolved with 008196a |
1 similar comment
Partially resolved with 008196a |
Partially resolved with 3cc9c02 |
Resolved with 92a4775 |
Our ONE REPO TO RULE THEM ALL is getting large, and we need to start thinking about breaking things out.
The text was updated successfully, but these errors were encountered: