On Sun, May 3, 2009 at 2:50 AM, Joe Barnhart <joe.barnh...@gmail.com> wrote:

>
> Yarko --
>
> I can't say about others, but for me the key missing features in the
> wiki are:
>

..........

>
> I don't want anyone to feel like I'm telling them what to do.  I am
> just a messenger, bearing the bad news that we still do not have
> significant community involvement in solving our documentation
> dilemma.  While I am becoming more proficient at reading Python ;-), I
> believe we need more accessible documentation if we are ever to take
> on Django or PHP.
>

Joe -

I understand...
I think constructive ideas (that kind of "telling what to do, and why - that
counts the benefit of all involved"  --- this in my book is VERY GOOD, VERY
DESIREABLE! ;-).

I should clarify - I threw away a quite angry response to rev's post - this
is what I was reacting to.

He suggested a (!) J2EE wiki (gag!);

That post used words, which cumulatively I felt quite angry about - but I
threw away my response when I realized it was probably not ill-intentioned
(I looked at his posts and trouble w/ another python framework, and
re-installing python several times, and decided to just let it slide).

None-the-less, so that the group can see what I see - these are more than
social or communication issues, they are clarity of speaking and description
which directly affect design issues, so I notice them very much for those
reasons.

Phrases from that post which criticized, but added nothing:


   - ...worth to reinvent the wheel?
   - ...you realize you're a long way from a polished product.
   - Time and effort can better be spent on...
   - ...focus on a consistent stable and...
   - Don't scatter your efforts...

There was no "here's what I suggest"; ther was no "here's why I think that
would be better..."

It was just criticism, opinion, complaining....

Criticising to make a project better is great stuff.  When you care about
the project, care about others, it shows - and works.  This is what I see
from Massimo most all the time, and learn from him more than from the code -
it is a powerful lesson.

Criticising so your ego feels better - that is, so you can "explain away"
your difficulties to yourself, and think "it's them, not me..." --- is just
hot air.

I accept that the latter happens (we are human; _I_ do that sometimes;  it's
my sign to me that I don't understand something and need to ask more
questions);

I don't like when the latter grabs a position and begins to get repeated by
others.

Hope that helps clarify.

- Yarko

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to