[Bigbang-dev] BigBang @ IETF 116 Summary: Many changes on the horizon

[Sebastian Benthall]

Hello,

This past week was IETF 116 and an extraordinarily busy week for BigBang.
I wanted to note a few outcomes and propose some action items while it's
all still fresh.

- We had a large number of pull requests at the hackathon. Some are still
awaiting review. Once we've reviewed and merged this new work, I will
motion to do a 0.5.0 release.

- We had very good meetings with the Sodestream team and inaugurated the
RASP Research Group at IETF. Niels and I have set an intention to migrate
the BigBang repository from github/datactive to a new github organization,
github/ietf-rasprg. There it will sit 'beside' other repositories from
Sodestream and others. I will do some research about how to do this. We
should consider the (broad) implications of this together in a meeting in
which other Core Developers have the option of attending.

- RASP RG meetings are somewhat differently regulated than our BigBang
meetings. My current view is that these should be kept as separate. I know
Niels has for his own reasons suggested fully combining all RASP and
BigBang workflows, but Stephen (from Sodestream) and I agree its premature
to make those changes. There are lot of moving parts, and potential norms
collisions (around, for example, code review and documentation).
Integration will come happily in time.

- One major question is if there will be a RASP RG meeting at IETF 117, and
if so, who attend in person, and who chairs it. Ping Nick Doty -- we were
wondering if this interests you. There is a separate RASP RG mailing list
which we should perhaps use for coordination. I personally am not in a
position to make any such plans for another month or so.

- While we did some work on the dashboard at the meeting, there are some
kinks in the development process and docs to work out. And there are
questions about the architecture and how it relates to the RASP research
infrastructure that we have been imagining together. Essentially,  the
"dashboard" now is imagined rather expeansively as an application built on
BigBang. It's not yet clear to me what the relationship between the
governance of this application (which may well become the first RASP
product developed by people from Sodestream and BigBang teams) and the
governance of library code (what is currently in the BigBang repository)
will be. We will need to work this out.

In the short term, the highest priority in my view are the code reviews and
0.5.0 release, as these require no messy procedural changes.

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