[Mailman-Developers] Fwd: Re: GSoC 15 - Interested in contributing to Postorius​

[y1dothie at gmail.com]

(Sorry Stephen)

---------- Forwarded message ----------
From: "Akshay Shah" <y1dothie at gmail.com>
Date: Wed, Mar 25, 2015 at 12:21 AM
Subject: Re: [Mailman-Developers] GSoC 15 - Interested in contributing to Postorius
To: "Stephen J. Turnbull" <stephen at xemacs.org>

> I wanted to work on "Feature request: Editable fields in User profile
> <https://bugs.launchpad.net/postorius/+bug/1432383>" in the postorius web
> ui. Would this be an easy enough issue to pursue? Where do I ask if I have
> any questions about it? I have already commented on the page but not reply
> yet.
> On Tue, Mar 24, 2015 at 8:41 AM, Stephen J. Turnbull <stephen at xemacs.org>
> wrote:
>> Akshay Shah writes:
>>
>>  > My name is Akshay Shah.
>>
>>
>> Pleased to meet you, Akshay.  Welcome to Mailman!
>>
>>  >  1. Can the Dashboard and Subscriber profile page be done together
>>  >     within the GSoC timeline?
>>
>> I think this would not be useful as the users' tasks are quite
>> different.  It's better to pick one and do a super job on it than to
>> do merely satisfactory work on both.
>>
>>  > 2. I have fairly good amount of experience with NodeJs, will my
>>  >    resume be a good enough factor for you to decide or would you
>>  >    rather have me do a pre-project (I would love to do a
>>  >    pre-project)?
>>
>> Rather than a pre-project we prefer you to do a bugfix.  Any bug, easy
>> is OK.  Feature implementation is also OK.  The point is that you
>> become familiar with our workflow as much as it is for us to see your
>> work output.
>>
>> https://bugs.launchpad.net/mailman
>>
>> Use the "advanced search" link with tag = easy (the tag entry field is
>> way down at the bottom).  Note that most of the "easy" issues seem to
>> be "taken" in that somebody's already working on them, check the
>> comments to find out who.  Most likely most of the issue have *not*
>> been checked for "easy" so don't let lack of an "easy" tag stop you
>> from working on an interesting issue.  If it isn't clear how to
>> proceed after a few minutes, you might want to ask here if the issue
>> is maybe "too hard" for a GSoC application before continuing (and
>> maybe try a different issue in the meantime).
>>
>>  > 3. [NEW IDEA] Introducing search feature in the Web UI. Search
>>  >    lists, members, settings, and/or domains. Would introduction of
>>  >    Elastic Search with NodeJs be a feasible option for the GSoC
>>  >    Timeline? How detailed should I get about introduction of this
>>  >    topic?
>>
>> I don't see why this feature needs to be so complex.  There are a few
>> sites like universities and project "forges" that deal with thousands
>> of lists and tens of thousands of users, but "thousands" is still easy
>> and efficient enough to do with a simple database lookup (and regexp
>> matching on the results if desired) through the Django ORM (HyperKitty
>> and Postorius) or SQLAlchemy and the REST interface (Mailman core),
>> and it will be consistent with the code in the rest of the
>> applications.
>>
>> If you have use cases where a more complex search would be helpful,
>> please explain it.
>>
>> Regards
>>
>>