Author Topic: Missing status "bespoke" (Read 889 times)

xavier · August 21, 2012, 04:30:48 pm

Hi,

(follow up on a discussion on a mailing list)

I think there is a need to be able to share extensions that might be stable (as in "it's in production already") but that aren't generic enough to be used by another site out of the box. things like id being hardcoded, logo of the org, messages that are specific...

ie. things that would need another use case or two to be made generic.

Got a few, that are probably 90% useful for one of you and I'm happy to share, provided that you do the missing 10% (and for the ones that are agpl3, to contribute back)

Not sure it's a status, but don't want to suggest adding a field just for that either. Or might be the solution is to use tags?

X+

kasiawaka · August 23, 2012, 07:12:48 pm

Good idea, I understand why this would be useful. Added to our discussion list and we will come up with a solution that will satisfy the "Status" field requirements but at the same time, provide information that more work may be required to use the extension. I will post here an update here on progress of implementing the solution.
Kasia

CiviCRM Community Forums (archive)

News:

Author Topic: Missing status "bespoke" (Read 889 times)

xavier

Missing status "bespoke"

kasiawaka

Re: Missing status "bespoke"