Ciao Mat Ciao Mat I think concrete examples help.
My use case. I like to try promote TW (though promotion is not on your list :-) on Twitter because its effective and Twitter I know well. There is an infinite listening audience there. I am doing 7,000% less than I could because every bl**dy TW resource I want to point to I have to research, find the address for documentation and the install, know if the author needs acknowledging on Twitter (i.e. are on Twitter or not) etc, find them there, craft a post, check it. *PLEASE give me standardly laid out tiddler for every resource worth posting about ...* 1 - download address 2 - documentation address(es) 3 - support address 4 - author address(es) 5 - data of release or version # if available 6 - description Then recycling info over Twitter would be a doddle and we could begin to dance it. Ideally I'd like to generate a resource list from a Tiddler set of, say, 600 resources, output it to a Twitter robot poster and leave it get on with it for six months at a time. Then I can concentrate on responding to questions about them, not the hand-crafting of them. As is its unviable. *And a consequence is TW is not getting the important exposure it deserves.* Right now I'm looking to use David Gifford's TiddlyToolmap, since its the most comprehensive list around. But that is huge work as the entries don't come up in a browser in any standard way (as there is NO standard way defined for listing a resource). That is NOT usable for a wider audience who need a standard approach so it doesn't get confusing. So I still have to check every entry and re-write it. That's too much to do often. Regarding your own depiction of example scopes ... IMO I think its important to define the Final Usage of "Data" as precisely as possible in order to layout what you talking about in practice--down to the level of fields and whatnot. I think your list may be currently too broad... Mat ... - contribute code to e.g Github (probably via an API) - co-develop TW stuff without e.g Github - collectively build repositories (for e.g plugins) - collectively build documentation - discuss TW stuff - discuss non-TW stuff Delimited basic resource finding I suspect is critical across the board at the moment? (Not saying no to anything else, just trying to find a viable handle to work forward from.) Just thoughts Josiah -- 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/0cb413d0-adc5-4904-aec3-4ed330a20417%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
