On 28-09-15 04:27, Ben Coman wrote:
Git is very flexible which implies complexity for newcomers to it.
What is required on top of git is a "well defined" workflow. I see
sometimes on this mail-list that people design their tools for
flexibility since they don't want to *impose* a workflow on people,
which is a commendable philosophy, but slows adoption by newcomers.
It may be useful to define "this is *the* way its done here" , with
the standard proviso that there may be missteps that need to be tuned.
There is no such thing as one workflow. That is to say, the one workflow
is simply very complicated, as different people need to solve different
problems with design data management. The problems of the core pharo
team are not those of the community.
To do this well it would be good to work with personas, like in
http://gsoc2013.esug.org/projects/distributed-issue-tracker
Adoption will come only when a sufficiently large, consistent and
complete part of the stakeholders needs is covered. Personas are also
very useful to drive the documentation.
Stephan
