Sustainability and Succession Planning

[orcmid]

A webinar announcement reminded me that projects have lifecycles as do the documents that they produce and efforts that are sustained. This needs to provide for retirement of an effort, providing some sort of soft landing, as well as turnovers of contributors and leadership.

Working in the open and especially adoption of open-source development approaches has versions of this for document engineering as much as for other "software" knowledge-worker efforts.

I presume that any extensive document engineering is a companion or component of a substantial effort of some kind. In that case, it might be too large-scale for something like this docEng view. I do wonder if attention to scaling, or systematic replication as components of a surrounding context is worthy of some consideration.

There may be patterns that support such flexibility. I wonder what they are.