Skin Master is a role to ensure that skin development is coordinated, that best practices are carried forward and that pressing issues are resolved in a timely manner. Without someone taking responsibility for this issues will continue to drift as they have for the last year or so, resulting in wasted effort, duplication, and incompatible implementations of the same piece of functionality.

Ideally assignment of this important role would be part of the CoreTeamNominationDiscussions process. To encourage the timely conclusion of that process, I request that interested parties state in this document what responsibilities this role would have. Please feel free to refactor to keep the document terse.

Responsibilities include:

• To set strategy of how the skins are to fit within the TWiki development process
• To identify opportunities to rationalise and ConsolidateFunctionalityFromSkins
• To push for and sponsor functionality coded by skin developers to get implemented in the core or plugins, as appropriate
• Maintainance of documentation (identify what needs to be written, ask the community to write it, give seal of approval when done)

Taking on this role will offer the following benefits:

• Enhance your LeadershipSkills

-- MartinCleaver - 14 Jun 2003

To ensure problems like...

• We ran into problems in our new Web when we discovered that all edits were being owned by TWikiGuest in spite of everyone successfully logging in. It turns out that the GnuSkin docs don't say anything about changes to the /bin/.htaccess file that are required by GnuSkin, as per EditAuthenticationNotWorking -- someone should get that important installation note into the distribution. -- ChristopherAllen - 04 Jul 2003 &
• BugInHttpEquiv

... are caught early

-- MartinCleaver - 04 Jul 2003