avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen McConnell" <mcconn...@apache.org>
Subject RE: [VOTE] Stephen McConnell as a committer
Date Sun, 26 Sep 2004 07:13:15 GMT


> -----Original Message-----
> From: Niclas Hedhman [mailto:niclas@hedhman.org]
> Sent: 26 September 2004 04:49
> To: Avalon Developers List
> Subject: Re: [VOTE] Stephen McConnell as a committer
> 
> On Sunday 26 September 2004 07:24, David Leangen wrote:
> 
> > The main reason that I am so impressed with this project--and have
> > committed myself to it now by refactoring my entire project to use
the
> > current version of Avalon--is mostly thanks to the incredible
support
> > given by Steve. Quite frankly, I have never seen that type of 
> > committment to any open source project. What has impressed me most 
> > about Steve is that he is really concerned with the project's users.
> <snip/>
> > However, it appears to me that Steve is setting an important trend, 
> > one that at least for me inspires even greater confidence in the
ASF. 
> > Isn't this the type of image that that ASF _should_ be projecting?
> 
> Unfortunately, we have been told by the overlords of ASF that users
> doesn't matter much. 

I would disagree.  Instead I would say that there is a different
perception.

> That can also be seen on many projects where the users@mailing list 
> often (there are many exceptions) is left to the users to fend for 
> themselves.
>
> In my, and most definately Steve's, opinion that is truly sad, but ASF
at
> large only look at "community", which means the contributors ability
to
> co-operate, get along, and each pull small straws to a big stack.

This is closer to the mark.  The definition of community - is it the set
of developers granted commit privs on a project?  Is the set of people
who are subscribed to a list? Or is it the users of products produced by
a project?  

I would argue that a community is made up through a cycle of value.  I
think that a cycle of value limited to developers 'scratching an itch'
is too restrictive.  

Instead the interesting things start happening when you introduce users
into that cycle.  In particular you start to see much more discussion
around competence development by the end-user.  This leads to closer
involvement in the development of functional requirements, input into
product positioning and promotion, and interestingly, professional
network development linking users-with-other-users and
users-with-developers.

Cheers, Steve.




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message