I would like to narrow down and hone in on a few key points from my longer email moments ago: ---- I think Terri's email about GSoC is good in theory; the GSoC pages on the development homepage and linked to from there could use some work, and I am committing to begin addressing them, as of now ---- I think the "can I work with this" assessment is needed but I don't know exactly how to help but want to help very much ---- I am asking for some input regarding the best means for sharing the development environment image to be made available for interested contributors to mailman (.ISO? AWS image?)
Thanks for your time! R/Chris On Sat, Feb 16, 2013 at 7:19 PM, Chris Cargile <[email protected]>wrote: > Hi Terri (and others whom I have met yet): > As a newcomer, I would like to introduce myself to the team (aside from > Barry), since I have not previously been very active on the > mailman-development lists. Apart from having attended what I believe was > the most recent all-hands IRC meeting I really haven't chimed in much, and > most of what I have inquired/commented on has regarding installation and > where-to-dig-in stuff. > > Although this may seem a roundabout way of getting to a more substantive > point, I think it allows me to transition to Terri's points pretty easily: > as a newcomer to the MM3 playing field/GSoC, I think I can offer an > unbiased examination and reflection upon Terri's posting and suggestions > (not in respective order), as follows: > > 1) creation of a prove-your-skills-match or "can I work with this code > base" test would be of use as a self-assessment tool and/or possible aid > come time for GSoC mentoree applicant assessment. And to hopefully expand > on this a bit when I came into trying to grasp the architectural > fundamentals at work within Mailman without having examined the codebase, I > began reading through an article that Barry wrote in the AOSA > book<http://www.aosabook.org/en/index.html>, > which was great for me (but may not be "necessary" for others) and was able > to take this on the go vs. needing my laptop to view source code, etc - > thought I should suggest linking it on either the wiki, or dev portal > somewhere > > 2) I was able to get a VM instance of MM3 runnng based on the a) *Mailman > in 5 mins tutorial* and b) a bug clarification/workaround Barry > posted<https://bugs.launchpad.net/zope.interface/+bug/1090762> (following > our q&a in the IRC meeting in January). WRT development progress and the > outline of what's on the development roadmap, I struggled a little with > jumping right in (and was perhaps taking a direction altogether separate > from the consensus anyways) but I would like to: > - share my thoughts on the GSoC page (Terri linked to below); particularly > regarding the DEV home page and content for GSoC applicants (as disclosure, > I think I will be applying as one thereof in the near future) > - and I would be pleased to begin working on the sharing of an ISO or > other type of image that allows a quick initialization of the mailman > testing/development environment; I was thinking about approaching this from > a standpoint that AWS allows for easy virtual machine to run Ubuntu and it > worked for me getting a Mailman2 instance set up on > AWS<https://test.ncmacharleston.org/cgi-bin/mailman/listinfo>with relative > ease, going forward with setting up an AWS image (which > offers a WWW-accessible development instance, from the outset) > > I look forward to our future on these endeavors and learning how I can > best develop my skills, position myself as a better candidate for GSoC > mentorship (thru mailman or any other), and to seeing how I can propel the > project. > > Also, I would like to remotely attend the python sprint, if venue's > network connection allows > > See you soon - chris cargile > > On Sat, Feb 16, 2013 at 4:11 PM, Terri Oda <[email protected]> wrote: > >> I've set up an ideas page for Mailman in GSoC 2013: >> >> http://wiki.list.org/display/**DEV/Google+Summer+of+Code+2013<http://wiki.list.org/display/DEV/Google+Summer+of+Code+2013> >> >> Right now it's seeded with some particularly clearly-defined ideas I >> received by email, but more ideas are better, so please feel free to add >> things or modify the page (or argue about why it should be modified here). >> I'll be going through my own bug queues and other emails later this >> afternoon. >> >> Things I'd like to see other than ideas: >> - a VM we could hand out to students to shortcut the process of setting >> up a development environment >> - A set of simple assignments for students to try as a quick "can I work >> with this codebase?" test. >> >> I'm thinking things like "add inline help to one of the options in >> postorius and post your code as a branch on launchpad" that aren't >> technically terribly technically challenging. The idea is to give the >> students a task they can complete and give us something to require in their >> applications as proof that they'll be able to work with us. It's basically >> "solve an easy bug and post your code" but we'll want things more >> specifically defined in case the queue of easy bugs isn't so hot when the >> students start arriving. >> ______________________________**_________________ >> Mailman-Developers mailing list >> [email protected] >> http://mail.python.org/**mailman/listinfo/mailman-**developers<http://mail.python.org/mailman/listinfo/mailman-developers> >> Mailman FAQ: http://wiki.list.org/x/AgA3 >> Searchable Archives: http://www.mail-archive.com/** >> mailman-developers%40python.**org/<http://www.mail-archive.com/mailman-developers%40python.org/> >> Unsubscribe: http://mail.python.org/**mailman/options/mailman-** >> developers/follybeachris%**40gmail.com<http://mail.python.org/mailman/options/mailman-developers/follybeachris%40gmail.com> >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > > _______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
