unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Lord <lord@emf.net>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Nick Roberts <nickrob@snap.net.nz>, emacs-devel@gnu.org
Subject: Re: Summer of Code projects for GNU
Date: Sun, 20 Jul 2008 23:27:45 -0700	[thread overview]
Message-ID: <48842C61.5070509@emf.net> (raw)
In-Reply-To: <87tzejvo5d.fsf@stupidchicken.com>

Chong Yidong wrote:
> Nick Roberts <nickrob@snap.net.nz> writes:
>
>   
>> In the past Emacs has not been directly involved but, assuming that Google run
>> a Summer of Code in 2009, I think that we should suggest some projects.  It's
>> still a long way off but successful projects appeared to be quite organised,
>> e.g.,
>>
>>         http://www.gnu.org/software/grub/grub-soc.html
>>
>> At the moment, I'm just looking for some consensus.
>>     

Are you sure the GNU project should be supporting GSoC?

For their investment in the project, Google gets a lot of volunteer
marketing, with people putting up posters at universities, press
coverage, etc.   Yet, they don't talk about free software but, rather,
open source.   And, in administering the project, they collect a lot
of HR-type recruitment data, both demographic and individual,
about the students.   And, they pick the funded projects by fiat rather
than accountably.   And, they arguably underpay the host projects
relative to the supervisory and reporting obligations they impose.
And, Google is very much a proprietary software company with
no signs of trying to change that.

I think GNU (and FSF) should look at the past few years of
GSoC, at the amounts of money spent on students and towards
FSF, add that up, and say:

"Hey, we appreciate support.  But this process is, at best, inefficient.
Your terms for getting that money is problematic.   How about just
giving us that money directly, instead, through one or more NPOs,
earmarked for development?   We don't want to encourage aspirants
to your program to advertise for you gratis.   We don't want to be obligated
to report to you in those ways.   We just want to advance software freedom
and develop free software and we can do that much better if you just
give us the money with fewer strings attached."


-t










>> For my part, I would like to suggest the migration of GDB in Emacs from
>> annotations to fully using GDB/MI and perhaps integration with ECB.  I have
>> quite clear ideas about how to do that and I am willing to do the mentoring.
>>
>> But it would be good to have other suggestions, which would require mentoring,
>> too.
>>     
>
> Good idea.
>
> One project that I can think of is a rewrite or revamp of the
> customization code.
>
>
>
>   





  reply	other threads:[~2008-07-21  6:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19  1:34 Summer of Code projects for GNU Nick Roberts
2008-07-21  4:47 ` Chong Yidong
2008-07-21  6:27   ` Thomas Lord [this message]
2008-07-21  6:20     ` Nick Roberts
2008-07-21 13:26     ` Chong Yidong
2008-07-21 14:01     ` Miles Bader
2008-07-22  2:48     ` Richard M Stallman
2008-07-30 13:27   ` Bastien

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=48842C61.5070509@emf.net \
    --to=lord@emf.net \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    /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).