Correction: #Pijul ... it is a #dvcs / #scm system written in #Rust, and an evolution of some of the ideas behind #Haskell's #Darcs, including fleshing out the theoretical basis and solving a couple of major bugs.
Is the #Fossil #scm #vcs a #blockchain? Maybe not, but the article illustrates how many concepts of a blockchain are used in fields other than cryptocurrencies.
I think y’all know I favor the #Fossil #SCM / #DVCS over #Git (though I’m giving #Mercurial ( #Hg ) another look as well. I’m resource-constrained as well as energy-limited, but I have been thinking of standing up a miniature software forge for !FNetworks projects and users, likely using Kallithea (which can use both Hg and Git) and also having some Fossil repos (but not as part of a forge).
It's pretty demoralizing to never get any responses from anyone but @lnxw48a1, but I am nothing if not persistent.
I realize I could interact more and gain more followers and I could post more. Maybe I'll give Mastodon a shot a see if I get more interaction there. I don't think I've joined an instance but maybe I have.
Minimum of five years of software development and design or systems administration or level 3-4 technical support experience.
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Understanding of software best practices; #SDLC, #SCM and #Agile development principles.
Excellent written, verbal, and presentation skills
Role: Open Source Staff Engineer/Solutions Architect
Location: #Louisville, #CO or #Minneapolis, #MN
Position Summary:
Perforce is seeking a Open Source Staff Engineer/Solutions Architect to join our OpenLogic team. As a member of the support team, you’ll be responsible for assisting our clients to work through their technical questions on open source including ‘how to’, trouble shooting and recommendations on product use. Additionally, based on needs of our customers, you will be involved in presenting training classes (both onsite and remote depending on need of the client); short-term professional service engagements to assist with architect and design solutions; working on internal projects; and enhancing current skills by continuing to learn new open source technologies.
OpenLogic provides enterprise services for hundreds of open source projects — including #OpenJDK, #Kubernetes, CentOS, and #MariaDB — so you can boost efficiency and savings with free software, while cutting risk.
Responsibilities:
Interact with end users on technical problems.
Tier 1, 2 and 3 support for CentOS and related open source products.
Drive resolution of those problems, which include:
Open source software issues.
Questions around open source software usage.
Questions around use and best practices.
Review of the architecture and design where software is implemented.
Conduct professional services and training engagements.
Research, understand, and advocate open source software.
Interact with various open source communities.
Drive early resolution of issues.
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
May require 15% travel while completing on-site consulting.
Position Summary:
Perforce is seeking a CentOS Support Engineer to join our OpenLogic team (that's my new team, but this is not my specific position), responsible for providing 24x7 break fix support and services on Open Source technologies to our OpenLogic customers. This position will work closely with members from Support, Sales and Professional Services to assist in resolving a wide variety of customer issues. OpenLogic provides enterprise services for hundreds of open source projects — including OpenJDK, Kubernetes, CentOS, and MariaDB — so you can boost efficiency and savings with free software, while cutting risk.
Responsibilities:
Interact with end users on technical problems.
Tier 1, 2 and 3 support for CentOS and related open source products.
Drive resolution of those problems, which include:
Open source software issues.
Questions around #opensource software usage.
Questions around use and best practices.
Review of the architecture and design where software is implemented.
Conduct professional services and training engagements.
Research, understand, and advocate open source software.
Interact with various open source communities.
Drive early resolution of issues.
Make strategic contributions to the CentOS core and surrounding ecosystem, provide bug fixes ahead of the community where needed
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
Requirements:
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Strong knowledge of the Linux kernel and system architecture.
Understanding of software best practices; SDLC, #SCM and Agile development principles.
Ability to develop with C/C++ in a #UNIX environment.
Utilization of common Linux C/C++ build tools such as gcc.
Solid understanding of CentOS 6.x and 7.x and included frameworks like firewalld, systemd, etc.
Strong #RHEL/CentOS background required
#Debian/ #Ubuntu, #SUSE/ #openSUSE/ #SLES, other distro background a bonus
C, shell scripting, #perl, etc
Virtual Machine experience with qemu/kvm, #Azure, #AWS, VirtualBox, #Vagrant
General experience such as: radius/ #Kerberos, lda, ipa/idm, monitoring, vpn, containers, centralized systems management, automation (ansible, chef, puppet, etc), version control (git, etc) or security hardening (CIS, STIGS, PCI-DSS, etc)
Excellent written, verbal, and presentation skills
Knowledge of open source packages
Database administration; #postgresql/ #mysql/ #mariadb experience very desirable
Experience with Linux distro package building (#rpm, #deb, ipkg, etc) preferred
Existing contributions to the CentOS community a major plus
Interact with end users on technical problems.
Tier 1, 2 and 3 support for #CentOS and related open source products.
Drive resolution of those problems, which include:
Open source software issues.
Questions around open source software usage.
Questions around use and best practices.
Review of the architecture and design where software is implemented.
Conduct professional services and training engagements.
Research, understand, and advocate open source software.
Interact with various open source communities.
Drive early resolution of issues.
Make strategic contributions to the CentOS core and surrounding ecosystem, provide bug fixes ahead of the community where needed
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
Requirements:
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Strong knowledge of the Linux #kernel and system architecture.
Understanding of software best practices; #SDLC, #SCM and #Agile development principles.
Ability to develop with #C / #C++ in a UNIX environment.
Utilization of common #Linux C/C++ build tools such as #gcc.
Solid understanding of CentOS 6.x and 7.x and included frameworks like #firewalld, #systemd, etc.
Strong #RHEL/CentOS background required
#Debian / #Ubuntu, #SUSE / #openSUSE / #SLES, other distro background a bonus
C, shell scripting, #perl, etc
Virtual Machine experience with #qemu / #kvm, #Azure, #AWS, #VirtualBox, #Vagrant
General experience such as: radius/Kerberos, lda, ipa/idm, monitoring, vpn, containers, centralized systems management, automation (ansible, chef, puppet, etc), version control (git, etc) or security hardening (CIS, STIGS, PCI-DSS, etc)
Excellent written, verbal, and presentation skills
Knowledge of open source packages
Database administration; #postgresql / #mysql / #mariadb experience very desirable
Experience with Linux distro package building (#rpm, #deb, #ipkg, etc) preferred
Existing contributions to the CentOS community a major plus
My new team (and my old team too, actually), is looking:
Interact with end users on technical problems.
Tier 1, 2 and 3 support for #CentOS and related #opensource products.
Drive resolution of those problems, which include:
Open source software issues.
Questions around open source software usage.
Questions around use and best practices.
Review of the architecture and design where software is implemented.
Conduct professional services and training engagements.
Research, understand, and advocate open source software.
Interact with various open source communities.
Drive early resolution of issues.
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
May require 15% travel while completing on-site consulting.
Requirements:
Minimum of five years of software development and design or systems administration or level 3-4 technical support experience.
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Understanding of software best practices; #SDLC, #SCM and #Agile development principles.
Excellent written, verbal, and presentation skills
Expert level in a number of open source packages.
Broad and deep familiarity with multiple projects to include #Java and #J2EE, #JBoss, #ActiveMQ, #Drools, #HornetQ, #Hibernate, #Spring, #Linux (focus primary on #CentOS or #Ubuntu), #Apache #HTTPD, Apache #Tomcat, #MySQL, #PostgreSql, Open source project and community participation and Production/24x7 experience.
Database administration; postgresql/mysql/ #mariadb experience very desirable
Expertise in #Cassandra, #Kafka, and/or #cloud-native applications is a plus.
One of ikiwiki's features is the very good #vcs (or #scm) integration. My wiki came into existence not only as a directory of .md filws but also as a #mercurial repository. I can 'hg push' to it via SSH and a hook automatically refreshes everything. Visitors can 'hg clone' the source via HTTPS. (Git mirror is currently broken). Any comments or edits made over the web will be tracked as an automatic commit in the repository. As a bonus, there's links to the history and diffs via hgweb. Neat, yes?
It's funny to think of !perforce as config management like !chef, but #SCM is the initialism Practical Perforce uses. I'm fine changing the !config group to be SCM if people prefer.