Document Related

TWiki.FormattedSearch, TWiki.TWikiVariables, TWiki.TWikiShorthand (TextFormattingRules almost identical), TWiki.TWikiForms, TWiki.TWikiDocsStyleGuide, WikiEditor, EditDaemonWithGVimIntegration, VimEditor, Sandbox.NewContents_unfinished, Support.RdiffUrls

Plugins

all links in this paragraph are to the Plugins web unless otherwise noted. Development - Codev.RenderPipeline RestructurePluginsDevelopment, PluginsInCVS, Codev.MorePluginHooks Features - SpacedWikiWordPlugin, SmiliesPlugin, CommentPlugin, InterwikiPlugin, FindElsewherePlugin, SpellCheckAddOn, RecursiveRenderPlugin, SlideShowPlugin, PollPlugin, PeerPlugin (Codev.PeerRatingSystem), TouchGraphAddOn, PurplePluginDev, WebServicesAddOn, TreePlugin, CacheAddOn, Sessions - UserCookiePlugin, SessionPlugin

Advocacy

TWikiAdvocacy, HowToGetInternalBuyInForTWiki, UsabilityIdeas, Main.TWikiPlatformPresentation, Main.TWikiPresentations, Plugins.SlideShowPlugin, TWikiDeployment, Sandbox.TWikiCourseOutlineExample2, http://wiki.org/wiki.cgi?TipsForSiteOperators Some links about the people driving TWiki like CoreTeam, TWikiUserGroup, TWikiUserGroupsInUS, WikiReferences (interesting articles). TWiki.TWikiAdminCookBook and TWiki.InstantEnhancements both have absolutely great ideas. Skin_ideas_from_Peter_Masiar

Sandbox: Sandbox.GrantBowTest for me.

Developers

RestructureCodevWorkFlow, ProductionReleaseChecklist, PatchGuidelines has requirements for helping out the core team with code. VariableVARS_request, TWikiDebugging, TWikiTemplatingSystem, GatewayTopic, SimplifyInternalMetaDataHandling, PluginApiForTopicHandling, Plugins.PluginCvsToolsAddOn, Plugins.PluginPackagingHowTo, MoveAllPluginsToCvs, StepByStepRenderingOrder

Applications

TWikiTrackingTalk, BugTrackingInTWiki, TWikiForge

TWiki Gallery

lists of TWiki sites - Main.TWikiInstallation, Codev.TWikiOnWebHostingSites, Main.TWikiSuccessStories, Main.TWikiStories, Main.OlderTWikiInstallationList Other sites running TWiki in no particular order (loads of great ideas) - visiblearea.com - the best skin I've ever seen, decafbad.com thwackety.com nevadamissouri.net nebuladevice.sf.net Main.LufWiki Danish_apartments Java_IDE] OSA_Foundation foxkid-net twiki coming soon edusmart.sf.net-missing Cleaver.org

TWiki Stories

TicketWiki, Main.TWikiAnnouncements, TWikiVsOtherProducts, bscol.com, decafbad.com, linux.com-article, Clarify-Engine

Ward Cunningham

http://c2.com

Increased User Centered Focus

The culture of highly textual information overload that TWiki carries with it is frightening to beginning users. It unduly increases the learning curve for those interested in the TWiki development effort. The community badly needs some input from real UI designers. This input needs to be matched up with some skilled TWikiSkins developers. I bet it wouldn't take long to get done with the right people. Documentation must be updated as you go, not an afterthought.

Positioning

Stellar technology is not enough. Wiki perception must be repositioned. You can't redefine people's existing associations for key terms or force strange spelling on users. Terms must be clearly defined and consistently used. "Open Source" expectations must be fulfilled.

Stronger Community

Not all current CoreTeam members are active. I don't know if any face to face meetings have ever taken place. The social side of the community needs to be maintained to understand new input in a consistent way, to share the workload of managing the various tasks and to encourage new developers to help out as best they can. You must walk your talk, especially trying to promote a collaboration tool. QA and feedback cycles can also be improved.

Eat Your Own Dogfood

The http://twiki.org site needs to set an example in many different ways. We need to demonstratate through our own actions the right way implement the technology and build a social structure for evolving the TWiki code base itself.

Streams

Plugins written on a Perl code base allow many kinds of translations, filters, lenses, transcoders, intermediaries, etc. Like GNU coreutils (try info coreutils on any *nix system), sed and awk before, Perl is not only a full programming language but is designed for stream processing.

My Efforts

IRC - Codev.TWikiIRC Download Policy - TWiki.TWikiRegistration http://twiki.org/download.html ApprovingRegistrations NoRegisterDownload New Logos - HighResolutionLogos Purple - Plugins.PurplePluginDev Caucus Skin - Plugins.CaucusSkinDev My - MyTWikiOrg Diffs - HumbleDiffs Success - Hurd story webalizer - WebalizerStatistics

Security

Holes MUST be fixed, especially for corporate use. I see no security team or process in place to address issues that come up. TWikiSecurity is a discussion, not a gateway topic. ShouldNoViewImplyNoEdit - GrantBowPrivate is an experiment.

Streamlined Defaults

I have many percieved and real concerns, some are barriers to TWiki adoption. Install - TWikiDeployment InstallationForDummies TWiki.TWikiAdminCookBook TWikiUnixInstaller Ease of use perception - TooUglyForNonTechnicalUsers ShorterURLs ShorterCaseInsensitiveURLs GoBox Case issues - FileSystemNameClash DontUseCaseToFindWikiTopics Simplification - Support.StrippedDownTWiki TWiki.RoundEdgeSkin SimplerTWikiDistribution GoIsSearch ThreadedDiscussions - sf.net software integration used by Edusmart-missing-site

Streamlined Administration Features

The BeijingRelease feature of automated Web creation helps quite a bit. LinkChecker WebalizerStatistics Password stuff - EmailResetPassword ForgettingPasswords

Interactivity

TWikiIRC InstantNotification Bookmarks - MyTWikiOrg TWikiBookmarklets TWikiAsABookmarkManager SupportMoinMoinStyleBookmarks Email Integration - The implementation details of email integration are key to easier adoption and use. There's been much discussion on Codev but little (from what I can see) forward movement on email use in the core code. EmailNotificationEnhancements - Mail Lists like list.org - Mailman Support.TWikiManagedMailingLists Wikilearn.MailingListArchives (Wikilearn.SearchingMailListArchives, Wikilearn.MailListManagers) Collaboration - TWikiAsWebProxy ties together ideas like no other document I've written before. Also see SemanticWeb, IbisWiki (also ACzWikiNameEncodingIsCryptic) and Plugins.TouchGraphAddOn. Applied to developers the concept becomes similar to SourceForge - TWikiOnSourceForge TWikiForge WorkFlow (older) weblogs - WebLog (example Main.WikiBlog)

TWiki Philosophy & Goals

TWikiMission - note this is in Codev not TWiki web! ReadmeFirst AlternativeTWikiTargets Higher Profile for TWikiMission, a highly important document.

Development Lifecycle

QA - streamline, develop and maintain processes. Feedback paths are not yet optimized. Alphas can be downloaded but Betas still require a registration. TWiki Help Needed - new maintainer for Plugins.CommentPlugin

Renaming

RenameTWiki (a case issue) RenameWebToZone RenameMainWebToHome RenameTheMainWeb HighResolutionLogos - You can't ship logos with questionable intellectual property.

Other

Offline - ReadWriteOfflineWiki Palm - MegaWiki sounds fascinating. I want to find time to install and try it soon. XML & Integration - TWikiAsWebServicesServer XmlRpcForWebApps

Codev Form

The form applied to every Codev page needs to be redone. It's clear that the MasterRefactor started previously was NOT completed. This highly visible and social task of redoing this needs to be saved until after BeijingRelease is out the door.

No matter what state the Codev web is in, it will be seen as an example. I hope that it will be viewed by OUSTSIDERS as well as insiders as a positive example. I will try to codify and edit these thoughts into a form of problem - solution - result. Identification of a user audience is important. Is access available to the Apache logs on sf.net? I'll have to check for the sf.net projects I am an administrator for.

TWiki (WebChanges)

Main (WebChanges)

Support (WebChanges)

Plugins (WebChanges)