[Mailman-Developers] GSoC Project: pgp plugin

Jonas jonax at openmailbox.org
Tue Mar 22 09:30:49 EDT 2016


I was not going to exclude anyone from a discussion relevant to them or
start an offtopic conversation.

I uploaded my draft yesterday, summerofcode.withgoogle.com worked after
I switched from firefox to chromium.
However to update the file to my local working copy – I can't help it– I
had to create a new file and update the proposal url on my dashboard so
please make sure to look at the most recent links. You should find my
2nd GSoC Proposal Draft on your dashboard. Any feedback would be very
much appreciated.

On 18.03.2016 23:17, Abhilash Raj wrote:
> We need you to fix one easy bug so as to judge your capability to
> actually implement the proposal that you are proposing. Although, we
> have mandated one patch towards your application, a small documentation
> patch and some of your previous patches to different projects
> (preferably, but not required, in Python) could work. Does that sound
> good? I can point you to several places we need more documentation ;-)

I would appreciate that.
I guess if it doesn't neccesarily has to be merged, I will get to make a
mr until friday and include it in my proposal (by now, at least my
gitlab id is there).
Also, if neccesary, I can show you some more very small patches I have
contributed to other projects over the years, it would just take some
time to dig them up.




On 19.03.2016 04:22, Stephen J. Turnbull wrote:
>  > > And/Or Abhilash Raj, may I send you those?
>  > 
>  > I guess you can upload drafts of proposal (in google docs) on
>   > GSoC's website and we all mentors can have a look at it/comment on
>  > it if needed.
> 
> Please do register and upload a draft as soon as possible, even if
> very incomplete.  The Google SoC system is all-new this year, and has
> been distinctly slow the last day or two since student applications
> opened.  I don't expect it to crash, but if it does, *it is not an
> excuse for not being registered*!  That's Google policy; if you don't
> have an application on file by the deadline date, you *cannot* become
> a GSoC intern.  We have zero input to this policy.  OTOH, we can work
> around incompleteness in the event of system problems.
> 
> I haven't seen the student UI, but I've heard that you can mark your
> proposal "draft" (or maybe you have to mark it "final", which amounts
> to the same thing).  So you don't have to worry that an incomplete
> draft will count against you (in Mailman, we don't make judgments
> until applications close in any case).
> 
> If the draft seems *wrong* in some place, we'll let you know about
> that quickly.  If it's still incomplete on 3/22 or so, we'll ping you
> about that.
> 
>  > > To make a first impression, I thought about writing a general
>  > > blog post on the state of mailinglist/group communication
>  > > encryption that covers the efforts toward encrypted lists in
>  > > mailman.
> 
> That's a good idea in itself, but not a substitute for a patch.
> 
>  > > Could that work as a first impression instead of fixing
>  > > a bug in mailman? The easier ones seem to get patched faster than
>  > > I can catch up.
>  > 
>  > We need you to fix one easy bug so as to judge your capability to
>  > actually implement the proposal that you are proposing.
> 
> That's somewhat inaccurate.  The reasons you need to fix a *Mailman*
> bug are
> 
> 1.  You have to post a merge request, which means
> 2.  you know a little bit about our Gitlab repos, and
> 3.  a little bit about Gitlab, and
> 4.  have a Gitlab account.
> 
> That might not be a problem for you, but we've had issues in the past
> where the student floundered for a couple weeks midproject with the
> registration and submission procedure.
> 
> To judge implementation ability, other projects you've done or
> contributed to are valid evidence, of course, as long as you can point
> us to the code.
> 
>  > I can point you to several places we need more documentation ;-)
> 
> I don't care who does it (Abhilash direct-to-tracker, or Abhilash-to-
> Jonas-to-tracker), but please make sure all are filed on the tracker.
> 



More information about the Mailman-Developers mailing list