A summary of how you would intend to complete this project.Reasons why Google and KIWIX should sponsor it (How useful will it be to our end users? Why do you think you can achieve this?).A brief description of the aims of the project.A title (basically a few words to tell us what you plan to achieve).Do you have any experience using source control e.g.How many hours are you able to devote to your chosen project each week?.Do you currently have any other summer commitments?.Do you have any prior open source experience?.Have you participated in Google Code-in in the past?.
#Kiwix googleaply code#
Have you participated in Google Summer of Code in the past?.Your e-mail address (and other information that may be useful to contact you, e.g.Your application should contain the following information: While your code is compiling, look through the GsoC student guide from FLOSS manuals. But then again you could be smarter: be bold and ask why things are this way and not. If you think you know the problem better than the mentor does, it could be that you have misunderstood it. A good summary shows us that you have done some thinking and want to confront an actual problem. Even better: explain why you ask this question.
Asking them is proof to us that you are serious. We have all been new to Kiwix once, we have all needed to ask questions. Rule 1: Ask questions! Not generic ones, but specific ones, on the repo (so we know what they pertain to).
When you think of Kiwix, think Wikipedia (Be bold!) or think Nike (Just Do It!). You typically want language data from GitHub, core tools from our repo. Play with it, and see what you could improve.
#Kiwix googleaply install#
Become familiar with Kiwixįirst, install Kiwix. We want to look into previous works you’ve done, even if it’s a little game for your sister, it will tell us how you think. Create a GitHub accountīut – you should already have one (or SourceForge). Once you are in the #GSoC channel, even if you’re idling or don’t say anything, you’ll discover more about how Kiwix works. We don’t post it here so you are forced to read the contributing.md file. There’s a link to get an invite in the repositories.
We’re not saying that following the advice below will automatically get you a mentor, but going through it will give you a pretty good chance! Join our Slack channel Simply show that you’re proactive and you will be in the top 10% already. So read it before asking questions! But if you have another idea, that’s great and we want to hear all about it. If you find yourself asking do you have any XYZ projects… – you didn’t read the ideas page and that will make us sad. If the mentors remember you, your chances of being picked are higher. Refine your application based on that feedback. Get in contact with your potential mentor as soon as possible by sending your proposal via the GSoC interface, and ask for feedback: it doesn’t need to be pass-or-fail, particularly if we like your initial idea. We get a lot of proposals: some good, most bad. If you know of any breaks or absences beforehand, be upfront about them and plan around them. Don’t forget to leave time for getting familiar with the platform (this should be ideally before, or during the community bonding period), and for documentation. Show you have a definite plan with dates and deliverables, split into weeks is probably best. Three months may seem like a long time, but it isn’t. Time flies, project tend to overshoot or end up being more complicated that thought, so try to err on the safe side: this is a sign of maturity. But if you have a «way out there» idea, don’t panic! We’re still interested, but we’ll try to find a subset of it which is achievable in the time scale available. We’re more likely to accept ideas which are realistic than ones which are «way out there». Here are the main tips to help you in writing your GSoC application (thanks to the folks at Apertium!) 1.
0 kommentar(er)
