Make it easier to create a new extension project under /extensions
Currently the process to create a new Gitlab project under /extensions is to ask on the extensions mattermost channel. The procedure is documented here: https://lab.civicrm.org/extensions/extensions-directory/wikis/how-to-request-a-new-extension-project-on-gitlab (i.e. it's hard to find).
How could we make it easier?
At the Barcelona sprint, we had discussed some possibilities, such as making it go through civicrm.org (and then use the Gitlab API).
- Pros: the civicrm.org user dashboard should be a good starting point for engagement, so it makes sense to have it there
- Cons: many extensions do not have a c.o extension node, in part because there are many mandatory fields, and sometimes you just want to publish a quick WIP extension, and not bother with paperwork. (although this has been cited as a criticism: many WIP extensions with little info, provides little value)
Possible solutions:
- We could keep the current process, but have better documentation (which could be on the c.o dashboard), and have more extensions maintainers that can create new extensions.
- We could have a hybrid process, where newcomers for whom using the chat feels very clunky, does not seem like a good fit and would prefer a form to guide them, while still allowing ad-hoc creation of extensions via requests on the chat.
- We can improve the "new extension" form node, so that it's just easier to use, less friction, obsoleting requests on the chat.
@MikeyMJCO Did I miss anything? Other thoughts?