Progress being shown with CubicVR.Octree.js, frustum issues arrising

So another day has gone by, I've managed to get the system culling objects, but not correctly. Having glanced through the AABB code and frustum code, I'd have to assume my issue right now is with the frustum, as the AABB code is giving consistent results. The frustum code has been reused from the old implementation (which I firmly now believe didn't actually work correctly, at least not in the latest build) and it seems to be the source of my trouble, I am considering simply writing a new one from scratch, shouldn't take more than half a day.
At the moment, the system isn't actually even using the octree, instead using the isolated AABBs of each object to do its culling. I plan to make use of the octree, but not until I have it correctly culling at the AABB level, once that works, I know the frustum code is working correctly.
I plan to get this completed within the next few days, a week tops. But the fact that I haven't submitted anything for 0.4 yet is too pressing. I am going to be submitting this current build as my 0.4, I have gotten a fair bit done, so hopefully it will suffice. I really wish I had picked up this bug for my 0.3, everything would have sorted out much better. I will continue working on the bug and blogging about my progress each day, and with Humph's permission, update my 0.4 submission as I make progress. But for now, this is where I am marking my 0.4.
Below will be a short list of what has been accomplished for my 0.4 as of the time of this blog being published:
-Octree tests brought back to operational status
-Old octree implementation stripped out (Frustum code salvaged)
-New octree code added as module
-Octree components tied into system (migration about 70% done)
-Scene now culls scene objects using frustum and object level AABBs (frustum incorrect, causing unwanted culling)

Incorrect expectations: Octree.js migration into CubicVR

As the title describes, my initial expectations about this migration were not accurate. I went into this with the expectations that the octree.js code had been coded towards use in CubicVR, but instead it seems to have been coded as a simple stand alone octree system, and at that, not a fully complete one. I am a little confused as to why they seem so interested in integrating this new octree system though it lacks much of the functionality of the current one. These are questions I am gonna have to ask them about tomorrow I guess.

So far, the two sound things I think I've managed to accomplish has been bringing the old tests back to operable status (patch has already landed), and the migration of much of the math work in octree.js into the CubicVR.Math.js (scratching the redundant code). After that, I am really unsure whether or not I am going in the correct direction with this work. I am rather chaotically patching the new system into place, and have recently just got the octree "operational". I am unsure as of now if the octree is actually doing anything or is simply wasting cycles accomplishing nothing, but it was my goal for tonight to get the octree.html test running with the new system in place. This system implementation into the scene object just sits on top of all the old stuff, for simplicity for now, I plan on cleaning it out, but on the other hand, perhaps I should consider scrapping this whole bunch of code and starting from scratch with a better idea of what I am getting into....

The biggest thing I have against scrapping what I have done is simply that my 0.4 for OSD600 was due days ago, and I still have nothing submitted. I'd really like to have this whole thing implemented, reviewed, and completed properly before submitting it as my 0.4, but for it to reach that status may take another week, especially considering I have exams this week. I am pretty much completely out of time, so perhaps a somewhat rickety implementation submitted tomorrow would be better than a correct implementation submitted in a week.... not sure, hopefully D. Humph can give me advice on this.

If I were to scrap what I have, I'd think I'd take a more orderly approach to it, first tearing out all of the octree related stuff from the current build of CubicVR and getting it back to operable status again, then starting to add in the new implementation piece by piece on a more or less clean slate. SecretRobotron wasn't around today, so hopefully I can talk to him and ccliffe and see what they thing the best choice would be, and weigh that with my already late submission...

CubicVR Octree progess part 2

So the tests are working, the changes had to be made in the Scene object, not sure if the changes I made follow standards, but I simply added the variables to the local object (added this.) and the variables were no longer falling out of scope. This shouldn't cause too much of a problem since these variables are reset every render pass and are hooked into the Octree object, so it shouldn't conflict with anything else. I'll ask for a code review on the change when I make a pull request.
Been analyzing how CubicVR uses its current octree implementation to see what I have to change and where. I was hoping their operations would line up a bit more seamlessly, but its gonna take some modding on both ends (the new octree system as well as many of the CubicVR source files) before I can get them working together correctly. I am hoping to have this finished up by the end of the night, the fact secretrobotron hasn't been on IRC today makes this a little more difficult as he would know the most about what can and cannot be changed in the new octree implementation, but I'll do what I can. If I change something I am not supposed to, hopefully it will be picked up during the code review. Obviously, with the tests now working, I should be able determine if everything is running correctly. I've already benchmarked the old implementation, and am hoping to see some improvements with the new one, if not, I hope to not see a drop in performance, as that would likely indicate I may have messed it up some.

Progress on CubicVR octree migration

I was assigned issue 26 earlier in the week, which is about migrating a new octree system written by secretrobotron into CubicVR.
I started out by testing that the current octree tests were working, so I could benchmark the current implementation and test and benchmark the new implementation to see that it has been implemented correctly. Unfortunately, almost all the tests were either partly or completely broken. I informed the people in the #paladin channel on Moznet, and I volunteered to get those working as well. This naturally pushed back my schedule, but there really wasn't a way around it.
Thus far I've found one of the bugs, which fixes about half the tests, which was a function call that hadn't been updated to keep with the changes of the octree. The other breaking bug seems to be that a variable is falling out of scope, though I'm not sure why. Once these tests are fully functional again, I'll head to work on the actual migration again.
On another note, the tests for Mouselock weren't added to the patch because they were not working correctly. I had done a test review for one of the tests, but no one noticed that there was a duplicate on the list (of 20 items) and that what I was working on had already been done, so that was a great waste of time. More work needs to be done on the test reviews, but I need to finish my work for CubicVR first. If there is still work to do when I'm done, I'll gladly help finish this out.

Burning the midnight oil....

So, as I figured, the IRC channel came alive later in the night. I noticed no one had grabbed the test_syntheticMouseEvent test review and went underway. After making a series of changes, mostly stylistic and only a few that actually affected code, I configured it to work with the harness and it was ready for testing. rhung had been complaining that he was unable to get the tests to run correctly, so I pulled from his repo and attempted to run them, but it didn't work, not because it would fail, but because the tests would simply lockup and not proceed. Not sure as to why it is failing. Really I am writing this blog to pull myself away from issue for a minute while I try to think of what could be causing the problem...

My posts often lack anything particularly helpful to the reader, so I'm just gonna list some tips I've either found or been given. Just to make this worth your time reading.

1) Its always a good idea to keep your whitespace clean in your code, heres a few regex commands that can help keep your code nice and clean (mind you these are all for vim, but you should be able to translate most of them to other apps(ignore the %, thats vim only)):
-Remove whitespace at the end of a line: %s/\s$//
-Replace tabs with (2)spaces: %s/\t/ /g
-Replace (2)spaces with tabs: %s/ /\t/g
NOTE: These are obviously not made to be safe with string in your code, they will manipulate anything in the file

2) Build tips for linux:
-When using a make file use the -j# argument to specify how many jobs this make uses, generally you should use the number of core your computer has plus one. So on a quad core computer it should look like: make -j5
-For time consuming builds, screen can be a lifesaver. Screen is a linux utility you can use that will essentially make a virtual client, one that does not expire when you close your SSH connection. So you can start a build on a server, and leave it running, close your connection and come back to it later. I'll list the basic commands here, for more detail go here.
$ screen <-- open a new virtual client
(Once in a 'screen') Ctrl+a d <-- detach from the screen
$ screen -R <--Reconnect with the screen
NOTE: if you use screen twice instead of using -R, you will make a second client, and -R will no long work, you will need -r and specify the screen id

Thats all the tips I can think of right now. Hope this helps someone.

Freedom and confusion at the end of the day

Luckily I am now done all my work for other courses, so I can pretty much submit all my time to OSD, which I am pretty happy about. Things are moving around quite randomly with the mouselock implementation at the moment, making trying to contribute to it fairly difficult... NorthWind and myself have been trying to get a piece of work for the reviews for the past few hours, but have been unable to find anyone to give us a solid answer on how things are being distributed. The IRC channel has been surprisingly dead considering it is the end of the semester, perhaps not everyone is scrambling to finish work for other courses at the time. So for the time being, I'm avoiding working on it entirely, as I don't want to end up wasting my time or breaking someone else's work. I would have hoped it worked out like the test assignment did, that we all had a central point to contact (in the case of the test assignment, rhung) to figure out who was doing what and how things were supposed to flow together, but alas, no dice.

Instead I am getting back to work on my involvement in the CubicVR project. I have been assigned the task of migrating an octree implementation into CubicVR and removing the current implementation. I am hoping to have this fully implemented and tested before next week, and have it land next week. Hopefully this will suffice for my 0.4 assignment. Luckily I already have a decent understanding of how octrees work, so the migration will hopefully be a piece of cake.

If people start showing up and talking in the IRC channel at some point today, I am likely to redirect my efforts back to the mouselock, but until then, I'll put myself to work on CubicVR.

0.3 material testing system

I got all the common material types working into the testing system, and got the camera controls working so the materials could be more accurately checked. Not much else was added to the tester. I attempted to get another bug to work on, but the ones listed were either already taken or seemed like to large of bugs to pick up at this one. I'll leave ccliffe a message in hopes he can get me some more work to do. I feel the work done in this tester wasn't good enough to account for 0.3, so I guess my only option is to do an extra amount of work for 0.4 to make up for this.

Getting 0.3 caught up

Ya know, as a programmer, being separated from your computer, and thus your ability to work, for several days can make you feel awful helpless... but thats neither here nor there.

Still working on 0.3 as of now, though it was due a few days ago. Still trying to fix up the testing platform, though the tester and fix I made for 0.2 landed early last week. I want to get this tester to a point that I think it is actually worth while, capable of testing all the materials and with the ability to fine tweak the testing environment without actually changing code... So far I've changed the interface to better reflect how it will be controlled, added camera controls, and did some more research on the material system in CubicVR. I still have to get the materials all in and working, and I wanted to implement both an automation process and a environment dump into the testing platform, so I still got a day of work on it. This could have been done on time, yet my inability to remember to pack my laptop when I leave severely hampered it.

Even when I get the tester done... I don't feel it will be enough for me to justify my 0.3, so I'll take a glance through the CubicVR bugs, and see if I can nab one that I can fix in a day and bundle that in with the tester as 0.3. I have become pretty familiar with the way CubicVR works that I can't imagine it will be difficult to finish. I guess I am hoping do a bit extra will excuse my tardiness.

As a cool side note, the Doom 3 source code was released. I am pretty excited to get a chance to dig through it, see if I can find any patterns or conventions use that I can learn from and adopt.

Mouse controls in Firefox: Going from the ground up

So we were tasked with trying to find some way of manipulating the mouse controlling code for the Firefox browser. For those who haven't seen it before, the Firefox code base is massive, so randomly choosing where to start will likely leave you stranded with no way to find what your looking for. It is in your best interest to start from something you are already familiar with and move from there. Even in foreign code, there will be many overlapping tools or code bases you are likely to already be familiar with. So I started from the lowest level I could find, simply because I am most comfortable and knowledgeable there, which in this case was the Windows API.

So I went into this thinking two things:

• I am trying to find where the browser gets the mouse data so I can manipulate it
• This build is compiled on Windows, so it needs to talk to the Windows API to get hardware input

So this left me with an easy opening, I'd simply search through the code base looking for Windows API input based function calls, and that would narrow down my search to a few files. It did, leading me to the \widget\src\windows\ folder. From there I found nsWindow.h and nsWindow.cpp; after glancing through the .h file, I knew I was looking for things that modified the sLastMousePoint variable. With a quick flip through the CPP file, I found where it was initialized, and where it was updated, the DispatchMouseEvent function. Having had the needed information passed in by the function, I glanced down to find the GET_Y_LPARAM functions that set the event pointer position which later altered the sLastMousePoint variable. Knowing I had found the entry point for the mouse information, I simply swapped the X and Y values for the mouse and tested it. As expected, the browser now though the movement on the X was on the Y and vice versa. With that working, I called it a day, I now knew where the raw mouse information was injected from the OS.

If anyone wants more information on this, comment and I'll post an updated post with more explanation.

**Update** - If my previous explanation was too wordy, here is a simple code sample.

mozilla-central\widget\src\windows\nsWindows.cpp

bool nsWindow::DispatchMouseEvent(PRUint32 aEventType, WPARAM wParam,LPARAM lParam, bool aIsContextMenuKey,PRInt16 aButton, PRUint16 aInputSource)
{
bool result = false;
UserActivity();

...

nsIntPoint eventPoint;

eventPoint.x = GET_Y_LPARAM(lParam);
eventPoint.y = GET_X_LPARAM(lParam);

nsMouseEvent event(true, aEventType, this, nsMouseEvent::eReal,aIsContextMenuKey
? nsMouseEvent::eContextMenuKey : nsMouseEvent::eNormal);
...

Javascript: The language everyone wishes it wasn't

Having just gotten to watching the Crockford videos (well, 2 of 5 so far) due to the video's intimidating length (~7.5 hours in total), I'll say its definitely interesting and worth viewing. If you haven't yet seen them, they are easy to find on youtube (yahoo theater versions seem to have been moved or taken down).

The first part about the history of programing was quite interesting, but fairly inconsequential and can be skipped if you want to save yourself an hour and a half of time. It can be found here.

The second part really starts getting into the workings of javascript and its relationship to the browser. Crockford outlines many advantages and disadvantages to javascript, almost all of which I already knew, but he also outlined the ES5 standard, which had many awesome things that I think javascript sorely needed. The video can be found here.

Of the pros he discussed, the only thing that particularly sticks out is the sheer dynamism of the language, mostly given to it through its use of prototypical inheritance. This dynamism allows for a program to undergo a drastic change in structure or scope with less tedious refactoring involved when compared to other languages.

Of the cons he discussed, they all seem to stem from a simple lack of forethought on the part of the language's developers. Many of the issues came from the developers trying to make the language accessible to beginners, while they did manage to succeed in this, it resulted in many pitfalls that still plague the language today. One that stuck out to me was the NaN variable, as I didn't know that NaN does not equal NaN and that NaN is subsequently toxic to all numeric operations there after that use the NaN. Seems like a fairly useless implementation; I recall Objective C (terrible language btw...) having a similar situation with NaN, but I am unsure if NaN didn't equal NaN in that language.

The part I found most interesting was the new things that were being introduced in the ES5 standard. I was unaware of this functionality, but much of it seems very useful and would address many of the problems I have with javascript. A short document on the ES5 changes can be found here. These changes seem to primarily introduce ways to give greater control over the objects you create and use in javascript, giving you the ability to more rigidly and accurately structure your objects which in turn allows you to more accurately structure your scripts. I am not sure as of right now how widely supported these are across all the browsers out there, but I would hope that it is a fully supported standard by now, as I would like make use of these features in my future scripts.

I'm gonna finish this out by expressing an opinion I've had about javascript for sometime now... What holds javascript back is its attempt to be accessible and easy to learn. This is great for beginners but will seriously hold back the development of a more complex and intricate system that requires a large complicated infrastructure and mass resources to work. I think it may be in the interest of developers to create a new language, keep javascript around for compatibility and for beginners to code on, but give us the option of a cleaner, more robust language that we can work on for larger, more complicated systems that run in the browser. If the browser really is the future platform, the thing we are heading towards for all of our entertainment and media like some suggest, then a better implemented language is a must, because it will take far too long to improve and restructure javascript as to where it is the language we all need it to be.

Using git and setting up my git server

Having used git for a few months now, I seem to have become fairly comfortable with it and have started implementing it into other projects that I have on the run. Really, with the exception of some initial start-up processes it can really be used as nothing more than a simply SVN server, so people familiar with SVN shouldn't have much of a problem operating git at a basic level. From this basic level, the users can slowly start unwrapping the layers of functionality within git. It doesn't seem to be too different from mercurial, I've heard some argue that git has a better branching system but I have heard opposing arguments that git lacks some of the utility that mercurial offers.

One con of git that I have noticed is that due to the way git works, simply making copies and copies of data as it branches and whatnot, it makes it inviable to keep binary resources(images, models, etc) grouped in with source code. If a project were to ever become large are well distributed, the sheer disk space usage that these resources would incur would very quickly spin out of control. I suppose this isn't too much of an issue, as it is probably good practice to keep your resources separate from your repo system anyways, instead using a more specialized solution to distribute a program's binary resources.

I recently got a git server running on my own personal server using gitosis. It was surprisingly difficult to get running, but this likely has a lot more to do with the fact that git server software are not usually built to run on Windows Server 2008 and are instead meant to run on Linux based system. Though through the use of cygwin and a few hours of tweaking I got a private git server running. If anyone is interested in having a place to privately store your code (as opposed to github which public unless you wanna drop like $8/month), you could set up your own git server running on your desktop or, once I get the security tightened up and tested on my server, I may be willing to give people accounts on my server so they may have access to a git repo that is unaccessible by the public.

Building Firefox in debug

So, I have recently attempted to build firefox in debug mode on windows. Having follow the instructions posted here after having downloaded all files from the git repository. Things were moving smoothly until I attempted to execute the make process, in which case it displayed the following error:
client.mk:121: *** This source tree appears to have Windows-style line endings. To convert it to Unix-style line endings, run "python mozilla/build/win32/mozilla-dos2unix.py". Stop.

I ran the python script it suggested, and after processing it, I re-ran the make process, but it continued to fail with the same error. I have looked up some in information on this problem, some have indicated that I have to set a option when I pull from the repository... I have yet to test this but I will update this when I have successfully completed the make process and share my findings.

**UPDATE** - So, found out why those errors were coming up, funny because I believe David Humphrey mentioned this in class (or someone did) but I didn't understand the context of what he was talking about. The problem is that git wasn't configured to deal with windows line endings correctly, so by entering the following command:
git config –global core.autocrlf false

and re-cloning the repo, this issue should be fixed.

**UPDATE** - So, took a while but it finally finished building. When I go to run it, for some reason it opens up my normal firefox application instead of the nightly build, but I'll figure that out tomorrow.

CubicVR Issue 30 - 0.2 Tester

So I finished the first run through of the material tester. I decided to develop more of a testing platform instead of a simple tester for materials, allowing the user to use and tweak the settings of the tester on the fly. I only managed to incorporate three basic material types into the tester, but the basic lighting and and dynamic object creation component seems to work. I plan on hopefully having this tester finished by 0.3, working with all materials and all lights, as well as other things that may end up conflicting in the system. It can be accessed here https://github.com/CloudScorpion/CubicVR.js/blob/issue30-dev/tests/material%20regen/Material%20Test.html

The other issue I am working on is the dirty material issue. I couldn't figure out much else to do other than simply adding the dirty flag variable to the materials and incorporating it with my previous changes. It can be accessed here https://github.com/CloudScorpion/CubicVR.js/blob/issue30-dev/source/CubicVR.Material.js

So that will hopefully suffice for 0.2. Hopefully I will have more time to sink into 0.3 than I did into 0.2 but only time will tell. I'm still unsure if I am supposed to submit this 0.2 somewhere, I haven't found anything about it on the wiki, hopefully I can contact David Humphry today to find where I can submit this stuff, if I even have to...

Getting back to things....

I've been working on a material testing system for the last while, in a hope to make a system with enough utility to do more than simply test one or two things at a time. I've also added the "dirty material" flag to all materials to my original bug, but I'm a bit confused on where else I can go with that bug, thus I have been concentrating on the test system.

My time has been strung quite thin lately, dealing with tests and assignments from other classes and dealing with details pertaining to my other jobs, I haven't gotten to blog much lately, mostly because I haven't had time to dabble in OSD work at all, thus I'd have nothing to blog about. Hoping to finish this 0.2 tonight since I have another assignment due in a few days for another class.

CubicVR Issue #23 version 0.1 release

It took me some time to figure out how CubicVR works, but now I have a basic understanding of its workings and was able to create a 0.1 release that isn't completely worthless. The issue was that when a material was initialized with an opacity of 1.0, it could not because changed because the shader was already setup not to do alpha blending for performance reasons. Subsequently, material that started opaque could never change.

My development proceeded in three steps. First, I created a tester page to recreate the bug so that I could test to see if my solutions had fixed it or not. This tester can be found here. I simply displayed two boxes on screen with the camera spinning around it with controls at the top to adjust one of the box's material's opacity, which started at 1.0. This tester was partially based off of the Normal Mapping render tester that was already on the repo.

The second step was a very simple fix by forcing all opaque objects to having blending on them. This fixed the issue but at a needless cost, so I had no intention of considering it an actual fix.

The final step was the development of the fix submitted as the 0.1 release. This fix kept track of whether or not the material had blending enabled on it, while the system was rendering the materials if it came across a material with blending not enable and an opacity below 1.0, the shader would be cast aside and a new one generated on the spot. Its obviously not the best solution, but it seems to work well enough for the time being.

CubicVR Material Bug

I have been suited with a material transparency bug for the CubicVR 3D graphics system. The problem seems to be that when a material is initialized with an opacity of 1.0, that it cannot be changed afterwards. It was mentioned that the material system might just as well benefit from some form of dirty flag that will force the material to be regenerated during the next cycle so that inconsistencies like this should not be an issue any longer. I had a fair bit of experience in 3D graphics (for about a year now) so I was also asked to look into another issue, which is to create an automated test suite for the all of the commonly used material types. If no one else ends up wanting to grab that one, I might take it on board as well.

I have just recently completed a small test page that replicates this issue so it should make it easier to identify the state of my bug fix as I am developing it. It is a simple pair of boxes with the camera spinning around it and a control at the top of the page to allow you to change the transparency of one of the boxes, using the other box as a reference point. Its nothing spiffy but with it complete I am hoping I can have a rough bug fix ready before mid-night.

The Open Source Community Readings

The readings for week 2 were pretty interesting , both based around the same concept, the open source community, but both presented in different and interesting ways. Both of their concepts seemed to be tried to inspire the same thing, the motivate people into jumping into the open source community, because they David said, you are not going to be invited in.

The most powerful idea they both seemed to be presenting was that, trying to wait and build up your skills before jumping into the open source community is a flawed approach, though one that is pretty much the standard approach used elsewhere. They tried to emphasize that its OK to just jump in and absorb whats going on around you, its OK to try and fail. By simply taking part in any small part of the community, you are helping build the community, and even if what your attempting to do fails, you will learn enough not to make the same mistakes the next time and you will grow more integrated into the community.

One thing that struck me about what Mike Beltzner said was that one of the most useful skills you will learn in the open source community is who you should listen to, and who you can safely ignore, and that you can probably safely ignore 80% of the those who are communicating in the community. This spurred a few conflicting thoughts in my head, while I would naturally completely agree with such a statement, that most talk is simply noise, it makes me wonder if that means in the open source community, if you are just entering the scene, does that mean your goal is to try and fight your way into the 20% margin of people worth listening to? Or is it OK to simply go ignored until you have done something worth listening to, though this sorta conflicts with the idea that you should just jump in and try....

One last thought I had came from David's speech about the festivals. By simply going to the festival, does that really make you part of the community? Or are you simply there to utilize the fruits of the community's efforts? What I am trying to differentiate is the use of the community vs participating in the community. A festival doesn't come together the day of, it requires much planning and preparation, and by simply going to the festival doesn't make you a part of it. How do you make the transition from festival goer to actually participating in it? While I believe there is value in going and seeing and understanding the activities, the transition into actually becoming a part of it hasn't been well illustrated here...

Open vs Closed Licenses

For this entry I have read the BSD license and the proprietary license for Skype. I will be illustrating 3 things about these licenses that stuck out to me below.

The first thing that stuck out to me was their vastly differing sizes. The BSD license seems to be written in a broad, vague, all encompassing manner using very simple and easy to understand concepts to dictate the purpose of the license. It would seem that it is written this way to invite people to read, understand and use the license to its fullest. In contrast, the Skype license is very long, repetitive and very bloated, repetitively using long strings of synonyms to concretely dictate very simple ideas that could be written much more concisely. It seems the purpose of this tactic is so that consumers will not actually read these and simply agree to them, thus allowing them to sneak in sketchy terms that the user might otherwise not agree to.

The second things that stuck out was not a difference between the licenses, but a similarity. Both licenses dictate that if the software somehow ends up causes any form of damages, that the copyright holders are not liable. With the BSD license, it pretty much flat out states that no matter what you can't go after the copyright holders for anything no matter what the software may end up damaging. The Skype license spends several paragraphs dictating what they are not liable for, but at no point flat out states that they are not at all liable for any damages as the BSD license does. Interestingly, the Skype license also spends a fair bit of time dictating what belongs to what company, presumably spreading around liabilities.

The final thing that stuck out specifically about the Skype license is that they pretty much state that you don't own anything and that they can change anything as they will without notice. If you purchase a phone number from them, in the eula they state that you do not own it, that they can change it at any time and that you cannot transfer ownership to another person if you wish. It also states that any content you put up can be taken down for any reason at any time and they are not required to put it back up or return it to you. They also reserve the right to cancel your account at any time if they believe you have in anyway broken any agreements you agreed to, which can be changed at anytime and by simply continuing to use the product you agree to the amended terms.

Those are what really stuck out to me about those licenses. One thing it makes me question is the viability of the BSD license in a business situation, because the use of it makes it impossible to hold the creators liable, making it hard to want to invest time/money into software could fail at any time and there would be no one liable for the possible damages or loss of data/time/money as a result of the failures....

Sickness, recovery, and so many open sores...

I'll start with the obligatory yet meaningless reason as to why this is my first blog in some time; I got pretty sick last week and I really wasn't able to accomplish much of anything. I am finally catching up on my work now and though this post will be quite outdated and possibly meaningless, I'll write it anyways, gotta keep the spirit alive right?

The readings put open source development is a slightly new light that I hadn't considered before. I have never been a huge supporter of open source development, not that I am particularly against it, but I am just not one to look at a proposed methodology and simply accept it as being a more correct or superior methodology without having given all other methods serious consideration. With that said, open source development does seem to have a very concrete and everlasting place in the software development world. Still I can't see it overtaking all aspect of software development, closed source development has just as concrete a future in the software world.

The cathedral and bazaar paper illustrated where I think open source development really thrives, where people have a common issue they need solved. With Eric's example of his fetchmail project, he made it seem that he was able to muster up such an large number of people to assist him because they wanted to see the product work, they wanted the problems that they had fixed and that they just wanted to feel like they were contributing something useful. Though I have started noticing more and more that open source seems to be more like an intern program, something you do simply to be able to put it on a resume or to start making contacts and gaining experience, be it unpaid. But perhaps my views on this are clouded, on the tail end of college and only seeing this trend in my peers desperately clamoring for employment.

There is one thing I find brilliant about the bazaar method, quite obviously its greatest strength, which is illustrated in Eric's version of Linus' Law; "that given enough eyeballs, all bugs are shallow". Any programmer knows that finding bugs and narrowing down their cause is likely to be your greatest source of wasted time when you are trying to develop something. Having your clients act as testers and developing rapid fixes for the bugs that arise is probably the best way to make the most out of your programmers time, allowing them to develop more things faster. But this does come with one risk, and that is of course taxing your clients patience, which is why the split distribution is such a good idea, having one stable and one unstable build, allowing the clients to revert to the stable versions if they simply want to work with the product without dealing with bugs.

That about raps up my thoughts on these readings. One thing I did find funny about the people in the video was that, you would think that open source figures like them would be open and (to a degree) submissive but in fact they came across as very territorial, especially towards each other.

As a last note, I filled in my wiki page with some basic information about myself, so if you want to know a bit more about me, check out http://zenit.senecac.on.ca/wiki/index.php/User:CloudScorpion.

OSD600 Blog

I am not really gonna say anything in this blog post, simply putting it in to make sure it works.