Conversation
Notices
-
#hiring Technical Support Analyst - Check out this great #job at my company #jobopening #applynow http://bit.ly/2EDYRqf
This is for the #Australia office, and you must know #Chinese.
-
@musicman Is that your new company? You were with Nagios, right?
-
That's correct. I went from a little over 8.5 miles one-way to ~8.5 blocks. I suppose I should have sent that post to !vcs, since it's actually perforce and git related, and not just a, say, finance position. We did have have #gitfusion and #gitswarm, but those are deprecated and now we have #Helix4Git. I don't have a sense yet for how much I'll be able to stay in git land, but we do have a fair amount of FLOSS tooling at https://swarm.workshop.perforce.com/ -- for the most part, I don't think the stuff there is useful outside of perforceland, but some of the #SDP stuff could pretty easily be refactored to work with other products, I think. This is what one of our consultants that occasionally works on the SDP said anyway, and I understand his argument. It's a step backwards as far as FLOSS-ness, but before I agreed to an interview I made sure there would be no restrictions on me contributing to Apache or git. There are not. It might be different for someone hired as a developer, but that doesn't really matter for me personally since that is not, and likely will never be, my role.
-
@musicman Didn't know Perforce did any free software at all. Thank you for broadening my knowledge.
-
@musicman Getting that kind of relief in your commute situation does sound like a move up. I'm happy for you that you could find something that close.
-
yeah, I think if !nagios had better community relations the commute might have been worth it, but the #icinga fork really soured things for a lot of people on both sides (I suppose that pretty much always happens, to some extent). Nagios LLC still takes contributions on Core, but it may be that contributions were being rejected that competed with XI.
We'll see how things go at Perforce, but my hope is that after my non-compete is over Tarus will have some remote openings at #OpenNMS. Back in 2007, OpenNMS sponsored a conference I spearheaded. They were a local-to-me company at the time.
As far as I'm aware, perforce is still gratis for people working on open source projects. Why, in 2018, anyone would do that, I'm not sure. I'm not sure when the policy started, but I bet back before #git, that actually meant something to people.
-
@musicman I don't know OpenNMS. There's probably a FLOSS Weekly ep about it I should listen to.
-
@musicman Ha! Not only one, they were there right at the beginning too!
https://twit.tv/floss15
https://twit.tv/floss418
-
they are compatible with NRPE...and a bunch of other stuff. I don't really know anything about OpenNMS other than that. :) I should fix that, but I think the first priority is learning Spanish since I want to go to South America and my wife pretty much said knowing Spanish was a prereq....even though we could easily go to Bueous Aires (I know this is incorrect, but do not care enough to find out the correct spelling) where my old roommate lives or to Georgetown (which is in the only English-speaking part of South America...but whatever, I don't make the rules, I just follow them)
-
so, I did not realize this until about 5 minutes ago, but our primary command line interface is BSD and appears to have been since at least 2014: https://swarm.workshop.perforce.com/projects/perforce_software-p4/files/2018-1/LICENSE
I still think it is weird that BSD has "All Rights Reserved" right up there at the top.
-
@musicman @clacke "All Rights Reserved" is more of a magical legal formula than any particular statement of license.
-
@blp @musicman Actual lawyer Richard Fontana disagrees and spent energy and time during his time at Red Hat to get rid of it on the Fedora sites. It is a contradiction to first reserve all rights and then turn around and give them away one line later.
-
@musicman BSD generally doesn't have it, just they by reflex included it with their copyright statement.
https://opensource.org/licenses/BSD-2-Clause
-
@clacke @musicman Well, if it can be gotten rid of, I agree that's even better.
-
@blp @musicman It's redundant at best, contradictory at worst. They should get rid of it.
-
I don't remember any such magic from law school. This sentiment likely stems from the US pre-Berne. The whole Berne thing is super-complex because the bill was in '76 if memory serves. Started in '78. We didn't "fully" go in until '88 (or '89), and really didn't go in until Golan v Holder...in 2012. And I think VARA was '94. What a complete and utter mess.
-
The way Bradley Kuhn explained it to me when I was on the Johns Hopkins legal team was that the idea was that the All Rights Reserved applied to the copyright notice itself, but I still don't think that's the intent, since I don't think anyone would mind if they created a different license for a new project. Really, what's needed is a definition of the license, and then you can reference it. I don't think the current text is ambiguous, but I think that would be best practice to eliminate the doubt.
Douglas A. Whitfield
Hallå Kitteh
Ben Pfaff
All Federati Nu: Federated N-series GNU Social content and data are available under the