[Bigbang-dev] BigBang 1.0 Architecture

[Sebastian Benthall]

Hello,

Last week was very productive.
One thing that came out of it, as well as earlier engagement around
refactoring the older BigBang code, is some greater clarity around BigBang
use cases and how people are using what's there.

One thing that's clear is that there are some inconsistencies in how the
repository is being used as it supports more-or-less independent research
efforts.
 - The architecture of the newer ListServ code is basically separate from
the earlier codebase, with a lot of parallel features (data collection,
analysis, visualization)
 - Data from different projects is distributed across different examples
directories, though what's needed by use cases is a rational strategy
around pulling and combining this data

Figuring out how to use the repository coherently is also conceptually
related to the next big item in the documentation, which is laying out
contributor guidelines.

The nature of this beast is that it's hard to settle through just one
person's efforts. It requires consensus.

I'd like to confirm that our next meeting is scheduled for Dec. 17, 9am
EST, and that others can make it for this time. We don't have a lot of time
left to use the Prototype Fund resources and it seems like we've only just
now identified the real pain points in terms of software design (or lack of
it). I'm wondering how to best join forces moving forward.

Best regards,
Seb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20211206/b1e3d809/attachment.htm>