[Bigbang-dev] BigBang 1.0 Architecture

[Sebastian Benthall]

Thanks all for confirming the meeting time.

It's a good question about scope. I'm not sure.

I'll try to show up with as many concrete propasals in hand as possible,
based on what the open questions are.

I'll see what additional PRs I can do otherwise.

Of course we could settle things in the GitHub issues but there seem to me
to be some intersecting issues. We can't write good contribution guidelines
if we aren't clear ourselves on how the code should be structured.

Christoph, I believe I once saw a UML diagram that you drew up for BigBang
when you started working on ListServ stuff. But I haven't been able to find
it. Is that available somewhere?


On Tue, Dec 7, 2021, 6:50 PM Nick Doty <npdoty at ischool.berkeley.edu> wrote:

> Thanks Seb for all your recent BigBang work and for this overview/plan for
> the next meeting. I can confirm that I plan to attend, Friday, December
> 17th at 9am US Eastern.
>
> Is the goal to get consensus on a refactoring of the core libraries? Or
> just on the documentation/contributor guidelines about how new
> code/functionality should be added?
>
> Cheers,
> Nick
>
> On Mon, Dec 6, 2021 at 3:59 PM Sebastian Benthall <sbenthall at gmail.com>
> wrote:
>
>> 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
>> _______________________________________________
>> Bigbang-dev mailing list
>> Bigbang-dev at data-activism.net
>> https://lists.ghserv.net/mailman/listinfo/bigbang-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20211207/53e48bee/attachment-0001.htm>