Re: [FFmpeg-devel] [PATCH] doc: add a few note for sponsorship candidates.
On Wed, 25 Mar 2015 11:10:36 +0100, Nicolas George wrote: From fca492987eef197aa91a92c2ebe37ac3ff0acc58 Mon Sep 17 00:00:00 2001 From: Nicolas George geo...@nsup.org Date: Thu, 19 Mar 2015 21:51:19 +0100 Subject: [PATCH] doc: add a few note for sponsorship candidates. +As for FFmpeg, there is not much to do: choose a proposed project that you want to +do, select a qualification task for that project that is not already taken +by someone else, announce your chosen qualification task on the ffmpeg-devel +mailing list, then start coding.. Nit: s/../. But I wouldn't waste time on that nit unless other changes are going to be made. Looks good. Thanks. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] doc: add a few note for sponsorship candidates.
On Thu, 19 Mar 2015 20:43:55 -0400 Ronald S. Bultje rsbul...@gmail.com wrote: Hi, On Thu, Mar 19, 2015 at 4:53 PM, Nicolas George geo...@nsup.org wrote: +If at any point you have any question, do not hesitate to ask them. +Actually, yes, hesitate a few seconds, in case this question will make you +look dump. So read on. s/dump/dumb/. Also, I'm not sure that's a good attitude, we surely want students to be able to look up google'able stuff themselves, but asking questions to their mentor should be encouraged (and if the mentor thinks it's goole'able, he should feel comfortable saying so). +1 Sure, we require the candidates to think on their own (and experience shows that unfortunately shows that they don't always do), but this language is just offensive and also seems to discourage asking questions at all. Maybe rephrase it as something like While GSoC attendants should be able to solve problems on their own, it's OK to ask questions if you're stuck. See, now we don't think you're dumb anymore, but yes we expect that you put some effort into it. +At this point, you are ready do look in the code for the way of doing your +actual qualification task. s/do/to/. Ronald ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] doc: add a few note for sponsorship candidates.
On Fri, 20 Mar 2015 10:43:55 +0100 Stefano Sabatini stefa...@gmail.com wrote: On date Friday 2015-03-20 09:57:58 +0100, wm4 encoded: On Thu, 19 Mar 2015 20:43:55 -0400 Ronald S. Bultje rsbul...@gmail.com wrote: Hi, On Thu, Mar 19, 2015 at 4:53 PM, Nicolas George geo...@nsup.org wrote: +If at any point you have any question, do not hesitate to ask them. +Actually, yes, hesitate a few seconds, in case this question will make you +look dump. So read on. s/dump/dumb/. Also, I'm not sure that's a good attitude, we surely want students to be able to look up google'able stuff themselves, but asking questions to their mentor should be encouraged (and if the mentor thinks it's goole'able, he should feel comfortable saying so). +1 Sure, we require the candidates to think on their own (and experience shows that unfortunately shows that they don't always do), but this language is just offensive and also seems to discourage asking questions at all. Maybe rephrase it as something like While GSoC attendants should be able to solve problems on their own, it's OK to ask questions if you're stuck. See, now we don't think you're dumb anymore, but yes we expect that you put some effort into it. I don't think this is offensive but smart candidates will figure when and how to ask good questions by themselves, being told explicitly would be annoying for them. Also the focus is not about smart/silly, it is about finding a good tradeoff between mentee and mentor's time effort when asking/replying to a question. In general mentors' time is precious (because they're usually busy and/or are delivering their free time), so the candidate/mentee should do most of the effort, and ask questions only when he/she's put some efforts into trying to solve an issue, and show this effort when putting out the question. Of course, but telling a candidate that his question may be interpreted as dumb is the wrong way to go about it. It sound dismissive and unfriendly. Making demands is ok, but premature punishment or prejudice is not. (Yeah, we know most candidates will probably be bad, but there's no reason to repel potentially good ones just out of pessimism.) So, adding my two cents: GSoC attendants should be able to solve problems on their own, but it's fine to ask questions if you're stuck or if you are not sure about your task. When asking questions, you are also expected to show how are you trying to solve the related issue. Sounds ok to me. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] doc: add a few note for sponsorship candidates.
On Thu, 19 Mar 2015 21:53:12 +0100, Nicolas George wrote:
+@chapter So yeah, I would like to work on FFmpeg for
@url{https://code.google.com/soc/, Google Summer of Code} /
@url{http://sophia.estec.esa.int/socis/, ESA Summer of Code in Space} /
@url{https://www.gnome.org/outreachy/, Outreachy} / [insert here the latest
trendy program]. What must I do?
Dump the So yeah,.
+For the organization that sposors the program, there is probably a lot of
+paperwork. But frankly, we do not care; if we liked paperwork, we would be
+managers, not hackers.
s/sposors/sponsors
However, I don't think this paragraph is very helpful as it is.
Maybe something like this:
Refer to the homepage of the sponsor organization for information about
eligibility, timeline, required paperwork, etc. This process is the
full responsibility of the intern; the limited available FFmpeg mentor
time is best spent on providing help specific to coding.
+For us, there is not much to do: choose a proposed project that you want to
+do, select a qualification task for that project that is not already taken
+by someone else, announce you are about to start working, and then do so.
As for FFmpeg: choose a proposed project that you want to do, select a
qualification task for that project that is not already taken by
someone else, announce your chosen qualification task on the
ffmpeg-devel mailing list, then start coding.
+If at any point you have any question, do not hesitate to ask them.
...on the ffmpeg-devel mailing list or #ffmpeg-devel IRC channel.
I'm aware you mention contact info below, but I think it's good to
drill this info.
+Actually, yes, hesitate a few seconds, in case this question will make you
+look dump. So read on.
I think this do not contribute anything helpful and can be removed.
+@chapter How do I contact you? And, in fact, who are you?
+
+The people who work on FFmpeg do so mostly on their free time or as a
+complement to their regular job in computing or consulting. To contact us,
+you can use the devel mailing list or personal mail, depending on the
+contents of the message. Use discretion. You can also try the IRC channel.
To @url{https://ffmpeg.org/contact.html, contact us}, you can use the
ffmpeg-devel mailing list or the mentor's personal mail
s/devel/ffmpeg-devel
+@chapter How do I get to work?
+
+First, download FFmpeg. Not a prebuilt binary. Not a source snapshot. A full
+Git clone tree. If you do not know what that means, then you have reading to
+do.
See @url{https://ffmpeg.org/git-howto.html, Using git to develop
FFmpeg} for more info.
+You should subscribe to it, because otherwise, your mails will be held for
+approval instead of arriving in a few seconds.
approval for up to 48 hours
Hopefully that may stop at least one user from sending one or more
messages to the queue, then subscribing, then re-sending again
resulting in dupes depending on how vigilant/lazy I am while clearing
the queue.
+Also, be aware that some mail user agents send mails that are unreadable
+except by themselves; some have strange ideas about paragraph formatting and
+apply them to code snippet too. You can have a look at the low-tech mail
+archive on the FFmpeg site to see how your mails actually look like.
low-tech @url{https://lists.ffmpeg.org/pipermail/ffmpeg-devel/,
mailing list archive}
+@chapter What if, in the end, I am not taken?
s/taken/accepted
The rest of it looks good to me. Thanks for taking the time to do this.
Lou
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] doc: add a few note for sponsorship candidates.
On Thu, Mar 19, 2015 at 09:53:12PM +0100, Nicolas George wrote: Signed-off-by: Nicolas George geo...@nsup.org --- doc/Makefile | 1 + doc/sponsored_internships_howto.texi | 148 +++ 2 files changed, 149 insertions(+) create mode 100644 doc/sponsored_internships_howto.texi Not sure if the best place is there or the wiki, but at either place, something like that should be useful. Comments? overall very nice, i like it [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB When you are offended at any man's fault, turn to yourself and study your own failings. Then you will forget your anger. -- Epictetus signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] doc: add a few note for sponsorship candidates.
On Thu, Mar 19, 2015 at 09:53:12PM +0100, Nicolas George wrote: Signed-off-by: Nicolas George geo...@nsup.org --- doc/Makefile | 1 + doc/sponsored_internships_howto.texi | 148 +++ 2 files changed, 149 insertions(+) create mode 100644 doc/sponsored_internships_howto.texi Not sure if the best place is there or the wiki, but at either place, iam not sure either but in general when in doubt i would probably tend more toward the wiki as it can be edited and maintained by a larger group of people, iam not sure this is relevant or not here [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Into a blind darkness they enter who follow after the Ignorance, they as if into a greater darkness enter who devote themselves to the Knowledge alone. -- Isha Upanishad signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
