@@ -284,6 +284,66 @@ the patch series got merged.
284
284
### Support
285
285
-->
286
286
287
+ ## Developer Spotlight: Brian M. Carlson
288
+
289
+ * Who are you and what do you do?
290
+
291
+ I'm a software developer living in Houston, Texas, US. I've long been
292
+ involved in the FLOSS community, mostly with one-off patches,
293
+ documentation improvements, and other maintenance-related work. I'm a
294
+ polyglot programmer, and I contribute to Asciidoctor, among other
295
+ projects. I also enjoy biking and writing in my spare time.
296
+
297
+ Professionally, I'm a developer with cPanel. There I do maintenance
298
+ work on our product and development tools, manage alternating releases,
299
+ advise on security design, and of course maintain the copy of Git we use
300
+ internally and ship to customers. I also perform some training for
301
+ developers, QA, and documentation folk on how to use Git and how to use
302
+ it more effectively.
303
+
304
+ * What would you name your most important contribution to Git?
305
+
306
+ One of the things I've really enjoyed doing is making Git work better
307
+ over HTTP with Kerberos. I use Kerberos for my internal network
308
+ infrastructure at home, and Git has gone from not working at all to
309
+ being very robust and reliable using Kerberos authentication. There are
310
+ still some usability issues we can improve on, though.
311
+
312
+ * What are you doing on the Git project these days, and why?
313
+
314
+ Most of my time is spent on converting the code to use a structure for
315
+ object identifiers (hashes) instead of one-off arrays everywhere. This
316
+ improves the quality and maintainability of the code, and it also makes
317
+ it easier to switch to a different hash than SHA-1. Depending on the
318
+ hash that's chosen, we could also potentially improve the performance of
319
+ Git as a result of that work as well.
320
+
321
+ * If you could get a team of expert developers to work full time on
322
+ something in Git for a full year, what would it be?
323
+
324
+ One thing I know is a pain point for a lot of people is very large
325
+ repositories, whether that's in terms of number or size of files, total
326
+ repository size, or number of references. I've personally had to
327
+ troubleshoot some of those problems, and I'd love to get some additional
328
+ improvements in that area to make Git perform better and use less space.
329
+
330
+ * If you could remove something from Git without worrying about
331
+ backwards compatibility, what would it be?
332
+
333
+ I think I'd remove the dumb HTTP and FTP support. It tends to perform
334
+ really badly, requires per-repository server-side configuration to get
335
+ right, and complicates the smart HTTP protocol code.
336
+
337
+ * What is your favorite Git-related tool/library, outside of Git itself?
338
+
339
+ To be honest, it's zsh's built-in vcs_info functionality. It
340
+ automatically detects what branch I'm on, if I'm in the middle of an
341
+ operation like a rebase or cherry-pick, and whether changes are staged
342
+ or not, as well as providing pretty good completion. It works with a
343
+ wide variety of Git versions and of course has the scope of features
344
+ you'd expect from zsh.
345
+
346
+
287
347
## Releases
288
348
289
349
@@ -301,4 +361,4 @@ __Git tools and sites__
301
361
## Credits
302
362
303
363
This edition of Git Rev News was curated by Christian Couder
< ; <
[email protected] >
> ; and
304
- Thomas Ferris Nicolaisen
< ; < [email protected] > > ; , with help from
XXX .
364
+ Thomas Ferris Nicolaisen
< ; < [email protected] > > ; , with help from
Brian M. Carlson .
0 commit comments