Hi everyone, an update on the silverstripe-labs vs silverstripe organisations; I've transferred the following repos from silverstripe-labs to silversripe:
Transferring modules betweens organisations re-sets the access setting, and so I needed to reapply these. For most of the modules, I looked at commit and merge activity to see who is actually looking after the module and used that to apply admin rights.
If anyone feels it would appropriate for them to have admin rights for any one of these modules, please approach one of the admins listed below (or me) and make your case :-)
silverstripe-auditor: mateusz, stojg, halkyon are admins
silverstripe-selectupload: tractorcow, chillu are admins
silverstripe-securityreport: tractorcow, chillu are admins
silverstripe-secureassets: tractorcow, halkyon, dhensby are admins
silverstripe-registry: tractorcow, chillu, halkyon are admins
silverstripe-iframe: tractorcow, chillu, dhensby are admins
silverstripe-fulltextsearch: tractorcow, chillu, halkyon, dhensby, hafriedlander are admins
silverstripe-externallinks: tractorcow, chillu, halkyon are admins
silverstripe-crontask: tractorcow, stojg are admins
silverstripe-tagfield: tractorcow, dhensby, assertchris are admins
silverstripe-dms: dhensby, tractorcow, chillu are admins
The following modules are administered by the core team:
silverstripe-frameworktest
silverstripe-reports
silverstripe-sqlite3
silverstripe-behat-extension
silverstripe-testsession
This is not a complete transfer process, but I've made a start. I was working down the list from most-recently-updated.
Once we've transferred out the modules that are still maintained, we'll rename silverstripe-labs to silverstripe-archive.