retry calls on SSH commands were added to avoid temporal server errors
HTTP 404 errors are managed when user’s organizations are fetched
generic RateLimitError exception is used
In Mediawiki backend, the log messages written when a revision is not found were set to ERROR when the real level should have been WARNING.
The URL used to fetch jobs in Jenkins was not common to all servers.
When UUIDs are generated with some input data, some errors may be raised due to problems encoding invalid characters on the input. To avoid these problems, a surrogate escape control error has been set when data is encoded to UTF8. (#123)
We want you to test Perceval and Grimoire following the under development tutorial. If you are a GitHub user you might try The Cauldron for free to analyze some GitHub organizations. And of course, feedback, issues and pull requests are always welcome!!!
Not everything in inner source is about community building [but a big portion!] and the infrastructure is basic to foster collaboration, transparency and community building.
This post is about aspects to have in mind when deploying the tooling needed to provide support to developers within the organization and across business units.
There is a more extended version of this infrastructure topic in the work-in-progress book about inner source: Managing Inner Source Projects that we, in Bitergia, are writing. Specifically in the infrastructure chapter. This is available under a CC-BY-SA 4.0 license and anyone is more than welcome to propose new sections, improve the current ones and collaborate in any way. Please feel free to redistribute!
We are hiring a Python developer to help us developing GrimoireLab, our stack for software development analytics. We are looking for a smart, high-energy person, with a passion for learning, contributing and collaborating in free, open source projects to work with us in Madrid (Spain) area.
We offer a 6 month job, with possibilities for a later extension, and a salary range of 25K – 35K € / year.
Commuting at least three days a week is required
No Agencies Please
Effective communication and collaboration in English
Experience developing with Python (+2 years)
Free, open source software knowledge and background
Experience with collaborative tools, including Git and GitHub
We would like to do a background check: GitHub profiles or other ways for checking past developments are welcome.
Other skills and experience that will be valued
Participation in free, open source software projects (please include references)
Test Driven Development (TDD) and Continuous Integration
About the Company
Bitergia analyzes community software development processes to help companies like Red Hat or Intel, and organizations like Linux Foundation, Mozilla or Wikimedia Foundation to understand and manage the free, open source software, and inner source projects in which they are involved. Bitergia provides training and consultancy for managers and teams willing to take advantage of software development metrics to improve their effectiveness.
When looking back nowadays to the work done on diversity, I’ve realized that it has been quite a trip! My first approach to the topic was in an informal meeting with Nithya Ruff, currently at Comcast. She mentioned that the OpenStack Summit in Tokyo reached (as far as I remember!) 13% of women attending the Summit. And this was a great number if compared to previous summits as the percentage kept growing. But she also mentioned that they received a tweet asking about the current number of technical contributions. Then this is where we decided to have a look at that issue: have numbers, and try to produce some of them from a quantitative point of view.
We are pleased to announce that we are writing a book about inner source.
We have been collaborating for some months with companies that are developing this methodology to produce the software they need. They were pioneers who early on realized that inner source has lots of benefits for talent management, software development, and business improvement. And now others are asking us for advice about implementing inner source.
So we have decided to bring together all our knowledge about inner source, share it and ask for open collaborations. We want to do this as openly as possible. We are building it as a GitBook, posting each chapter and asking for reviews. We will announce each part on our blog. So stay tuned and don’t miss a thing!
We are all used to open source projects. Concepts such as community, code review process, continuous integration, geographically distributed contributions, community managers, and a whole myriad of terms and collaborative way of working are usual for all of us. And enterprises are learning from this open process. Those are changing the direction of their development models to a more open one within the organization. Initiatives such as the Inner Source Commons where companies such as PayPal or Bloomberg are publicly exposing their case, help others to deal with the usual problems they face.