I wonder what to do first. There is the obvious which will keep me busy today: a few hours on User Research, writing interview scripts and thinking about personas and defining the first use case to implement for myself (which is going to be adding a comment to an issue). There is the not-so-obvious: how to communicate around fedeproxy, beyond the announcement that funding was granted.
I guess the question really is: “how would I like fedeproxy to communicate if I was not involved in it but interested about its development?”. It currently is nothing but an idea, which is something I don’t feel very comfortable communicating about. I’m therefore inclined to keep a low profile until I start using fedeproxy for myself on a real use case. The real use case is very modest (adding a comment to an issue) but I’ll rely on it to do real work, that is contributing to Ceph and I’m hoping it will be a good show case to explain what fedeproxy is about.
Maybe that’s all the communication fedeproxy needs? I’ll draft a blog post to publish on https://fedeproxy.eu along these lines at https://hedgedoc.softwareheritage.org/I8EOzMehRk-CLOscCQ3CdA#