IIT Palakkad Students Talk about Drupal and Their Summer Internship with Zyxware
https://www.zyxware.com/sites/default/files/styles/user_image/public/pictures/Z_ribbon.png?itok=va3zzVQA
BY webmaster
1 year ago
Drupal
0
comments comment

Second year Computer Science Engineering students of IIT- Palakkad did a short stint at the Kochi branch of Zyxware Technologies as part of their summer internship. Here are some excerpts from a talk with Adrian McDonald and Anish Mathew. We also got a chance to hear from their professors after they did a presentation about it at their college, which we have added at the end.

Q. First let’s start with some casual questions on life at IIT Palakkad, how do you relax?

We have extra curricular activities. We have tennis and football other than that we spend our time with friends. So that is our main form of relaxation.

Q. Anish, you are from Kerala but Adrian, how do you find Kerala different from Kolkata?

Kerala is a beautiful place especially Kochi. Culture is different but yes, it is really scenic.

Q. Have you been to any other part of Kerala?

Kochi and Palakkad so far.

Q. Why did you choose to intern with Zyxware? How long was it?

Anish: We were actually looking for internships and we wanted to target companies where the number of employees were small in the office, so we could get a more real life experience. And then our professor told us about Zyxware that they had come there to the college and might be working on our website. We heard about it and we read that you were working on Drupal: Drupal Open Source , so I got interested in that. That was the reason.

Adrian: The main reason was that because it was Open Source. Our professor did tell us that since we were working in a small group, the focus that we would get will be more concentrated than anywhere else. That was why we choose Zyxware. We had another offer from a company in Bangalore but they said that your evaluation will be done weekly but here we get evaluations every single day. So I think this is more focused and it is much better this way. So we made the right choice. We are at the tail end of our 6 week internship.

Q. What were your first thoughts and observations when starting the internship?

Anish: This is my first interning experience. I thought the atmosphere would be more strict but then after coming here I found out it was much more pleasant and people are more supportive. The expectations are that I would learn something new and would be able to contribute to Drupal. So we have been going through the course. I find that I can contribute with some more effort.

Adrian : It is the same.

Q. What were some of your internship responsibilities?

So the first responsibility that was given was more of an examination, more of a test. We were given a list of a few of the things that were needed to be done over Drupal, over the site builder. And then we started understanding how Drupal works from the inside.

Q. Were you both familiar with Drupal before or Open Source?

No, we weren’t. About a week before we came for the internship, we received a link to a site to catch up with the site builder. That is what we did.

Q. What was the most interesting thing that happened while you were interning here?

Anish: Honestly, it was the treats that we got on Friday. The atmosphere here is almost like a college. There during intervals and lunch break, people are like shouting. At lunch time here people are talking and interacting. That is fun.

Q. What was the favorite part of your internship experience with Zyxware?

Adrian: We had sessions with our mentor. He told us about his experiences and about how Open Source Software developed and what were the other applications of Open Source. That was also good.

Q. As your time at Zyxware comes to a close, what has it been like or what did you learn from your overall experience at Zyxware?

The experience was very good. We got more than what we expected. We had more mentor time. We had two mentors. Vimal and Mishal. They explained to us a lot which was much more than we expected. It meant a lot to us. And then whenever we sent a mail we got a reply whether it is good or not. That was also good. We are planning to maybe come back in December during our winter break, we have not finalized it yet.

Adrian: Well, that is a request we are trying to make actually.

Q. How would you describe our company culture?

Everyone is co-operating with the interns. Helping each other. So when anyone has a doubt, we can always see them asking others. So it is not one person that answers but everyone comes and gives their input.

Q. What about you, Adrian?

The same thing because we had a doubt on a particular project and we were stuck for a while. Our mentors guided us through and helped us solve it.

Q. How would you describe your experience working on Drupal?

We actually were not trying to make a website. That was only the first week. Then we started learning how Drupal works. We were reading Drupal code and all that. So actually we are working on Drupal 8. Since it is object oriented it is actually challenging to find out how Drupal 8 works. But then over the weeks, we have come to a good understanding.

Q. Adrian, would you like to add something?

I think the community is very vibrant in Drupal. So while we were learning to contribute to the pipeline, we saw a lot of people were contributing. What is a contribution, to add a particular feature or not, the discussion went into all of this. We had to read through that. Then we had a chance to collaborate with people that were experienced in Drupal and all that.

Q. Did you find Drupal a steep learning curve?

Steep learning curve definitely. Cause we were not used to so much object oriented programming.

Q. What are your future plans concerning contributions to Drupal?

When you asked us what have been our responsibilities for internship, what we mentioned was what we did for the first week. After that we made a presentation. We made a slide for the presentation on Drupal . We will be making the presentation this weekend. And then we started searching the Search 404 module and giving patches for it. So we have started contributing to the contributed modules now. So after this internship, during the coming months we will be continuing to contribute to Drupal. We are interested in doing that.

Q. What did you learn in your internship that you can now apply to the classroom setting or to your future?

I think firstly it is writing proper codes. Our mentor stressed on following the style guide and writing the code according to that. That is one thing we are going to take away from here.

Q. What about you, Anish?

The same thing of course and working on Open Source has been a good experience. So we will be definitely writing that on our CV. Plus this internship. We came here because we were interested.

Q. What skills did you acquire or what did you learn during your internship that you will be able to highlight in your resume, cover letters, and/or interviews?

We got the opportunity to work on Open source. That is the main highlight. Plus what we said earlier. Before this, we had done lab courses so we could do coding ourselves. Working on a single project by ourselves. Here we saw, other people are working on team projects so we know how they collaborate. Vimal gave an extensive talk on how to manage a team project on a Git environment and all that. So that is something we will be taking away from here. When we work on group projects we will be making use of that. So I think more than what we are going to put on our resume, Zyxware helped us to use this information to make something else and then apply that on our resume.

Q. What will be a word of advice you will give to those who seek internship? What are its benefits?

One major thing that our professor actually told us, while trying to choose internship was to focus on places where you will get a personalized atmosphere. So when we chose Zyxware, one of the main reasons was that apart from the Open Source part we were informed that the set up was small. So whenever someone is trying to get an internship our advice to them is to try to go to a startup or a small place where you will get personalized attention rather than going into a big company just for the name of it. And the experience has been very nice at Zyxware.

Q. Do you have any suggestions on how we could improve the internship programme of Zyxware?

If it is possible to work with a team. We have been directly mentored, but if we could work on a project that they were working on. And also if we could work on something called pair programming. If we could be allowed to work on something like that. That would help.

So we now know how the software works. But we would also like to know how the software is used. It was kind of like a crash course. We would like to know all about it. How to build a website using Drupal and all that. We can always learn it. But getting a personalized experience is much better.

This is pure learning, having more interns would have been nice.

Feedback from the Professors

"One of the major objectives of the internship is to get hands on training for our students with real life experience and working in a professional software development environment. This gives them the familiarity to deal with live projects instead of the experimental ones done in our labs. With regards to the presentation that they did at the institute, this was one of the best in terms of quality. The regular feedback the students got from their mentor in Zyxware really helped in their internship learning. Based on the presentation and the input from the students we would love to send more students to Zyxware as part of our internship program.”

Dr. Jasine Babu, IIT-Palakkad

"The presentation of our students who came to Zyxware for internship was well structured and informative. Many internship presentations tend to loose the audience because the students focus only on what was learnt and do not put enough thought on how to convey that effectively in a 15 min presentation. We are also happy that the students could get to work on a complex problem and familiarize themselves with the issues of scalability and maintainability. This exposure that they got in Zyxware cannot be replicated in a college setting and really benefited the students."

Dr. Deepak R., IIT-Palakkad


RELATED ARTICLE

close

on 01st January 2008 / by webmaster
We have added a few new modules to our site recently. Two of these are the StumbleThis module and the DiggThis module. Drupal already had a DiggThis module available for download but there was no StumbleThis module. StumbleUpon has been a popular source of traffic for zyxware.com and we wanted users to have an option to add any of our pages to their StumbleUpon favorites. So we created our own StumbleUpon module. Normally people use stumbleupon toolbar to stumble websites. However when the toolbar is not enabled this provides an easy way to add the URL to the stumbleupon favorites. The StumbleThis button will be shown on the left of the content inline. Positioning of the StumbleThis button can be controlled by the weight option in the admin menu. By setting a negative value you can have the button displayed on top of the post while a positive value will take it to the bottom of the post.Click here to download the StumbleThis module for Drupal. The module has been tested with Drupal 5.1. Please use the comments form below if you have any questions or suggestions. Open Source Web Development Drupal Blogging Free Software Drupalgive Leave a reply Your email address will not be published. Required fields are marker * Sean (not verified) access_time 24 May 2019 - 16:59 Hi there, I uploaded the files, enabled the modules to use SU, and now I see the link, but there is no icon... How can I fix this? Thanks, Sean webmaster access_time 24 May 2019 - 16:59 In reply to Icon doesn't show by Sean (not verified) What do you see when you view the source? Search for stumblethis_button and you should be able to see the code for the image and the URL. Then you should be able to troubleshoot from there. Juicy Couture Addict (not verified) access_time 24 May 2019 - 16:59 thanks for the post. would love to hear more of you. by the way, drupal's really popular nowadays as it has easy and fast features. you agree with me? thanks. Add new comment
more_horiz
close

on 16th January 2008 / by webmaster
Most webmasters do not realize this, but a lot of the content on lot of websites can be accessed from multiple URLs. A simple example would be where www.example.com and example.com leads to the same page. This is a fatal mistake in Search Engine Optimization and search engines penalize you for duplicate content. The correct configuration would be where the above two urls will lead you to the same page but example.com will redirect you to www.example.com with a 301 (Moved permanently) status which will not result in search engines penalizing the page. It is very easy to configure 301 redirects using Apache .htaccess file and the process is the same for a Drupal installation also. The article is relevant only to those webservers running Apache. There are two ways in which you can issue a 301 redirect using .htaccess on an Apache Webserver. One is using a mod_alias Redirect statement and the other is using the mod_rewrite Rewrite statements. Redirect statements take paths and assign corresponding paths to be redirected to while rewrite statements take regular expression patterns and associate paths where matched urls have to be redirected to. When you install Drupal, it will automatically insert statements in the .htaccess file that will allow you to redirect www.example.com to example.com or vice versa. The only thing you have to do normally would be to uncomment the statements corresponding to your preference of accessing your domain ie with or without the www part. # If you want the site to be accessed WITH the www. only, adapt and # uncomment the following: # RewriteCond %{HTTP_HOST} ^example\.com$ [NC] # RewriteRule .* http://www.example.com/ [L,R=301] # # If you want the site to be accessed only WITHOUT the www. prefix, adapt # and uncomment the following: # RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC] # RewriteRule .* http://example.com/ [L,R=301] There is however a problem with the above redirections in that they lose the rest of the URL. Say for example if you try to access example.com/somepath and your configuration is to use the www prefix the user will be redirected to www.example.com but the somepath part will be lost. This can easily be rectified by the following small change in the Rewrite Rule # For the first option you can use the following rewrite rule # RewriteRule (.+) http://www.example.com/$1 [L,R=301] # # whereas for the second you can use the following rewrite rule # RewriteRule (.+) http://example.com/$1 [L,R=301] These modifications will ensure that the user will be redirected to the correct page with or without the www prefix and without losing on your page ranks. So make the necessary modifications and make sure that you can access the pages to your site using only one version of the URL. The above configuration of .htaccess should be used not just for Drupal websites but for all websites. If however your problem is the reverse, ie you don't have pages corresponding to the URLs that the user typed, ie if you are getting lot of 404 errors (page not found errors) and users are thrown to the default Page not found page, you can try installing the Drupal Search404 Module to search for the keywords in the URL and show relevant results to the user. You can read more about apache mod_alias and apache mod_rewrite at the apache official documentation Apache mod_rewrite and Apache mod_alias Web Development Drupal SEO Drupal Planet Leave a reply Your email address will not be published. Required fields are marker * Anonymous (not verified) access_time 24 May 2019 - 16:59 Hello. I'm trying to make example.com show as www.example.com, and I'm running into difficulties. I'm on Apache 2.0 and using the following lines in my httpd.conf file: RewriteEngine on RewriteCond %{HTTP_HOST} ^xxxxxxxxxx\.com$ [NC] RewriteRule ^(.*)$ http://www.xxxxxxxxxx.com/$1 [L,R=301] When I go to http://xxxxxxxxxx.com, I get http://www.xxxxxxxxxx.com (as expected). However, when I go to http://xxxxxxxxxx.com/node/1 (it's a Drupal site), I get a 404 thrown and the URL changes to xxxxxxxxxx.com/var/www/drupal/node/1. Same thing with www.xxxxxxxxxx.com/node/1. Any suggestions? I want to run without Drupal's .htaccess file (instead incorporating these calls into my httpd.conf file). webmaster access_time 24 May 2019 - 16:59 In reply to Rewrite including filesystem path by Anonymous (not verified) I think the problem is with the base path which results in the redirection to /var/www/ part. The best approach I would think is to start with drupal htaccess and then strip out parts and move to httpd SNVC (not verified) access_time 24 May 2019 - 16:59 This is definitely a good guide. Thanks for this. wellyson access_time 24 May 2019 - 16:59 This is really nice and helpful. Add new comment
close

on 07th January 2008 / by webmaster
We have volunteered to take up the maintenance of a very useful Drupal module - Search404. As of today we are the official maintainers of this very useful Drupal module. We know that this is going to be a challenge for us, being a young company and with a young team. But we do feel that it is our responsibility to give back to the Drupal community at least some part of what it has given us. About Search404 Module Normally when a user types in an incorrect URL in a site the web server will issue a 404 error (page not found error) and correspondingly redirect you to a 404 error page. If there is no custom 404 page on the server the browser will show the 404 page not found error to the user. This could happen when either the user types in the URL himself or he clicks on a URL incorrectly typed in another page. Another case when such errors happen is when content is deleted or moved in a site and the search engine indices have not been updated to reflect the removal or change. The web crawlers of search engines on getting a 404 error will take out the URL from their indices. The normal web user will however be totally lost when he sees the 404 error page. This is especially true if the user came from a search result page and has no idea about the navigational structure of the site or the content organization of the site. Drupal however shows its own 404 error page and avoids showing the grotesque, default 404 page that would otherwise be shown by the browser to the end user. Even this 404 error page is only a bare page with just the information that the page cannot be found. The Search404 module intelligently does a search for the terms in the URL while still issuing a 404 error. This will ensure that the URL gets taken out from the search engine index at the same time making sure that the user is given some options in terms of navigating in the site. You can check out how this works by clicking on the following non-existant URL Drupal Modules from Zyxware. Even though the page does not exist you get what you wanted to get to. If you have any questions, issues or suggestions regarding this module you can either post them as comments to this page or post your issues at the Search404 Module at Drupal.org. Open Source Web Development Drupal Leave a reply Your email address will not be published. Required fields are marker * ian douglas (not verified) access_time 24 May 2019 - 16:59 I notice your updates on the Drupal modules page has some patch files, but they are patches for an older version of the 5.x branch of search404. Do you have any expectation on when a version for Drupal 6 will be ready? webmaster access_time 24 May 2019 - 16:59 In reply to when will search404 for drupal 6 be ready? by ian douglas (not verified) Hi Ian, We are currently working on moving Search404 to Drupal 6. The port has already been done and we should have a release up on drupal.org by tomorrow or worst case by monday. Cheers Anoop John Team Zyxware Dejan (not verified) access_time 24 May 2019 - 16:59 In reply to when will search404 for drupal 6 be ready? by ian douglas (not verified) I think that's been up for a while... did you check the download page? Add new comment
Leave a reply
Your email address will not be published. Required fields are marker *

Filtered HTML

  • Web page addresses and email addresses turn into links automatically.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
The content of this field is kept private and will not be shown publicly.
CAPTCHA This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.