[wp-hackers] support for custoim post types + custom feilds
Edward de Leau
e at leau.net
Wed Jun 30 23:30:30 UTC 2010
I think the discussion on additional software like plugins to be installed
on enterprise servers is not a WordPress specific problem.
In general whether it's Oracle software, Microsoft software, IBM software,
whatever brand there is always the friction between the development project
and the group that has to put it under maintenance. Two total different
In general I think it depends on the list of requirements you agree upon
with the business in the first place. Because if a business partner really
wants a specific requirement that can only be fulfilled with a plugin then
this will in general overrule maintenance and security teams. If this really
conflicts with a non functional requirement such as security then it can
become an issue and has to be escalated to the business partner to make a
decision on it so the business should make the decision not the maintenance
team. Once the business says "I want it", the tek teams can jump as high as
they want but it needs to go in.
If there are no signed requirements for a specific piece of additional
software up front then of course the maintenance department will say no. So
don't sell "WordPress" but sell a solution with a list of matching business
requirements instead (imho).
In general I think Enterprises will include an architectural review before
signing. So this means that your architects and the architects from the
company sit together and make some architectural overviews, some high level
use cases and maybe already some high level non functional requirements. So
maybe even before signing these non functional requirements versus a plugin
discussion can already come up. And I think (indeed) that
the trustworthiness of an additional specific supplier plays then a large
part in the outcome. In general the "functional architecture" is based on
use cases and is understandable by the client. The "non functional
architecture" goes to the infra architect / security / etc... to make some
detailed models based on that.
I think the deployment, configuration management and maintenance of the
plugins is only in a later phase when the project has already started
because that would come of more detailed designs from the project on the one
hand and the operational detailed model on the other hand. I think that is
more "technical" and like "they will find a solution for problems".
So to prevent discussions "in the technical implementation" it is best to
cover your ass to make the list of requirements as long and as specific as
possible during the first phase and have them signed off. Then there will be
no discussions later. If there are problems to be expected then these will
only affect your time planning.
And make different waves of implementation. The first on requirements only
for WordPress and then a second wave under a second contract for specific
plugins that makes it also easier to "glide in" these extra business
Then again nothing new compared to any other software project.
Edward de Leau
More information about the wp-hackers