Ben Boeckel

If needed, we can add API calls to the `gitlab` crate to support this. We already support depagination too.

There's also the question of which instances to scrape. `gitlab.com` is obvious, but the GNOME and freedesktop.org instances should probably also be on the list (at least).

We host our own GitLab instance with our own runners. However, we only use Docker containers for Linux (so far). We do use "bare metal" for macOS and Windows, but...

I know we have some licenses; I'll ask about what kinds they are, how they are stored, and whether we can set up a network server for them for CI...

Does that work with only `gitlab.com` or is it any GitLab installation? I don't see it mentioned there at least.

It's all wrapped up in the TriBITS package logic. I suspect that the new TriBITS stuff should make the installed targets more useful, but I'm not sure. I am able...

You can do this: ```cmake target_include_directories(Ioss INTERFACE "$") ``` where `${include_install_dir}` is whatever TriBITS passes to `DESTINATION` for the header installation. Repeat for other library targets as necessary.

Hmm, maybe `#[serde(tag = "type", rename_all = "snake_case", default = "http")]` would be a better location for that?

```rust while let element = seq.next_element().unwrap_or(Some(FieldKind::Unknown)) { field_kinds.push(element.unwrap()) } ``` You should match on the error state, not just the `Option`-ness. Something like this structure is what you want: ```rust...

Hmm. Well, *something* is making `next_element` not end on its own. I suggest debugging what all of the `next_element` returns are. Something has to change when it gets to the...