That's right: Yorba was unfortunately not chosen as a mentoring
organization for this year's Google Summer of Code. Oh well. The good
news is that GNOME was chosen (as expected) as a mentoring organization,
and the GNOME people have expressed interest in having students work on
Shotwell projects. So this is a possible path forward. Some of us at
Yorba will apply to be mentors. The deadline for student applications
is April 8 (see
http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline)
so I'd encourage any students interested in working on Shotwell this
summer to apply by that time. If anyone's new to this thread, please
see Yorba's list of suggested summer projects at
http://trac.yorba.org/wiki/SummerCodeIdeas
Andreas, I think that either in-app video playback or FTP/HTML
publishing would be good summer projects. Migration to SQLHeavy is
probably something that the core team should consider, though if we look
at this soon and decide it would make a good summer project then we can
add it to our list. I'm not at all concerned about adopting other
database backends since I think it's unlikely we'd want to move to
anything other than SQLite.
Regarding a performance test suite, I think we'd want to build that as
part of a larger automated testing effort, which we've been thinking
about a test suite for a long time (see
http://trac.yorba.org/ticket/1068). But that will probably involve lots
of design and code refactoring and so is probably a project for the core
team.
Thanks for your mini-biography, and we'll look forward to your application.
adam
On 03/19/2011 07:26 AM, Andreas Brauchli wrote:
Hey Adam,
Unfortunately it seems that yorba hasn't been chosen as mentoring
organization as it's not listed.
This of course means more competition for us students as we will have to
grab GNOME spots. Not an easy task but certainly worth the challenge.
Besides the projects I listed on my previous mail I found a few other
ones that would interest me:
A project around SQLHeavy ( http://trac.yorba.org/ticket/3312 ). It
should include the evaluation without disturbing the main development
flow around shotwell.
The downside I see with SQLHeavy is that it might hinder the adoption of
other DB backends, if this is a concern (unless SQLHeavy itself is
adopted to be more of a GObject/Hibernate with various backends.)
A test suite for shotwell which would also generate the performance
numbers on a fixed set of data such that the development of progress can
be more closely/precisely tracked - the inflate image duplication tool
could optionally be integrated into it. My main concern there is that it
randomizes the dates of the photos which make it non-deterministic.
I would also have suggested a tracker integration as it would be pretty
GNOME related but since we can now write tags back, this comes pretty
much for free.. I'm not sure if there is other data worth tracking that
is not in EXIF/XMP. Maybe the event names and photo label?
Anyway, I would be happy to formalize good applications proposals for
any projects a yorba staff (yorbanito?) would be willing to mentor :)
Since I would really like to apply, I'll shortly present myself in a
more formal light:
I'm a 26yo 6th semester undergrad CS student at ETH Zurich, Switzerland.
I've got two years of full-time dev. work experience (I developed
managed C# code with a mid-sized swiss software company). I also
participated in a few open source projects like nGhost (c++) a car-pc
media center, the vala compiler (vala) where I wrote a few patches and
bindings, a few others with mainly small contributions (c/java/perl).
For shotwell I wrote the initial champlain map-widget integration and
I'm currently working on a naming event provider which given a date
returns a meaningful string for a few holidays (see
http://trac.yorba.org/ticket/2882 ) like the author of the report says:
nothing urgent but cool :)
best
andreas
On Mit, 2011-03-16 at 22:32 +0100, Andreas Brauchli wrote:
Hi Adam,
On Mon, 2011-03-14 at 10:38 -0700, Adam Dingle wrote:
Andreas,
thanks for the interest in working on Shotwell for Google Summer of
Code, and apologies for the long delay in responding - as you probably
know the Yorba team has been pretty busy working toward the upcoming 0.9
release.
No worries, 0.9 is an important release!
I'm happy to report that Yorba has applied to be a Summer of
Code mentoring organization this year.
This is great news for us students - I really hope yorba gets accepted
as mentoring organization.
You can see our list of project
ideas here:
http://trac.yorba.org/wiki/SummerCodeIdeas
Alternatively to working on a sharing solution (see next chunk), I would
be interested in:
- play videos directly in Shotwell rather than via external player
(#2820)
- FTP publishing, with optional generation of a static html gallery
I do think that the Shotwell server idea might be too big for a Summer
of Code project, however. We do want to take that on someday, but there
are lots of open questions to answer about how exactly Shotwell should
work in a client/server situation and I think making this all work well
is probably a major project for the core team. If you have a
well-developed vision for exactly how this should work and how you would
modify Shotwell to make that happen, feel free to post it here and we
can discuss more. Otherwise I'd encourage you to look at our ideas page
for other projects that I think would be easier to take on this summer.
Cheers -
I agree that the server idea is indeed a major project. My vision is
certainly not too elaborated yet - the planning would be a particularly
critical part of the project.
Best of luck for the 0.9 release
andreas
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
