As agreed on the conference call, I have set up a tiddlyweb hosted instance of Eric's insideTW document which we have all committed to using, to help document the jQuery migration: http://tiddlyweb.test.tiddlywiki.org:8080/insidetw/recipes/insidetw/tiddlers.wiki
Since Eric has put a lot of hard work into this document, I'll allow him to explain what it does and how it should be used. It is viewable by all but you need to log in to make changes. I've set up user accounts for interested parties that I know of and the credentials will be forwarded via email. I'll be away between April 8th and 14th but Eric has access to the server. So if anyone else would like an account please make your request to Eric. Note that this is currently hosted on an UnaMesa test server, but this is no obstacle to using it. We can at a later date move this to the wiki.tiddlywiki.org machine if we want to. However if we choose to do so I'd prefer for someone a little more experienced with server configurations than myself to carry out this task, since that machine hosts other services that the community relies on. Hope to see the insideTW in heavy use when I get back after Easter! Regards, Saq On Apr 4, 9:52 am, Saq Imtiaz <[email protected]> wrote: > The "IRC minutes" of the TiddlyWiki Developers' call which took place on > April 3rd can be found here:http://tiddlywiki.org/wiki/Dev:Conference_Calls/4 > > *Summary:* > > - A re-commitment by everyone to ensure that every change to the > TiddlyWiki core code has a ticket on Trac referencing it. This is > particularly important since changesets do not allow comments and > discussion > whereas tickets do. > - Agreement to attempt using Eric's "Inside TiddlyWiki" document to track > jQuery related refactoring. (One tiddler per function, to record > the changes > made to said function and the reasons behind it.) > - Saq and Eric will work together to deploy said document using > TiddlyWeb so that everyone may begin using it. > - Releases during the jQuery related refactoring period will be more > frequent. Possibly once every month, or every other month. However, > internal > releases amongst all TiddlyWiki developers rather than public releases > might > be utilized to optimize this process and ensure that proper testing takes > place before new code goes public. > - Unanimous decision that we need more documentation of the TiddlyWiki > core code and that this documenation needs to reside in the JavaScript > files > themselves. A syntax for this documentation will be agreed upon which > allows > readability of the documentation in the JavaScript files as well parsing > via > tools such as Code Illuminated or JSDoc. Towards this end, those who have > not already done so have committed to reading and providing feedback within > the next two weeks on the syntax for core code documentation in the > following thread: > http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/35b... > - Tickets 974, 609 and 608 to be implemented. > - Eric commits to submitting patches for his tickets in the future. > (pending resolution of his problems with generating patches) > > Saq --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
