TWiki Feature Proposals

Follow-up of WhatIsIn04x01. This topic was cached 23 hours ago (refresh)

Release 4.2, 5.0 and onwards follow same release process and 14-days rule as we used for 4.1.

New feature proposals will by nature be for the next TWiki release 5.0 (GeorgetownRelease)

When you add a proposal you must create a new topic describing your proposal. You can use the form below.

For the community to accept a proposal you must propose something that you are prepared to implement yourself or by an already committed developer.

The 14-day clock does not start until

• There is a committed developer
• The date of commitment field has a date (so the application below can show it)

You are welcome to propose enhancements without a committed developer but then the community is only able to discuss the feature, not to accept it. But you may be lucky that a developer picks up the idea and decides to commit himself to implementing it.

• To track the last changed proposal topics with committed developer visit ChangedFeatureProposals
• To track the last changed proposal topics without a committed developer visit ChangedFeatureProposalsUncommitted

Submit Proposal

Submit new feature request

Please start a new topic for each feature request.

• Consider filing a Support question unless you are very sure that you cannot do what you want with the current feature set or with one of the many Plugins.
• Please scan over the existing feature requests to see if it has been requested already.
• NOTE: you might want to make yourself familiar with our Acceptance/Rejection Process of new features.
• If you are including code to implement features, thanks for contributing to TWiki's development! Please see the PatchGuidelines to make your patch easier to apply.

Page name:		Example: BinaryFileDiffersError (use a WikiWord)
Page title:		Example: Topic save gives a Binary file differs error
Motivation:		Reasons why this feature is needed, and why it is suitable for adding to the next release of TWiki
Description:		Enter a relatively short summary of the request
WhatDoesItAffect:	API, Auth, Documentation, Install, I18n, L10n, Performance, Plugins, Prefs, Refactoring, Rendering, Search, Security, Skins, UI, Usability, Vars	Hold CTRL to select multiple items
	Your request is submitted after you Create, Preview and Save the page.

NewFeatureProposals

Proposals

New Feature Proposals

Proposals that have a committed owner (the ones without a committed developer are not covered by the formal release process and 14-days rule.

Note that the 14-days rule clock start ticking when a proposal has a committed developer and it stops when anyone that are registered as a user on twiki.org raises any concern.

Proposals where 14-day rule applies

Topic	Summary	Committed	Developer	Concern
CloneTopicLinkUnderMore GeorgetownRelease	Clone topic feature in More screen	2008-04-30 8 days ago	MartinCleaver

Proposals with concern raised (14 day rule does not apply)

Topic	Summary	Committed	Developer	Concern
CentralizeAndHideAdminInstructions GeorgetownRelease	Centralize and hide administrative instructions	2007-12-29 131 days ago	LynnwoodBrown	KennethLavrsen
DatabaseStore GeorgetownRelease	DBIx (perl database) backed TWiki topic Store	2007-04-05 399 days ago	SvenDowideit	KennethLavrsen
DiffAttachments GeorgetownRelease	a small patch that will show you the diffs of attachments	2007-05-20 354 days ago	SvenDowideit	KennethLavrsen
EnginesAsContribs GeorgetownRelease	TWiki Engines distributed as Contribs	2008-04-27 11 days ago	GilmarSantosJr	CrawfordCurrie
MakingVarVARTopicCapable GeorgetownRelease	%VAR should be able to return variables at the topic level, not only at the web level.	2008-03-17 52 days ago	MartinCleaver	MartinCleaver
MultiStoreRefactor GeorgetownRelease	Refactor the Store to allow multiple plugable backends	2007-10-11 210 days ago	SvenDowideit	CrawfordCurrie, KennethLavrsen

Feature Proposals Ready For Release Meeting

A Feature proposal is ready for release meeting per release process when

• Proposals that have a committed developer willing to drive the proposal to implementation. There is no requirement how soon and a developer is later allowed to uncommit if it later turns out that he does not have the time.
• Proposals have had at least one concern raised by any person with a twiki.org access
• The community has had enough time to end the discussion, but could not reach full consensus
• It is normally a Customer Advocate that decides that a feature is ready for a release meeting.

Note that the 14-days rule clock stop ticking when anyone that are registered as a user on twiki.org raises any concern and it does not ever start again! Then acceptance is either by consensus or by release meeting decision.

%VARCACHE{ refresh="24" }%

Topic	Summary	Committed	Developer	Concern
ProcessAddToHeadAdds GeorgetownRelease	Process addToHEAD adds	2007-02-25 438 days ago	ArthurClemens	SvenDowideit
TWikiFormInheritance GeorgetownRelease	Proposed feature for inheritance of TWikiForm fields	2007-09-19 232 days ago	KoenMartens	SvenDowideit, KennethLavrsen

Accepted Feature Proposals

Proposals that have a committed owner and have been accepted according to the release process

%VARCACHE{ refresh="24" }%

Accepted proposals waiting to be implemented

Topic	Summary	Developer	Reason	Release
AddDataToRegistrationHandler	add the registration data to the parameters of the registrationHandler	SvenDowideit	AcceptedBy14DayRule	GeorgetownRelease
AddFinishHandler	Add a finishHandler() for plugins	MichaelDaum	AcceptedBy14DayRule	GeorgetownRelease
AddFooterParameterToSEARCH	Add footer parameter to SEARCH to match the header	SvenDowideit	AcceptedBy14DayRule	GeorgetownRelease
AddIsEmptyToIFVariable	Add an isempty operator to the IF vairable	RafaelAlvarez	AcceptedByReleaseMeeting	GeorgetownRelease
AddUserToGroupsOnRegistration	Add User To Groups On Registration	SvenDowideit	AcceptedBy14DayRule	GeorgetownRelease
CaseInsensitiveUserMapping	Ignore differences in case between registration and login	SvenDowideit	ConsensusReached	GeorgetownRelease
CreateHomeWebConfigVar	Create a new $TWiki::cfg{HomeWebName} configure variable	ColasNahaboo	AcceptedBy14DayRule	GeorgetownRelease
DisableWikiWordsWithNumbers	Provide option to disable numbers in WikiWords	KennethLavrsen	AcceptedBy14DayRule	GeorgetownRelease
ExtractAndCentralizeFormattingRefactor	Refactor format rendering to use TWikiIterators? (adds paging, consistency and speed)	SvenDowideit	AcceptedBy14DayRule	GeorgetownRelease
MoreAttractiveForm	Render form with more attraive appearance	ArthurClemens	ConsensusReached	GeorgetownRelease
MoveToJQuery	Enhance PatternSkin to use jQuery	ArthurClemens	AcceptedByReleaseMeeting	GeorgetownRelease
PreInstallNatEditContrib	Make NatEditContrib? a default extension starting from 4.2	MichaelDaum	ConsensusReached	GeorgetownRelease
ResultSets	Result Sets to abstract search results, lists, and GROUP definition	SvenDowideit	AcceptedBy14DayRule	GeorgetownRelease
SearchResultsPagination	Search results pagination	ArthurClemens (spec), SvenDowideit (code)	AcceptedByReleaseMeeting	GeorgetownRelease
ShorterUrlSupport	Support in TWiki.pm for Shorter URLs, ommiting HomeWeb and WebHome	ColasNahaboo	AcceptedBy14DayRule	GeorgetownRelease
SummaryBasedOnSearchTerms	Make topic summary optionally based on search terms	ArthurClemens	AcceptedBy14DayRule	GeorgetownRelease
TWikiCache	A pluggable caching service and built-in HTML page cache	MichaelDaum	ConsensusReached	GeorgetownRelease
TWikiStandAlone	TWiki as a Standalone Server	GilmarSantosJr	AcceptedBy14DayRule	GeorgetownRelease
TocFailsForIdenticalHeadingNames	Headings with same text generate same anchor, and TOC doesn't work	HaraldJoerg	AcceptedByReleaseMeeting	GeorgetownRelease
TopicCaseSensitivity	URL's that have correct spelling, irrespective of case will goto that topic.	SvenDowideit	AcceptedByReleaseMeeting	GeorgetownRelease
TopicMovedMessageTooVisible	Topic moved message at the bottom of normal view is too visible. Move to diff page	LynnwoodBrown	ConsensusReached	GeorgetownRelease

Accepted proposals in progress of implementation

Topic	Summary	Bugs Item	Developer	Release
ControlOverVariableExpansion	Control over Variable Expansion	Bugs:Item3647	PeterThoeny	GeorgetownRelease

Completed Feature Proposals

Proposals that have been completed following the release process

%VARCACHE{ refresh="24" }%

Completed Proposals (Merged to core or to default plugin)

Topic	Summary	Bugs Item	Developer	Release
AddControlOverTocRendering	Add control over TOC rendering	Bugs:Item4153	ArthurClemens	FreetownRelease
AddGetSessionKeysToFunc	Get a hash of all the names of session variables		CrawfordCurrie	EdinburghRelease
AddGetUrlToTWikiFunc	Add TWiki::Net::getUrl functionality to TWiki::Func	Bugs:Item3552	CrawfordCurrie	FreetownRelease
AddGlobalSettingToAllowNonWikiWords	Add global setting to allow non-WikiWords		ArthurClemens	FreetownRelease
AddIsInGroupVariable		Bugs:Item4809	SvenDowideit	FreetownRelease
AddIsTrueToFunc	rationalise and publish the interpretation of "true" in tag parameters	Bugs:Item3806	CrawfordCurrie	FreetownRelease
AddSanitizeAttachmentNameToTWikiFunc	Add SanitizeAttachmentName To TWikiFunc?		CrawfordCurrie	FreetownRelease
AddTHeadAndTFootToTWikiTables	Add THead and TFoot to TWiki tables	Bugs:Item3741	SvenDowideit, ArthurClemens	FreetownRelease
AddTWikiAdminUser	Adding a default twiki admin user with password defined in configure		SvenDowideit	FreetownRelease
AddspaceOutWikiWordtoFunc	Add spaceOutWikiWord to Func		ArthurClemens	FreetownRelease
ChangeTopicContextOnTheFly	Change the TWiki context so it behaves as if it was processing a different topic	Bugs:Item3781	CrawfordCurrie	FreetownRelease
ChangedLinkShouldPointToMostRecentChanges	MailerContrib - 'Changed' link should point to most recent changes, not the entire history	Bugs:Item4461	AndrewRJones	FreetownRelease
CopyPreviousRevisionTopicContentIntoNewRevision	Improved UI for copying topic content incl meta into new revision		ArthurClemens	EdinburghRelease
DecisionOnNativeSearch	Remove native_search from default build	Bugs:Item4713	CrawfordCurrie	FreetownRelease
DeprecateRcsDirectoriesFeature	Deprecate RCS Directories Feature	Bugs:Item4863	KennethLavrsen	GeorgetownRelease
DeprecateTWikiFuncGetOopsUrl	Deprecate TWiki Func getOopsUrl	Bugs:Item3772	CrawfordCurrie	EdinburghRelease
DeprecateTWikiFuncPermissionSet	Deprecate crusty permissionsSet function	Bugs:Item3578	CrawfordCurrie	FreetownRelease
EnhanceMailerContribToAllowExclusionOfWebs	Enhance MailerContrib To Allow Exclusion Of Webs	Bugs:Item4075	AndrewRJones	FreetownRelease
EnhanceMailerContribToObeyViewPermissions	Enhance the MailerContrib so it respects access permissions on topics	Bugs:Item4284	AndrewRJones	FreetownRelease
ExpandStandardEscapes	Add function decodeFormatTokens to decode format tokens to TWiki::Func	Bugs:Item3841	CrawfordCurrie	EdinburghRelease
KeywordSearch	Adding keyword search		ArthurClemens	FreetownRelease
MergeFuncUsersContribWithFunc	merge functionality for managing users/groups to core	Bugs:Item2354	CrawfordCurrie	FreetownRelease
PassMetaToHandlers	New parameters in handlers to support permission checking		CrawfordCurrie	EdinburghRelease
RefactorUsersCode	Refactor user management to eliminate user object and inefficiencies		CrawfordCurrie	EdinburghRelease
RememberCookieLogin	TemplateLogin option to "keep me logged in"		CrawfordCurrie	FreetownRelease
RemovePasswdAndResetpasswdScripts	Remove redundant passwd and resetpasswd scripts	Bugs:Item4063	CrawfordCurrie?	GeorgetownRelease
ReplaceKupuWithTinyMCE	Proposal to replace Kupu with TinyMCE in TWiki 4.2	Bugs:Item4433 and Bugs:TinyMCEPlugin	CrawfordCurrie	FreetownRelease
SearchWithTWikiQueryLanguage	Add TWiki Query Language to SEARCH	Bugs:Item4041	CrawfordCurrie	FreetownRelease
SimpleOperatorsInIF	Simple operators to significantly enhance %IF	Bugs:Item4473	CrawfordCurrie	FreetownRelease
SimplifiedUserMappingCodeInterface	The TWiki 4.2 UserMapping? , Password and LoginManager? interfaces.		SvenDowideit	FreetownRelease
SupportStandardEscapesInIF	Allow standard escapes in IF statements	Item4140	CrawfordCurrie	FreetownRelease
UseIsoDates	Use ISO Dates	Bugs:Item4139	KennethLavrsen	FreetownRelease
WhatVersionsOfPerlAreSupported	Request to raise the required Perl version from 5.5.3 to 5.6.1		KennethLavrsen	FreetownRelease

Proposals that were implemented as non-default Plugin

(these may be rejected proposals where the developer decided to implement the feature as plugin or other extension instead)

Topic	Summary	Bugs Item	Developer	Release
TWikiInstaller	TWiki is getting an Installer		SvenDowideit	FreetownRelease

Rejected Feature Proposals

Proposals that have been rejected following the release process

Proposals that have been rejected can be put back in "UnderInvestigation" if a committed developer alters the proposal or the mood has changed in the community.

%VARCACHE{ refresh="24" }%

Topic	Summary	Bugs Item	Developer	Reason
AddAjaxContribsToDistribution	Add AJAX Contribs to Distribution		ArthurClemens	RejectedByReleaseMeeting
AddAttachmentsParamToFormat	add topic="" to META and $attachment() to SEARCH format			None
ChangeContactAuthorFirstPolicyNotifyAuthor	Change plugin ContactAuthorFirst policy to NotifyAuthor		KennethLavrsen	None
EditTemplateWithDiscussion	Edit Template Topic with Discussion Section		PeterThoeny	RejectedByReleaseMeeting
InitialiseNonPluginExtensions	Support an initialisation function for non-plugin extensions	Bugs:Item3997	CrawfordCurrie	ConsensusReached
PluggablePermissions	Plugin hooks to permission checking		KoenMartens	None
PreInstallSmartEditAddOn	Pre-install SmartEditAddOn			NoCommittedDeveloper
ProvideAccessToWebMetaData	Provide access to web meta-data		CrawfordCurrie	ConsensusReached
SimpleFieldQueriesInMETASEARCH	Add query support to METASEARCH	Bugs:Item4041	CrawfordCurrie	ConsensusReached

Parked Feature Proposals

Proposals that have been parked because they failed to fullfill the basic criteria in the release process mainly

• Proposals must have a developer that commits to drive the feature to completion (there is not demand on how soon).

Proposals may also be parked after acceptance because the developer realise that he cannot find time to implement the feature. Someone else are then welcome to pick it up.

%VARCACHE{ refresh="24" }%

Topic	Summary	Bugs Item	Developer	Reason
CreateHomeWebVariable	Create HOMEWEB variable as distinct from MAINWEB. Superseded by CreateHomeWebConfigVar.		LynnwoodBrown	AcceptedByReleaseMeeting
DeprecateGetViewUrl	Deprecate TWiki::Func::getViewUrl			NoCommittedDeveloper
DynamicFormOptionDefinitionsUsingInclude	Parse INCLUDE in form definition topic			NoCommittedDeveloper
EasyUrlQueryHandling	Easy url query handling		ArthurClemens	None
FriendshipLogos	Plusher versions of SteffenPoulsen's logo / other alternative logos			None
GraceFullFallbackForPluginTWikiVariables	TWikiVariable for non-installed plugins should fallback gracefully		SvenDowideit	None
MultipleAnchors	Multiple Topics within one page get the same Link-Anchor			None
NOAUTOLINKForUnderscoreWikiWords	More NOAUTOLINK options for use with underscore wikiwords			None
NewEditPreferencesPlugin	An enhanced EditPreferencesPlugin which stores values in Main.TWikiPreferences		KennethLavrsen	AcceptedBy14DayRule
SupportTranslationInPlugins	Add translation support for extensions authors			NoCommittedDeveloper
TWikiFns	TWikiFns - lightweight type of extensions			NoCommittedDeveloper
TopicDisplayName	Topic display name			NoCommittedDeveloper
UpdatePluginsPlugin	Show when there are new versions of installed plugins			None

-- Contributors: KennethLavrsen - 30 Oct 2006

Discussion

I renamed the topic from TWikiFeatures04x02 to TWikiFeature04x02 (singular), in anticipation of a picklist for proposed feature topics.

-- PeterThoeny - 30 Oct 2006

Ken, I tried to make sure that unreviewed items are not marked %DONE%, but I realised that while I know what has been implemented, there is no record of what has been accepted. How can I tell? There are very few ticks above, surely there has been more discussion than that? There needs to be some sort of link to the release meeting decision.

Later: I reverse-engineered as many approvals as I could....

CC

Thanks CC: Actually many of those you call 14-day rule are consensus decisions. They were not ignored. They were simply discussed and ended up with an agreed spec and no open concerns. Then I evaluate that there is no need to waste release meeting time on them. But I will consider this scenario in the twiki app I work on so this "consensus reached" state can be flagged as opposed to "open concerns". Example is ChangeTopicContextOnTheFly. Don't worry about changing the decision description again above. I do that when I implement the app and populate the form fields.

-- KennethLavrsen - 09 Apr 2007

OK. I was too curious to not walk quickly through the proposals. All of them were handled correctly. It shows that the 14-day rule works well. In no case were a proposal totally ignored. There was just no concerns raised. Good to see the process working. When the twiki app is done it will be possible to make a search to show those that are under the 14-day rule - before and after. It will also enable the customer advocates to put a little acknowledgement on those that are 14-rule accepted for traceability when people ask how the decision was made a year later.

The difference between a 14-day rule acceptance and a consensus acceptance is that with consensus there has been concerns raised - typically about spec - and an agreement has been reached with no concerns left open.

-- KennethLavrsen - 09 Apr 2007

Please note that on 22 Apr 2007 the TWiki Application for new features and especially the ChangeProposalForm has been updated to match the process. But there is still another days work in updating the current proposal topics and to replace this page by a number of searches. But 90% of the work is done.

-- KennethLavrsen - 23 Apr 2007

All old proposals - also the completed and parked now have the required forms and the concent that puts them in the right buckets. So from now on the process is no longer manual. Easier for all of us. It was about 30 hours of work to get that done by we Customer Advocates will have a much more reasonable job now.

-- KennethLavrsen - 25 Apr 2007

Excellent work Kenneth! It must have taken quite some time to update all proposals, thank you very much for making the release process more transparent for all of us!

I added a cache to this topic since it loads kind of slow due to the many reports.

-- PeterThoeny - 27 Apr 2007