On Fri, Jun 12, 2015 at 5:41 PM, Walty Yeung <[email protected]> wrote:

>
>
> On Friday, May 15, 2015 at 8:05:24 AM UTC+8, Walty Yeung wrote:
>>
>>
>>
>> On Thursday, May 14, 2015 at 5:24:27 AM UTC+8, RjOllos wrote:
>>>
>>> On Mon, May 11, 2015 at 9:53 AM, RjOllos <[email protected]> wrote:
>>>
>>>>
>>>>
>>>> On Saturday, May 9, 2015 at 11:21:56 PM UTC-7, Walty Yeung wrote:
>>>>>
>>>>> and my question is, is the bite-sized tasks (
>>>>> http://trac.edgewall.org/query?status=new&status=assigned&status=reopened&keywords=~bitesized&group=component&order=priority)
>>>>> still the optimal entry point of contribution now? I asked only  because I
>>>>> saw most of the tickets there are actually pretty old, and I am not sure 
>>>>> if
>>>>> they are actually outdated now, however, I don't mind to start with the
>>>>> minor changes at all.
>>>>>
>>>>
>>>> In case you are looking for specific suggestions on where to start,
>>>> #11937 should be fairly tractable:
>>>>
>>>> http://trac.edgewall.org/ticket/11937
>>>>
>>>
>>> In case I've led you into a ticket that is more challenging than it
>>> seemed from the outset, please don't be afraid to work several tickets in
>>> parallel. That's usually what I do since I like the feeling of progress
>>> from knocking out a ticket or two each week, and not every ticket I pickup
>>> leads to immediate progress.
>>>
>>> - Ryan
>>>
>>
>>
>> No problem, I would have a look of other bite-sized tickets under the
>> milestone of  next-dev-1.1.x
>> <http://trac.edgewall.org/milestone/next-dev-1.1.x>
>>
>> Thanks.
>>
>
>
> hi,
>
> I am sorry that I bring up this thread again.
>
> I have recently made the patch for #10144 and #11937 about 3 weeks ago,
> and I still have no idea if such patches are fine or not.
>
> Please don't misunderstand me, I am not trying to push for anything, but I
> would like make sure I am on the right track (the patch format, style, and
> code quality etc...) before I move on to other tickets.
>
> thanks.
>

Hi Walty,

I'm sorry for the delay, and thank you for bearing with us. I'll try to
review your patches for tomorrow, and also suggest some tickets that are a
bit more straightforward to implement.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to