[Systers-dev] status report GSoC for Systers

[Robin Jeffries]

Some comments (I sent you a lot of comments on your code separately)

On Sat, Jun 27, 2009 at 2:18 PM, Anna Granudd <anna.granudd at gmail.com>wrote:

> Hi,
> time for the next status report. During the last two weeks I was supposed
> to have finished documentation and working on one more bug. After consulting
> my mentors though, they agreed that I could keep working on the
> documentation at the end instead (when I better understand the code) and for
> the moment resolving bugs
> Hence, what I've done in the last two weeks was working on and resolving
> the following issue:
>   -adding a possibility to respond to archive messages
>   -check signup form for blank essay
>   -separated essay from dlist and making it possible to have either no
> essay in a dlist or an essay in a non dlist
>   -found an error in the code that made all new lists dlists, fixed this so
> either dlist or non list could be chosen


>   -possibility for the list creator to chose what text to have in the
> questions for the essay


I didn't understand how the UI for this works.  Can you show me where that
is?
It is possible to chose the essay related text in the current system by
modifying the template file.  Can you tell me why your solution is better
for the list creator?


>   -adding a debug mode that controls the verbosity of the logs (I need
> feedback on what should (not) be written to logs in production mode)


This is a WONDERFUL feature -- it turns on and off the info log.  Others of
you should enable this as soon as we have it integrated.

>
>
> Sorry for not writing out the exact names and numbers of the bugs, I don't
> have access to internet at the time I write this (I'll send the email as
> soon as I get online).
>
> For the next two weeks I'll continue fixing the unsubscribtion from a
> conversation by clicking the link in an email of a conversation. If someone
> could please tell me how this acctually works today when clicking the link I
> would appreciate this a lot, I couldn't manage to unsubscribe myself from a
> conversation without unsubscribing from the entire list (using the current
> link).
> Hopefully Robin will get better soon so we can take a look at the database
> inconsistency together, trying to resolve this as well.


Did you see the comments I put in the bug report?

If you start on the database/email unsubscribe problem, can you make that a
new branch, as we might want to integrate it before we integrate your other
stuff.

Get as far as you can with the database inconsistency issue, asking
questions as you encounter them, and if I can't get back to you immediately,
you can work on other stuff till I can.


>
>
> Another issue that I'd like some help resolving is that after working on
> dlists and non dlists the subscribers of a non dlist no longer receive email
> from the conversations but the emails only end up in the archives. Also,
> when writing an email to the list the +new feature works for dlists as well
> as for non dlists (indicating still some error when creating the list). Any
> ideas on how to fix this?


I sent you a pointer to what I think the emails only being in the archives
problem is.  The lack of  +new working for dlists is a bug that didn't used
to be there, so I think that +new working for non-dlists is also the same
bug.  I suspect it has to do with the bug about all lists being dlists (or
has to do with your fixes to that bug)

Robin


>
> Wish you all a nice weekend and thanks,
> Anna
>
>
>
> On Sat, Jun 13, 2009 at 5:31 PM, Robin Jeffries <robin at jeffries.org>wrote:
>
>>
>>
>> On Sat, Jun 13, 2009 at 1:51 AM, Anna Granudd <anna.granudd at gmail.com>wrote:
>>
>>> Hi,
>>> those of us participating in GSoC 2009 for Systers were asked to send in
>>> a
>>> status report every two weeks, so here's my first.
>>>
>>>
>>>
>>> Finally a question. I started setting my dev. env. up using Kubuntu 9.0.4
>>> and Python 2.6.2 figuring that newer versions of Python and Ubuntu than
>>> recomended from Systers probably shouldn't cause any problems. Halfway
>>> through I noticed that the version of Mailman Systers use (2.1.10) wasn't
>>> compatible with these (apparently a known bug if you google it) so I had
>>> to
>>> start over and install the recomended Ubuntu 8.04 and Python 2.5. No
>>> problem
>>> so far, my only question is if there are any plans on updating the
>>> version
>>> on Mailman we use to the newer 2.1.12, which is compatible with the newer
>>> versions of Python etc? Just out of curiosity (btw, I also noticed how
>>> much
>>> I had missed the older version of Ubuntu so I'm happy being back to this
>>> anyway :) )
>>>
>>
>> That certainly on our list, but right now, as you will see when you start
>> fixing bugs, it's a lot of work to update, as there are some fixes that are
>> not well separated in the code (some because of earlier programmers not
>> taking this into account, some because none of us have figured out how to do
>> it).  So it becomes a project in itself (probably a week's worth of work
>> full time, more if some change is incompatible with what we are doing),
>> probably something we will do this fall or winter.  We thought that getting
>> these bugs fixed (and some of the other projects) would get us closer to
>> being able to merge our changes with mainstream mailman, and then we won't
>> have this problem each time mailman updates.  (That's the long term goal.)
>>
>> And, thanks for the status report.
>>
>> Robin
>>
>>
>>>
>>>
>