[MacPorts] SummerOfCode2013 modified

Thu Jul 25 14:32:46 PDT 2013

Page "SummerOfCode2013" was changed by marius at macports.org
Diff URL: <https://trac.macports.org/wiki/SummerOfCode2013?action=diff&version=8>
Revision 8
Comment: Added project description.
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCode2013
=========================================================================

--- SummerOfCode2013 (version: 7)
+++ SummerOfCode2013 (version: 8)
@@ -35,3 +35,92 @@
 Things are getting better and better, as I need less and less help from my mentors. I have managed to cover 3 of the modules of port1.0 (portactivate, portclean and portutil), but I have developed enough confidence to step up the pace and increase my developing speed. The tcltest framework really seems a great fit for our needs, fact confirmed by Rainer. Still a lot of work needs to be done, and as wee discussed on our last meeting, we may need to reorder some things in our roadmap for this summer, but not after we talk to the rest of the community and listen to the other developers' opinions.
 
 The need for good documentation is really felt, once I dig deeper into the functionality of MacPorts, so I will make sure the test I develop come with good instructions on how to use the framework, add new tests to it or change it. I have already started with short comments in the code and some README files that will help me write the final documentation. The midterm evaluations is near, so I'd better get back to work.
+
+
+
+___________________________________________________________________________________________________________________________________________
+
+== Personal ==
+
+* Name: Marius - Vlad Coțofană
+* E-Mail: marius.coto at gmail.com
+* IRC/IM: mariusc (IRC), cmarius02 (GTalk, Skype)
+* University/Enrollment: "Politehnica" University of Bucharest, studying Computer Science, 2nd year.
+* Location/Timezone: Bucharest, Romania (GMT+2)
+* Programming Knowledge: C/C++, Java, Python, Shell Scripting (bash).
+* Short Bio:
+
+Hypnotised by computers from an early age, I began programming in high school. Learning C opened a new world for me and changed the way I used to see a computer. I followed Computer Science at the University, that brought me a whole range of other programming tools and languages, but C remained my favourite. I have adopted Linux, for almost 2 years, learned it, used it, taught it to other students and then decided to move on. OS X offered a new experience, much powerful and sharper and I decided to further improve it.
+
+Detail-oriented and highly analytical person, I have always tried to get involved in as many projects as possible, get around people that are better trained than me and learn from any experience. Although it takes me some time to connect to new people, I am devoted and helpful in any circumstances. Stubborn and punctual, I cannot stop until all work is done.
+
+ 
+
+== Project ==
+
+=== ABSTRACT ===
+
+The lack of a proper testing environment is slowing down the development of the main project. Having an improved testing framework, that makes it easy for adding new tests and having a more comprehensive suite of tests, is essential to being able to refactor the code correctly. This also leads to an decrease in the time needed for adding new features and patches.
+
+=== DETAILS ===
+
+I will begin by setting up the necessary development environment, 2 weeks before the actual beginning of the coding period, time in which I will also make sure I have iterated through all of the Tcl features and I have a good understanding of how MacPorts source code is structured.
+
+In the first half of the coding period, I will review existing tests and further enhance them. This will walk me through the way they are constructed, so that I can maintain a consistent form and syntax throughout the entire testing framework. Having gain a sense of how things work, I can then begin writing new tests that will first cover the most important modules, and then continue and try to get as much coverage as possible.
+
+The second part will be focused on regression tests: improving existing ones and possibly adding new ones. Testing every part of the code is a good way of assuring correct behaviour, but as more and more functionality is added, new tests have to be added too. I will build an easy way of adding new tests, consisting in templates that are easy to use and understand. Having good documentation over the testing framework, is one of the objectives that would also be covered during this period. This will ease the work of people who want to add more tests or further extend the framework, and being open-source, inspire people who need testing for their own projects.
+
+Below you can find a tentative timeline, structured in 2-week intervals, as a generalised form from this detailed plan.
+
+=== TIMELINE ===
+
+Community bounding (1 June - 16 June):
+
+* prepare development environment
+* further read on Tcl
+* study MacPorts sources
+
+First coding period (17 June - 28 July):
+
+* 17 Jun - 30 Jun: review existing tests and improve them
+* 1 Jul - 14  Jul: add unit tests for MacPorts base and the Portfile API
+* 15 Jul - 28  Jul: add more tests that cover all modules
+
+Second coding period (29 July - 8 September):
+
+* 29 Jul - 11 Aug: improve available regression tests (and possibly add new ones)
+* 12 Aug - 25 Aug: build a new, easy way for adding new tests
+* 26 Aug -   8 Sep: write full documentation for the testing framework
+* 9 Sep - 17 Sep: review code
+
+The remaining time between suggested 'pencils down' and firm 'pencils down' serves as buffer for unexpected changes and delays.
+
+ 
+
+=== Additional Questions ===
+
+* What are your experiences with Mac OS X so far? (How long do you use it, did you switch from Windows/Linux, etc.)
+
+I started using Mac OS X just 5 months ago (December 2012), when I bought a new notebook. Coming from a Linux world, I decided to switch because it had so many problems that I had to spend most of the time repairing them, rather than spending it developing. Of course, OS X, has its problems too, one of which is the lack of a proper package manager. MacPorts is a great solution to this problem, so I plan to be part of it.
+
+* Have you used MacPorts before, and if yes, for how long?
+
+I have used MacPorts since my first week with OS X (5 months ago), like one of my friends suggested, as a response to my complaints.
+
+* Do you have experience with other package management systems such as FreeBSD ports, Gentoo Portage, Debian APT, etc.?
+
+I have previously used many Debian-based distributions so I am familiar with DPKG and APT, but also tried YUM and RPM.
+
+* Have you already made contributions to MacPorts? (New ports, port updates, etc.)
+
+No contributions yet. I have focused on reading the code and understanding how it works. I plan to have my first commits before the coding period begins.
+
+* Have you already made contributions to other Open Source projects?
+
+Sadly, I do not have any major contribution to other Open Source projects, and that is the reason why I am so exited to start this project.
+
+* How much experience do you have with Tcl and C?
+
+C was my first programming language and quickly became my favorite. I began writing C code from high school and continued with it two years in my university studies, where I have also added POO notions (C++). This language has proven to be very powerful and feature rich, that is why I plan to stick to it.
+
+I began learning Tcl for two weeks, starting with the tutorial on the official site (as people from the MacPorts IRC-channel suggested) and already have made some scripts to further understand its features. My little experience with Tcl is backed up by a fairly large history (2 years) with shell scripting using bash.
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/SummerOfCode2013>
MacPorts <http://www.macports.org/>
Ports system for OS X

This is an automated message. Someone added your email address to be
notified of changes on 'SummerOfCode2013' page.
If it was not you, please report to .
