Skip to content

Contact

Contact

A small, deliberate page on how to reach the maintainer. There is no ticket system here. Substantive questions get substantive answers.

How to reach the maintainer

This site is run as a small reference notebook, not as a service desk. The right routes for different kinds of message are listed below.

Corrections to a page

If a page contains an error of fact, that is the most useful thing to flag. Mention the page URL, the sentence or claim that looks wrong, and a brief note on what the correct version should be if you know.

Questions about Ubigraph workflows

The support page covers the questions that come up most often. If the page does not answer yours, a short message is welcome. Keep it specific. Include what you tried.

Questions about the paper shelf

The papers section and the three companion notes - Blitz arrays, C++ templates as a Turing-complete language, and the Veldhuizen thesis - cover what the site says about each reference. If you can point at a verified source for one of the PDFs, that is genuinely useful.

General comments

Welcome, but please be specific.

What this page does not offer

A few honest limits:

  • There is no published email address on this page at launch. Forms are not used either.
  • There is no support phone number.
  • There is no live chat.
  • There is no commitment to respond within a fixed time window.
  • This site does not take consulting work. Project questions are out of scope.
  • This site does not accept guest posts, link exchanges, or content collaboration.

These limits are not a posture. They are how a small reference notebook stays useful instead of drifting into something else.

What works well in a message

Short, specific messages get good replies. The most useful ones tend to share four properties:

  1. A clear topic. Ubigraph, a specific demo, a specific paper, a specific page.
  2. A clear question or a clear correction.
  3. Enough context to act on without back-and-forth.
  4. No attachments unless they are necessary.

Long, vague messages get slower replies because they need to be broken apart before they can be answered. That is not anyone trying to be difficult. It is just how a small inbox stays workable.

Privacy when you write in

Anything you send is treated as a working note. Personal details are not added to any list, not shared with any third party, and not published on this site. The privacy page covers what the site does and does not collect on its own.

Reasonable expectations

Replies come in batches rather than on demand. There is no announced schedule. If you have not heard back after a while and you still think the question matters, a short follow-up is fine.

If the question really is urgent, this site is not the right place for it. A current general resource will serve you better.

Other useful pages

  • About for what the site is and what it is not.
  • Support for the most common help questions.
  • FAQ for direct answers to common questions.
  • Changelog for what has changed.

That is the contact policy. Plain, deliberate, and the same for every reader.