Please create my journal outline, the blank project plan and notes pages on the wiki (I don't want to mess up the names).<div>I've filled up the missing information.<br><div><br></div><div>Thanks,</div><div>Marius<br>
<br><div class="gmail_quote">On Tue, May 8, 2012 at 5:43 AM, Olly Betts <span dir="ltr"><<a href="mailto:olly@survex.com" target="_blank">olly@survex.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you're one of our six selected GSoC students, please read through this<br>
email and attend to anything which needs doing. If anything is unclear,<br>
please ask.<br>
<br>
I've created a page on the wiki for each of the selected projects, which<br>
are all linked from this overview page:<br>
<br>
<a href="http://trac.xapian.org/wiki/GSoC2012" target="_blank">http://trac.xapian.org/wiki/GSoC2012</a><br>
<br>
There's a table of useful information on each summary page. Please check<br>
that this is correct for you, and fill in the missing information. For<br>
most of you this is:<br>
<br>
* "work hours" - we realise you probably won't be working exactly the<br>
same hours every day, but it's useful for us to have some idea when we<br>
can expect you to be around. We also encourage you to be on IRC in<br>
#xapian at least while you are working, as that will make interaction<br>
easier.<br>
<br>
* repository location - I've filled this in where I already know it, but<br>
for the rest of you please clone/fork our repository, push it to<br>
a public location, and put a link to that on your project's wiki page.<br>
There are already xapian git mirrors on gitorious and github, but any<br>
public hosting site is OK. If you need help getting to grips with git,<br>
just ask - that's what we're here for. Don't forget to actually push<br>
changes regularly (at least once a day is good) so there's a remote<br>
backup of your work, and so we can easily review your work.<br>
<br>
* Journal - this is for you to document your progress, which will help<br>
the mentors (and other interested people) to follow how you are doing,<br>
and is also likely to help you. If you already have a blog, or would<br>
like to start one, then you can just post to that with a tag, or in a<br>
category, so that it's possible to just see the posts about the project.<br>
Then link to that from the wiki page (the trac wiki format for external<br>
links is:<br>
<br>
[<a href="http://blog.example.org/" target="_blank">http://blog.example.org/</a> Journal]<br>
<br>
If you'd prefer to just maintain the journal on the wiki, let me know<br>
and I'll create an outline for you, like the one we used last year.<br>
<br>
During coding, you should aim to make at least a couple of entries each<br>
week. It doesn't need to be anything formal - just what you're working<br>
on, what you have recently completed, what obstacles you're frustrated<br>
by, etc. Communication is an important part of your project.<br>
<br>
* Project plan - this is for the project plan part of your application<br>
- i.e. the bit which talks about the project and the timeline. We want<br>
a publicly visible copy of this so that anyone in the wider Xapian<br>
community who is interested in the project can see it. You can either:<br>
<br>
+ Copy the proposal to the wiki. We did this last year, and the<br>
main annoyance is that you need to reformat it to use trac's<br>
wiki syntax.<br>
<br>
+ Mark your proposal as "public" in melange and link to it there.<br>
Note that this means that personal information in the proposal (like<br>
phone numbers, etc) will be public. If you'd like to remove such<br>
things, ask Dan or me and we can record them elsewhere and allow you<br>
to edit the proposal.<br>
<br>
+ Attach the proposal to the wiki in some other format.<br>
<br>
* Notes - this is intended as a place to note down any information which<br>
is useful to you and/or other people interested in the project, such<br>
as links to background information and other useful resources, TODO<br>
items, other notes, etc. You may prefer to keep such information in<br>
a README in your code repository, in which case you can just link to<br>
that.<br>
<br>
Feel free to create more sub-pages or links if you'd find them useful.<br>
<br>
Each project has a "primary mentor". One reason is because someone needs<br>
to be in Google's system as your mentor, but they are also responsible for<br>
making sure you do actually get a response to questions, and things like<br>
that. But we're intending to use a similar "group mentoring" approach as<br>
we did last year, so you'll be expected to discuss issues and ask questions<br>
in public via the #xapian IRC channel or on the xapian-devel mailing list.<br>
This is better for you as it means you don't have to wait for one person to<br>
be available to respond, and better for us as it makes it easier to keep<br>
track of how everyone's doing. Public communication is also the way open<br>
source projects usually work, and GSoC is meant to give you experience of<br>
working in an open source project.<br>
<br>
If there's an issue you'd rather not disclose in public, then you can<br>
either talk to your primary mentor, or to one of the admins (that's Dan<br>
Colish and me).<br>
<br>
"To do" summary:<br>
<br>
* Set up your git repo (if you haven't already).<br>
<br>
* Fill in missing info (and correct any errors) in your page under:<br>
<a href="http://trac.xapian.org/wiki/GSoC2012" target="_blank">http://trac.xapian.org/wiki/GSoC2012</a><br>
<br>
Good luck with your projects, and we look forward to getting to know you<br>
better over the course of the next few months.<br>
<br>
Cheers,<br>
Olly (on behalf of the Xapian GSoC mentors)<br>
<br>_______________________________________________<br>
Xapian-devel mailing list<br>
<a href="mailto:Xapian-devel@lists.xapian.org">Xapian-devel@lists.xapian.org</a><br>
<a href="http://lists.xapian.org/mailman/listinfo/xapian-devel" target="_blank">http://lists.xapian.org/mailman/listinfo/xapian-devel</a><br>
<br></blockquote></div><br></div></div>