Should there be a TiddlyWiki Steering Committee?

#1

TiddlyWiki is currently using a Benevolent Dictator Governance Model, which is led by a benevolent dictator and managed by the community. This model has proven to be very successful. TiddlyWiki, Linux, and Python being examples.

We have the comfort that any changes committed to the core are scrutinized by long time devs to TiddlyWiki. But also see that many leaders have ideas which are great, but difficult to get the community motivated - time is compressed for us all.

Do you think that the advancement of TiddlyWiki would benefit from going to a different model of growth:

1.) Stearing committee of core devs and community members.

2.) Fund raising efforts and sponsorship donations for dev.

3.) Let tiddlywiki continue to grow via community contribs.

4.) If you build it - they will come.

#2

Not until there are clear lists of TiddlyWiki use cases and whatever other lists that accurately define the community. Actively monitor the forums and note recurring questions / concerns / problems / needs / requirements / whatever.

And then, threre has to be a way to make these visible and keep them accurate / updated. As tides and currents ebb and flow.

All of that if a steering committee is to reflect and represent a community.

Otherwise, the committee is steering based on what goals? What agenda? What info?

Whatever a steering committee would do, I’m thinking better the entire community had the methods and the means of collaboratively doing what a committee would do. (Surveys, whatever.)

I like the Benevolent Dictator Governance Model. Maybe your suggestions would be excellent for a “community edition” or spin-off (focused purpose, narrow use-case) edition(s) of TiddlyWiki ? Then have feedback loops between the main edition and other editions.

All of that said, what needs to be steered? What problem needs to be solved? Is there something broken that needs to be fixed? If not, why fix it?

#3

IMO, it’s fine as is. People can fork it if they feel it necessary.

1 Like
#4

What ever direction we may go in the future I would like to see more small team collaborations, project and edition development. These would generate more real world expierences and provide useful feedback to devs but only when things cant be resolved in the current release.

It is my view that sometimes core and plugin development is running ahead of the mature adopton of features already available in the core. It is causing a proliferation of addons all of which have values in there own right, but as a total environment its getting very complex.

As a prolific supporter in this forum I am starting to see a large number of reoccuring issues which have multiple solutions when we could be solving these more strategically and through native tiddlywiki and improved documentation. Filling gaps in the variables, configuration, macros and hackability, so problems can be solved with an instruction rather than yet another javascript plugin which has its own bespoke instructions. Solutions built on core features educate the user to solve thier own problems, solutions built on addons demands more learning that is not nessasarily transferable back to native tiddlywiki.

But then, what do I know?

1 Like
#5

I think that a very pertinent point to the issue raised in the OP.

From my POV, TW is very rich.

So how you lift-out/up specific use cases and give them extra attention?

I have contributed on a few projects; mainly through giving feedback.
But these have mainly been about TW workings (e.g. “Multi-Column Layout” & “Custom Markup”) rather than “end-apps” (e.g. “TW Ethnographer”; “TW Photographer”).

A comment
TT

1 Like
#6

Right. There is repetition over time.
Why does that happen?
I think partly, despite the move to Discourse from GG, the system here for precisely locating solutions past is still weak.
We lose solutions constantly??

Partly this is because we are all individuals and collective push tends to the workings of TW intrinsically rather than being End-Application focused.

TBH, I think it is as much a social-cultural issue as anything else??
You need an almost “forensic” attitude to it’s history to fully leverage TW?? :smiley:

Projects-for-Purpose (e.g. “Kindergarten Games”; “Guide To Digital Colour”; “Senior Health Monitor … etc”) do have clarity of final aim that can be good–if you are interested in such an app.

Just a comment
TT

#7

I agree but here we need to bring in other subject matter experts SMES. This why I want to get a multitude of collaborations happening so we have the practices in place to do exactly what you suggested.

#8

So, how?

Just a query.
TT

#9

Assumption 1 ?? :smiley:.

Just FYI (and I don’t know if I am right) is that the user-base here is too narrow to achieve that kind of leverage?

If enthusiasm and knowledge were king then we should reign.

On both counts we ain’t so stellar and don’t.

Why is that, @poc2go? Best, TT

#10

Start with the what!

Now, choose a SME subject and hopefully find someone here interested in it, but we need to find where they lurk and invite them.

  • Recently I reached out to the PyScript team suggesting they may want to consider a python implementation in tiddlywiki similarly to @Charlie_Veniot Basic Programming environment.
1 Like
#11

I’m a bit confused on the purpose of the steering committee. TiddlyWiki does not have an organizational structure supporting it. Is this a topic to gauge support for spinning up such an organization with the implication somewhere down the line there will be an organized steering committee for the core?

I know a majority of the discussions regarding changes to the core happen directly on Github, but I think this is more about answering the question, how to ensure TiddlyWiki lives on without Jeremy serving at all times as the steward of everything?

1 Like
#12

Right. TBH, I wasn’t so clear what the aim of the OP actually is.
As far as GitHub goes and core work I think it looks pretty healthy already! It certainly don’t need my help! :smiley:

The aspect of the OP that emerged I got interested in was basically: How do you both develop for and promote TW to specific user groups?

Something like that.

Best, TT

1 Like
#13

@TW_Tones, not wanting to put water on your fire. But I think in practice there is a serious modifying “caveat” (limitation) to your appeal. What is it?..

I don’t think there are that many active people here who are specialists in specific fields (except, perhaps, computer science?). Well there is @DaveGifford who has done sterling work on Christian concordances. And of course there are others. But “pool is very small.”

My guess is, to get traction active-outreach may be needed???

Just a comment
TT

#14

Before responding to @TiddlyTweeter perhaps rather than a steering committee what if we had a “community voice” forum to inform the developers and enthusiast’s where to find improvement’s and better doco to support adoption of tiddlywiki. It could also act as an organised (but not the only) “Voice to the core team”.

As per my post here that appear to drift from the OT, actually I hope for lots of little SME steering committees to develop over time.

Generally that is true but there are quite a few that are not so active, come by occasionally or are lurking and we regularly have someone new here because they are focused on particular outcomes see examples below;

Yes, I am promoting active outreach, but I think there are seeds already in the community.

  • personal productivity
  • Genealogy
  • Student note taking in class and study
  • Research
  • Publishing
  • Developing a database for various activities
  • Project teams and management
  • blogging (inc to self as log)
  • building websites
  • Bible
  • Trains
  • Pasta

Personally I have a few projects and interests for which I may be able to find a tribe;

  • Home/business/hobby database of objects, locations (electronic Marie Kondo)
    • Including database of electronic devices, tools and appliances
  • Personal health log and tracking
  • Work instructions processes, procedure and documentation
  • Business intelligence system
#15

Without going too anthropological on your arse.

My general impression is that “tribes of users” often exist in hinterlands.

Okay? So what is my point?

My point is “CATCH 22” … that “To make a TW that illustrates TW you make a TW.”

Though to make a TW that illustrates the variability of counting systems you needs be good at them …

Annotation 2019-10-11 145847
Annotation 2019-10-11 1458471000×2398 261 KB

Just a comment
TT

2 Likes
#16

“It is no mystery I know my way from here …”

@TW_Tones one is precious as the other. Angels line your pockets.
So how do you engage the Other here?

TT

#17

A step, @TW_Tones, might be to get names of these interested you know for these interests …

Screenshot 2022-06-04 112037
Screenshot 2022-06-04 112037696×536 60.9 KB

Do you have any?
TT

#18

Keep your eyes peeled and you will see them.

1 Like
#19

As the OP, maybe should quantify what I was thinking when posting the topic.

As long time ‘user’ of TiddlyWiki - mostly digging around GG and now this discord for plugins that have been contributed by the community, has enhanced distribution of my dribble (information) to co-workers and friends.

Myself, am a long time JavaScript dev, and still not all that great with TiddlyWiki markup - filters, defines, and tags <$twtag param="" />. But have followed, understand, and use the JS functions in $tw core over the years. Most of my modules are calling JS core functions.

I would like to contribute to TiddlyWiki - and expand my knowledge - but do not know were to start? A high-level guide of what projects are of importance to the direction of TiddlyWiki, focused on where is TiddlyWiki expected to be three years from now? What are the plans forward? where it is to go?, are there any plans? where do I go to help?

There are many ‘tribes’, usually focused on a very specific use of TiddlyWiki - which am all for - but what if I wish to contribute in a broader sense?

An ‘official’ organized steering committee could define, support, direct, and motivate the community to projects that are believed by higher level persons and developers to be important for TiddlyWiki’s growth.

A definitive guide as to where the core and editions are headed, to design and define sub-tasks that need to be done. A set of distinct tasks that need to be implemented for project completion. Maybe meetings to discuss fluid and unexpected changes in the project, resolve misunderstandings, discuss priorities, and blocking issues.

IMO - This community skill set is awesome! An array of community devs with differing skills and strengths given small, modular contributions can to bring global projects into reality and impact TiddlyWiki releases. Is a waste not to manage that skill set for the progress of TiddlyWiki into the future. Requires focus, organization, and direction in order to tap that skill set.

Only way I know to do this - is with a steering committee. Please advise.

2 Likes
#20

I thought your post very interesting! (though I’m not any kind of programmer).

I only have one overall observation. Kinda generic. My impression (over years; but less than yours!) is TW is well-coordinated on its core developments.
Basically as an end-user it’s backwards compatibility is brilliant.
I have rarely had to sort out any compatibility mess.
I think that matters???

Regarding the specific OP on the idea of a “Steering Committee”.
I’m not so clear how you would ever achieve that in a way that would support your intent??

Put crudely … approved developments in core TW seem to be (sensibly) conservative (conservative with a small “c”) already?

Just comments, I happy to comment more if needed.
TT