Merging processes and assemblies into a single space type
Processes and assemblies were (and still are presented as) spaces with different goals :
Processes are designed to be structured in phases, supporting rythmed participatory processes that have definite start and end dates.
Assemblies are conceived to support perennial working groups. Topics, mandates and members may change, but the group infrastructure remains.
Over the years, processes and assemblies have become more similar, one incorporating (mostly from processes to assemblies). I am aware other minor differences exist, but structurally wise, the most salient differences between both are:
Processes cannot be associated in a hierarchical way (one cannot create sub-processes, like sub-assemblies).
Assemblies cannot be structured in phases.
It has often been difficult to me to justify the separate existence of these two space types beyond these two differences. The divide may have been justified in the past, but does not make that much sense to me anymore: the differences between processes and assemblies have gone from being assets I could benefit from choosing one or the other, to becoming limitations forcing me to choose one or the other.
I therefore suggest that we start reflecting on how both space types could be merged into a single one integrating both's advantages.
I am afraid that space types being part of the very core architecture of Decidim, having both been built and evolved separately since inception may make this move a very complex one. But it is this essential nature of the issue what pushes me to find value in the possibility of simplifying this unnecessary complexity stemming from the past.
Share