Reasons for me to hate Ubuntu

So, I get settled in to download and build the source code for our new project and wouldn't you know it Ubuntu crashes.  It was so bad that I couldn't even boot into the Linux based system.  So, I do a clean install--knowing it'll wipe out my work from last semester and guess what?  Yep, the install fails!  So, I wiped it clean and went a different route...I'd heard of installing OS's in a virtual box so I figured it was my time to invest in learning that.  I failed the first time because the virtual box didn't like the 64-bit Ubuntu exe that I downloaded (dumb because I have a 64 bit box...who knows?) so I try again by downloading the 32 bit version and it installed without a hitch.  I spent about another hour doing the updates and making a few changes.  Once I got back to the project at hand (our source code) I come across some interesting information...it is only supported on version 9.1  (which as you can probably guess by now, what I installed was their latest 10.1)  I started to install 9.1 virtually as well, then I read further...even 9.1 won't allow the emulator to work because of a broken security configuration.  After muttering a few "inconsiderate" words to my project I set out to see what it is actually supposed to run on.  The best option appeared to be Debian, so off I go again downloading and installing yet another OS today.

Since we ran into issues with rapidSMS, my group and I have chosen to tackle a different problem...this time on an area of Sugar Labs that will not be similar with the other two groups working on it.  Since it is such a large project with many different flavors to look into, we're still in the process of narrowing down what fits us best.  So, I did join this version of their IRC chat, because it doesn't require additional software to be installed (which will allow me to access it at work).  I joined one of the mailing lists (bugs) because I thought that would help in our next assignment of finding a suitable bug to attack; however, there are several mailing lists and I figure we'll be on a few of them before this is over.

Debian install took forever but was a rather straightforward install and FINALLY, I get back to my original project some 6 hours ago!  After following their directions for Debian install by the letter, I made it all the way to the build command and keep getting the error "Refusing to run as root." (its getting rather hard now not to spell out why I like Windows better than this!)  So my problem is...after hours of frustration and time lost, the only thing that I can show for my efforts is the fact that my box has 3 operating systems (one great one--Windows) one fixed and 2 virtual OS's.  Maybe tomorrow after catching up on the work I didn't get done today, I'll find some time to devote to this endevor again :(

Success!

TortoiseSVN ROCKS!  With less than 10 minutes of time spent downloading, installing and rebooting my box, I was already in business.  The only foul up I had, was that I originally linked the space I set up on my box to the URL we were given--instead of the ....cirdles.....playground/test.  This was easily corrected and I am now able to upload, checkout, make changes, revert to a previous version, commit my file, etc...  I toyed around a little bit and found out what "blame" did...cool!  Like I mentioned earlier, I learned how to revert to a previous version of my file, renamed it, tested using the "diff" function...all in all it was much smoother than NetBeans or SubCommander!

Next up was to start setting up my personal server.  What I thought would be the most effective use of my time was to test VisualSVN since others had success with it.  Again, I had no problems installing it; however, it was a little tricky to set up, but NOTHING like what I was dealing with on Wednesday/Thursday!!  I spent the better part of another hour just trying things I was a little hesitant of trying on the group side (like locking and branching) just to get an understanding of how it works.  I also (among other things) tested setting up permissions so that only I could edit something...interesting.  Just like on our "playground," I am able to do all the things to my repository (on my server) also...cool, I might have some uses for this later.

Overall my experience with TortoiseSVN and VisualSVN was great...of course it’s always great when it works right?  I only wish that I would have started on this path instead of wasting the time I spent on the other path!  Next step will be getting and building the source code for our project…sounds like a Saturday job!

Addendum: TortoiseSVN ROCKS!!!!!

Its not subversion it was a downright disruption of my day!

The first part of my project was uneventful. Logging into our cirdles “playground” was straightforward and completed without any problems at all. The real problem was, “what do I do here?” I could view and edit, but had no way of uploading my own content to the repository. I had done some checking and discovered that Subversion was already installed on my box when I installed Ubuntu.

After some searching (and scratching what hair I have left) I was guided toward the realization that I needed a client to accomplish task at hand. I initially tried NetBeans and had no problems setting up the connection with our repository but was unsuccessful in getting it to work for me. Next I found Subcommander (which only needed to be installed though the Synaptic Package Manager) that is showing promise. I was actually able to sync my local box with the repository but when I tried to “commit” my own files, I wasn't able to see them in our “playground.”

I'm sure I am overlooking something and will try again tomorrow before asking for help. Netbeans will probably be what I will use, but it would be good to know a couple of ways to put subversion to work. I was a little disappointed that I didn't get to the source code today...completely ran out of time and other work took priority...now I'll have to try to get it done over the weekend instead of getting ahead.

Research and Planning

Most of what has been done since Thursday has been looking into the history of rapidSMS and trying to get any leads into how we can contribute to the project.  The project has only been around since 2008—although no one has a definitive date as to when its inception actually began.  It was not too hard to find out that graduate students from Columbia University developed this with funding provided by UNICEF.  The first use of the rapidSMS framework was (and is still in use) in the Malaw project and since then, rapidSMS has been used in projects encompassing six different countries!

The most challenging problem to date is to determine exactly what or where we can contribute to this project.  Since it is a framework, there is the option of building something that uses it—but after a few weeks with Ryzom last semester, that is a scary thought.  We did get an interesting response from a member of the rapidSMS Google group that sounds promising…so we’ll struggle with this problem some more.

In the meantime I thought that I’d get the source and attempt to build the code on my box; however, I hit a snag when I booted back into ubuntu and was reminded that (for some unknown reason) the ubuntu wireless drivers will not allow me to connect to my apartment's router.  It works fine at school, so instead of downloading in windows and attempting to shift from ubuntu to windows and back again, I'll just wait until tomorrow when I can work on it at school.

A peek into the past

Well it's a good thing that I didn't try to fit "The Cathedral and the Bazaar" reading into my day yesterday...I definitely would not have finished it and be in any state of mind to reflect on it!  Mr. Raymond put a lot of information into this work--a pretty fair amount of technical information too--which introduced the impact of Linux on the computing world as he journeyed us back in time to his foray into working on (and eventually taking the reins of) an open source project that interested himself.

Raymond was an accomplished programmer who simply wanted a software package that allowed him to have more control over his email--and before long he was not only contributing to an existing OSS project, but would eventually take the project over and rename it to encompass his contributions to it.  I'm not sure that I would have gone to all that trouble--I surely don't have the time to even consider something like that at this point in my life--but it is a good thing that people like him do.  It would be hard to comprehend what life would be like were it not for those who invest their lives towards solving a plethora of problems.

I definitely liked his use of "cathedral" and "bazaar," and must admit that I wasn't sure what that would be referring to--and he actually explained that EARLY on.  The idea that the coding style of a bazaar (or a conglomerate of people working on many different things at once on a project that happily accepted and implemented most of their ideas) would be more effective than a cathedral style (a system of only a few "holy" people reverently working together on the project) seems impossible; however, (as Raymond points out) Linux has proven its point.

To be honest it was hard to vigorously digest his technical information, but he made it as interesting as possible.  I also liked his references by Dr. Brooks--I remember his articles from last semester and the timely announcement of Netscape becoming an open sourced project (I feel old now...I remember that happening) although I must admit that back then I didn't really understand the significance of that.  Perhaps the only complaint I would have over the article though....I did like the XHTML format (moving from page to page seamlessly) but I must admit that after a while I wondered "how long is this?"  It was a good article/short story but after a while I won't lie...I was glad to see the bibliography and acknowledgements pages :)

Moving Forward

Today we finalized our team project (which will be the RapidSMS project) and we will be spending the rest of this semester working with it.  It should be an interesting project but perhaps the most important hurdle of determining what particular aspect of it that we really want to focus on is looming ahead.  I was able to easily join the IRC for RapidSMS, which was surprisingly easy to do (I was even able to add a custom link from my blog to it as well—see the bottom of this page).  Since IRC is also a new venue for me, I am not sure if I am overlooking something because I really don't see any "traffic" or chatter on the IRC.  At the present time there are only 4 other people signed in (besides myself) and I honestly don't see any interaction between them or anything there to do other than to "chat" with them.  I'll check back later on that one!

I also successfully joined their Google group with NO problems.  You actually had to be approved for membership by filling out a short form and giving your reasons for wanting to join (probably to keep out bots or something) and it took less than 20 minutes for them to send my "acceptance to the group" email.  Once arriving at the group's main page it is obvious that LOTS of communication goes on here!  With just some simple browsing around I'm seeing a variety of issues discussed on this page—it should be helpful, more on that too later.  I went ahead and placed that link on my blog page as well so I won’t have to bookmark it (see top right corner).

I still have to read “The Cathedral and the Bazarr” but probably won’t get to that until tomorrow—so that’ll give me something to add then.

Taking Shape

I did like that today each group was able to spend time hashing out ideas on which FOSS projects our group would be most interested in contributing to.  I felt it was productive and believe that any of the 3 projects we're looking into would make for an interesting experience for us.

RapidSMS would have us working with cell phone's SMS technology for the purposes of helping people plan & communicate in disasters and other desperate situations.  OO4K would present the opportunity to work with "office" software that is designed to be used by kids.  IfPeople uses a vast "toolbox" that enables its customers to put the WWW to work for them in the most efficient manner.

We still have a few days to investigate our top picks, which will be what is on tab the next few days!

Back to the millstone

After an enjoyable 4 weeks it is time once again to start pulling the stone a little closer to the finish line.  I haven’t made the time to do a blog before so this will be my first experience at that…a similar truism could be said for my use of wikis, so I expect a few bumps along the way.

We formed our team today in class and started the arduous process of determining good meeting times.  Hoping to spend some quality time tomorrow looking into our project possibilities….but for tonight, it is time to make a serious start at reading Chapters 1 & 2!