Its been almost a fortnight I guess without a blog post, so continuing with the series, I have a couple of updates.
From tomorrow, Google Summer of Code Student Evaluations will start tomorrow on wards, so all the best to all the students who have worked hard over the summer and helped open source organizations grow. An extra applause for the mentors who have really worked hard over the summers and have contributed their personal time to get these students involved. Specifically, from an openSUSE point of view, I hope everyone passes these evaluations.
Apart from these things, I have also hit a couple of realizations over the past fortnight,
I have gone worse in programming, something that I intend to improve upon in the next six months
I waste a lot of time, I really need to optimize time so that I can work much more efficiently.
And then as news, humblefool one of India’s top programmers died of a car crash. There is an excellent eulogy written by Animesh on quora, I urge you to read it and take inspiration from it.
openSUSE welcomes Google Summer of Code 2014 participants. Thanks to Google, openSUSE has an excellent number of slots and an equally excellent number of mentors and students for Google Summer of Code 2014. Throughuout the summer, students participanting in this program will code for openSUSE and its sister organizations ownCloud, MATE and Zorp and help them move forward. The best part of GSoC is that most of the code written by students will go upstream and will benefit openSUSE in general also. Along with this, we have an equally good range of projects that will improve
the existing openSUSE architecture.
The list of successful students are :
1. Travel Support Program application – Karthik Senthil
2. Playlist Functionality for ownCloud Music App – Volkan
3. ownCloud Calendar Application in angularJS – Raghu Nayyar
4. openSUSE GSOC ideas: Cool live flash – Zsolt Peter Basak
5. Open Source Event Manager (OSEM): Refactor user management model – Stella Rouzi
6. Open Source Event Manager (OSEM): Implemention Organizer Dashboard – cbruckmayer
7. MATE: Port from deprecated GStreamer 0.10 – Michal Ratajsky
8. Integrate Snapper Snapshot browsing into openSUSE Desktop tools – Oguz Kayral
9. Implement an application-level LBaaS driver for Zorp – Péter Vörös
10. Extend Git-Review to support BitBucket – xystushi
11. Event Splash page for Visitors In Open Source Event Manager Application. – Gopesh Tulsyan
12. ePub support in Atril (MATE) – Avishkar gupta
13. Add Snapshot management API to libvirt Xenlight driver – David Kiarie
14. Improving the functionality of the extensions system in Caja – Alexandervdm
In the following weeks I will talk a lot more about these projects and get to know these students well.
It all began abruptly, when Akif Khan ( a prospective student ) asked me to discuss my GSoC experiences at his college. The idea instigated quickly instigated me as I longed to visit a College Campus and meet real open source people after a long time, so I agreed without giving a second thought, we decided that we will meet up on Saturday at Faculty of Eng, Jamia Millia Islamia.
I reached Jamia Millia at time and was pleased to find an enthusiastic culture of open source led by the students over there. Lots of students from other colleges were a part of the meetup too. A few things that I noted my experience there are as follows :
Students were enthusiastic and really wanted to contribute to open source. Since most of them were fresh(wo)men, they were enthusiastic about the GSoC experience and how it could help them.
Discussion how to select a project, write a proposal and how to communicate with the organizations was taken up.
One of the most enthusiastic things that I heard was “I really want to do it, despite of getting through GSoC” which is pretty much any open source organization wants. Hopefully, we have more students who think like this and even more who turn their thoughts into action. Overall, it was an excellent talk with a bunch of enthusiastic people :).
After Google Summer Of Code 2011, openSUSE plans to participate in Google Code-in. It is an excellent opportunity for openSUSE to meet young talents and introduce them to the ways of open source.
What is Google Code-in?
It is a contest hosted by Google for pre university students every year where they are encouraged to participate in open source projects and are awarded cash prizes for their contributions from Google. Various open source organizations participate in it and mentors from every organizations help these students to get up to speed and advice them on how to complete the challenge. The contest period is from November 21st to January 16th 2012
What are tasks?
Every open source organization has a lot of cool ideas in mind and likewise every member of the community has some ideas in his minds. These ideas are collated and put together and are categorized into three levels of difficulty – Easy, Medium and Difficult. Students are rewarded points as to what task they complete.
Deciding the tasks
The mentors decide the task, off -course community can suggest but at the end of the day it is the mentor’s discretion on what task they want to work on. Tasks can be anything and for a more accurate description of the tasks visit here.
Note that not all tasks will be code related, so even a non-technical guy with enough experience with other skills can participate in Google Code-in as mentors. Tasks can range from Documentation to translation, artwork to marketing and off course what is a code-in without code related tasks like code refracting, testing, finding and squashing bugs and a lot more things.
Preps for Code-in
openSUSE has already started preparations vigorously and is already coming up with a list of tasks and is looking for mentors. While lots of us have already signed, we are looking for lots more to sign up as mentors and see more interesting tasks ahead.
More information can be found at en.opensuse.org/openSUSE:GCI and http://en.opensuse.org/openSUSE:GCI_Tasks
Please test it thoroughly,and let me know if common troubleshooting use cases for a single monitor is supported. If there is anything missing let me know. Xinerama is not supported
For both factory and 11.4.
Next up is touchpad, which I will finish by this thursday. And will begin pencil downs the following week onwards.
Its been a long time I posted anything, but things look promising now, SaX3 is moving forward and 2 of its module have been completed, the keyboard module and the mouse module, so please test it and give me your feedbacks and if there are any bugs. BUGS will certainly be squashed, I dont know about UI changes. Suggestions are welcome. I plan to work on touchpads next.
This is my 2nd report, this week not to show much for the users, but we did a quite interesteing things. SaX is now module oriented.So, if anyone wants to write a module for SaX3 it is possible now. Besides the important things which I did was
Learn the augeas C api
Submitted a .desktop lens for augeas
It is module oriented
Tried out Doxygen
SaX3 is now localised.
The launcher is now complete 🙂 Again, the source code is here http://github.com./manugupt1/sax3 Regarding modules, If anyone wants to check out how modules work, they work using .desktop files in /usr/share/sax3/modules.d. If you will remove it we can remove it from the launcher.
This week I worked on SaX3 internal UI architecture, offcourse we will be using libyui but we wanted to make it as flexible as possible so that the UI Library can be replaced by anybody and still keep SaX usable, for that we implemented the factory pattern and most of the code was working. Finally, we have something working and the screenshots below show that SaX3 is working in graphical mode and ncurses mode.
I am adding screenshots of the launcher that will launch various configuration modules such as keyboard, mouse, graphic card etc etc . Also this is just a start and by the time I present my next report I week, this will be much cleaner and you can play around more with it. Right now it does not do anything so dont get surprised.