[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openocd-development
Subject:    Re: [OpenOCD-devel] OT: Group dynamics
From:       Peter Stuge <peter () stuge ! se>
Date:       2015-07-24 10:05:26
Message-ID: 20150724100526.18321.qmail () stuge ! se
[Download RAW message or body]

Peter Stuge wrote:
> the responsibility and yes burden for contribution really lies with
> the contributor.

It's essentially the same human behavior as in other (offline) groups.

A person entering into an unknown group consciously or unconsciously
demonstrates their compatibility with the group by how they act.

If their actions align with the group then they just "blend in" with
the group - it may even seem to everyone as if the new person was a
part of the group since forever.

But if the new person's actions don't align so well with the group
then the group typically makes this known in some way or other, more
or less subtle. The new person then has to decide whether they want
to adapt in order to join the group, or whether they prefer not to
adapt and to be pushed out of the group.

There really are persons and groups where everything automatically
fits, but when not, either the person or the group has to change,
and we humans are pack creatures, so the group usually wins.


There are classic examples of how peer pressure makes people do bad
things (start smoking to hang with the cool kids in school? :) but
IMO open source projects is an excellent example of how peer pressure
can lead to *good* habits.

The review-centric workflow supported by Gerrit and used with or
without Gerrit in countless projects results in significantly better
software. I recommend reading this:
https://www.ibm.com/developerworks/rational/library/11-proven-practices-for-peer-review/

The flip side of that coin is that contributions can't be expected to
be included immediately, or even what contributors feel is timely.

As both a user and a developer I very much prefer the software
improving over the project including all contributions. This will
take time.

If what one actually wants is student code without review then go for
it - full steam ahead - but don't confuse that development style with
a review-centric workflow as used in most open source projects with
more contributors.


//Peter

------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
[prev in list] [next in list] [prev in thread] [next in thread]