Perforce is seeking a Technical Support Engineer. Needs to be able to speak fluent #German.
Represent Perforce as the first point of contact for their technical support queries. Review scope of customer issue and determine best course for resolution. Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers. Resolve customer issues. Resolve database and performance issues. Research, document, and escalate cases according to procedure. Customer driven feedback to functional areas in order to influence process/product improvements. Author technical documents on common issues and solutions in order to build the knowledge base. Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
2 or more years’ experience providing support directly to enterprise customers. Technical or Bachelor’s Degree in #IT, #CS or similar. #Linux experience Basic #networking experience Experience w/ #Perforce, #Git, or other !vcs is desirable.
It's like grafts, except it's more generic and it can be transmitted between repos!
Instead of a line <commitid> [<fakeparent0> ... [<fakeparentn>]] in .git/info/grafts for just manipulating the ancestry of a commit, you can "now" put an object, any type of object, in refs/replace/<sha1toreplace> and git will use that instead of the real object.
git-replace --graft <blah> <bluh> does the same using this mechanism as adding a line <blah> <bluh> to .git/info/grafts would.
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.
It currently can _view_ things, there's no "Add issue" or "Reply" functionality and it is _not_ intended for web-facing (but running locally for local repositories).
Added the !newgroup !vcs aliases as !git !perforce and !bzr. I'm happy to add more options to the description of the group. My own personal interest is #git integration with #perforce, which is why I aliased it as such. Perforce has some !freesoftware tools, so if you want links, let me know!
The only issue is it's proprietary. I'm going to try to position myself with the #git integration as much as possible. So... is there a git group around here?
@xj9 @moonman #Fossil is my favorite. #Git is too complicated for anything I've ever done. (Planning to look at Mercurial #hg and #Darcs and Bazaar #bzr sometime.)