Sumana Harihareswara writes:
> http://en.flossmanuals.net/GSoCStudentGuide/
> http://www.harihareswara.net/sumana/2013/05/12/1 and
> http://www.harihareswara.net/sumana/2014/02/26/0 helpful in guiding you.
Thanks for the blog references!
But these are generic, do you have anything more about t
Hello,
I'm Ana Badescu, and I'm a first year Artificial Intelligence graduate at
Polytechnic University of Bucharest, Faculty of Automatic Control and
Computer Science, looking to participate in GSOC 2015, hopefully with
Mailman!
You might believe that I arrived late. However, I have just install
This is spam. Don't do it without checking with the list owner
(coursemailman-developers-ow...@python.org) first.
Brianna Laugher writes:
[spam deleted]
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/
Please don't repost material you've already mostly posted. Just put
your proposal in Melange and we'll get to it. Unless you're getting
close to your limit of 5 (or whatever, that was the limit last year),
in which case you should ask the GSoC staffers how to withdraw
proposals you aren't going t
Andrew Stuart writes:
> I assume a great deal of thought has gone into message threading
> and how it works. Is there anyone willing to share the basics with
> me - specifically as it relates to Mailman and related projects?
Currently Mailman and Postorius don't care at all. HyperKitty has it
Hi!
First, let me thank you all for your applications. I was a little
worried when were approved as an org ourselves, but we've got a bunch
of good ideas and nicely done applications here, so we aren't going to
have trouble filling our slots, I think.
Second, I don't necessarily speak for the ot
Murray S. Kucherawy writes:
> The difference between this idea and "l=" is that there's still a
> signature covering the added part, that of the MLM.
No, there isn't, not when it leaves the poster's MTA. This is the
same for your proposal and for "l=".
People have learned to deal with top-pos
prakhar joshi writes:
> what if we create separate tables for each class in the
> mailman/src/mailman/styles/base.py and store the name and their attributes
> in it with user_name with it.
Who are these "users" (subscribers? admins?) and why do you want to
associate styles with users? Please
prakhar joshi writes:
> One thing how these templates will be stored for the user is still a doubt
> for me ? Can you please help me with that ?
Not until late next week. I haven't thought about the problem at all.
Anyway, designing the implementation is really your job.
Here's how I would g
Refer to the bottom of this email for some previous quotes from @barry on this
topic. I’ve also had off list discussions with Barry in which he has mentioned
this same topic so it seems to have some previous thought gone into it.
I’m wanting to raise the topic of “fine grained subscription cont
Hi,
I am Prabhanshu Abhishek, second year undergraduate student at Indian
Institute of Technology,Kanpur (IIT Kanpur), studying Computer Science and
Engineering.
I am very much interested in the project GitHub/Development tools
integration under Gsoc'15.
I have given much thought on how it can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 18.03.2015 um 16:29 schrieb Prabhanshu Abhishek:
> 2)the gsoc idea page says that it is necessary to fix at least one
> bug, but i have not been able to find some bug that is beginner
> friendly and related to my project, can you give me some bug
Hi folks
I assume a great deal of thought has gone into message threading and how it
works. Is there anyone willing to share the basics with me - specifically as it
relates to Mailman and related projects?
There is of course plenty of information on google which I am researching
including the
Hello
I recently submitted my proposal for Dynamic Sublists, since I haven't had
much discussion on this idea with mentors it would be nice to have some
reviews. I request Terri, Barry and Steve to have a look whenever they find
suitable and other mentors can also help me if they wish too.
There
Hello. I am the person who originally wrote up this idea. I am not going
to mentor it; I am not skilled enough at working with Mailman, and I
have other time commitments, so I will not be mentoring this or any
other Google Summer of Code student or idea.
On 18/03/15 12:48, Stephen J. Turnbull wrot
On Tue, Mar 10, 2015 at 6:51 PM, Stephen J. Turnbull
wrote:
> > It's certainly the case that this proposal only deals well with
> > footers. The specific algorithm is to construct a MIME tree and
> > sign parts of it; specifically, sign all of it, and then verify all
> > of what you get firs
Hey Barry,
Do you think I can help you work on that? Or would you prefer doing the
initial branch resurrection?
Anything I need to know before I start?
Any mention of "the one big feature needed before core can be released"
tends to make me a little bit nervous, and I try to avoid being nervous ;
what if we create separate tables for each class in the
mailman/src/mailman/styles/base.py and store the name and their attributes
in it with user_name with it. I think the attributes for the classes
defined already will be fixed? So now if we feel the requirement of
including new things to style (
hi,
so we should have templates already created in a folder with default
values of the attributes in it. the templates will be of "BASIC OPERATION",
"BOUNCES" etc. and under each of the template we will gonna have
attributes for it and then we can apply these templates on the list and
even us
Few other points:
* You need to submit your proposals to GNU Mailman organization and *not*
Python Software Foundation like last year. We have been selected as a
separate organization this year.
* The application template is up on melange, please have a look before you
submit your applic
20 matches
Mail list logo
