Health first, Eric.:D Still, glad to hear an update.
w

On Wednesday, June 18, 2014 4:17:41 AM UTC+2, Eric Shulman wrote:
>
> First, allow me to offer my profound apologies to Yakov (and the entire 
> TiddlyWiki community) for not responding sooner. 
>
> As you've no doubt noticed, while I've continued to answer questions 
> online (via GoogleGroups as well as private emails), my recent overall 
> level of effort on behalf of the TiddlyWiki community has not been like was 
> in past years.  Unfortunately, I've been struggling with some long-term 
> chronic medical problems and this has been, as you can imagine, a major 
> distraction from my work on TiddlyWiki, as well as having a serious impact 
> on my already tenuous financial situation as a self-employed consultant.
>
> As a result, most of my time is spent pre-occupied with trying to get 
> healthy while keeping ahead of the bills, and haven't been able to put as 
> much focus on TiddlyWiki development as I would like.  Regrettably, and 
> despite my best intentions, I have not published an update to the 
> TiddlyWiki Classic core code in nearly a year, and several 'fixes' and code 
> enhancements to the TWCore that were submitted months ago as "pull 
> requests" to github are not yet incorporated into a published TiddlyWiki 
> Classic release build.
>
> While this may give the impression that all development on TiddlyWiki 
> Classic has ended, I want to assure you that this was not, and is not, the 
> plan.  Although TiddlyWiki 5 development is at the forefront of 
> TiddlyWiki's growing future, TiddlyWiki Classic still provides a rich 
> "ecosystem" of plugins and customizations that offers a significant value 
> to many people, and the current TiddlyWiki user community will undoubtedly 
> make use of their existing TiddlyWiki documents for quite a long time.
>
> It continues to be my intention, regardless of my personal situation, to 
> provide ongoing support as well as periodic updates and enhancements to the 
> TiddlyWiki Classic core code for as long as needed.  Of course, while this 
> is all well and good, what is needed in the immediate short-term is a 
> specific plan for getting an update to the TiddlyWiki Classic core 
> published as soon as possible.
>
> To achieve this and help me get back "up to speed" quickly, I would like 
> the active assistance of as many people as possible to help me review and 
> prioritize the existing github pull requests, as well as any additional 
> changes that they feel should be submitted for the next TWCore update. 
>  Ideally, this should take no more than a few days, perhaps a week.
>
> Once that is done, I can start incorporating those changes into the TWCore 
> code base and then build/post a beta-test version so that the updates can 
> be confirmed as "safe and stable" for release.  If that can be accomplished 
> quickly (within the next few weeks) and there are no "show stopper" 
> problems along the way, I should be able to publish an official update 
> (TW2.8.2) sometime in July.
>
> Following that, we should begin focus on the *next* update, so that we can 
> establish a clear plan and schedule so that the TiddlyWiki community knows 
> what they can expect in the future.
>
> Again, my heartfelt apologies for having 'dropped the ball'.  I greatly 
> appreciate your patience and understanding...  now, let's get things going!
>
> Much thanks,
> -e
> Eric Shulman
> TiddlyTools / ELS Design Studios
>
> YOUR DONATIONS ARE VERY IMPORTANT!
> HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"...
>    http://TiddlyTools.github.com/fundraising.html#MakeADonation
>
> Professional TiddlyWiki Consulting Services...
> Analysis, Design, and Custom Solutions:
>    http://www.TiddlyTools.com/#Contact
>

-- 
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 http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to