[Pharo-project] [Pharo-users] Need someone to lead Fix of the Day contest [WAS] Re: Need help with 1.3 Full Image

laurent laffont laurent.laffont at gmail.com
Sun May 15 08:07:26 CEST 2011


Another idea is to have the issues list sorted by id desc (most recent on
top) instead of older ones on top.

Laurent.

On Sat, May 14, 2011 at 10:04 PM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:

>
>
> On Sat, May 14, 2011 at 8:53 PM, Pat Maddox <patmaddox at me.com> wrote:
>
>> On May 14, 2011, at 9:53 AM, laurent laffont wrote:
>>
>> On Sat, May 14, 2011 at 6:30 PM, Mariano Martinez Peck <
>> marianopeck at gmail.com> wrote:
>>
>>>
>>>
>>>>> I try to solve some issue in the issues tracker from time to time, but
>>>>> it's often difficult
>>>>> when outside your expertise. So doing it with others might definitively
>>>>> help.
>>>>>
>>>>
>>>>
>>>> Fix of the day contest has the advantage of being compatible with every
>>>> people timezone / agenda.
>>>>
>>>> We can also synchronize CODTC and FOTDC in order to comment classes
>>>> related to the fix.
>>>>
>>>> Now we just need someone to lead the FOTDC. I already do COTDC so is
>>>> there a good soul ?
>>>>
>>>>
>>> well, I've started by renaming the thread and attaching Pharo-users.
>>>
>>> Laurent, maybe you should clarify what "lead"  exactly means.
>>>
>>
>>
>> Everyday:
>> - choose an issue for the contest
>> - write it to the mailing list
>> - push to ask help
>> - contest is done when a slice is put in inbox
>>
>>
>> Indeed, much like COTDC is.
>>
>> Laurent.
>>
>>
>> That would be awesome! I was looking at the bug tracker (
>> http://code.google.com/p/pharo/issues/list#) yesterday to see if there
>> were things that I could help with...but even when looking at "open" issues,
>> many of them are several years old, and have a state of "Accepted." So as
>> someone not actively involved in pharo development, I have absolutely no
>> clue what actually needs to be fixed.
>>
>> I'd like to help, the bug tracker doesn't give me much guidance (or at
>> least I'd benefit from an explanation of how it's structured), and so
>> guidance from someone who's active would be really helpful.
>>
>
>
> You can also check those tagged as milestone 1.3 which means that they
> "should" be more or less new.
>
> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3+&colspec=ID+Type+Status+Summary+Milestone+Difficulty&cells=tiles
>
> cheers
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110515/63b345e9/attachment.htm>


More information about the Pharo-project mailing list