Proposal: development

What happened:

• A spam measure was implemented that rendered existing wiki pages uncommitable (.html surveillance) even for those registered and logged in.
• An email communication was created by a team member to clarify why pages are rejected
• A clarification was made in regards to the spam measure taken.
• Miscommunication: Memeber expected developer to notify team when issue is resolved.

Developer has concerns around the effectiveness of a wiki as communication tool.

I share similar concerns and can understand we have internal discussions mixed in with external discussions around the pages of wikiindex.

This is a proposal to consider implementing a 2nd wiki for the purposes of keeping the signal-to-noise ratio of developments discussons related to the evolution of the wikiindex platform.

Possible options:

• 2nd MediaWiki - most straightforward, perhaps password protected. Move all proposals and meeting minutes to this wiki
• Trac
  • wiki only for development discussion.
  • milestones to give a sense of where our structured data is going
  • issue tracker to ensure closure of issues reported by the team and key user base (ie. we most likely will only invite key registered members who actively participate and/or show up to meetings - this is a separate discussion)
  • source control - keep our platform under strict change control. be able to rollback changes that break the system. be able to invite other developers as needed. immediate function: keep a baseline of the wiki software itself.

I'm confused. Is this a problem that happened on WikiIndex? Or on some other wiki? I think source control is a wonderful thing, and I encourage you to go ahead and implement it. I've been using Subversion recently, which underlies Trac, and the revctrl wiki discusses other options. But I don't see how any of the options you've listed would prevent the miscommunication you describe above. --DavidCary 14:18, 24 November 2008 (EST)