[geeklog-devel] GSoC 2011 announced
websitemaster at cogeco.net
Mon Jan 31 09:24:28 EST 2011
For a GSOC project can we group a bunch of smaller similar projects together
to get 3 months of work? For example along with Aloha we could also add a
number of feature requests that are in the bug tracker for edit forms. The
upside to this is as a smaller project is finished we can then get it
incorporated into core before they start on the next small project.
Also would it be frowned upon if we had projects that are continuation of
previous years GSOC projects?
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: January-29-11 3:53 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] GSoC 2011 announced
Dan Stoner wrote:
> Are adding editors really so simple? It seems like there are a lot of
> "quirks" that could use some polish.
Keep in mind that we're looking for projects that would keep a student busy
for 3 months (and that's working on it more or less full time).
I'd say a working integration of Aloha, i.e. being able to save, create new
stories, and respect permissions, should take about a week. Then you'd have
to do it again for the other areas / plugins as well (staticpages etc.). Add
another few days for some nice support of autotags, and the image upload (if
available). That should still be way less than a month's worth of work.
Since Aloha is an inline editor, it's probably worth taking a fresh look at
how Geeklog works from that perspective. Like, for example, being able to
edit "normal" blocks without going to the editor would be a nice new
feature. So there may well be some more work here. Still not sure if there's
enough for a full-fledged GSoC project, but we should start collecting these
ideas. Use the wiki.
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel