Re: [FE-discuss] Weekend IRC Based Sprint

Hi,

My project releases just got pushed back due to a delay in getting
hardware so my schedule just changed and I will be occupied the
weekends of Sept 24, Oct 1 and Oct 8.  The weekend of Sept 24 is
likely to be the least busy of those for me if it needs to be one of
those weekends. My other weekends look to be fairly free at this
point.

-Chris

On Tue, Aug 30, 2011 at 9:45 AM, Chris Lambacher <ch...@ka...> wrote:
> Hi,
>
> The following weekend, Oct 8, would also be okay for me, but I'm in
> Canada and that is our Thanksgiving weekend so I am likely to have
> some responsibilities around that (we are hosting this year).
>
> -Chris
>
> On Tue, Aug 30, 2011 at 6:22 AM, Christoph Zwerschke <ci...@on...> wrote:
>> Am 30.08.2011 04:59 schrieb Chris Lambacher:
>>>
>>>  - Bugs:
>>>       - fix the critical ones so that we can do a 1.2.5 release and
>>> start on a 1.3.x series that can break compatibility with Python 2.3
>>> (see https://sourceforge.net/mailarchive/message.php?msg_id=27762170
>>> and related thread).
>>>       - Close enough that we can make a the move to the bitbucket
>>> issue tracker without to much effort to convert the existing bugs.
>>
>> That was what I had in mind.
>>
>>>  - Documentation:
>>>      - fill in the pieces that went missing like the validators page
>>> (is this from a partial conversion to Sphinx?)
>>
>> See Ian Wilson's patch which I have already committed.
>>
>>>      - move doc hosting to Read the Docs (we'll maintain
>>> formencode.org as the url)
>>
>> The main problem is getting autodocs to work on RTD. It seems the project
>> user needs to be whitelisted for that. I'll try to contact the RTD people
>> via IRC to solve this.
>>
>>> Discussion so far has revolved around it being over a weekend. I am
>>> pretty booked up through the end of September but the weekend of Oct 1
>>> looks like it will work for me. How does that suit other people?
>>
>> Unfortunately that's not possible for me. The weekends before or after would
>> be better.
>>
>> -- Christoph
>>
>
>
>
> --
> Christopher Lambacher
> ch...@ka...
>



-- 
Christopher Lambacher
ch...@ka...