Current problems with robot

[rafilong]

Problems that need fixing (will update)

• ranger finder not working

[niharmitra]

Why, of all people, would you make an issue on GitHub!?! You have a terrible reputation as is(lol), and we already have assignments.md to place these things. And we are already fairly self organized, so why do we need this issue suddenly? Did someone tell you to make an issue, because I feel it's pretty unnecessary right now.

Thanks for not spamming, Nihar :P

On Tuesday, February 18, 2014, Rafi Long notifications@github.com<javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

Problems that need fixing (will update)

• flush trigger - not stopping / glitching
• ranger finder not working

Reply to this email directly or view it on GitHubhttps://github.com/team8/fenrir/issues/4 .

[tekknolagi]

Nihar,

Abuse is never tolerated in robotics, including online. I will be speaking to you privately.

Max

On Tue, Feb 18, 2014 at 11:31 PM, Nihar Mitra notifications@github.comwrote:

Why, of all people, would you make an issue on GitHub!?! You have a terrible reputation as is(lol), and we already have assignments.md to place these things. And we are already fairly self organized, so why do we need this issue suddenly? Did someone tell you to make an issue, because I feel it's pretty unnecessary right now.

Thanks for not spamming, Nihar :P

On Tuesday, February 18, 2014, Rafi Long <notifications@github.com<javascript:_e(%7B%7D,'cvml',' notifications@github.com');>> wrote:

Problems that need fixing (will update)

• flush trigger - not stopping / glitching
• ranger finder not working

Reply to this email directly or view it on GitHub< https://github.com/team8/fenrir/issues/4>

.

Reply to this email directly or view it on GitHubhttps://github.com/team8/fenrir/issues/4#issuecomment-35470322 .

[sauyon]

It's also kind of what issues are for...

[rafilong]

Why me? Because I was there working on the code with James, and as we finished the final code at around 11-11:30 there were some things that we couldn't finish. I wanted to make sure that bugs in the code that weren't gonna be fixed on time were to be able to be fixed. If we don't have a list of these things before the robot is shipped, we won't know what the problems are until the competition. And that's something we probably want to avoid.

[niharmitra]

First off, I'm sorry that my original message came off as abusive. This was not at all my original intention, and in hindsight, I realize that when I typed in a casual way that I would have talked to Rafi, certain things were not clarified, and the message would be very different when read than when heard. It appears that my message was interpreted based on the joke I was trying to make (and unfortunately phrased badly), while my actual point seems to have been obscured.

My intended message was like this: "Lol Rafi, why did you make a GitHub issue? You remember what happened last time....

But anyways, you know that a couple weeks ago programming team decided to make assignments.md for this purpose? We didn't want to use the issues system, so instead we decided to put any goals/tasks in that document instead"

I hope you can see that my intended message was that programming team had already put into place something for this purpose. As you can see by the fact that there are only 4 issues, programming team doesn't like the issues system. While you may disagree with this decision we (many members of programming team in an informal discussion) made, the alternative chosen was to merely create a readme style document that people could view when they weren't sure what to do (this was assignments.md that I referred to in my original message) The fact that Rafi did not know about assignments.mdled me to believe that it was possible that Rafi created an issue merely because nobody from programming team told him about this, and thus I thought that I would.

in the end it turned out that we didn't really use any of the systems since the consistent attendance of people like James and Tyler made it so that word of mouth was used practically all the time to learn what was happening with the robot. This was what I was referring to by our "self-organization" in that it could have been sufficient for Rafi to use word of mouth.

Again, I apologize for my mean message, and hope that this one is much clearer. Nihar Mitra

On Wed, Feb 19, 2014 at 12:32 AM, Rafi Long notifications@github.comwrote:

Why me? Because I was there working on the code with James, and as we finished the final code at around 11-11:30 there were some things that we couldn't finish. I wanted to make sure that bugs in the code that weren't gonna be fixed on time were to be able to be fixed. If we don't have a list of these things before the robot is shipped, we won't know what the problems are until the competition. And that's something we probably want to avoid.

Reply to this email directly or view it on GitHubhttps://github.com/team8/fenrir/issues/4#issuecomment-35476414 .

[rafilong]

Thank you Nihar

Thanks, Rafi Long

On Wed, Feb 19, 2014 at 7:31 AM, Nihar Mitra notifications@github.comwrote:

First off, I'm sorry that my original message came off as abusive. This was not at all my original intention, and in hindsight, I realize that when I typed in a casual way that I would have talked to Rafi, certain things were not clarified, and the message would be very different when read than when heard. It appears that my message was interpreted based on the joke I was trying to make (and unfortunately phrased badly), while my actual point seems to have been obscured.

My intended message was like this: "Lol Rafi, why did you make a GitHub issue? You remember what happened last time....

But anyways, you know that a couple weeks ago programming team decided to make assignments.md for this purpose? We didn't want to use the issues system, so instead we decided to put any goals/tasks in that document instead"

I hope you can see that my intended message was that programming team had already put into place something for this purpose. As you can see by the fact that there are only 4 issues, programming team doesn't like the issues system. While you may disagree with this decision we (many members of programming team in an informal discussion) made, the alternative chosen was to merely create a readme style document that people could view when they weren't sure what to do (this was assignments.md that I referred to in my original message) The fact that Rafi did not know about assignments.mdled me to believe that it was possible that Rafi created an issue merely because nobody from programming team told him about this, and thus I thought that I would.

in the end it turned out that we didn't really use any of the systems since the consistent attendance of people like James and Tyler made it so that word of mouth was used practically all the time to learn what was happening with the robot. This was what I was referring to by our "self-organization" in that it could have been sufficient for Rafi to use word of mouth.

Again, I apologize for my mean message, and hope that this one is much clearer. Nihar Mitra

On Wed, Feb 19, 2014 at 12:32 AM, Rafi Long <notifications@github.com

wrote:

Why me? Because I was there working on the code with James, and as we finished the final code at around 11-11:30 there were some things that we couldn't finish. I wanted to make sure that bugs in the code that weren't gonna be fixed on time were to be able to be fixed. If we don't have a list of these things before the robot is shipped, we won't know what the problems are until the competition. And that's something we probably want to avoid.

Reply to this email directly or view it on GitHub< https://github.com/team8/fenrir/issues/4#issuecomment-35476414>

.

Reply to this email directly or view it on GitHubhttps://github.com/team8/fenrir/issues/4#issuecomment-35510454 .

[rafilong]

Now that the only issue is the rangefinder, I don't see much point in keeping this issue