unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joshua Branson <jbranso@purdue.edu>
To: help-gnu-emacs@gnu.org
Subject: Emacs developers help wanted for Purdue University's Hack the Anvil
Date: Tue, 03 Mar 2015 20:35:34 -0500	[thread overview]
Message-ID: <54F66166.1070502@purdue.edu> (raw)

 Hello Emacs developers! 

	I'm a recent Purdue University graduate, and fellow emacs hacker!  I'm emailing you, because I could use your help this weekend!  Purdue University (in West Lafayette IN) is organizing this awesome hackathon: http://hacktheanvil.com/ (March 6-8). 50 companies are coming to give away various prizes for the best and coolest apps/games/hardware hacks. The companies are also going to be sending talented developers to help the 400 Purdue students develop an app/game or use a cool API. So, that's why I'm planning on giving away a $20 prize (plus candy) to the hacker/team that makes a really cool emacs minor mode in the 36 hours that they hack, and if a hacker needs help on an emacs hack, I can answer their question. But, there's one problem...

	I'm not a great emacs hacker (I know, woe is me   ).  I've only made 2 emacs minor modes and contributed only a small code snippet to web-mode. Plus, I'm not an expert lisper, BUT if I am going to give away this prize, I'd like to be able to answer some really hard/deep questions about emacs lisp. Here's your mission, should you choose to accept it:  Would use be willing to dig deep this weekend? Can you set aside 2-4 hours (or more if you really want to.  I won't complain.) between Friday March 6th 7pm and Sunday 11am (central time) to skype with me or a Purdue hacker this weekend at the hackathon, if we have questions about how to hack an emacs minor mode?

	To be more specific, you probably won't have to answer too many questions. Most of the hackers find out how to do stuff on their own and rarely ask for help, because we're a proud bunch of nerds.   So if you do decide to help, you'd probably be able to sit by the computer and watch a movie or tv show, until someone comes and asks me a question that I don't know to answer.  Also, you can pick the hours that you want to help, because I don't expect you to get up at 1am to help answer a question. 

	
    Thanks,

    Joshua Branson

P.S. I'm sorry I'm asking you to do this so close to the event, and I hope you'll forgive me. Also, I'm not sure if this is the best list to be sending this email to. Should I send this email to the emacs-devel mailing list as well?






             reply	other threads:[~2015-03-04  1:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  1:35 Joshua Branson [this message]
2015-03-04  4:40 ` Emacs developers help wanted for Purdue University's Hack the Anvil Vaidheeswaran C
2015-03-04 11:33 ` Thien-Thi Nguyen
2015-03-04 11:56   ` Thien-Thi Nguyen
     [not found] <mailman.1260.1425433307.31049.help-gnu-emacs@gnu.org>
2015-03-04  1:52 ` Emanuel Berg
     [not found] <mailman.18235.1425443899.31050.help-gnu-emacs@gnu.org>
2015-03-04 14:28 ` Joshua Branson
     [not found] ` <mailman.1296.1425479298.31049.help-gnu-emacs@gnu.org>
2015-03-04 18:16   ` Emanuel Berg

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=54F66166.1070502@purdue.edu \
    --to=jbranso@purdue.edu \
    --cc=help-gnu-emacs@gnu.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.
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).