Commarch Report

Resources:

Source Code repository: 

https://github.com/jcbrand/converse.js 

Mail list archive: http://librelist.com/browser/conversejs/ 

Documentation: https://conversejs.org/docs/html/index.html 

Other communication channels: jc@opkode.com

Project Website and/or Blog: https://conversejs.org/

A. Describe software project, its purpose and goals.

Converse.js is a chat client that runs on a browser as a JavaScript-based plugin, allowing site visitors to chat using the XMPP protocol.

B. Give brief history of the project. When was the Initial Commit? The latest commit?

The first commit to the project is on June 10, 2012 by jcbrand. Issues are regularly fixed and new features are added occasionally.

C. Who approves patches? How many people?

jcbrand act as both the project manager and contributor

D. Who has commit access, or has had patches accepted?  How many total? 

 About 10 people have made significant changes to the project that have been approved by jcbrand

E. Who has the highest amounts of "Unique Knowledge?" (As per your "Git-by-a-bus" report. If there is a tie, list each contributor, with links if possible) 

 jcbrand 

F. What is your project's "Calloway Coefficient of Fail?"

 The project passes Calloway Coefficient of Fail with flying colors, with a total score of 0.

G. Has there been any turnover in the Core Team? (i.e. has the same top 20% of contributors stayed the same over time? If not, how has it changed?) 

 No, the core team has not changed(jcbrand in this case) However, a few developers have become active in the project at different times. 

H. Does the project have a BDFL, or Lead Developer? (BDFL == Benevolent Dictator for Life) 

jbrand again

I. Are the front and back end developers the same people? What is the  proportion of each? 

 Yes, everything is handled by the same person 

J. What have been some of the major bugs/problems/issues that have arisen during development? Who is responsible for quality control and bug repair? 

A major bug existed in the project is that Converse.js sometimes empties the contact list and crashes the browser occasionally when a user is trying to load a huge amount of contacts.The problem is later fixed by jcbrand

K. How is the project's participation trending and why? 

There were a few major spikes in the code frequency graph on github early last year, but since then additions have stabilized and jcbrand seems to be making regular updates to the code.

L. In your opinion, does the project pass "The Raptor Test?"(i.e. Would the project survive if the BDFL, or most active contributor were eaten by a Velociraptor?) Why or why not? 

No, jcbrand almost is the only permanently active contributor and if he is eaten by a Raptor, a new developer will have to take over the project. 

M. In your opinion, would the project survive if the core team, or most active 20% of contributors, were hit by a bus? Why or why not? 

No, for the same reason that it fails the Raptor Test. 

N. Does the project have an official "on-boarding" process in place?(new contributor guides, quickstarts, communication leads who focus specifically on newbies, etc...) 

Yes, the documentation provided explains requirements, features, development details and troubleshooting solutions and is very easy for newbies to get started.

O. Does the project have Documentation available? Is it extensive? Does it include code examples? 

Yes, the documentation is extensive for developers, users and all newbies.

P. If you were going to contribute to this project, but ran into trouble or hit blockers, who would you contact, and how? 

jcbrand who will be available on the mailing list and GitHub issue list.

Q. Based on these answers, how would you describe the decision making structure/process of this group?  Is it hierarchical, consensus  building, ruled by a small group, barely contained chaos, or ruled by a single or pair of individuals? 

 The project is ruled by a single individual

R. Is this the kind of structure you would enjoy working in? Why, or why not?

 Yes, the size of the project is relatively small and simple. This helps up to spot bugs easier and communicate with the project owner(in this case).