Organization Personas
Jon Stahl has some Initial Thoughts on a “Plone For Nonprofits” bundle.
The first comment beneath the blog post was to do with Linguaplone a plugin or 'product' for Plone which allows a site to be translated into many languages.
While there are probably plenty of reasons for and against including this (or any other products), it occurred to me that maybe we should define a typical not-for-profit organization, e.g.
Number of employees, volunteers, events, venues, in-house tech experience and so on.
We shouldn't take these numbers and average them out for all organizations because that just ends up creating a fictional 'average organization'. Instead we should pick (or create) two or three typical organizations and make these kind of decisions based on them, sort of organization personas.
I think (in this particular case) we should at least defining a persona for the person in the organization who has to install the product and deal with support and feature requests.
But in general, do you think it would be a useful thing to create these organization personas?