Introducing Community Cards

#1

The original Project 2036 post includes the following paragraph:

[Jeremy focussing on the core] means organising ourselves a little more formally so that others can start to form teams and partnerships to take on all the other things that need doing. I am delighted that this has already happened with MWS: @Arlen22 has stepped up to take the lead, and is surging ahead with an improved implementation, working with others in the community to do so

It is undoubtedly going to take some time to organise things differently, and we will need enough people who are willing to help.

We need to start somewhere. A basic attribute of formal organisations is that things are written down: the organisation chart, lists of team members, goals and so on.

The challenge for us is that members of the community may use different usernames for different services such as TalkTW and GitHub which makes it hard to unambiguously refer to a user. We want to be able to say things like This feature is being worked on by @X's team with @Y and @Z helping.

So, one simple thing that I think will give us a useful foundation for these efforts is to introduce community @usernames for use on TiddlyWiki. I’ve begun a PR which lays the groundwork in the form of procedures and CSS to render “community cards” for projects and for people.

The idea is that people would submit their own card as a PR, initially manually or eventually using a friendly front end tool like the PR maker by @saqimtiaz.

Community cards can incorporate a small bitmap avatar. I think it might be helpful to enforce pretty tight size restrictions on the avatar field. I found using https://squoosh.app/ helpful to get the size as small as possible.

The preview should be fairly self explanatory. I have added a card for myself and one for @ericshulman to mark his status as the member of the community who has been active the longest.

I have also started the process of adding four initial projects. My intention is to illustrate the structure afforded by these community cards using realistic data; this is not (yet) a complete proposal for the substance of the team organisation.

https://deploy-preview-9069–tiddlywiki-previews.netlify.app

This system is primarily intended for people who are active in the project, with the very loose criteria of being a net contributor to the community.

I would welcome questions, suggestions and other thoughts.

image
image1516Ă—2868 474 KB

4 Likes
Discourse is too opinionated
#2

Is this too early? If we have an official MWS-based TiddlyWiki forum server, we could have account on it and this will be very natural.

#3

Hi @linonetwo I hope that MWS will indeed become our primary means of collaboration. But this initiative is about publishing definitive information about the team structure of the project. Experience with other subsidiary sites like tiddlywiki.org and links.tiddlywiki.com suggests that they are off the beaten track and hard to find for regular users. So, I’m in favour of publishing the information as part of the main site, using GitHub in the regular way for updates and maintenance. This centralised architecture makes things easy to find, and easy to track over time.

#4

I’ve been assuming this is just an early preview of what’s coming. So I haven’t looked to submit a card for myself.

Would you like people to start doing so?

#5

At this point, I’m seeking feedback on the idea and implementation of community cards. The next step will be to merge the changes to the tiddlywiki-com branch to make them visible on tiddlywiki.com. Then we can ask people to submit their cards, perhaps offering the help of some volunteers who have the requisite GitHub skills.

In parallel, we’ll start to identify and form the teams that we need. We can start with the main project team and the MWS team, establishing weekly calls to work together on pursuing the goals of the team.

This is all very provisional. I haven’t done this before, and so I will need help from people with experience and enthusiasm if this is to succeed.

3 Likes