Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment It's the economy, stupid! (Score 1) 628

Once all (or most all) the work is being made by robots, who will receive salaries, that then will be spent on the goodies the robots are producing?

You see, you need CONSUMERS to earn money from them. And the government, TAXPAYERS - by the way.

Or they plan to "fix" this little problem by paying salaries to robots, giving them vacations, etc? =P

Comment Re:Are you sure? (Score 1) 863

so configure journald to simultaneously spit out text log files to syslog/rsyslog or you can export them to text files when you need them. its not hard.

Doubling the computing power needed to do something that I already had?

Increasing the risk of failure without adding nothing of value?

And yet, you got +1 Insightful points?

Comment Re:Options... (Score 1) 155

The problem is in finding developers to support the project in the first place...which includes companies being willing to let some of their employees do some of it on company time. The website is NOT the big roadblock here, by a long shot. So forking it accomplishes absolutely nothing, and moving the repository to SourceForge, while not a terrible solution to the "no more website" issue, really doesn't address the true problem.

I understood that the problem is the company not willing to do support anymore - ergo, they're not expending any resources on gathering developers to help. You see, you need expend employee's time in order to look for help out there: you can not find what you don't look for.

And, if you don't know, Source Force is not a web site hosting service. It's a full blown software development infrastructure. Code repository, communication, releasing, bug tracking, support.

Comment Options... (Score 5, Insightful) 155

"Fork" the thing on SourceForge or similar service. SYNC the repos and web pages there over the time while trying to gather collaboration.

Perhaps you can manage to get there what your company doesn't. At very least, this will guarantee the project's surviving when your company shuts the support down.

At very worst, you'll have a way to save the project's source code and documentation to posteriority when the company support ends.

In the mean time, you can negotiate a hand over to Apache, GNU or any other Open/Free Software Foundation.

Comment Re:I'm not convinced (Score 1) 387

you sound like a great asshole to work with... like a typical drama queen on a reality TV show.

Well... I was a really great person to work with. For 4 months. And I regret every single day. And the project's stakeholders too.

It's not pretty. It's not nice. But it worked.

I'm not proud of it. But I would do it again if needed without a second thought.

I'm an asshole? Probably. But this asshole here is going to put food on the employee's table. And mine's too.

Comment Re:I'm not convinced (Score 3, Interesting) 387

Unfortunately, it works well for me.

I spent 4 months trying to be polite and respectful - only to see my project going through the tubes.

It was only when I got pissed off and, literally, attacked verbally some (well deserved, by the way) key people that things started to get done.

I yelled, I cursed, I became blatantly offensive - including, sadly, some other people that didn't deserved (neither had the temper to hold it).

However, now I have control over the project. Things are getting done, deliverables are getting delivered. And my only other real regret (besides yelling to whom didn't deserved it) is that I took too long to get mad. One month earlier, and I would had managed to deliver the project on the proper due date (and got some more sleeping nights).

If you are really committed into delivering good products, the decision about how you behave doesn't belongs to you anymore: you will do what you have to do to get shit done.

Slashdot Top Deals

"Look! There! Evil!.. pure and simple, total evil from the Eighth Dimension!" -- Buckaroo Banzai

Working...