Tuesday is NSCoderNight for the SF folks. Which is perfect. I can yell at
people to get on irc in person.
David
On May 3, 2010, at 7:44 PM, Evan Schoenberg, M.D. wrote:
>
> On May 3, 2010, at 1:35 PM, Eric Richie wrote:
>
>> I'm good with Jordan's suggestion of Tuesday the 11th if that works
>> for the others who were interested in attending.
>
> That'll work for me.
>
> -Evan
>
>>
>> -Eric
>>
>> On Mon, May 3, 2010 at 2:30 PM, shawn khan <shawn.k...@gmail.com> wrote:
>>> Hello,
>>>
>>> Is there a date on the meeting? I think that we should still try to have
>>> one, this will give new programmers and existing ones a chance to know how
>>> to really move forward.
>>>
>>> Thanks,
>>> Shawn
>>>
>>> On Mon, May 3, 2010 at 1:11 PM, Eric Richie <e...@adium.im> wrote:
>>>>
>>>> On Wed, Apr 21, 2010 at 12:11 AM, John Bailey <rekkano...@rekkanoryo.org>
>>>> wrote:
>>>>> On 04/20/2010 11:22 PM, Eric Richie wrote:
>>>>>> Are there any outstanding issues other than the Y! thing (and maybe the
>>>>>> MSN security patch) that we would need to take care of for 1.3.11?
>>>>>
>>>>> Gadu-Gadu support in the libpurple 2.5.9 included in Adium 1.3.10 is
>>>>> quite
>>>>> deficient as well, due to the bundled libgadu being practically
>>>>> prehistoric. It
>>>>> looks like the following revisions from the im.pidgin.adium.1-4 branch
>>>>> would
>>>>> need to be plucked (if cleanly possible) to the im.pidgin.adium.1-3
>>>>> branch to
>>>>> fix both Gadu-Gadu and Yahoo! JAPAN:
>>>>>
>>>>> e6348335d02982e12c2be1a30517d7ea46569c51
>>>>> 48c2553ef4b46482b26f021c97d2569c1b053227
>>>>> 6a525a20cfffe39369fb58b72aeaf5194aa468d9
>>>>> 692d75f8dc28e433931f5a4b036c145f132c42ba
>>>>> 91e41e5288f7f90048a8cf7d05bedc87aacfa3de
>>>>> 47085b9fe64551b697ca9ba601b8c0323e47c449
>>>>>
>>>>> I have not yet tried to apply these revisions to the adium.1-3 branch.
>>>>> I don't
>>>>> see a point in doing that until there's a decision about whether a
>>>>> 1.3.11 is
>>>>> necessary. Also, I'm not sure what revision would be necessary for the
>>>>> MSN
>>>>> security fix mentioned. If someone does know, I'd be happy to pluck it
>>>>> across
>>>>> with the others listed above when a decision is reached.
>>>>
>>>> We need to move forward with this. John, if you get a chance would
>>>> you mind plucking those changes for us? (If someone does happen to
>>>> know that changeset for whatever that MSN fix was, please speak up.)
>>>> Once those changes are merged I'll try to make some time and get a
>>>> 1.3.11b built later this week so we can verify the fixes before
>>>> releasing shortly thereafter.
>>>>
>>>> -Eric
>>>>
>>>
>>>
>>
>
>
