[consulting] Req for (paid) support

[Dan Robinson]

I think we're juggling a couple of things here - which is why it is a
complex question.

1) Technical vs. Consulting - I think that we need to ultimately make
this distinction - otherwise we wind up with two different lists dealing
with technical issues.
2) Culture - I like the Consulting list a lot because I feel "at home"
here.  I feel like an observer (and sometimes pest) on the Dev list.
3) Size of the community - One issue to address is that as the size of
the community grows so must the number of lists.
4) Requirements and Decision making - Consultants have a unique and
important view of the product, the community and it's users.

I would suggest we really try to put any question that has to deal with
the implementation of technology on the dev list.  Otherwise we run the
risk of splitting important participants off the conversation.  I think
that the Consulting list should deal with all of "our" issues - that are
not shared within the rest of the community.  Obviously this is not
perfect - but we could start here and see how it goes. 

Also as far as the job announcements I think it is fine to put them on
this list for now - we can always move them.

Dan


>I think we disagree on this.
>
>As a consultant, I have the task of trying to get drupal to behave for the client.
>I have clients who want drupal <-> email solutions.
>
>All efforts I have put into this so far have lead to the system not 
>doing what I want.
>
>So there are two paths. First is the path of changing how the current
>system works. This is the development path and the one you are talking about.
>
>The second path is to find the recipe to make the current tools do what we want.
>This is the path that I am talking about.
>
>If there are aspects of this that should be development discussions that is 
>fine. However, I am still looking for the consulting question -> 
>
>How do I make the current tools work in the context of my current clients?
>
>Perhaps I just don't understand the tool enough and there is actually 
>a way to make it work as I am trying.... And this is not a development question.
>
>
>The problem is that we all pick up our particular tool and use it over and over.
>The developers pick up the hammer, and everything looks like a nail. The consultants
>pick up the screwdriver and everything looks like a screw....
>
>
>
>
>
>
>=?utf-8?q?B=C3=A8r_Kessels?= <ber at webschuur.com> writes:
>
> % Well, talking about the technical details of why and how a mailinglist to=
> % =20
> % forum mirroring system should (or does not) work, is clearly not consulta=
> % nt=20
> % related, but belongs in a development ML.=20
> % 
> % B=C3=A8r
> % 
> % --=20
> % | B=C3=A8r Kessels | webschuur.com | website development |
> % | Jabber & Google Talk: ber at jabber.webschuur.com
> % | http://bler.webschuur.com | http://www.webschuur.com |
> % _______________________________________________
> % consulting mailing list
> % consulting at drupal.org
> % http://lists.drupal.org/mailman/listinfo/consulting
> % 
>
>-----
>John Sechrest          .         Helping people use
>                        .           computers and the Internet
>                          .            more effectively
>                             .                      
>                                 .       Internet: sechrest at peak.org
>                                      .   
>                                              . http://www.peak.org/~sechrest
>_______________________________________________
>consulting mailing list
>consulting at drupal.org
>http://lists.drupal.org/mailman/listinfo/consulting
>
>  
>