[Soc-coordination] Please subscribe to the new Outreach list!
[Resending with the proper address T_T] Hi all, The new list for the Outreach Team (that will be used for GSoC and Outreachy announcements, as well as our interns' periodic reports) has now been created! Please go ahead and subscribe at https://lists.debian.org/debian-outreach/ The soc-coordination@l.a.d.o list will be discontinued as soon as possible, and will _not_ be used for the next round of programs. Cheers, -- Nicolas Dandrimont ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] Bug#798199: New list: debian-outre...@lists.debian.org
Package: lists.debian.org Severity: wishlist Hi all, I would like to request the creation of a new list, debian-outre...@lists.debian.org. Name: debian-outreach Short description: Public discussion of the Outreach Team's activities Long description: Discussion of Debian's participation in internship-like programs, such as Outreachy, Google Summer of Code, ... Program administrators and members of the Outreach Team will send announcements regarding Debian's participation to this mailing-list. Debian interns will send periodic reports of their work to this mailing-list. Rationale: The current mailing-list, soc-coordination on alioth, has become a burden as its name is GSoC-specific and, sadly, it is riddled with spam, which often makes gmail users get unsubscribed automatically after bounces. Now that the Outreach Team has been permanently delegated as such, and as we are between programs, now would be a good time to migrate to a proper, non-program-specific mailing-list on official Debian infrastructure. Category: I'm torn between Developers and Misc Debian, with a slight preference for the latter. Subscription policy: open Post policy: open Web archive: yes I'd like to bootstrap the list with the subscribers and archives from soc-coordination (although after a quick glance it doesn't seem possible to get those archives without admin intervention), please let me know how to provide them to you once the list is created! Thanks in advance, Nicolas for the Outreach Team. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] DebConf15: GSoC student talks
Hi all, The DebConf content team has confirmed that they have alloted us two back-to-back 45 minutes slots for GSoC student talks. As we expect around 10 students here, that will be plenty to fill the slots :) I would like to encourage all the students who did not submit a specific talk to prepare giving a talk during this session. This is a great way to show off your work and to make it known to the wider Debian community! There will be video coverage of the event, so your talk will be registered for posterity ! Please email me back with a synopsis of the talk you would be willing to present. I expect us to be able to give out 12-15 minutes slots (so being able to squeeze in 6 to 8 talks accounting for the regular break between 45 minute slots). The schedule is not final yet and therefore I'm not completely sure on what day that session will happen. However, I would like to collect all the slides as early as possible: I would like to avoid having to shuffle hardware around between short talks, so please make sure to have your slides available as PDF. Thanks, -- Nicolas Dandrimont BOFH excuse #329: Server depressed, needs Prozac signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] [GSoC students] Please register for DebConf15 now!
Hey all, I would like to remind everyone that if you want to come to DebConf, you need to register to the conference NOW, as space in the Youth Hostel is starting to get tight and you will not get a room if you don't register. The registration info is on this page: http://debconf15.debconf.org/registration.xhtml Note that for the students who asked for food+accomodation sponsorship, you should have received a mail from the DebConf bursaries team confirming your status. We are still pending confirmation on the travel sponsorship funds. You should register anyway, as you will not get a room if you don't. We will let you know as soon as we can confirm the travel sponsorship. I will also submit a talk proposal for the students that would like to give a short presentation: we bundled the GSoC talks together last year and I think it went pretty well :) Cheers, -- Nicolas Dandrimont BOFH excuse #92: Stale file handle (next time use Tupperware(tm)!) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] [GSoC Students and Mentors] Start of the coding period: reports, blogs!
Hi all, The coding period has started! That means that from now on, we (program administrators) expect from you (students) a weekly report of your activities. We would like the reports to be sent on the weekend (Saturday or Sunday). No need to go into the minutiae of all the changes you have done over the week, two or three paragraphs are enough. However, we expect you to tell us what you've done for the week (please point to your repository, your documentation, ...), what you intend to do the following week, and how that compares with your original plan. This helps us (admins) know whether everything is under control for your internship, and avoids surprises :) Now that you are a part of the Debian community, I would also love to syndicate your blogs (well, if you have one) on planet.debian.org. To do so, please point me to an English-language-only RSS or Atom feed, and a Hackergotchi (if you want to have one) and I'll get it syndicated. More info : https://wiki.debian.org/PlanetDebian Enjoy your summer with us! -- Nicolas Dandrimont I once witnessed a long-winded, month-long flamewar over the use of mice vs. trackballs...It was very silly. (By Matt Welsh) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] GSoC Students: Come join the community during DebConf15!
Hey all, [all students Bcc'd] While you are busy getting better acquainted with your mentors and our community, we would like to talk to you about DebConf, which will be happening August 15th-22nd, right at the end of the coding period of this year's GSoC. DebConf is the yearly conference of the Debian project. It's a week long event attended by many contributors to the Debian project. It is a great time to learn more about the wider community and little things about the project. A time to meet new people, hear developers talk about their work, get together for high bandwidth meetings, discover weird card games, and enjoy life! It would also be a great opportunity to wrap up your project and make it known to the wide Debian community. As our budget for sponsorship is limited, we might not be able to provide support for every one of you. But we need your help to get a better picture. Please answer the following questions [privately] before May 13th (next Wednesday): - Do you want to come to DebConf? - Will your mentor be at DebConf? - Do you want to give a talk at DebConf? (5 or 15 minutes “lightning” talks are the perfect opportunity to present your GSoC project and a great learning experience if you have never done public presentation before) - Do you need sponsorship for your travel expenses? - If yes, how much? (with details! Where are you flying or taking a train from...) - Do you need sponsorship for food and accomodation? (on your own, it costs 33€ per night for lodging and 3 meals) Please be quick, and we will let you know ASAP how Thanks, -- Nicolas Dandrimont BOFH excuse #112: The monitor is plugged into the serial port signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] Debian welcomes its Google Summer of Code students
Hi all! The newfangled Debian Outreach Team is proud to welcome the 17 students selected to be part of the Google Summer of Code this year. We're delighted that two of those 17 students were Outreachy applicants, and have been accepted to GSoC through that program. We have a wide range of selected projects this year, from improving QA tools, adding new packaging helpers, all the way to creating a Debian bootable OS using another compiler. You'll find below the full list of projects, students, their work plan, and their mentors. QA and Developer tools -- Debsources ( http://sources.debian.net/ ) as a platform Orestis Ioannou - https://wiki.debian.org/SummerOfCode2015/StudentApplications/OrestisIoannou Clement Schreiner - https://wiki.debian.org/SummerOfCode2015/StudentApplications/ClementSchreiner mentored by Stefano Zacchiroli and Matthieu Caneill Add new checkers in Debile (rebuilding the archive with various dynamic, static analyzers or compilers) Lucas Kanashiro - https://wiki.debian.org/SummerOfCode2015/StudentApplications/LucasKanashiro mentored by Sylvestre Ledru Apport Integration in Debian (a crash detection and reporting tool) Yuru Shao - https://wiki.debian.org/SummerOfCode2015/StudentApplications/YuruShao mentored by Ritesh Raj Sarraf and Aron Xu Archive built with ASan (Address Sanitizer a fast memory error detector) Mohit Bhakkad - https://wiki.debian.org/SummerOfCode2015/StudentApplications/MohitKBhakkad mentored by Sylvestre Ledru Blends Web Sentinel Akshita Jha - https://wiki.debian.org/SummerOfCode2015/StudentApplications/AkshitaJha mentored by Andreas Tille Developer Dashboard Harsh Daftary - https://wiki.debian.org/SummerOfCode2015/StudentApplications/Developer%20Horizon mentored by Daniel Pocock Porting and archive-wide enhancements - Improve Debian reproducible builds ( http://reproducible.debian.net/ ) Eduard Sanou - https://wiki.debian.org/SummerOfCode2015/StudentApplications/EduardSanou Maria Valentina Marin - https://wiki.debian.org/SummerOfCode2015/StudentApplications/MariaValentinaMarinRodrigues mentored by Lunar, Holger Levsen, Reiner Herrmann and Mattia Rizzolo. Bootable Clang-Built Debian Joseph Lee - https://wiki.debian.org/SummerOfCode2015/StudentApplications/JosephLee mentored by Sylvestre Ledru Improve the Debian MIPS ports (mips, mipsel, mips64el) Arturo Borrero Gonzalez - https://wiki.debian.org/SummerOfCode2015/StudentApplications/ArturoBorreroGonzalez Gustavo Alkmim - https://wiki.debian.org/SummerOfCode2015/StudentApplications/GustavoAlkmim mentored by Anibal Monsalve Salazar Packaging-related projects -- Automated configuration of packaged web applications Thiago Ribeiro - https://wiki.debian.org/SummerOfCode2015/StudentApplications/ThiagoRibeiro mentored by Antonio Terceiro Android Tools in Debian Kai-Chung Yan - https://wiki.debian.org/SummerOfCode2015/StudentApplications/KaichungYan Komal Sukhani - https://wiki.debian.org/SummerOfCode2015/StudentApplications/SukhaniKomal mentored by Hans-Christoph Steiner and Markus Koschany Integrate Debian with Android Jivan Ghadage - https://wiki.debian.org/SummerOfCode2015/StudentApplications/Jivan%20Ghadage mentored by Kumar Sukhani and Hans-Christoph Steiner Coinstallable PHP Versions Murukesh Mohanan - https://wiki.debian.org/SummerOfCode2015/StudentApplications/MurukeshMohanan mentored by Ondřej Surý If you want to follow those projects during the summer, you're welcome to subscribe[1] to the soc-coordination@lists.alioth.debian.org mailing-list, where the students will send their weekly reports throughout their internship. [1] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination We hope our interns will spend productive summer with us, and we expect our community to give them the warmest of welcomes! Cheers, - Nicolas, on behalf of the Outreach Team. signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] Call for Debian projects and mentors in the Google Summer of Code 2015
Hey everyone, Do you feel that it's been a long time since Debian participated in a mentoring program? Well, fear not, this is your lucky day: Google Summer of Code [0] is starting its 11th edition right now, and the Debian Project will be applying for a mentoring organization spot again this year, for the tenth time [1]. Our application can only be accepted if we have published a list of project proposals by the time Google reviews organization applications. Google ends their review on February 27th, so we need your help! = What does Google Summer of Code do for Debian? = Google Summer of Code is a series of student internships, paid in full by Google, where the student works for a Free Software organization such as Debian during the summer, and receives a stipend if the project is successful. We have found that GSoC is a good way to get new (and old) contributors interested in the parts of Debian that you consider important, and to keep some of them involved with Debian even after the program ends. Putting together project proposals for GSoC allows you to showcase your part of the project, in part for prospective GSoC students, but also for the Debian community at large. = How do I propose a project for an intern? = If you have an idea for a project, please do TWO things: - Publish the idea on the wiki page [2], filling out the template - Drop us a mail on the coordination mailing-list [3,4] This two-step process helps us track project ideas and allows us to discuss the project proposals in detail (scope-wise and length-wise). You need to know (or remember) that the raw coding phase for GSoC lasts a bit less than three months, and therefore plan the project accordingly. If you're a student, and you have an idea for a project, please submit it too! Everyone (Member of the Debian project or not, student or not) is welcome to submit their ideas, and to try and find people willing to mentor the projects. However, the project wiki page is split in two parts: Project ideas and Projects with confirmed mentors. Please put your project in the right section, and note that mentors are critical to the success of a GSoC project. We WILL remove Projects ideas without confirmed mentors before the student application period starts. Don't panic! mentoring takes time, but not _that_ much time, and all the less if you find a motivated co-mentor (something we very strongly encourage you to do). Furthermore, we admins will be here all the way to help you when and if you need it. Should you need help about drafting a project proposal, or anything else related to GSoC, please drop us a mail on the ML [3,4], or drop by on our IRC channel [5], and we'll see what we can do! Cheers, - Nicolas, Sylvestre and Tom, your GSoC'15 admins [0] https://developers.google.com/open-source/soc/ [1] https://wiki.debian.org/SummerOfCode2015 [2] https://wiki.debian.org/SummerOfCode2015/Projects [3] soc-coordination@lists.alioth.debian.org [4] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination [5] irc://irc.debian.org/#debian-soc signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] GSoC students and mentors group photo
Hey folks, Aigars suggested that we should gather around and take a picture of the GSoC students and mentors present at DebConf. I guess the easiest way to do so, would be to piggy-back on the regular group photo meeting, happening tomorrow. Therefore, if you want to be on that picture, please stick around after the regular photo. Thanks, -- Nicolas Dandrimont BOFH excuse #238: You did wha... oh _dear_ signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] GSoC students and mentors group photo - TIME UPDATED
* Nicolas Dandrimont ol...@debian.org [2014-08-28 18:57:34 +0200]: Hey folks, Aigars suggested that we should gather around and take a picture of the GSoC students and mentors present at DebConf. I guess the easiest way to do so, would be to piggy-back on the regular group photo meeting, happening tomorrow. Therefore, if you want to be on that picture, please stick around after the regular photo. So, I've been notified that at least two people involved in GSoC are leaving tomorrow morning and will miss the group picture. I propose we move the GSoC picture taking today during the afternoon break at 15:30 PDT (to make it convenient, in the same spot Aigars will take the pictures of people that will have left tomorrow). Everyone involved in GSoC in Debian, either this year or in years past, is invited to join us, and even if you're a mentor w/o student or a student w/o mentor! Sorry for the shuffling around and thanks for being here! -- Nicolas Dandrimont BOFH excuse #166: /pub/lunch signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Length of time for Debconf talks
* Joseph Bisch joseph.bi...@gmail.com [2014-07-23 20:37:12 -0400]: How long will each student have for his/her Debconf talk as part of Looking back on a Debian Summer of Code? Hi Joseph, Due to the high number and level of submissions, the DebConf talks team asked me to have a single GSoC session instead of the four separate talks, which enabled them to squeeze more talks in. To compensate, we have been assigned (well, will be assigned really) two talk slots, which means 1h45 of talk time (accounting for the 15 minute recess at the end of the session). So that means that you should aim for a 20 minutes talk, plus 5 minutes for questions. There will be time to schedule an ad-hoc talk for followups during the designated hacking time, if there's interest. And there's always the hallway track :) Cheers and see you at DebConf, -- Nicolas Dandrimont BOFH excuse #382: Someone was smoking in the computer room and set off the halon systems. signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] [GSoC Students] End of bonding period / Start of the coding period
* Sylvestre Ledru sylves...@debian.org [2014-05-16 09:53:09 +0200]: Next week, Monday May 19th, the coding period starts! From next week, we expect a weekly report every Friday (i.e. the first one will be May 23th). It should take an hour max to write. You don't have to go into much detail. However, missing those weekly reports will very badly reflect on your evaluations (you will be failed). Your weekly reports should be sent to this list (and probably cross-posted to a project-specific mailing-list, if one exists). Cheers, -- Nicolas Dandrimont BOFH excuse #9: doppler effect signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] [GSoC Students] [DebConf] Please register *now* if you want to go to DebConf
Hi, As was discussed previously, we encourage our GSoC students to attend DebConf. To that end, we engaged with the DebConf team regarding food+accomodation sponsorship for GSoC students. The outcome of that discussion is that, as this year's schedules are matching, GSoC students should just register for sponsored food and accomodation as every other Debian contributor, before the normal deadline of May 15th. So: please go to https://summit.debconf.org/debconf14/registration/ to register. If you miss the deadline, you won't be eligible for food and accomodation sponsoring. Sorry for the short notice. There, you should tick the sponsored food + accomodation checkboxes. The travel fare sponsorship will be taken care of, by ourselves (GSoC admins), separately, so you shouldn't check that box. In the textboxes, just describe your situation: you're a GSoC student selected by Debian, you're working on this and that project with your mentor. This should just be a formality. Make sure you tell Sylvestre and myself when you have registered on the DebConf website, so that we can get back to you regarding the reimbursement of your travel expenses. Thanks, -- Nicolas Dandrimont BOFH excuse #174: Backbone adjustment signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] [Mentors and Students] A primer on the how the GSoC Student application period works
Hi, * Leandro Doctors ldoct...@gmail.com [2014-03-12 12:48:13 +0100]: 2014-03-09 23:02 GMT+01:00 Nicolas Dandrimont ol...@debian.org: The way we do student applications in Debian is that the students put their application on our wiki (instructions and list on [3]), and use google-melange only to link to that application. No need to copy-paste the whole page, just have them put a link. That way we keep everything in a central place that is easy to work with for us. On the other side, the official FAQ on Google Melange [0] says: ++ 11. Should students send proposals directly to the mentoring organizations? No, all proposals should be submitted to the mentoring organization using the 2014 program site. Proposals submitted outside of the 2014 program site will not be considered for Google Summer of Code. ++ Does this mean that by April 21st, we applicants should actually *add into melange* the actual (final, polished) application text from the Debian wiki? No, it means that only applications that have been somehow recorded in melange will be taken into account by Google. The FAQ entry has been carried over from last year, so the way we do things just keeps working. So, to make it clearer, we want the full applications on the Debian wiki, and students have to record their application on Melange to be considered. They can just put a URL to the wiki on their melange application page. Cheers, -- Nicolas Dandrimont Avoid the Gates of Hell. Use Linux (Unknown source) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] [Mentors and Students] A primer on the how the GSoC Student application period works
[Registered mentors[0] Bcc'd for the first and last time. Please subscribe to the soc-coordination list if you didn't already] Hi all, First of all, thanks a bunch for having proposed a project for this year's GSoC in Debian. Our project idea list looks stronger than ever! Sorry for the long-winded mail but there's a lot of stuff to say about student applications :) Earlier tonight, I have cleaned up our project list[1], by moving the projects that had a mentor in the SummerOfCode2014/Projects namespace, and by hiding the ProjectProposals in the index. Mentors, if you haven't already, please register on google-melange, following the two steps described on the wiki[2]. That's the platform where you'll evaluate your students during the course of the program, so at least one mentor per project needs to be registered there. If all the mentors are there, we don't need to run after people to fill in evaluations and your admins are less grumpy. Go register already! The student application period opens at 1900 UTC tomorrow (March 10th), and closes at 1900 UTC on Friday March 21st. What that means is that a student needs to have submitted a formal proposal on google-melange.com in that time period. Students are free to refine their application until the time our student acceptances are sent to Google, that is until April 17. That leaves the students a good month to talk with you and come up with the perfect proposal. They just need to have submitted *something* to Google before March 21st. Of course, the earlier the better (melange can be a bit difficult under load)! The way we do student applications in Debian is that the students put their application on our wiki (instructions and list on [3]), and use google-melange only to link to that application. No need to copy-paste the whole page, just have them put a link. That way we keep everything in a central place that is easy to work with for us. Mentors, feel free to direct your students to the more relevant medium of communication for your project. You might want to use the soc-coordination list for inital contact as that's where students are usually directed (e.g. on our wiki page or on Debian's melange page). It might be a good idea to hang out on IRC too, as we have some students asking questions there. We can usually guide them or redirect them, but it's easier for everyone if you're there already. Mentors, timely interactions with students are a must, even if just to say We're reviewing your stuff and we should be able to reply in a few days. Those kids are very enthusiastic, and it doesn't take much latency to demotivate them. For each proposed project idea, we will accept zero or one student (we also usually limit the number of students per mentor, but that shouldn't be an issue this year). We do things in a few steps: - At the beginning of April, we will ask for your gut feeling on whether an applicant will be a good match for your project. That helps us request a realistic number of student slots from Google. - Hopefully, we get all the slots we ask for (which has usually been the case). - Once student slot allocations are done by Google, we will ask the mentors for a ranking of the applications they received. That is, you're in the driver seat all the way and you get to decide who does your project. Google doesn't have a say, and the admins don't usually interfere. Suffice to say that ranking student applications is *HARD*, and the top-notch applications can get decided by a coin flip. If you have two strong contenders, tell us! There are several deduplication rounds (for students that applied to several orgs), and we have had top students apply to two orgs and get picked in both. If we know you have two strong profiles, it makes it easier on everyone. If there are irreconcilable differences between the orgs, we can always ask the student. :-) Mentors, to help you rank applications, we strongly advise you to propose your students a warmup task of some sort, to see how they can deal with your software and how they interact with you. For instance, have them fix a bug, write a patch, make or adopt a package related to your software stack, ... Thanks for reading thus far! Don't hesitate to follow up on the mailing list if you have any doubts or questions. And you can always contact us privately (sylvestre@d.o and olasd@d.o) if you have any issue you can't raise in public. Eager to receive those student applications! Cheers, Nicolas Dandrimont [0] Mentors and co-mentors don't really have a different status, so from now on we'll only talk about mentors, don't be surprised. [1] https://wiki.debian.org/SummerOfCode2014/Projects [2] https://wiki.debian.org/SummerOfCode2014#I_want_to_mentor_a_project_in_Debian [3] https://wiki.debian.org/SummerOfCode2014/StudentApplications signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination
Re: [Soc-coordination] Mentoring: what next?
* b...@debian.org b...@debian.org [2014-03-08 18:31:45 +0100]: Hi, I submitted a project proposal [1] in the wiki a while ago but I haven't seen any news. Apparently we were selected as a mentoring organization, but the wiki is out of date and I don't know if there's anything I should do to promote the proposal, etc.. Yes, we've been selected, and the wiki was mostly up to date (save for the only sentence you read, apparently :P). Your next step is to register as a mentor on the google-melange platform. If you want to promote your project, blog about it, send it to an upstream ML, get in touch with students that you might know, and lurk on this mailing list for potential student questions. The official blog post is at http://bits.debian.org/2014/02/call-for-students-gsoc-2014.html The formal student application period opens on Monday, for two weeks (until Friday March 21st). We want students to submit their application on our wiki. If you get enquiries by students, please point them to the instructions there. https://wiki.debian.org/SummerOfCode2014#Ideas_list_.2F_Participating_.2F_Applying I'll clean up the wiki from the projects that failed to find a mentor tomorrow, to prepare for the incoming flood of applications. Don't hesitate to ask if there is any info on the wiki that looks outdated. Thanks, -- Nicolas Dandrimont BOFH excuse #208: Your mail is being routed through Germany ... and they're censoring us. signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] GSoC 2014: mhonarc replacement for lists.debian.org
* Pali Rohár pali.ro...@gmail.com [2014-03-05 14:40:51 +0100]: 2014-03-05 14:14 GMT+01:00 Nicolas Dandrimont ol...@debian.org: * Pali Rohár pali.ro...@gmail.com [2014-03-05 11:24:19 +0100]: Hello, I already wrote that I'm interesting in project for archiving and formatting emails from mailinglists. I asked confirmed mentor formorer for this project [1] and he wrote me that he would happy to accept this application. But there is one important thing about it. For my bachelor thesis I have already started doing something similar/same. So I need to know if I can to participate with this project [1] for GSoC 2014 and reuse my bachelor project code or continue working on it for GSoC. In my opinion according to this Google GSoC FAQ [2] it is allowed. But is it OK for Debian as mentoring organization? Or are there any other problems? As an org admin I have no problem with that, provided that the original software is free and published in some way, and that your modifications stay that way. All the more so if the project mentor already ACKed that the software would fit. Software reuse and adaptation is perfectly fine, all the more so in a distribution where doing just that is our core line of work. Obviously you'll have to go through the normal student application process and get ranked using the same criteria as other students would be, but you won't be forced to build everything from scratch, if your mentor says it's OK. And if the code is published free software, then any student is free to do the same and build their application upon that same base. (As an aside, having some software written already proves, to some extent, your worth as a GSoC student, and therefore can only help the mentor evaluate your application in a favorable light) I understood project proposal [1] as not to extend any existing SW (like mhonarc), but create new one, because there is no good one. My bachelor project is not public yet (because it not working now and hard to use), but there is no problem to make it free. So it is needed to do some (non-working) code drop now (in the time of student application period) of my project under free license and mark it as original? Or it is enough to do that after I have something working? Note that I do not expect working executable code before end of student application period. [1] - https://wiki.debian.org/SummerOfCode2014/ProjectProposals/ListArchive We need to evaluate the realism of *your* project application. The proposal is just that, a proposal. You need to discuss *your* application with the mentor, and tailor that to the way you both want to do things. Nothing is set in stone, and even during the program things can be fluid: if the mentor and yourself can agree on a base project, a set of quantifiable goals, and a timeline to achieve those goals, then there is no issue about your application per se. There are a few requirements for a GSoC project: - Google needs to be allowed to do business with the student (think embargo) - organization admins need to request and allocate a slot for the project - the work needs to be completed by the student without depending on something else - the resulting code must be published under a free software license To assess whether we will request and allocate a slot for the project, we need to make sure, as admins, that the set of goals is achievable, that the timeline is realistic, and that the base you're working on is sound. Obviously, for the most part, we defer to our mentors as we are not the clients of the GSoC projects, merely facilitators for the relationship between Google, Debian, your mentor and you. I don't see how your mentor can assess that the work can be done if he doesn't see the code you will be working on. And that code needs to be free software at the end of GSoC. I wouldn't want to have to throw your GSoC's worth of work in a fire because of a licensing issue. Having a released, free software codebase beforehand swiftly solves both of the problems, and I would strongly prefer it that way. And that's how we usually do things in Debian, out in the open, under the scrutiny of our peers (and yes, we can spot whether a student blatantly reuses someone else's proposal without making it its own). So, really, the question is simple: Do you own the copyright to that lump of code you wrote during your bachelor thesis, and can you license it freely? Could you do that now? [I'll put a disclaimer here: making your code free software doesn't give you any advantage over other potential applications for that project: applications and students will be ranked according to their own merit. Having experience in software development gives you an edge, but not a definitive one, as the quality of student applications improves each and every year] Cheers, -- Nicolas Dandrimont BOFH excuse #297: Too many interrupts signature.asc Description
Re: [Soc-coordination] GoSC 2014 Project proposal
* olivier sallou olivier.sal...@gmail.com [2014-02-15 16:34:46 +0100]: Hi, I have added a project proposal to extend bootstrap-vz (the new debian-build-cloud) [0] We expect to develop new provider and tools to build Debian cloud images. The project has been set in Projects ideas without confirmed mentors. How can it be moved to Projects with confirmed mentors ? Hi Olivier, Interesting sounding project! I just moved the page to the Projects/ directory instead of ProjectProposals. Cheers, -- Nicolas Dandrimont On a normal ascii line, the only safe condition to detect is a 'BREAK' - everything else having been assigned functions by Gnu EMACS. (By Tarl Neustaedter) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] GoSC 2014 Project proposal
* olivier sallou olivier.sal...@gmail.com [2014-02-15 17:35:56 +0100]: [snip] I was looking for mentor registration for Debian/GoSC, but the link on Debian wiki [0] to Google Melange [1] returns a 404 Not Found error. I tried to change gosc2013 to gosc2014, but it does not work either. Timeline shows that orgnization review application is in progress, so this may be the cause (Debian not being accepted yet), but if this is the case, maybe wiki could be updated to put the date after which we could apply. (and do you know when mentors will be allowed to apply ?) That's correct. Melange will open when the accepted orgs will be announced. I updated the wiki to that effect. Cheers (and sorry for the wasted time), -- Nicolas Dandrimont Problem solving under linux has never been the circus that it is under AIX. (By Pete Ehlke in comp.unix.aix) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Call for Debian projects and mentors in the Google Summer of Code 2014
Hi Antonio, * Antonio Terceiro terce...@debian.org [2014-02-10 18:10:39 -0300]: [not subscribed to the list, please keep me in Cc:] Done. [snip] I just wrote a proposal for a project related to debci: https://wiki.debian.org/SummerOfCode2014/Projects/DebianContinuousIntegration In the list of deliverables I added some of the major efforts that I see for debci at the moment, which might be too much for a GSoC project. Can Is it OK to decide on the exact scope together with the student at the beginning of the project? It is perfectly fine to come up with a rough list of ideas and requirements at this stage. One thing we very strongly encourage mentors to do, however, is to provide students with a small task to do, to show their skill and how they approach problems during the application period. It can be as simple as adding their name to the footer of a webpage, or in the log of a check run, ... During the student application phase, the students are expected to make the projects their own: give a detailed list of deliverables, plan their schedule, etc. It's during that phase, that we will be able to give feedback about the realisticness of the project proposal according to the skills they have shown beforehand, the duration of the program, etc. Thanks for coordinating this effort. Thanks for your project proposal! Cheers, -- Nicolas Dandrimont BOFH excuse #193: Did you pay the new Support Fee? signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] Call for Debian projects and mentors in the Google Summer of Code 2014
Good news everybody! Google Summer of Code [0] is starting its tenth edition right now, and the Debian Project will be applying for a mentoring organization spot again this year, for the ninth time [1]. Our application can only be accepted if we have drafted a list of proposals by the time Google reviews organization applications, that is, on February 21st. Therefore, we need your help! = What's that Google Summer of Code? = Google Summer of Code is a series of student internships, paid in full by Google, where the student works for a Free Software organization such as Debian during the summer, and receives a stipend if the project is successful. We have found that GSoC is a good way to get new (and old) contributors interested in the parts of Debian that you consider important, and to keep some of them involved with Debian even after the program ends. Putting together project proposals for GSoC allows you to showcase your part of the project, in part for prospective GSoC students, but also for the Debian community at large. = How do I contribute? = If you have an idea for a project, please do TWO things: - Publish the idea on the wiki page [2], filling out the template - Drop us a mail on the coordination mailing-list [3,4] This two-step process helps us track project ideas and allows us to discuss the project proposals in detail (scope-wise and length-wise). You need to know (or remember) that the raw coding phase for GSoC only lasts eight weeks, and therefore plan the project accordingly. If you're a student, and you have an idea for a project, please submit it too! Everyone (Member of the Debian project or not, student or not) is welcome to submit their ideas, and to try and find people willing to mentor the projects. However, the project wiki page is split in two parts: Project ideas and Projects with confirmed mentors. Please put your project in the right section, and note that mentors are critical to the success of a GSoC project. We WILL remove Projects ideas without confirmed mentors before the student application period starts. Don't panic! mentoring takes time, but not _that_ much time, and all the less if you find a motivated co-mentor (something we very strongly encourage you to do). Furthermore, we admins will be here all the way to help you when and if you need it. Should you need help about drafting a project proposal, or anything else related to GSoC, please drop us a mail on the ML [3,4], or drop by on our IRC channel [5], and we'll see what we can do! Cheers, - Nicolas for the Debian GSoC admin cab^Wteam [0] https://developers.google.com/open-source/soc/ [1] https://wiki.debian.org/SummerOfCode2014 [2] https://wiki.debian.org/SummerOfCode2014/Projects [3] soc-coordination@lists.alioth.debian.org [4] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination [5] irc://irc.debian.org/#debian-soc signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Debian / GSoC 2014?
* Daniel Pocock dan...@pocock.pro [2014-02-03 13:43:32 +0100]: The organisation application process opens today with a February 14 deadline Has any decision been made about whether Debian will participate this year? We'll apply, yes. Are the same admin team still delegated by the DPL or does it need to go back to him to make a fresh delegation for 2014? The delegation needs to be redone anyway, as it was time-limited. And it will be a bit of both, as at least one member is stepping down from the admin team. I intend to send a call for projects to d-d-a tonight or tomorrow morning (UTC+0100). In the meanwhile, the project proposal page is open on the wiki[1]. We'll probably send a separate call for project endorsements to this mailing list later. [1] https://wiki.debian.org/SummerOfCode2014/Projects -- Nicolas Dandrimont lp1 on fire (One of the more obfuscated kernel messages) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Weekly Status Report 2 - scan-build the archive
* Léo Cavaillé leo+deb...@cavaille.net [2013-06-29 01:25:49 +0200]: [snip] The program for next week is : * Check with Paul if my install of debuild.me is fine and my almost-finished INSTALL doc is right/useful. * Finish to write scan-build wrapper for debuild.me * Finish a commit for firehose including minimal modifications to fully support scan-build plist output. Hi Léo, Thanks for the report. Seems everything is going well and according to plan, hopefully the cloog hitch will not set you back too much :) See you next week, -- Nicolas Dandrimont BOFH excuse #93: Feature not yet implemented signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Weekly Status Report The OpenJDK and Debian 6.22-6.28 by ShuxiongYe
* Shuxiong Ye yeshuxi...@gmail.com [2013-06-28 22:18:23 +0800]: Hi, Weekly Summary I take exams this week and do nothing. Next Week 1. Finish fixing all bugs left. They are 3 pending upload bugs(patch are available, just upload them) and 1 serious bug(need some deeper exploration). 2. Do the rebuild using openjdk7 Hi, I hope your exams went okay. Thanks for reporting anyway. :) I look forward to a report with more substance next week... Cheers, -- Nicolas Dandrimont BOFH excuse #193: Did you pay the new Support Fee? signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Weekly Status Report 6.17-6.21 by ShuxiongYe
[Cc'd you to get your attention. I won't do that in the future if you don't ask for it explicitly, so please monitor the list for replies ;)] * Shuxiong Ye yeshuxi...@gmail.com [2013-06-21 20:23:13 +0800]: Hi, I am ShuxiongYe, a graduate from Peking University. My GSOC project is The OpenJDK and Debian. The main goal of this project is to make packages compatible with openjdk-7, and to finish the transition to openjdk-7 for wheezy. Currently, I focus on fixing bugs tagged openjdk-7-transition. Weekly Summary 1. I make a patch for oauth-signpost. 2. I will take exams from 6.17 to 6.28, so I will not work full-time these two weeks. I start few weeks ago, and here is the packages I am working on. http://wiki.debian.org/SummerOfCode2013/StudentApplications/ShuxiongYe/PackageList Hi, Thanks for your report, and for the bugfixes. I see in your schedule that you planned time off for your exams next week, which is alright. Was the rebuild with OpenJDK 7 done during the community bonding period? (I guess so looking at the bugs linked from the page). Could you point us to documentation on the rebuild: the list of results and how the rebuild was done? Thanks again, -- Nicolas Dandrimont Debian GSoC org admin, checking in Ever heard of .cshrc? That's a city in Bosnia. Right? (Discussion in comp.os.linux.misc on the intuitiveness of commands.) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Weekly Status Report 1 - scan-build the archive
[Cc'd you to get your attention. I won't do that in the future if you don't ask for it explicitly, so please monitor the list for replies ;)] Hi Léo, * Léo Cavaillé leo+deb...@cavaille.net [2013-06-21 17:34:51 +0300]: What Google calls bonding period has been done successfully. I really feel welcome in debian and I have no problem to communicate with developers whatsoever. Thank you ! At the moment I am working with zack and Matthieu, I can see them when I go work some days at IRILL in Paris. Also, with Paul and David (from redhat) and of course with Sylvestre my mentor ! Sounds like amazing work conditions :) [...snip...] Thanks for the very detailed report. Just one thing that I feel is missing: could you tell us just a bit about your plans for next week? Thanks again, -- Nicolas Dandrimont Debian GSoC org admin, checking in. BOFH excuse #74: You're out of memory signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] [GSoC students] Weekly status reports wanted
[Cc'd you to get your attention, I won't do that in the future if you don't ask for it explicitly, so please monitor the list for replies ;)] Hi Paul, First, a tidbit: please avoid sending html email to the list: it's considered bad form as it makes the mails bigger for next to no gain. Thanks in advance! * Pavlos onexema...@gmail.com [2013-06-21 14:34:04 +0200]: Hello, I am paul sarbinowski and I am taking part in the Debian Android app project for 2013. The goal of the project is described here [1]. I have already created a repo in github for it [2] and added a readme file with some possible use cases for the app. Coding-wise I added some code for the basic ui skeleton of the app and i have started to check the bts and pts soap and dde api and how I can communicate with it in android. I communicated with the -qa list and with Don Armstrong to ask about possibly adding a rest api for bts/pts since it makes things much easier/lighter in android and I also filled a bug (feature request) for it in debbugs [3]. [1]: http://wiki.debian.org/SummerOfCode2013/StudentApplications/PawelSarbinowski [2]: https://github.com/uberspot/DebianDroid [3]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712979 This all looks great, thanks. I have a few small questions: - Do you have some screenshots of the application in its current state? I saw some mockups floating around but it'd be great to see and follow the real thing while it gets built. - What are your plans for next week? No need to go into much detail, it's just to get a feel of what's to come and whether things are going on schedule or not. Thanks again, -- Nicolas Dandrimont Debian GSoC org admin, checking in. Absolutely nothing should be concluded from these figures except that no conclusion can be drawn from them. (By Joseph L. Brothers, Linux/PowerPC Project) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Report 0 for Improvements to the Debian Search Project
[Cc'd you to get your attention, I won't do that in the future unless you ask for it explicitly, so please monitor the list for replies ;)] * Aarsh Shah aarshkshah1...@gmail.com [2013-06-21 18:24:39 +0530]: *Improvements to Debain Search - Report 0 [...snip...] Hi Aarsh, Thanks for your detailed report. Things look crystal clear and on schedule, so I don't have anything to add. Cheers, -- Nicolas Dandrimont Debian GSoC org admin, checking in. BOFH excuse #283: Lawn mower blade in your fan need sharpening signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Next steps for mentors?
Hi, * Daniel Pocock dan...@pocock.com.au [2013-05-05 18:02:36 +0200]: Hi, This is the first year I volunteer to support Debian's GSoC and OPW programs, so I don't know all the details about how people like to do things Now that we have applications, can anybody comment on some of the following: - is there any policy document (from the Debian admins, not Google) describing the process for selection of projects and students? - are there specific criteria that need to be rated or ranked when reviewing the applications? - what roles and responsibilities do the prospective mentors take in the final decision process? E.g. do the mentors need to inform Debian's SoC admins of their preferred student, or give a rating to each student, or something else? I wanted to send a mail along those lines, and I'll address those three questions at once: We don't have a formal policy document for the selection process, as it is very simple. We have done things that way for a few years now, and it has worked well so we keep the same process: Admins ask the mentors to select the best student application for each project they have proposed. If they aren't really happy with how their applications turned out, they should tell us so, and we'll drop the project from the pool. The GSoC Mentoring guide gives some good insight on what you should check for when selecting a student: http://en.flossmanuals.net/GSoCMentoring/selecting-a-student/ Once mentors have given us their shortlists, we have a pool of students we want to get on board. Google assigns us a number of project slots to fill in. If there are enough slots for all the students, we are done, and we will give back the excedent slots to Google. If there aren't enough slots, we as admins have to make the hard choice of what projects to drop. To help us in this process, we ask you to make your reviews of proposals known. This is one of the easy things to do on melange: on the page for a proposal, just leave a comment keeping the private box ticked. We don't have decided on specific criteria to rank the projects among each other, and to be honest I hope we won't have to... We'll let you know when we know how many slots we have and we will have thought it over between admins. - I understand the requirement for multiple mentors: do they all need to be registered in Melange? Some people are not keen to create Google accounts. Is it OK to have just one mentor per project in Melange, and others listed on the Debian wiki? Having several mentors listed in melange means that they all can do the evaluations and the feedback on that interface. Issuing timely evaluations is critical for us to keep our good standing with Google: for instance, access to the mentor summit is tied to that, and it might affect their evaluation of our application to further programs. If they really, really, *really* don't want to create Google accounts, we can't really force them to, but that would save all of us some precious time. If all else fails, the admins can fill in the evaluations, but they will get very grumpy doing so. Cheers, -- Nicolas Dandrimont, for the Debian GSoC admins BOFH excuse #270: Someone has messed up the kernel pointers signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] GSOC - Enabling free multimedia real-time communications (RTC) with Debian
[Cc:'ing you for the last time, please subscribe to the list[1] if you haven't done so yet, to get all the GSoC announcements] [1] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination * Jesús Pérez Rubio jesus.pe...@quobis.com [2013-05-02 11:40:25 +0200]: Hi, I'm interested in co-mentor the Google Summer of Code project Enabling free multimedia real-time communications (RTC) with Debian ( http://wiki.debian.org/SummerOfCode2013/Projects#Enabling_free_multimedia_real-time_communications_.28RTC.29_with_Debian ) [ snip nice intro ] Hi, Thanks for the introduction, for stepping up for mentoring a student, and welcome onboard! I just accepted your connection request on melange, so you should be good to go. Cheers, -- Nicolas Dandrimont BOFH excuse #363: Out of cards on drive D: signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] Bits from the GSoC admins: student application period ends tomorrow at 1900UTC, timeline for evaluating proposals
Howdy GSoCers, Summary: - Student application period ends May 3rd at 19:00 UTC - Students: • submit your application to Melange NOW, update the wiki summary • you have until May 17th to improve your proposal - Mentors: • slot allocation requests on May 6th, please tell us if you don't want one • we want you to rank proposals by May 17th • please keep your rankings private to students We're less than two days away from the end of the student application period. If you're a student, and if you haven't done so yet, that means that you need to register to melange and submit your application there NOW. If you're a mentor, and you have been contacted by students, make sure they have submitted something to melange and to the wiki. To make it clear, if you have not submitted anything to melange by the deadline, you won't be able to participate. The melange student application deadline is on May 3rd, at 19:00 UTC. To get that in your timezone, use the date -d @1367607600 command in a terminal. Don't wait for the last minute, as you can always iterate on your proposal afterwards! To help us make sure every student has submitted his application on melange, please link them on the wiki summary page[1]. [1] http://wiki.debian.org/SummerOfCode2013/StudentApplications The deadline for slot allocation requests is on May 6th, and we will likely ask for one slot per project where a student has manifested interest (which would mean 18 slots for now). Please tell us over the weekend if you don't feel like we need to ask for a slot for your project, it'll save all of us some time. We have set the deadline for evaluating student applications on May 17th, leaving us a few days to sync up before deduplication start (yes, I wrote May 22nd earlier, but really that's May 17th). We encourage students to work on improving their proposal and engage with their mentors until that time. Google asks us to keep the information on whether a student will be accepted or not private until they announce the accepted projects on May 27th. We kindly ask mentors to keep that info private, and to give all the students a chance to improve their proposal. We will contact the mentors privately to ask for details on the proposals they received, and how they rank them, during the 18-19 May weekend. Don't hesitate to followup on-list if something is not clear! Cheers, -- Nicolas Dandrimont, for the Debian GSoC org admins linux: the choice of a GNU generation (k...@cis.ufl.edu put this on Tshirts in '93) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] GSoC Mentors and Students: information for the student application period
Fellow GSoC'ers, The student application period is one of the busiest periods of GSoC. Here are some pointers to make the experience bearable! Executive summary for the impatient: - Register to melange NOW - Students need to submit formal applications to melange before May 3rd at 1900 UTC - Mentors are kindly asked to make themselves known on melange now First and foremost, now is the time to register to melange[1], the platform Google asks us to use to manage the GSoC program. It's the place where students submit their formal application, and where mentors and students submit their evaluations when they're asked to. [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2013 As I said in the previous paragraph, students MUST submit their application on melange. No application on melange means no GSoC project. However, as we did in previous years, we ask that you write your application on the Debian wiki, following the template[2], and linking to the student applications page[3]. For your application on melange, you can just link to the wiki. This helps us keep track of changes on the proposals over time, which is not really possible on melange. [2] http://wiki.debian.org/SummerOfCode2013/StudentApplicationTemplate [3] http://wiki.debian.org/SummerOfCode2013/StudentApplications Finally, we need mentors to register to melange too, link themselves to Debian[4], and apply for mentoring on the relevant projects[5]. That way, you will formally be known as a mentor, and asked to submit evaluations in due time. In your mentor application, please state clearly who you are and what project you went to mentor, melange makes it hard on us admins to know who you are... [4] http://www.google-melange.com/gsoc/org/google/gsoc2013/debian then Start a Connection or Apply as a mentor. [5] http://www.google-melange.com/gsoc/dashboard/google/gsoc2013 Proposals submitted to my organizations. We're available on irc or on-list for guidance if there is any issue. Cheers! -- Nicolas Dandrimont, Debian GSoC Org Admin of the day I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you. (By Vance Petree, Virginia Power) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] upstream involvement
Hi! * Daniel Pocock dan...@pocock.com.au [2013-04-10 08:56:04 +0200]: Hi, I just want to get some feedback on the extent that we can involve upstreams, either formally (as named mentor) or informally (e.g. collaborating through upstream mailing list, contributing to upstream source tree). I think upstream collaboration is a great thing for students to learn: Debian wouldn't exist without upstreams, and collaborating with them is key to improving not only Debian, but Free Software as a whole. However, see the caveat. I've proposed three project areas and I've already had enquiries from some excellent candidates for all of them. That's great. The overriding goal of each project is to fix some gap in the Debian eco-system, but some of the work may go into the upstream projects. For example, Debian has two TURN servers, neither of them supports database-backed (SQL, RADIUS or LDAP) user/password storage or any other distributed mechanism in Debian, so an interested student could really work on either of those projects and it would fill that gap. (Simply making another TURN server would not fill a gap in Debian.) I feel that this specific example mostly fills a gap in upstream projects rather than in Debian, and I don't see how this prevents Debian from creating a turn-key solution for WebRTC. So, in my opinion, engaging with upstream to make the software packageable more easily, or to fullfill a Debian-specific requirement is okay, but making a project that only benefits upstream as a Debian project is not. I understand this is part of a bigger project, but I feel that asking this of the student among Debian-specific tasks would make it too big a project. One related issue then is the number of projects/students that Debian will support: is there any hard limit on that, or is it only limited by the number of mentors who come forward? The slot assignment is made by Google after the student application period closes. We, as admins for the organization, make a request to Google for some hard requirement, plus a number of supplementary, nice to have slots. We should make the slot requests according to those guidelines: (well, I don't know yet if the other co-admins agree with that, so take it as my feeling for now) - We can't double-book projects, so we will ask mentors to rank proposals for their projects and ask at most one slot per project. - We won't overcommit mentors. I don't think it is reasonable for us to ask for more than two slots for a given mentor. Heavy co-mentoring might change that opinion. - Finally and most importantly, we will only request slots for projects that have a chance of succeeding, and that will directly benefit Debian. Hope this helps clear things up! Cheers, -- Nicolas Dandrimont We all know Linux is great...it does infinite loops in 5 seconds. (Linus Torvalds about the superiority of Linux on the Amsterdam Linux Symposium) signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] SummerOfCode2013/Projects wiki page organization, (co-)mentors needed
Hi all, Some of you might have noticed some weird page movements on the wiki, that mail should clear it all up: Following some prospective student questions about which projects Debian would be proposing this year, and some confusion that arose around the Projects wiki page, I split it off in two sections: one for projects with confirmed mentors/co-mentors, and one for projects without. Hopefully, this will help us better communicate to prospective students, and to prospective mentors :) I initially split the two sections in two separate pages, but was advised otherwise, as having all the projects on one page should help us secure enough project slots from Google during the organization application period, opening next week. I'd like to take this opportunity to remind all of us that projects without mentors won't happen. While we're still early in the program, and staffing all our projects is not critical yet, early bird students are looking at us already, and if they can be sure that their projects of choice will happen, if they really are motivated, they start working towards great proposals. Having said that, please take a look at the Projects seeking mentors, and if you think you could mentor one, please contact the advocates and add your name ASAP! The more co-mentors you can find for your projects, the less work you will need to do for it to succeed! Thanks for your help in making GSoC happen in Debian. Cheers, -- Nicolas Dandrimont your GSoC wiki janitor/org admin of the day BOFH excuse #350: paradigm shift...without a clutch signature.asc Description: Digital signature ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] GSoC proposals for mentors.debian.net
Le 29/02/2012 à 10:53, Gergely Nagy alger...@balabit.hu écrivit : Hi! First of all, apologies for the late reply, I had to spend a few days playing ping-pong with my unconcious, as the damn thing refused to let me know its ideas until I played with it. Hi, Thanks for your review, and for your enthusiasm! Nicolas Dandrimont nicolas.dandrim...@crans.org writes: [...] '''Semantic Package Review Interface for mentors.debian.net''' * About mentors.debian.net Debexpo (the software running on mentors.debian.net) is a collaborative package review tool. Debian as a community distribution, allows everyone to maintain packages in the archives. New contributors are supposed to go through a mentoring process, which includes reviewing packages made by a prospective contributor. The last sentence sounds a bit weird to me, the end of it at least. I'd think that cutting the sentence at which includes reviewing packages, and turning it into something like the following would make it easier to read: New contributors are supposed to go through a mentoring process, which - among other things - involves package review by more experienced members of the community. This way, you don't repeat the contributor word within the same sentence, and mention by whom the packages are reviewed (more experienced members - not neccessarily developers; and members of the community, as one does not need to be a @debian.org person to contribute useful review). I went with your formulation on the wiki page, thanks. Debexpo helps to host newly created packages and provides a review and management platform. Packages uploaded to Debexpo are being reviewed by experienced users and Debian Developers who will eventually upload them to official Debian archives. I'd turn this into: Debexpo helps with this reviewing process, by allowing anyone to upload prospective packages, request review and sponsorship, and in the end, have one's package uploaded to the official Debian archives. Though, I'm not entirely happy with the above either. I reworded this a little when making the wiki page, but kept the gist of it. [...] * '''Description of the project:''' [...] The first subproject would be to gather a new set of semantic metadata (e.g. an uploaded package is python-based, a package uses a certain packaging helper, ...) on packages uploaded to Debexpo, using the available Debian QA tools or ad-hoc heuristics. This new semantic metadata should then be matched to the interests of sponsors and teams, which would be taught to the software either automatically (by looking at the upload history) or manually (with a set of tags). An automatic matching of sponsor and package traits should make the mentoring process easier and faster. I'd expand on this, describing how this would make it easier for sponsors to find interesting packages to look at and review. Mentioning the huge diversity within debian, and the very different preferences and requirements by sponsors and team might sound scary at first, but if well put, also very interesting. I had a hard time expressing this, so I didn't. :) I agree that the proposal should be expanded to tell this. [...] Before I move on to the rest, I'd like to say that I like both parts of the proposal, but the two parts together seem too big to me, and I'd suggest splitting them. Since the latter kind-of depends on the former, and the former sounds more useful if only one would be implemented, I'd keep that, and consider the latter for next year, or as a project the student could do outside of GSoC, would s/he choose to remain involved. This could also be emphasized in this case, that you have interesting tasks after GSoC, so if the student is finished with the semantic stuff, there's still a lot more to do, so he won't be bored during the winter, either! We (as in the mentors.d.n people) were not quite sure that the two subprojects would fit in a single GSoC project. I therefore applied your idea of only keeping the first subproject as our GSoC project. I hope that the student taking on the debexpo project will in fact continue to contribute in the future (yeah, let's be optimistic). We will discuss amongst ourselves how to formulate the work to be done inside the debexpo project. We do have a wikipage already[1], but it's a bit stale and needs some love :). When the page will be in a better shape, we can link to it from the GSoC proposal. We could also use that wikipage to propose bite-sized work for prospective students to do to evaluate their prior knowledge. [1] http://wiki.debian.org/Debexpo/Development Other than this, I love the proposal, and I'd urge you to go forward with it, and add it to the wiki[1], in either form (it can still be refined n the next couple of days). [1]: http://wiki.debian.org/SummerOfCode2012/Projects I've done that. Again, thanks for your enthusiasm, let's hope
