On Thu, 27 Jan 2011, tiddlygrp wrote:
-- What happens to the contributor code? Chris indicated that contributors can move their code as they wish. For me that means some will move, some will stay, and some may move elsewhere. I think this contributes to the fragmentation of tiddlywiki even more.
That's interesting. I agree that finding stuff is and has been a big concern but I've felt that the contributors setup on svn.tiddlywiki.org has actually worked against discoverability of TiddlyWiki plugins. I think this is due in part to the special nature of those plugins: they are code that can run on the web but only in a TiddlyWiki. Therefore it makes sense that the point of distribution for such things ought to be a TiddlyWiki, on the web. Mind, the point of distribution and point of code repository does not have to be the same thing. So, my thinking is that where someone chooses to store their plugin code isn't that relevant to discoverability. Also, the fact is that the current setup, wherein all the contributors stuff is in the same repo mean that the repo (in part because it is svn, which is slow in modern terms) is extremely time consuming to update if you have the whole thing checked out. And then once you have thing there's so much there that has little to nothing to do with whatever your current purpose might be. You make a valid point about not knowing which dependencies you need to build a vertical, but I think that's already true, and already fixable with cook recipes. Those recipes can use content from all over the web, not just local disk. Effectively used, that can make the repositories associated with a repo tight and focused, with minimal duplication.
-- Lost history. I think just moving to github without history is a tremendous waste of knowledge and effort. I can see two relatively easy solutions: 1) Import history with svn2git and just continue with development (my preference). 2) Ditch history, keep trac/svn online AND start on github with a new MAJOR version of tiddlywiki. Then it is very clear for humans that a break in the source happened.
I think maintaining the history of the core will be fine. I'm less motivated about ditching code history than I am ditching stale tickets. -- Chris Dent http://burningchrome.com/ [...] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
