Student applications closed about 13 hours ago. Thanks to all the
students who applied to us.
We've made a start on reviewing proposals - please keep an eye open for
emails or IRC (if you're on IRC) as we may have further questions for
you.
One general note - like many orgs in GSoC, we do expect students to
contribute a patch as part of their application. This is very helpful
as it shows us how you approach problems and what you're like to
interact with, and also helps us to assess if your skill levels are
appropriate for the scope of what you're proposing to do.
A number of the proposals don't currently have a matching patch
contribution, but it's not too late to work on one - the initial phase
of proposal review is until April 22nd when we need to tell Google how
many slots we'd like. If you start now you should have time to
implement a bug fix or small feature and then work through the patch
submission process.
Cheers,
Olly
On Wed, Apr 10, 2019 at 07:56:39AM +0100, Olly Betts wrote:> One general note - like many orgs in GSoC, we do expect students to > contribute a patch as part of their application. This is very helpful > as it shows us how you approach problems and what you're like to > interact with, and also helps us to assess if your skill levels are > appropriate for the scope of what you're proposing to do. > > A number of the proposals don't currently have a matching patch > contribution, but it's not too late to work on one - the initial phase > of proposal review is until April 22nd when we need to tell Google how > many slots we'd like. If you start now you should have time to > implement a bug fix or small feature and then work through the patch > submission process.Just a reminder here as we still have only seen patches from a minority of applicants, and there's not a lot of time left to work through the patch review process before we have to finalise our slot request. (The process is that we need to tell google how many slots we want by this coming Monday. We don't need to decide who to allocate those slots to yet, but we don't want to request slots unless we're confident we can use them - there's no reallocation of unused slots so we'd be depriving another org of a slot if we ask for one and then don't use it.) Cheers, Olly
Hey Olly, So finally I managed to setup and implement the Omega server in my vagrantbox with dynamic CGI. I would like to know what is the good first step to add HTML5 templates( https://trac.xapian.org/wiki/ProjectIdeas#ReworkOmegatemplatestousemoremodernwebtechniques). I know that Omega uses templates for opensearch,query and few more. Also Can you please hint me towards setting up a ticket for the task (I can't find ticket for HTML5 subtask here : https://trac.xapian.org/report/1?sort=component&asc=1&page=1). Thanks. Prithi aks jugnu On Wed, Apr 17, 2019 at 4:34 PM Olly Betts <olly at survex.com> wrote:> On Wed, Apr 10, 2019 at 07:56:39AM +0100, Olly Betts wrote: > > One general note - like many orgs in GSoC, we do expect students to > > contribute a patch as part of their application. This is very helpful > > as it shows us how you approach problems and what you're like to > > interact with, and also helps us to assess if your skill levels are > > appropriate for the scope of what you're proposing to do. > > > > A number of the proposals don't currently have a matching patch > > contribution, but it's not too late to work on one - the initial phase > > of proposal review is until April 22nd when we need to tell Google how > > many slots we'd like. If you start now you should have time to > > implement a bug fix or small feature and then work through the patch > > submission process. > > Just a reminder here as we still have only seen patches from a minority > of applicants, and there's not a lot of time left to work through the > patch review process before we have to finalise our slot request. > > (The process is that we need to tell google how many slots we want by > this coming Monday. We don't need to decide who to allocate those > slots to yet, but we don't want to request slots unless we're confident > we can use them - there's no reallocation of unused slots so we'd be > depriving another org of a slot if we ask for one and then don't use > it.) > > Cheers, > Olly > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20190418/9d445f2d/attachment.html>