Hi, On Mon, Jan 9, 2017 at 8:13 PM, Fenil Shah <[email protected]> wrote:

Hi, Eduard,

Thanks for the information that you have provided. I will start going through this. In the mean time, I would like to know if you would want me to familiarize myself with any specific coding language or software

The developer guide should give you a pretty good overview of the coding languages involved: http://platform.xwiki.org/xwiki/bin/view/DevGuide/ Normally, it`s the standard web development HTML, CSS, JavaScript (+ JQuery). For the server side (i.e. in wiki pages), there is the scripting part (http://platform.xwiki.org/xwiki/bin/view/DevGuide/Scripting) that would mostly be composed of Apache Velocity scripts (a nice XWiki-focused introduction can be studied at http://platform.xwiki.org/xwiki/bin/view/DevGuide/XWikiVelocityTraining) but it can also mix a bit of Groovy (optional, usually needed for workarounds or more complex stuff) and it might be useful (optional, depending on the application) to know a bit of Java as well, in case you need to build your own components.

that would be helpful to me in order to work with your company.

Again, don`t mix a company with an Open Source project's community. Here, we are the community of the XWiki open source project. If you are interested in GSoC and Open Source, in general, you should clarify these matters (e.g. by reading up on https://en.wikipedia.org/wiki/Open_source or other resources on what open source is all about).

Also I would like to inform you that my main area of interest is front-end Web Development.

We can always use the help on front-end. The simplest advice I can give you is to download the product, start it and do a quick bug hunting session for small things like typos, misalignments in the UI, things that look ugly and could use a revamp, unusual behavior in forms or UI elements, etc. (small things). Once you find such surface bugs/problems, file up a bug report on jira.xwiki.org, get the sources and try to fix it. If you end up with a pull request on github containing your fix and it gets reviewed and accepted, your chances of being accepted for GSoC (shoud XWiki get accepted to participate in 2017 as well) increase dramatically. Not to mention that you would be actually changing the XWiki product yourself, through your contribution and thus, actively participating in an open source project. Hope this helps, Eduard

Regards, Fenil Shah

On Mon, Jan 9, 2017 at 4:35 PM, Eduard Moraru <[email protected]> wrote:

...

Hi, Fenil,

Nice to meet you!

Good thinking in starting early ;)

If you are interested in the XWiki product and our community, make sure to check out our website www.xwiki.org (download, documentation, dev resources, etc.) and the GSoC dedicated section http://gsoc.xwiki.org where you can find some advices for would-be GSoC students, getting started tips and previous year projects (section at the bottom). To make it easier, in case you don`t find them, the GSoC sutdent guidelines are http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Guidelines

We welcome you to get familiar with the product and, if you like it, to start contributing. We`re here for any questions or help you might need.

Don`t hesitate if you have any questions, either here, on the mailing lists, or on IRC (#xwiki on irc.freenode.net).

Thanks, Eduard

On Sat, Jan 7, 2017 at 10:38 PM, Fenil Shah <[email protected]> wrote:

...

Hi,

I am Fenil Shah, a 2nd year B.tech (ICT) student, and am interested in learning about open-sourcing and would like to work with your company for getting a better idea as to how I can contribute in the same. I have a basic knowledge in the following languages:

Java, HTML, CSS, JavaScript, Bootstrap, PHP, C, C++ and Python

My aim is to crack GSoC this year and would like you to guide me for the same.

Regards, Fenil Shah