Re: GSoC 2019 Update
PrithiPal Singh <[email protected]> Thu, 18 Apr 2019 10:48:34 -0700
| Newsgroups | gmane.comp.search.xapian.devel |
|---|---|
| Message-ID | <CADhxk0=aNaa_GuBi7vKvByX+qLniCssizRug5FyTe8iC7mV+pQ@mail.gmail.com> |
--000000000000238b4b0586d19d6f Content-Type: text/plain; charset="UTF-8" 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 <[email protected]> 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 > > --000000000000238b4b0586d19d6f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">Hey Olly,<div><br></div><div>So finally I= managed to setup and implement the Omega server in my vagrantbox with dyna= mic CGI. I would like to know what is the good first step to add HTML5 temp= lates(<a href=3D"https://trac.xapian.org/wiki/ProjectIdeas#ReworkOmegatempl= atestousemoremodernwebtechniques">https://trac.xapian.org/wiki/ProjectIdeas= #ReworkOmegatemplatestousemoremodernwebtechniques</a>). I know that Omega u= ses templates for opensearch,query and few more. Also Can you please hint m= e towards setting up a ticket for the task (I can't find ticket for HTM= L5 subtask here :=C2=A0<a href=3D"https://trac.xapian.org/report/1?sort=3Dc= omponent&asc=3D1&page=3D1">https://trac.xapian.org/report/1?sort=3D= component&asc=3D1&page=3D1</a>).</div><div><br></div><div>Thanks.<b= r>Prithi aks jugnu</div></div></div><br><div class=3D"gmail_quote"><div dir= =3D"ltr" class=3D"gmail_attr">On Wed, Apr 17, 2019 at 4:34 PM Olly Betts &l= t;<a href=3D"mailto:[email protected]">[email protected]</a>> wrote:<br></di= v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde= r-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Apr 10, 2019 at= 07:56:39AM +0100, Olly Betts wrote:<br> > One general note - like many orgs in GSoC, we do expect students to<br= > > contribute a patch as part of their application.=C2=A0 This is very he= lpful<br> > as it shows us how you approach problems and what you're like to<b= r> > interact with, and also helps us to assess if your skill levels are<br= > > appropriate for the scope of what you're proposing to do.<br> > <br> > A number of the proposals don't currently have a matching patch<br= > > contribution, but it's not too late to work on one - the initial p= hase<br> > of proposal review is until April 22nd when we need to tell Google how= <br> > many slots we'd like.=C2=A0 If you start now you should have time = to<br> > implement a bug fix or small feature and then work through the patch<b= r> > submission process.<br> <br> Just a reminder here as we still have only seen patches from a minority<br> of applicants, and there's not a lot of time left to work through the<b= r> patch review process before we have to finalise our slot request.<br> <br> (The process is that we need to tell google how many slots we want by<br> this coming Monday.=C2=A0 We don't need to decide who to allocate those= <br> slots to yet, but we don't want to request slots unless we're confi= dent<br> we can use them - there's no reallocation of unused slots so we'd b= e<br> depriving another org of a slot if we ask for one and then don't use<br= > it.)<br> <br> Cheers,<br> =C2=A0 =C2=A0 Olly<br> <br> </blockquote></div> --000000000000238b4b0586d19d6f--