[epf-dev] EssUP status update

["DJ de Villiers" <dj@xxxxxxxxxxxxxxxx>]

All

Below an update on the status of EssUP action items since our meeting in
Cupertino.

We decided rather than once again conducting an unstructured discussion
regarding the core concepts in EssUP, we will take some time to precisely
define them and position how they could benefit EPF. I am sure there will be
some overlap, but in other cases there will be distinct advantages to
adopting the EssUP concepts (maybe after the initial BUP release?) So we
will work on an explanation and will schedule a discussion when we can more
clearly communicate intent and semantics.

To my knowledge there are no legal implications restricting our involvement
or contribution, so we will be in a position to contribute whatever the EPF
team feels will be valuable - after we have together reviewed ad discussed
the EssUp core concepts (see item 1 above). In the meantime we will
contribute where we can such as contributing ideas for tasks and artifact
names etc. As Development discpline owner, I will do an analysis of what
needs to be changed today (based on meeting minutes etc).

We also agreed it would make sense to author a paper on separation and
composition of practices. We feel this will less valuable if it only
describes intent, so we suggest authoring this paper once we have discussed
and agreed the EssUP core concepts (see item 1) as they are fundamental to
being able to describe practices separately and compose them into a coherent
process. We all agreed in Cupertino that this is the ideal situation even
though it is not possible given the current tooling limitations. We have
made substantial progress in this regard and by that time we will be able to
provide some concrete illustrations which will be more valuable.

So for now its up to us to provide a clear and compelling description of the
primary benefits EssUP to EPF. After that we can take a decision about how
to move forward.

Thanks & kind regards


DJ