I'm also in favour of a move to github. To reply to some of Chris's proposals:
1) The TiddlyWiki svn repo is full of all kinds of stuff. What portion is to be moved... In addition to the components mentioned by FND (TiddlyWiki core (Trunk/core/, along with tests and such), Cook (Trunk/tools/cooker/) and jQuery plugins (Trunk/core/jquery/plugins/)) I think the following need to be migrated: >From association: a) locales (translations). I think it is important to have the translations in a repository so that people can build a non-English version of TiddlyWiki without manual intervention. The translators themselves do not need to learn github - they can use a tiddlyspace based system as suggested by Jeremy. What is required is that someone moves these translations into a repository so that they can be used by build scripts. This is similar to the current TiddlyWiki situation - most translators don't use subversion directly - the translation is normally in a TiddlyWiki which I then upload to subversion. I'd like to see the locale directory be a subdirectory off the core directory. b) Adaptors. Some are in the association, some are scattered in contributors directories - these would perhaps benefit from being in a common github repository. c) Possibly also the themes directory. >From verticals: a) the tiddlywiki.com vertical. Perhaps also the beta vertical (although git probably removes the need for this, since it could just be a branch). I favour several smaller repositories over one large repository and agree with Chris that there should be one repository that is "the core". I agree with the proposal to freeze the subversion repository and only move over the tip revision. The subversion repository and the trac source code browser should be left available so that the history is available for bug fixing and other purposes. 2. What about trac and tickets? -trac and the tickets therein will also be frozen in a read only state. tickets will _not_ be migrated... I'm only in partial agreement. I don't think that tickets should be frozen (I agree that they should not be mandated as a matter of course). I'd rather see some parallel running of the old and new ticketing systems. So, in actioning a ticket, a developer could either move it to the new issues system, and then make the fix, or just make the fix and then mark the ticket as fixed in Trac. Martin On 24 January 2011 13:03, rakugo <[email protected]> wrote: > I think this is a great move. > I personally think it would be best to start afresh in a TiddlyWiki > version of git - ie. not migrate anything. > > Some of the issues from 5 years ago to me are not issues as they have > been alive for 5 years without being solved - they haven't received > the conversation they require. If anything I think starting from > scratch would lead to rejuvenating the really important issues. For > instance the search is something I care about but I haven't been > following that ticket due to the fact it is "lost" amongst the trac > graveyard. It would be a good opportunity for the community to see > what people perceive as the most important issues and fix them. > > As long as http://svn.tiddlywiki.org and http://trac.tiddlywiki.org > (and the internet! :)) remains alive read only, the important ones > will not be forgotten and available including patches that have been > suggested previously. I can imagine us creating issues on git to the > important ones and referencing urls on trac. > > Jon > > On Jan 24, 11:20 am, Jeremy Ruston <[email protected]> wrote: >> > According to translations, it would be nice, if a translation wouldn't >> > add file size to the TW. >> > I'd like to have something like to include a "system-de" instead of >> > "system-en" >> >> That's it. It might be separate from the system bag, for instance "lingo-en". >> >> Cheers >> >> Jeremy >> >> -- >> Jeremy Ruston >> mailto:[email protected]://www.tiddlywiki.com > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/tiddlywikidev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
