-
Notifications
You must be signed in to change notification settings - Fork 8
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
Clarify support terms for this & related extensions #2
Comments
I think it's awesome Compucorp are introducing new contributors to the ecosystem! I propose that if Compucorp ask people to write an extension as a code exercise (which I think this is?), you add a requirement that they mention the scope and purpose of work shared until it is ready for prime time. This can help to combat "noise" / confusion in the contribution space. Thanks! |
Will do Chris, thanks for flagging this (but also note that any extensions on our github are work that we are producing)! This is an extension to provide the following functionality: https://civicrm.atlassian.net/wiki/spaces/PPI/pages/2260996/2.+Payment+Plan+Instalments Best Jamie |
Ah cool, I mistook it for one of the others and thought this would be the most central place to discuss. |
I see there are several extensions on Github of this type which seem related:
For CiviCRM sites looking for an extension and finding these on Github, it would be good to clarify whether these are supported extensions, learning/research projects, or something else.
Ensuring that each of these extensions contains a notice in the README and
info.xml
description to clarify the nature of the extension to sites might prevent sites installing something that doesn't work or is unsupported.The text was updated successfully, but these errors were encountered: