On Oct 23, 11:26 pm, Tobias Beer <beertob...@googlemail.com> wrote: > 2) I like the way you've discovered how to split up things ...and - > although the current "comunity" space today is far from being usable - But I think, the communitydev space is quit usable allready for the community contributors. But there are not many at the moment :) Hey folks jump in http://communitydev.tiddlyspace.com/#Contact
Important: comments is only available for members!! (at the moment) > this is clearly going in the right direction! I would even strip any > additional info and leave that in the TiddlyWorld space as a kind of > reminder of where the road might eventually lead to. +1 > 3) Topmost priority for me is to identify the most wanted community > features and list them in the communitydev space. I am not sure how > we're going to vote on these things... I implemented the tiddlyWebComments/comments plugin. For me an maias it works right well. I did one mini bug fix and some tweaking, that comments are excludeLists but the root tiddler is updated. So Activity stream works very well. > maybe for a lack of a better > alternative, let's just put our usrenames behind every proposition, > use google forms or micropoll.com and have people sign up for > voting... or simply use this group to discuss individual ideas... I > think we're really good at that. Anyways, having a list like that > surely would give an indication of what are the most desirable > features. see above > 4) As for community-supply... if anything, I think it really should > only contain the plugins being used by the community space, this is > wher€e components are being loaded into. +1. I think I removed the most redundant things allready. But needs to talk (skype) with matias. I think programmers have a different point of view here. > On the other hand, maybe we > really need a very basic 'admin-theme' space to be > included ...allowing us to create a public tiddler - like plugins - > without requiring the system-theme space(s). I think communitysupply allready is very minimal. A theme will be welcome, but is too early. Let's this discuss at the communitydev space. > 5) I think we would do good with a "community-sandbox". -1. I use communitydev space. If you need to test alpha plugins. Your own sandbox needs to be used. I think beta is fine for communitydev, but it shouldn't break it (for long :)) > Don't get me > wrong, I don't mean to clutter the spaces list with yet another... but > whenever some new feature or plugin is being explored in the community > context ...it should be tested in the sandbox ...which, of course, > (re-)includes the community space, whenever a new thing is being > tested ...everything still in test-mode should therefore be tagged > 'keep' or otherwise is prone to being deleted in an attempt to test, > well, something else. I think information tiddlers should be as fast as possible transfered to the community space. see above > 6) As for collaboration, you may have noticed the TypeWithMe > integration I have created ...now being available in the semantic > space. I really am not sure if this is very fruitful... so, what would > you think of this... does it make sense to use this as a > (complemantary) discussion/annotation tool? I like your improved typeWith.me "experiment". Let's have the comments in communitydev and typeWith.me in semantic space. As a new experiment and see what happens. > 7) Haven't gotten around making an updated version for the poup(macro) > space yet. This would be cool, since I think it would nicely fit for both community and communitydev. -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
