A multiple-persona exercise and question about repo description

[weex]

Hello folks,

This afternoon inspired by very thoughtful discussion in #11 and seeking to cure my tunnel vision on the developer, I reviewed the bunch of ways someone might find this project from a few perspectives: The end user, the instance admin, and the contributor. Maintainers I considered part of the contributor set for this exercise.

The result was pretty cool. I could see a bunch of new problems and created several such as Home page doesn't address each part of the community. I hope everyone's as comfortable as I am with all of these problems. They aren't urgent, they just exist and personally I find satisfaction in tackling them as time permits.

The reason for this post is because I have a specific question about a non-PRable setting. That of the repo description. Currently for Mastodon we have "C4 fork of your self-hosted, globally interconnected microblogging community".

The problems I saw with this is that C4 fork is inside baseball to a user, and the whole thing isn't very explanatory for an instance admin or contributor. I'm thinking a better description includes something along the lines of dynamic, immature and then simply names what was forked and what kind of thing that is.

So I propose "Dynamic, immature fork of Mastodon's federated social network software" Immature feels a but rough to me but it's accurate. Thoughts?

Thinking along the same lines for disapora* but rather than just have these kinds things change silently, I figured it would be good to discuss.

Thanks,

David

cc: @mariha @ledcoyote

[weex]

Thought about this for a couple days and I like dynamic but swapped the subjective immature (upstream was mature in both cases and that didn't change at the moment of forking) for a start date.

New descriptions are like "Dynamic fork of Diaspora's federated social network software, started Aug 2021"