search

gctools-outilsgc / gcconnex

A social network based on Elgg
Other
49 stars 44 forks source link

Split GC mods in seperate Repos - Add to Packagist #1150

Open smellems opened 7 years ago

smellems commented 7 years ago

Code for custom mods should be removed from the mod folder and moved to their own Repos, with a composer.json file, under gctools-outilsgc.

Some work was done during the hackathon gctools-outilsgc/gcconnex#426 - they might have a script that can extract the mods with the Git history.

We should have releases using tags on Github and use semantic versioning to be compatible with Composer.

Submit mods to Packagist under gctools-outilsgc and add Packagist integration hook to the GitHub Repo.

markwooff commented 7 years ago

I was able to pull out a GCcollab module into it's own repository for submitting to Packagist using the instructions here: https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/. This will persist the Git history.

ToferC commented 7 years ago

@Phanoix @markwooff @smellems @Troy-Lawson - please confirm status and how you want this issue to work. Do we keep a single issue or just use this as part of our milestone? Thanks!

Phanoix commented 7 years ago

I think we decided not to just split up a bunch of in some cases highly interconnected mods into separate categories, during the upgrade work it might become clearer what we can do with the mods that we do need to keep maintaining ourselves. Doing this right now would just make things less convenient/harder on everyone and provide little to no benefit, especially considering our current production environment.

smellems commented 7 years ago

For the current 1.12, we wont spliting them up. But going forward (upgrade to 2.3) I think we should create seperate repos for each of our mods so they can be installed using Composer and of course use upstream versions of 3rd party mods.

smellems commented 7 years ago

We should start with the Wet4 mod