Triage

This Thursday, May 17th, 2007, we will be triaging our Plugins Trac. There's quite a lot that needs to get cleaned up.

Issues To Address

  • Tickets! ✔
  • Any remaining instances of Gaim ✔
    • Besides history, no this doesn't count!
  • User Permission Issues: ✔
    • How to solve the spam issue
      • Use the spam filter plugins
    • Wiki editing permissions
      • Should users be allowed to?
        • Yes, anything that they shouldn't will be marked read-only and if it becomes a problem, we will turn this off.
  • Review ChannelGuidelines ✔
  • Determine policies ✔
    • Adopting external plugins
      • Should Pidgin/Finch devs be invited automatically? Should we treat them like anyone else?
      • What about other authors?
      • What about abandoned plugins?
      • Abusive plugins such as groupmsg and broadcast - we need a policy on what should be considered abusive and we need to spell that out in the wiki. We need to link to it profusely from the wiki areas for each abusive plugin.
    • Suggested policy of "Plugins will be considered for adoption based on functionality, code quality and interest of current developers." I'd like a page to go a bit more indepth on this.
      • Push access with be granted on a case by case basis.
  • Determine source viewing issues ✔
    • You can't browse our source from the site
      • Should we use viewmtn like Pidgin is? If so, two instances or just one? What about backend mtn database setup?
      • Should we set up tailor to convert to a private svn repo that could be browsed? (I strongly dislike this idea but felt it needed mentioned - John Bailey)
      • Resolution of viewmtn with a stub for the browse source link.
        • Datallah to tackle this.
        • ViewMTN is done ✔
        • Still need the browse source stub.
  • Discuss Plugins: ✔
    • L10N plugin
      • Like our old I18N page, but integrated into trac.
      • This will need to be written, but can be done simply.
    • Simple Ticket ✔
      • do we need it?
      • It will stop users from mucking with settings that they shouldn't.
      • General consensus right now is to go for it.
      • 'John Bailey - This is done. I have hidden everything except component.
    • Spam-Filter ✔
      • All agree, needs to be installed and configured.
      • Installed
        • We have configured an Akismet API key and thresholds and whatnot. Just need to keep up on monitoring.
        • WIKI_ADMINs (i.e. Developers and Trusted Contributors) should add regexes to the BadContent page when stuff slips through the spam filter.
        • John Bailey - I can delete ticket spam relatively trivially now. I just need to know which comments or tickets need deleted.
    • Mailman
      • This is more of a "it'd be nice", and have to be written
        • low priority
    • Planet ✔
      • Finish the plugin and set it back up?
        • Not many of us blog, and those of us that do, don't do it frequently. On top of that, those of us that do, are on http://planet.im/ so having another feed seems moot.
        • Not doing anything.
    • New Download Plugin
      • The current one sucks horribly for our use case
      • Should have an idea of releases
      • Upload to incoming, copy to download directory.
        • This avoids the race condition of gf.o having a faster upstream than the person uploading the files. 
          18:40 < grim> i'd like to see it keep up the most recent release for some platform
18:40 < grim> this _may_ get confusing, but we could possibly have it break it out as well
18:41 < grim> but say we just released 2.15, we should keep the 2.14 links up in "Current Release" 
              untill they're superceeded
    • Theme Plugin
      • This needs to be installed ✔
      • We need a new theme created, see below.
    • Last.fm
    • seti@home
    • Guifications Theme
      • I would like a plugin that made it easier for people to upload and maintain their guifications themes.
      • This may not be worth it since we're only keeping it working, but we do still have semi active theme development. 
        18:52 < grim> ok, so do we bother writing a plugin to handle gf2 themes?
18:53 < grim> we can always use the ticket system and a report
18:53 < rekkanoryo> indeed, stick with tickets, I think
  • Discuss Continuous Integration again ✔
    • This would probably be BuildBot, which IIRC has a trac plugin.
    • Undecided for now
  • RDBMS ✔
    • Should we change from SQLite? If so, to MySQL or Postgres?
      • Should we drop the ticket history, or some part of it? Most of our bugs are Windows specific Guifications bugs that we really can't fix because GTK+, Pango, etc. are at fault.
        • Staying with what's working for now. We'll address this again later if necessary.
  • Theme ✔
    • We need a decent one. Originally I was going to use a similar theme to developer.pidgin.im but they went ahead and used their header which I don't think we really want to use. 
      18:48 < rekkanoryo> what if we took their color scheme and figured out a way for the navbar to not suck?
18:49 < grim> yea that could be done
  • SSL Certs ✔
    • We can get these relatively cheap through steadfast, but we need to figure out how many we need, how we're going to set them up.
      • John Bailey: I think we should wait to use a cert with apache until we can figure out how to centralize authentication for (at minimum) both trac environments. Getting a valid cert for just guifications.org now may make sense for IMAPS, but as only a few people use it, it's not a priority in my opinion.
    • That means well need to get some more ip's as well if we have multiple http SSL certs.
    • We need to look for a trac auth provider that'll allow us to consolidate logins into login.gf.o
    • We'll need certs for login.gf.o, imaps, and lists.gf.o unless we can piggy back that on the login.gf.o one.

Interested in helping?

If you know python and the trac api, and are willing to help write some of these plugins, please let us know and we can throw together some more specific details.

Last Modified on Sat Aug 11 20:46:15 2007 by jbailey (10 months ago)