• Name: Colas Nahaboo
• Email: colas@nahaboo.net
• Comment: maintains Foswikis on work intranet, at home, and on personal sites
• Home Page: http://colas.nahaboo.net - Contact info: http://colas.nahaboo.net/ContactMe

Foswiki area of interest

• PublicCacheAddOn - maintained plugin - PublicCacheAddOnDev
• CreateHomeWebConfigVar - proposal (replaces CreateHomeWebVariable )
• ShorterUrlSupport - proposal
• ExplodeHierarchalWebsInBreadcrumbs - proposal (see AddTruncateVAR)
• ImproveAttachmentToTrashFlow - interested in
• SmartEditAddOn - co-maintainer
• TagMePluginDev - patches
• TWikiDevEnvColasNahaboo - howto
• Development.WYSIWYG - contributor
• TWikiRawEditDefault04x02 - howto
• SameUrlSameContent - discussion
• Tasks.Item5922 - working on
• Tasks.Item5176 - commited fix
• Tasks.Item5391 - assigned to
• Tasks.Item5393 - fixed by cdot
• Tasks.Item5447 - not really a bug
• Tasks.Item5345 - not urgent anymore
• DiffWordByWordAddOnDev

legacy:

• KoalaSkin - author, legacy
• NavbarPlugin - author, legacy
• TopicMovedMessageTooVisible - legacy discussion
• RefreshEditPageDiscuss - legacy discussion
• FormattedSearchRegexCountVariable - feature now in core

Personal goals on the foswiki project

Use cases

• Personal, public: maintain my personal web site as a fowsiki one. See http://colas.nahaboo.net
  Issues: security, view performance, SEO, simplicity
• Personal, private: continued use of foswiki as a familly & friends circles site to host all our information.
  Issues: French localization, Wysiwyg, flexibility, power, enhancements via scripts
• Work, private: continued use of foswiki as the backbone of our intranet sites: both for cooperative classic wiki and (new) more formal intranet pages.
  Issues: skin customization, Wysiwyg, scalability (we have 30,000 pages), entreprise integration (Search engines, LDAP, RSS, Sharepoint, ...)
• Work, public: continued use of foswiki as a tool for external R&D cooperations. See http://labs.ilog.fr
  Issues: security, spam prevention

Personal opinions

What do I think are principles to guide development for the foswiki system

• reliability - I do not have to monitor it
• trustability - I know that whatever disaster strike I will be able to recover
• perennity - I want to keep using foswiki forever to protect my data
• unixity - Be based on a very definite set of objects (everything is a file, files are lines of text) with powerfully simple tools to handle them, in a language agnostic way. And do not sacrifice unix power for windows portability
• manageability - I can install/update dozens of foswiki installs: I manage 8 separate production foswiki sites
• community - I want the system to be kept alive, and receive new ideas by a community of people with different backgrounds
• readability - the foswiki syntax can be used to take notes, or email twiki-unaware people

• #Set SKIN = pattern

Discussion