Adium

Time and Location

Thursday, 2007-02-08 in #adium-mtg

PSTMSTCSTEST
7 PM8 PM9 PM10 PM

Equivalent to 03:00 GMT on Friday, the 9th.

Agenda

  1. Issues in Adium 1.0
    1. People dislike the status icon overlay in the status item
      1. At least one person on irc, any others?
      2. cbarrett has heard people praising it on feedback.
      3. durin42 didn't initially care for it, but after he gave it like 2 weeks suddenly he realized he was using it constantly - it's kind of like the genie effect on the dock - seems superfluous at first, but long term it really does seem to improve the workflow.
      4. Zac says this is not really a necessary concern. The code in 1.1 (trunk) allows xtras authors to specify if they want the badging to occur. See MenuBarIcons
      5. Evan agrees with Zac.
    2. Fonts.
      1. Fonts have always been a problem, identifying and solving the problem would be a very positive impact on support in the short term
      2. Evan: I think that besides #6286 the biggest problem has to do with colors. Based on some reports, the 'save as default font' button doesn't handle colors right all the time, perhaps.
  2. What next? & General Items
    1. 1.1 development.
      1. Come up with a timeline for deciding what should go in.
      2. Continuation of betas? (edr1084)
      3. Development builds for testers? (edr1084)
        1. I think we should post a debug build with each release. Localizers need one, too, to be able to get to nibs, since we strip them of their ability to open in IB during a release. (Evan)
    2. 1.0.x releases.
      1. 1.0.1 soon! We've fixed some big issues already. (Evan)
    3. Target dates for releases? (cbarrett)
      1. I think if we set reasonable goals, it can help us have something to work towards -cbarrett
    4. Platform/Plugins (cbarrett)
    5. ModuleRefactorization (am)
    6. Unit Testing
    7. Parental Controls (the_tick & alangh)
  3. New Technology Demos & Disccusion
    1. WKMV2 (catfish_man)
    2. Airbag. Google's crash reporting framework. (cbarrett)
  4. Next Time...
    1. Figure out when the next meeting is.
    2. What worked and what didn't this time?

Minutes

Issues in 1.0

Status overlay in EMD

  • djbsquared points out this is not a 1.0.1 issue.
  • The_Tick brought up issue of user vs. author control
  • Decision: Leave things the way they are -- Zac's comment on 1.a.iv. is particularly relevant.

Fonts and colors

  • #1882 was brought up, with CFM's mockup.
  • Mac-arena's mockup from devl@ was also brought up.
  • Evan fixed the Set Default Font Button to show up when hit from Message View toolbar.
  • Other things to do in a 1.0.x timeline:
    • Retitle the button?
    • 21:26 < EarthMkII> how about "set style from selection"?
  • Make a ticket for further discussion. #6349 (milestoned for 1.1).

What next? and General Items

1.1 development

  • Get GSoC2006 improvements out before GSoC2007 starts ramping up.
  • Freeze 1.1 after this meeting. No new tickets for 1.1 unless assigned to a developer.
  • Mac-arena suggested a plug-in to enable the debug logger, which would always be present but simply turned off in release builds (as opposed to not there). And it can have a nag screen, so the user doesn't forget about it and so it doesn't get misused for evil purposes.

1.0.x releases

1.0.1: Friday, 16th.

Target dates for releases

  • plan: set goals for the next stage of the release cycle
  • 1.1b by end of March.
  • The_Tick suggests Quarterly releases might be good to discuss.
  • bgannin suggests that there shouldn't NEED to be a release every quarter, only the possibility.
  • cbarrett points out 3months might be too short for a large feature change.
  • CFM points out branches.

Platform/plug-ins

  • Things we can accomplish right now:
    • build an example filter plugin
    • build an example service plugin
    • flesh out plugin docs already on trac
  • 21:46 < Catfish_Man> 1) applescript
  • 21:46 < Catfish_Man> 2) (related) API
  • 21:46 < Catfish_Man> 3) plugins
  • 21:51 < Catfish_Man> 1) we have no one. 2) we had a SoC project that bombed, 3) we just covered
  • Version checking & backwards compatability (ticket #?)

Module refactorization

  • ModuleRefactorization pretty much sums it up
  • pick a small controller to test
  • Dock controller? (blocks on leopard)
  • Not 1.1 timeline.

Unit testing

  • ofri couldn't make it (thoughts to the ML?)
  • UITest framework is progressing
  • bgannin owner of unit tests
  • simple harness to make a test connection with each service
  • M-a suggests a Test service (possibly including eliza for chat simulation ;)
  • Identify mission critical paths, and test them

Parental controls

  • See ParentalControls.
  • Nobody present is against it.
  • cbarrett thinks it will be something we can do better than iChat
  • No.1 priority for CFM in parental controls is bludgeoning Apple into letting us integrate with theirs
  • Start work now in a branch
  • Identify key users to provide feedback

New technology demos

WKMV2

Airbag

  • allows us to get function and line numbers from builds distributed without symbols (does address lookup on the server)
  • may come with a web app?
  • less of an evil hack than our current crash reporter
  • objc support? (cbarrett will investigate)

Next meeting

Ping the list, somewhere around the 16th (but maybe not on that date, to avoid a release party).

What worked and what didn't

  • Good meeting, over all!
  • Scheduling not good for some people

Log

TownCrier's log.