[Systers-dev] GSoC Project Status - Students

[erica]

Hi all,

I've blogged: 
http://sherprog.com/teamwishlist/2010/06/06/progress-report-%E2%80%93-week-2-ending-6610/

This week was spent trying to reproduce bug 495331 and, upon failing to 
reproduce the bug, looking through code applicable to it.  While looking 
through the code with my mentor, Anne, we came across some extraneous 
code in Mailman.  I submitted the bug to Mailman and the suggested patch 
has been committed and will appear in Mailman 2.1.14.  I also wrote up a 
"How to submit a bug to the Mailman project" in the Systers Development 
Resources wiki.

Anne and I have another code reading session Monday and I plan to 
continue trying to reproduce the bug and read code surrounding the issue.

I have not been able to reproduce the error message in question.  This 
has made it quite difficult for me to determine a course of action 
towards fixing the bug.

erica

On 6/6/2010 10:14 AM, Anna Granudd wrote:
> Hi,
> I've been working with Barry to be able to install Mailman 3.0 after
> updating from karmic to lucid. I've also been designing the db for the UI
> and send my suggestion to both the Mailman developers list and to this list,
> systers-dev. I would appreciate if you could take a look at it when you find
> the time and tell me your opinion on it, the email can be found here:
> http://systers.org/pipermail/systers-dev/2010-June/000491.html and the
> suggestion here: http://wiki.list.org/display/DEV/Web+Interface+Status So
> far I only got answers from the Mailman developers list but I need your
> thoughts too before I start writing models that we may not be able to use
> later if the design proved wrong or I missed something essential. I think we
> need to have general DB discussion since it seems to relate to many of the
> projects this summer. Maybe an IRC meeting would be a good idea? Finally
> I've discussed how to best proceed with the UI and general decisions
> regarding it, such as communication with DB('s) only via the rest-client
> with my mentor Florian. So far I didn't update my blog...
>
> Thanks,
> Anna
>
>
> On Sun, Jun 6, 2010 at 11:43 AM, Yian Shang<yian.shang at gmail.com>  wrote:
>
>    
>> I've blogged:
>>
>> http://movicont.nfshost.com/blog/on-internet-and-the-mailman-archives-ui-survey
>> .
>> I'm thinking that all systers-related blog posts should be here:
>> http://movicont.nfshost.com/blog/tag/systers-dev
>>
>> Over this week I've been working on modifying/finalizing my use cases after
>> looking at the data obtained from the archives ui survey. I've also put
>> some
>> of this progress up on the wiki.
>>
>> I've also been looking through the code to try to figure out where to
>> modify
>> things for the archives ui. Hopefully by the beginning of next week the use
>> cases will be done and I can proceed with the coding.
>>
>> <
>> http://movicont.nfshost.com/blog/on-internet-and-the-mailman-archives-ui-survey
>>      
>>>        
>> --
>> Yian || http://movicont.nfshost.com/
>>
>>
>> On Sun, Jun 6, 2010 at 4:59 AM, स्वक्ष<vid at svaksha.com>  wrote:
>>
>>      
>>> On Sun, Jun 6, 2010 at 01:42, Jennifer Redman<jenred at gmail.com>  wrote:
>>>        
>>>> Would each GSOC student please post a status repot to this list about
>>>>          
>>> where
>>>        
>>>> you are in your project progress. It can be short but should include:
>>>>
>>>> 1 - What you've done so far
>>>> 2 - What you plan to accomplish in the next week.
>>>> 3 - Any problems you've encountered or questions you have.
>>>>
>>>> If you've blogged - please post a link.
>>>>          
>>> http://svaksha.com/category/libre
>>>
>>> With Jason and KJR, I'm supposed to be testing bug 583379 but am
>>> waiting for Kanika's feedback on
>>> http://systers.org/pipermail/systers-dev/2010-June/000504.html
>>>
>>> I'm trying out local installations of some web-testing tools and for
>>> one of them (funkload) I got some weird errors. Since I was trying it
>>> on 10.04 and getting errors, I tried it out with Hardy and it removes
>>> some packages that are a part of the MM and systers installation.
>>> Strange.
>>>
>>> $ sudo aptitude install tcpwatch-httpproxy --without-recommends
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Reading extended state information
>>> Initializing package states... Done
>>> Writing extended state information... Done
>>> Building tag database... Done
>>> Couldn't find any package whose name or description matched
>>> "tcpwatch-httpproxy"
>>> Couldn't find any package whose name or description matched
>>> "tcpwatch-httpproxy"
>>> The following packages are unused and will be REMOVED:
>>>   procmail sendmail-base sendmail-cf sensible-mda
>>> 0 packages upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
>>> Need to get 0B of archives. After unpacking 3191kB will be freed.
>>> Do you want to continue? [Y/n/?]
>>> Writing extended state information... Done
>>> (Reading database ... 151156 files and directories currently installed.)
>>> Removing sensible-mda ...
>>> Removing procmail ...
>>> Removing sendmail-base ...
>>> Cleaning up the queues...find: /var/spool/mqueue: No such file or
>>>        
>> directory
>>      
>>> done.
>>> Removing sendmail-cf ...
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Reading extended state information
>>> Initializing package states... Done
>>> Writing extended state information... Done
>>> Building tag database... Done
>>>
>>> Ben, the developer, has been emailed with more logs of all the errors
>>> on each partition and I am awaiting some feedback. Meanwhile, I'm
>>> planning to try out other tools this week.
>>>
>>> With patching, i've got to build a .dsc file from the stable branch
>>> checked out earlier, which is one of the other tasks planned this week
>>> (....considering that its 3am on sunday here).
>>>
>>> have a nice weekend!
>>> --
>>> thanks and regards,
>>> vid || http://svaksha.com
>>>
>>>
>>> To unsubscribe from this conversation, send email to<
>>> systers-dev+students+unsubscribe at systers.org<systers-dev%2Bstudents%2Bunsubscribe at systers.org>
>>>        
>> <systers-dev%2Bstudents%2Bunsubscribe at systers.org<systers-dev%252Bstudents%252Bunsubscribe at systers.org>
>>      
>>>>          
>>> or visit<
>>> http://systers.org/mailman/options/systers-dev?override=126&preference=0
>>>
>>> To contribute to this conversation, use your mailer's reply-all or
>>> reply-group command or send your message to
>>> systers-dev+students at systers.org<systers-dev%2Bstudents at systers.org>  <
>>>        
>> systers-dev%2Bstudents at systers.org<systers-dev%252Bstudents at systers.org>>
>>      
>>> To start a new conversation, send email to<systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
>>>        
>> <systers-dev%2Bnew at systers.org<systers-dev%252Bnew at systers.org>>
>>      
>>>>          
>>> To unsubscribe entirely from systers-dev, send email to<
>>> systers-dev-request at systers.org>  with subject unsubscribe.
>>>
>>>        
>>
>> To unsubscribe from this conversation, send email to<
>> systers-dev+students+unsubscribe at systers.org<systers-dev%2Bstudents%2Bunsubscribe at systers.org>>
>> or visit<
>> http://systers.org/mailman/options/systers-dev?override=126&preference=0>
>> To contribute to this conversation, use your mailer's reply-all or
>> reply-group command or send your message to
>> systers-dev+students at systers.org<systers-dev%2Bstudents at systers.org>
>> To start a new conversation, send email to<systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
>>      
>>>        
>> To unsubscribe entirely from systers-dev, send email to<
>> systers-dev-request at systers.org>  with subject unsubscribe.
>>
>>      
>
> To unsubscribe from this conversation, send email to<systers-dev+students+unsubscribe at systers.org>  or visit<http://systers.org/mailman/options/systers-dev?override=126&preference=0>
> To contribute to this conversation, use your mailer's reply-all or reply-group command or send your message to systers-dev+students at systers.org
> To start a new conversation, send email to<systers-dev+new at systers.org>
> To unsubscribe entirely from systers-dev, send email to<systers-dev-request at systers.org>  with subject unsubscribe.