Role of DPML
mcconnell at dpml.net
Tue Nov 2 06:01:21 EST 2004
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org [mailto:dev-dpml-
> bounces at lists.ibiblio.org] On Behalf Of David Leangen
> Sent: 02 November 2004 10:51
> To: Dev
> Subject: RE: Role of DPML
> I agree with much of what you're saying, but there are points that I
> strongly disagree with.
> > 1. Technology - COP and the J2EE alternative.
> > 2. Community - Open Participation Software.
> > 3. Business - Commercial solutions built-in.
> Good point.
> > Since you are bringing up 3., I would like to elaborate my view
> > on that, but I think this has been up many times.
> I think you're mixing up "marketing" with "business". "Marketing" and
> communications according to my definition are necessary for any
> community projects, commercial projects, universities, governments. It
> the process of getting the target audience to understand quickly what
> trying to accomplish. Marketing is not business, nor a subset of
> Even if we decide to not focus on business, marketing is still
> whether we want it to be or not.
I agree that there is a mix of terminology floating around here. My own
view is that DPML 'the community' will be developing good solid
marketing material that individuals and organizations will be able to
use as part of the promotion of the value proposition that DPML
> So, let's be careful to not mix the two up, which I'm also guilty of
> in my previous posts.
> So far, I believe that DPML (or at least Steve... maybe it's only him
> personally, I'm not so sure anymore) takes the issue very seriously.
> puts great care into the website and communicating what we're trying
> to do. I think that this aspect is essential to the success of the
> My guess is that you agree. So, I am thinking that your definition of
> "marketing" is closer to "sales" or "getting the customer to take the
> bait" or something like that. Correct me if I'm wrong.
My impressing is that we are touching areas that are central to the
culture and mindset that has been present for a long time. Looking back
at the history and the achievements - the focus has been very much
skewed towards very high technical integrity, a high degree of affinity
with real operation requirements, and a conviction that there is a real
and sustainable commercial model that can be established around this.
IMO that commercial model is much more related to the 'network' of
contributors, sponsors, users, and other actors yet to emerge. It's
from this perspective that I believe that the key role of DPML will be
in the enabling of a 'network effect' in respect to the way our products
add value, the way this value is communicated, and the way in which this
feeds back to the community.
> If we decide to concentrate on one particular aspect, such as just
> the framework up and running first, then looking into other aspects,
> as how to package the products, that's fine. However, I've seen no
> policy or road map so far on the approach.
> Maybe we need some kind of road map or vision document or something
> takes these issues into account...
Yep - I agree.
More information about the dev-dpml