emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: emacs-orgmode@gnu.org
Subject: Google Summer of Code update
Date: Sat, 14 Jul 2012 20:42:36 +0200	[thread overview]
Message-ID: <87vchqgp5v.fsf@altern.org> (raw)

Dear all,

this week, GSoC co-mentors and students spent time testing and
evaluating our GSoC projects.

Of the 3 ongoing projects, one will stop and the two others will

The "bugpile" project will stop: Thorsten produced lots of exploratory
writing for the design of a web framework based on elnode and Org, and
he wrote code for this.  But Eric and I feel like the project is not
going in the right direction.  So instead of spending too much time on
trying to agree about a new direction, we decided to stop the project.

This is a hard decision to take, but I think this is for the best.

I should thank again Thorsten here, as he's the one who convinced me to
go for the GSoC this year.  His code and docs remain available, and I'm
sure there are lots of ideas that will survive this experience.

  ~$ git clone git://orgmode.org/bugpile.git

Thanks also goes to Eric for his time mentoring Thorsten.

And thanks goes of course to Google! Being paid to write free software
is a priviledge -- even more when failing is just part of the game.

Aurélien's and Andrew's projects get boosted by the mid-term deadline,
check their repos:

  ~$ git clone git://orgmode.org/org-sync.git           [Aurélien]
  ~$ git clone git://orgmode.org/org-merge-driver.git   [Andrew]

*Please* read/test/review their code as much as possible: send feedback,
however premature you think it can be -- because *it is not*.

I just read this blog entry - "How to recruit open-source contributors":


This resonates very well with what I think and what I hope we will gain
from participating to the GSoC: new contributors.  So, please all take a
dive into the students' code, because that's how they will interact with
the list.  And students: please pick up questions on this list, pending
issues, known bugs -- and have a go, try fix things, report more stuff.
Do this in your free time :-) It will help you feel more comfortable
sharing your Org (coding) experience with fellows here.

Thanks for your support!


             reply	other threads:[~2012-07-14 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14 18:42 Bastien [this message]
2012-07-26 12:46 ` Google Summer of Code update 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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87vchqgp5v.fsf@altern.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).