After class on Tuesday we met and worked some more on our project. We decided to move forward on one of our small bugs and our big bug.
Another thing I did was e-mail some DIFFERENT people at ITK as far as our bugs not having been accepted yet. I also changed the subject lines. I found out putting the bug number got the messages filtered out for some reason.
And on the git page for my bug it says.....
Change has been successfully pushed.
Check it out: http://review.source.kitware.com/#change,1089
Thursday, March 31, 2011
Tuesday, March 29, 2011
FOSS update
Last week after class we met and attempted to work on our BIG bug. I knew we needed to stay on track with constantly working on it so I set up a meeting.
Unfortunately we ran into some roadblocks. We had trouble with the issue of the 3gb image. We are still researching that now.
Unfortunately we ran into some roadblocks. We had trouble with the issue of the 3gb image. We are still researching that now.
Thursday, March 17, 2011
POSSCON Speakers
I will talk to:
John Metric - Sugar CRM Business Application Framework
Steven Jackson & Roger Soper- Drupal
David Duggins - Starting a Business Using Open Source
On Friday I will be going to John Metric and David Duggins' talk.
Some of the Questions to ask:
John Metric - Why did you decide to make Sugar CRM open source?
David Duggins - Thoughts on using Sugar CRM for his process. What is his number one tip for running a software based company?
John Metric - Sugar CRM Business Application Framework
Steven Jackson & Roger Soper- Drupal
David Duggins - Starting a Business Using Open Source
On Friday I will be going to John Metric and David Duggins' talk.
Some of the Questions to ask:
John Metric - Why did you decide to make Sugar CRM open source?
David Duggins - Thoughts on using Sugar CRM for his process. What is his number one tip for running a software based company?
Tuesday, March 15, 2011
POSSCON
I received an email about POSSCON the other day asking me to confirm whether I was still going to the event. I replied that I was going Thursday. I'm hoping that today in class we will be talking about POSSCON for a little bit and what the situation is with the rides.
As far as our timeline, we had already done it before the break so that has been done.
As far as our timeline, we had already done it before the break so that has been done.
Sunday, February 27, 2011
My first bug
I fixed one of the VTK bugs tonight. The bug was 0010861 in the VTKPolyDataConnectivityFilter.
I had the source code for VTK straight on my system, so I had to install it through GIT instead. To do this I did the following:
cd VTK
git clone git://vtk.org/VTK.git VTK
git clone git://vtk.org/VTKData.git
./Utilities/SetupForDevelopment.sh
git remote add gerrit asbissad@review.source.kitware.com:VTK
git commit
git add
git push gerrit HEAD:refs/for/master/PrivateToProtected
I had the source code for VTK straight on my system, so I had to install it through GIT instead. To do this I did the following:
cd VTK
git clone git://vtk.org/VTK.git VTK
git clone git://vtk.org/VTKData.git
./Utilities/SetupForDevelopment.sh
git remote add gerrit asbissad@review.source.kitware.com:VTK
git commit
git add
git push gerrit HEAD:refs/for/master/PrivateToProtected
Thursday, February 24, 2011
TOS CH7 - 2/24/11
PATCHES
Exercise 7.2.2
The first diff command is VERY different than diff with -u.
The first one gave me:
6c6
< prntf(Hello World.\n");
---
printf("Hello World!\n");
WHEREAS, diff with the -u gave me clearer details.
It showed where the program changed, the lines, everything.
The UNIFIED diff is Unparallelled!
Exercise 7.8:
I received the following input when I did this exercise. Basically null is an empty file so everything in the diff is an addition(+)
--- /dev/null 2010-12-03 09:50:34.426290301 -0500
+++ foo.c 2011-02-24 11:41:59.000000000 -0500
@@ -0,0 +1,8 @@
+/*foo.c*/
+
+#include <stdio.h>
+
+main() {
+printf("This is a new file.\n");
+}
+
Exercise 7.9:
./configure was intense, as was make.
The text is a little confusing. I did not see those as two separate commands at first.
I would suggest some clean up in terms of the typos in the book to make things clearer.
The src/echo command worked.
Exercise 7.2.2
The first diff command is VERY different than diff with -u.
The first one gave me:
6c6
< prntf(Hello World.\n");
---
printf("Hello World!\n");
WHEREAS, diff with the -u gave me clearer details.
It showed where the program changed, the lines, everything.
The UNIFIED diff is Unparallelled!
Exercise 7.8:
I received the following input when I did this exercise. Basically null is an empty file so everything in the diff is an addition(+)
--- /dev/null 2010-12-03 09:50:34.426290301 -0500
+++ foo.c 2011-02-24 11:41:59.000000000 -0500
@@ -0,0 +1,8 @@
+/*foo.c*/
+
+#include <stdio.h>
+
+main() {
+printf("This is a new file.\n");
+}
+
Exercise 7.9:
./configure was intense, as was make.
The text is a little confusing. I did not see those as two separate commands at first.
I would suggest some clean up in terms of the typos in the book to make things clearer.
The src/echo command worked.
Tuesday, February 22, 2011
2/22/11
We had a good meeting this morning. We all met in the computer lab at 9am. I was able to test out the fix for the bug on my system, of which I wrote the how-to instructions on the team wiki. Honestly the code is much simpler than everything else leading up to it (i.e. installing and compiling all the correct files). It is nice to see just a little bit of overlap between this class and CSCI340.
We also just found the VTKSTLWriter Class Reference, which would have been nice to have a week ago. But we have it now so that will be beneficial. We did not find it from our searches, rather through corresponding with someone else on the project who recommended the page to us through comments on the Bug Page. His name is David Doria. He seems to be quite active and quick to respond, which is nice.
One thing we have had an issue with is getting our fix submitted. There was no clear documentation on it, so we placed a post on the VTK mailing list. We were informed that we need specific access to be able to post our bug. So right now that is still up in the air.
We also just found the VTKSTLWriter Class Reference, which would have been nice to have a week ago. But we have it now so that will be beneficial. We did not find it from our searches, rather through corresponding with someone else on the project who recommended the page to us through comments on the Bug Page. His name is David Doria. He seems to be quite active and quick to respond, which is nice.
One thing we have had an issue with is getting our fix submitted. There was no clear documentation on it, so we placed a post on the VTK mailing list. We were informed that we need specific access to be able to post our bug. So right now that is still up in the air.
Subscribe to:
Posts (Atom)