unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@MIT.EDU>
To: "Stephen J. Turnbull" <stephen@xemacs.org>,
	"emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
Subject: Re: GSoC 2013
Date: Sun, 5 May 2013 12:09:40 -0700	[thread overview]
Message-ID: <379181EA-3CC0-47CE-B870-C9E5273C34F5@mit.edu> (raw)
In-Reply-To: <87vc6xjumn.fsf@uwakimon.sk.tsukuba.ac.jp>


On 05 May 2013, at 08:48, "Stephen J. Turnbull" <stephen@xemacs.org> wrote:
> It's really bad form to have
> the student participating in the slot request process on a public
> list, don't you think?

Not really, no. It's only a potential problem with the politics of
who or what gets chosen when resources are tight. "2 essential of
2 slots" is not such a situation, there's no `vote' over which
student projects get mentored, and even if there were, I seriously
doubt anyone would vote against Stefan mentoring a project to improve
vc. This is `bad form' only in a theoretical alternate universe.

> Note I don't blame Fuqiao.  Although I don't know his work in detail,
> he seems to be precisely the kind of student that GSoC wants to
> support, engaged in Emacs development and likely to continue.  But
> that Emacs is so disorganized as a GSoC subproject that he could
> actually come to the point of posting such a thing speaks volumes
> about Emacs (as a GSoC subproject).

Meh. GSoC is not a school, even though they borrow the terminology
`student' and `mentor'. They're looking to support motivated
mentor-ees with initiative. That seems like exactly what happened
here.

Every year around the GSoC deadline there's some form of complaint
that there wasn't enough or the right kind of process around getting
GSoC students and mentors for Emacs, and that it's a shame that the
potential was wasted. GSoC is an effort to help get potential hackers
hacking, not to outsource programming needs to cheap labor. Anyone
who actually wants to see Emacs get more involved in GSoC needs to
start putting in organizational effort (creating process, identifying
projects, recruiting students, recruiting mentors, etc) *before*,
not *at* the deadline.

~Chad

P.S. Sorry for the rant.



  reply	other threads:[~2013-05-05 19:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 14:30 GSoC 2013 Daimrod
2013-05-04 17:54 ` Glenn Morris
2013-05-04 18:15   ` joakim
2013-05-04 18:18     ` Glenn Morris
2013-05-05  5:01       ` Xue Fuqiao
2013-05-05  9:19         ` Daimrod
2013-05-05 14:08           ` Xue Fuqiao
2013-05-05 14:34             ` Stephen J. Turnbull
2013-05-05 14:38               ` Daimrod
2013-05-05 15:48                 ` Stephen J. Turnbull
2013-05-05 19:09                   ` chad [this message]
2013-05-06  4:52                     ` Stephen J. Turnbull
2013-05-06  7:58                       ` joakim
2013-05-06  9:54                         ` Stephen J. Turnbull
2013-05-06 12:22                           ` Daimrod
2013-05-06 12:53                             ` Stephen J. Turnbull
2013-05-06 13:01                               ` Bastien
2013-05-06 15:32                                 ` Stephen J. Turnbull
2013-05-05 14:53             ` Daimrod
2013-05-04 18:23   ` Daimrod

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=379181EA-3CC0-47CE-B870-C9E5273C34F5@mit.edu \
    --to=yandros@mit.edu \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).