What to work on - even more ideas from convo with Jackie 2/5

• PresqueVu/Kuvu ("templating thing #2 & #3)
• note: "presque vu" (or some easier to remember spelling like "preskuvu" or "kuvu") is a French term related to deja vu - it's the feeling you get when you're about to have an epiphany, also described as having something on the tip of your tongue (but not quite coming out). "Kuvu," unfortunately, means "fungus" in Swahili. So that is probably not a good name.
  
• Three main features/modifications to opencores (note: feasibility/hardness uncertain)
• Kuvu Pages - Anyone can mark any wiki page they think would be helpful to the general community (not just their project) as a "kuvu page" (or some other better name). Kuvu pages get their contents indexed in a separate "kuvu search" keyword database, and when someone makes a new project or page, the description they enter is run through this search that pulls up kuvu pages with potentially applicable content - for instance, if you make a new project named "Ant Bike Mike Fanclub" you might get kuvu pages like "How to start a bike shop" or "Most common bike repairs" or "Bike toolkit starter list" shown to them in a sidebar for them to look at, link to, talk to people about, etc.
• Kuvu Templates (sorry, had to use that word.) Like Kuvu Pages, only these get transcluded instead of linking (if you pick them, their contents get copied straight into your new page - not like Transcluder in Deliverance which is, I think, more of a symlink rather than a copy - that is, if the original changes, your new page will change too.) Possibly with some "smart" auto-filled in spaces like putting in the right project name in the text. instead of linking (kind of like how PBwiki gives you some choices of "page templates" when you're making a new wikipage - Mel can demo real quick).
• Kuvu People - users can volunteer to become "guides" to newbies, and their profile page is scraped and put in... well, maybe another search keyword database, I really don't know how this stuff would be implemented. When someone signs up as a new user and puts in their interests (or creates a new project or page, for that matter) the good ol' search would be run, popping up possible "guides" that might be able to mentor you in whatever you're doing (or at least provide a good conversational partner).
• Making Life Easier For External Developers
• Deliverance seems like the primary candidate for this... openplans as a whole is another option, but would be pretty chaotic/big
• Basically, going through the new developer process (which I'm doing anyway) and making tools/tutorials in order to make it much easier for other organizations to build, customize, and use the openplans software suite (or parts thereof; modularity is great). It's coding and testing and writing and (maybe eventually) community-building/feedback-getting at the same time...
  
• Do this by using the same software tools to make Something That Isn't OpenPlans.org, and writing copiously during the process so that others can do a step-by-step follow - something like http://wiki.laptop.org/go/Bounties_for_awesome  - on a very tiny, pilot-y, no-financial-data, not-aimed-at-deployment scale might be a good demo candidate?
• Making "For Developers" pages, tools, etc.
  
• Privs delegation
• I asked Ian when he came over "what happens if a project admin gets hit by a bus?"
• Nobody knows, though it's been discussed before. some ideas we talked about
  
• admin privs could be rolled over onto the 2-3 most active / oldest / insert-other-criteria-here users if all admins do not log in for a certain time, like 6 months
• people can just manually email Brian or someone and ask them to fiddle with the databases, but this doesn't really scale
• in Request Tracker, people can "delegate" their privs if they're going to be away for an extended period of time - search for "Delegating Rights" in this page: http://wiki.bestpractical.com/view/ManualUsingWebInterface
  
• Other ideas I'm sure you have ;)
  

 What to work on - ideas from convo with Ian 1/29

• Template... thing, that will not be called template-thing soon
• models to diff
• mediawiki
• moinmoin
• pbwiki
• (what's currently being done by people using opencores)
• Getting to know everyone and what they do (the usual "Hi, I'm new.")
  
• Deliverance as something other people can use
• simple template project
• docs
  
• inter-group linking/collaboration (what do they care about?)
  
• creative commons licensing?
• accessibility?
• chat?
• OIPP? (one Irc-channel Per Project)
• ...or jabber, or something
• "The chatroom has... 0 people"
• bots?
  
• what happens when admins vanish?
• RT-style "privs delegation?"
  
• "make my site higher in search rankings!" (do NOT want to work on this one...) sitemetering, etc.
  
• translations/internationalization?
• where is metadata about projects stored ("this project is written in spanish" "this project is... in startup stage" "this project is about bikes")?
• helpdesking / user feedback (developer driven vs user driven features)? Bryan. (help pages)
• don't get overly distracted by shiny things (code! it is good!)
• "the ian presence bot"
  
• mobile? (notifications/sms/stylesheet-for-phone-sanity?)