Adium 1.4b18/1.3.11?
Jordan
jas8522 at gmail.com
Mon Apr 26 12:36:11 UTC 2010
Why don't we shoot for Tuesday the 11th then? I see someone (seemingly
David Munch) added the meeting on Trac:
http://trac.adium.im/wiki/AdiumMeetings
I put up a rough skeleton of an agenda - feel free to add/remove/change things.
Jordan
On Sat, Apr 24, 2010 at 1:07 PM, Eric Richie <eric at adium.im> wrote:
> If you guys think they'll be helpful, then sure, let's do it. Before it was
> getting to the point where they didn't seem to really be worthwhile because
> no one had much of any time to act on the things we discussed.
> What nights would work best for everyone? We should probably continue to
> have them on a weeknight as we have previously. Mondays and Tuesdays are
> probably the most convenient for me but if something else works better for
> the majority then I can do that as well.
> Let's shoot for the 2nd week of May as our target for the next one so that
> we can discuss any issues that come up in meeting Evan's suggested deadline
> for 1.4. Sound good? Just let me know when people think they might be
> available so we can pick a time.
>
> -Eric
>
>
>
> On Apr 24, 2010, at 9:40 AM, shawn khan wrote:
>
> Hello,
>
> I know I am new to the adium project and code. I just want to give my
> opinions on meetings. I believe that meetings will help move the code
> forward even if a little bit at a time. I believe we should do this
> bi-weekly. As I know these meetings will help new developers get into the
> code and project.
>
> Thanks,
> Shawn
>
> On Sat, Apr 24, 2010 at 9:00 AM, Jordan <jas8522 at gmail.com> wrote:
>>
>> I realize there might be a bit of a stigma associated with meetings
>> and that there'll always be a few people who can't make them, but I
>> think that regular meetings (bi weekly or at least monthly) might help
>> spur development. This includes our formerly active developers and the
>> new folks who might have a few questions and would like to get more
>> involved in the processes we use to decide on inclusion of new
>> features (among other things).
>>
>> It would also help us come to consensus for dates to set our
>> milestones - we used to follow them somewhat closely and it worked
>> fairly well. We could also go over some of those remaining tickets in
>> 1.4 and try to have Robby and I (and others?) help triage the
>> remaining 1.4 tickets. For example, we could specify a critical
>> priority for tickets to be placed in the 1.4 milestone.
>>
>> If not regular meetings, then we should probably at least have one
>> before the release of 1.4 just to make sure everyone is on the same
>> page. Although we do a pretty good job of keeping Trac in-line with
>> our priorities (minus some of the newer tickets that haven't been
>> triaged yet), there are always some things that are ambiguous and
>> should be discussed.
>>
>> Thoughts on this? Was it Thursdays we used to hold them on in previous
>> years?
>>
>> If Eric is OK with this, then he and I could take care of arranging it
>> as he and Chris had done in previous years.
>>
>> Have a great weekend everyone!
>>
>> Jordan
>>
>>
>>
>> On Sat, Apr 24, 2010 at 7:14 AM, Robert Vehse <robert.vehse at gmx.de> wrote:
>> >
>> > Am 24.04.2010 um 07:59 schrieb Christopher Forsythe:
>> >
>> >> I'm sorry, I mistook the 11 tickets not to a severity of Major or
>> >> Regression to mean that weren't as important as the 4 in those
>> >> severities.
>> >> If you think that keeping tickets which are "minor" in the milestone, I
>> >> guess the meaning of the minor severity has changed in a way that I was
>> >> not
>> >> aware of.
>> >>
>> >> My apologies for any offense, none was meant. I was only pointing out
>> >> that
>> >> the easiest thing to do to to get a release out is to get a few things
>> >> off
>> >> the list which can wait for a later release.
>> >
>> > No worries. I think I overreacted. Some of the tickets are not marked as
>> > they should be though.
>> >
>> >
>>
>
>
>
More information about the devel
mailing list