Christovis

Yep, agree, we should find a way to generalise this method and maybe place it in `utils.py` ? For Listserv mailing lists I have a function `ListservList.get_name_from_url(mlist_url)` [here](https://github.com/datactive/bigbang/blob/e6a7ba464fed84bfb0968fcbcc8079ed2d495727/bigbang/listserv.py#L812) that get's...

I was wondering whether [this](https://gist.github.com/ammarshah/f5c2624d767f91a7cbdc4e54db8dd0bf) might be helpful to filter out personal contributions, and [this](https://github.com/cncf/gitdm) to find affiliations (as suggested during the IAB-AID workshop.

Contributions per timezone is showcased for the 3GPP in this example: [timezones.ipynb](https://github.com/datactive/bigbang/blob/main/examples/3GPP/timezones.ipynb) and can easily expanded to hour of day. You can use it as a template for the IETF.

This is part of #417

Could you explain this a bit more. I don't know what is meant by top/bottom and tags? Is what every you describe here partially contained in the _Multi-dimensional scaling_ of...

**> How is the LISTSERV data stored locally after it has been collected, @Christovis ?** After a mailing archive or list has been scraped and single messages are a `mboxMessage`...

**> How does the LISTSERV functionality load the data from csv or mbox?** It is assumed that the user can by themselves identify the file format in which the data...

At the moment I believe we could have an: 1. `MessageParser(ABC)` that can contain functions like `from_url(), create_email_message(), get_datetime(), to_dict(), to_pandas_dataframe(), to_mbox()` such that they don't need to be duplicated....

@sbenthall given the new code structure that is emerging (at least for 3GPP, W3C, IEEE) is this issue still relevant or does it need to be rephrased?

For nice visualisation of the archive of mailing list communication network we could use [kumu](https://kumu.io/).