[Bigbang-dev] BigBang Accessibility

[Sebastian Benthall]

Hello,

I wanted to address the accessibility project in a separate thread....

Niels, you've pointed out the following items for the hackathon:


> - Get the dashboard working
>
- Have a development pipeline and documentation of the dashboard (in a
> similar manner to BigBang) to foster its future development
>

To some extent, this is just about elbow grease. And my elbows are in!

But speaking of norms, this does raise some questions about development
process of the dashboard vs. BigBang itself.

One thing that has come up with the dashboard project is that it has
dramatically changed the "user story" around how BigBang is used. We used
to essentially make every user try to do the steep onramp towards hacking
on BigBang itself. This is not "accessible", and now we are committing to
proper software packaging.

This entails a firmer distinction between BigBang 'users' and BigBang
'developers'. Different roles with different needs.

I think this is all a very good change! But it is better to be conscious of
it, as it involves a change of norms.

- Improve the usability of the dashboard
>

The dashboard is for the users, and so usability is paramount.
But who are the users? Can we recruit some at the hackathon to test the
dashboard, see what works for them?


> - Select more specific analyses for the dashboard (find them in existing
> notebooks, or write new notebooks)
> - Talk to IETF leadership about relevant metrics
>

I suppose this is where I'm most interested in the direction of BigBang.
I don't think the current 'examples notebooks' are particularly 'usable'.
They are really to demonstrate library functionality.

What are the users interested in using BigBang for?


> - Talk to Tools team about integration and exchange
>

I don't know what this means.


> I might also develop a some userstories for answering particular questions
> and using the dashboard.
>

I think this is actually essential. Please do this!

There is a bit of a tension between open source software development norms
and 'agile' product development norms. That tension is precisely due to
this developer/user split in the latter case. A disciplined pipeline from
user story to specification to implementation in product development (with
many iterative refinements along the way) could be good for BigBang. And it
sounds like future funding may depend on success with users.

- Seb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20230131/3af59198/attachment.htm>