Diego Mesa,
Jeremy, I hope you can respond to this and I hope you don't mind me
speaking of you, I hope you set the record strait where I am in error.
Diego, I empathise with your position. I would however characterise
Jeremy's involvement from two perspectives
- one a high degree of sense of ownership, which he deserves and yet he
is very open to community influenced change
- and tends to act as a quality control gateway (and limiting gate)
These aspects of Jeremy's knowledge and experience is essential to the
success of tiddlywiki so far, but it is true it makes him a single funnel,
and thus you can see why the results of key changes tend to be influenced
by his perspective.
The truth is I am making a personal and professional commitment to
tiddlywiki, and would like to be able to effect more change than is
occurring,
eg; My Git Hub issues that remain un-actioned, and conceptual ideas I have
trouble getting acknowledged
Not withstanding it does need this Quality control and vision of Jeremy or
a set of his delegates or collaborators.
For me personally, I deeply understand Jeremy's vision, yet I too am a
conceptual thinker and I see little changes that could make substantial
differences, that is I would like to be involved with conceptual changes.
I want to contribute to the Vision, Yet this understandable funnel of
Jeremy, is restricting change. It also requires me persuading Jeremy that
my input be taken seriously (not withstanding I sometimes get it wrong)
Sometime, I have difficulty persuading Jeremy, Yet know a number of others
in the community share the need for that same change, then I am shy of
taxing Jeremy's Time, or having extended length conversations trying to
persuade him. A Number of which just get left open and un-auctioned,
because understandably Jeremy does not have the time to attend to all of
these, especially when the argument is subtle or complex, and it does not
seem important to him.
I do think we need to build the collaborative top level here, asking Jeremy
to delegate or distribute more of the effort and control.
I agree that we should expand
- *Development goals/features that are:*
1. *planned and fleshed out ahead of time (think github milestones,
roadmaps, etc.) *
2.
*prioritized by the community (think github stars/votes in comments, etc) *
- *A responsive group of developers to handle a growing community of bug
reporters and contributors*
But I would also suggest if Jeremy can distribute some of his current
roles, it will be necessary to deconstruct what Jeremy does himself, for
example;
- Vision and core change
- Quality Control and best practice code
- Maintaining modualarity
- Selection and Development of key editions
- Selection and Development of key plugins
- Management of server and platforms
There is no way one person can take on all that Jeremy can/does do at
present
It needs something I call "Collaborative Distributed leadership". There are
people like Mario, Evan, Eric are clearly qualified to take on code and
release Quality assurance, I would claim insight to making documentation
and examples understandable and proposing small changes for great benefit.
You can see how Josiah is our best "tiddlywiki champion" , community
organiser and helps us "get real". Yourself and many others are also
qualified in one or more areas and I would acknowledge here with more time
like David Giffords Toolmap.
One key enabler in a "Collaborative Distributed leadership" is
understanding which areas are independent or interdependent, and when
interdependent how to establish a review process, and who is qualified to
perform this.
Sincerely
Tony
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/f7845747-d746-4d79-8f9e-93fc0ac91cdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
