You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rev_news/drafts/edition-54.md
+78-22Lines changed: 78 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,39 +83,95 @@ This edition covers what happened during the month of July 2019.
83
83
84
84
* Who are you and what do you do?
85
85
86
-
My name is Jean-Noël Avila, father of three daughters and husband of an incredibly comprehensive wife. I graduated a long time ago from a french engineering school, with a speciality in signal processing, not really in computer science .
87
-
88
-
Professionally, I work in the R&D team of a [small company](https://www.scantech.com) that makes industrial online measurement systems, and guess what, we're using Git as an ubiquitous revision control system (software, documentation); my colleagues know who they should call for any issue. Sadly though, I don't work on Git.
86
+
My name is Jean-Noël Avila, father of three daughters and husband of
87
+
an incredibly comprehensive wife. I graduated a long time ago from a
88
+
french engineering school, with a speciality in signal processing,
89
+
not really in computer science .
90
+
91
+
Professionally, I work in the R&D team of a
92
+
[small company](https://www.scantech.com) that makes industrial
93
+
online measurement systems, and guess what, we're using Git as an
94
+
ubiquitous revision control system (software, documentation); my
95
+
colleagues know who they should call for any issue. Sadly though, I
96
+
don't work on Git.
89
97
90
98
* What would you name your most important contribution to Git?
91
99
92
-
For the Git project itself, my most important and only contribution has been to deliver the french localization of the software since... 2013 (gasp!) and occasionally propose some patches to fix internationalization issues.
100
+
For the Git project itself, my most important and only contribution
101
+
has been to deliver the french localization of the software
102
+
since... 2013 (gasp!) and occasionally propose some patches to fix
103
+
internationalization issues.
93
104
94
-
At the beginning, I proposed some patches to fix glob-pattern matching in the `.gitignore` file, but even if it fixed the issue, it turned out later that the patch had introduced a performance regression. So I chose to stick to a less harmful activity in the community (although bad translation can be quite harmful).
105
+
At the beginning, I proposed some patches to fix glob-pattern
106
+
matching in the `.gitignore` file, but even if it fixed the issue,
107
+
it turned out later that the patch had introduced a performance
108
+
regression. So I chose to stick to a less harmful activity in the
109
+
community (although bad translation can be quite harmful).
95
110
96
-
In the Git ecosystem more generally, I've been working on translating the Progit book to French and managing with Peff and Pedro (@pedrorijo91) the publishing of the translations of the book on http://git-scm.com. So, to sum it up, not working on the core, but on the public interfaces of the project.
111
+
In the Git ecosystem more generally, I've been working on
112
+
translating the Progit book to French and managing with Peff and
113
+
Pedro (@pedrorijo91) the publishing of the translations of the book
114
+
on http://git-scm.com. So, to sum it up, not working on the core,
115
+
but on the public interfaces of the project.
97
116
98
117
* What are you doing on the Git project these days, and why?
99
118
100
-
Following the path of localization, what is a localized application worth if the documentation is still an impediment? In this idea, at the beginning of this year, I've started an effort to translate the manual pages in French and to propose the translation framework put in place for this purpose to other languages.
101
-
102
-
So far, only two languages have translated content, but I expect to have some more soon. The pages are already available at http://git-scm.com/docs/ . What is still missing is the packaging for other distributions of Git. Maybe when we have more content to provide.
103
-
104
-
* If you could get a team of expert developers to work full time on something in Git for a full year, what would it be?
105
-
106
-
Functionally, we've been bitten by some wrong merges of concurrent branches, and I wish Git could have some knowledge in patch algebra to better handle these corner cases. I know that it would be quite orthogonal to the present design, but even just detecting and showing warnings that something nasty is happening would prevent surprises (to say the least) of the users in complex histories.
107
-
108
-
From a translator's stand point, a project that would not require a big expertise while still being useful would be to introduce rules and factorize internationalization. This part of Git is still the wild west by some aspects with a lot of freedom left to developers to choose their own formatting. A sizeable part of these strings are almost identical: with or without an ending period, with quoted or unquoted `%s`, with uppercase or not. Some strings are very similar: "foo and bar are mutually exclusive", and so on. In the end, the number of segments to translate in Git amounts to 4674 for v2.23.0, which basically bars the entry to new translations.
109
-
110
-
As an aside, providing a `po` file for core strings and another one for less used strings would also help kickstart translations by focusing on more productive work for translators of new languages. I understand this kind of task would be Sisyphos' work, but that would really help the community grow by giving access to Git to users less educated in computer science.
111
-
112
-
* If you could remove something from Git without worrying about backwards compatibility, what would it be?
113
-
114
-
Translating Git and the manpages gives a good overview of what's available and what is being introduced. So far, I haven't experienced anything strinkingly bad about a particular feature. At the limit, I would make rebasing require a more advanced knowledge of Git's internals by not providing such an easy way to shoot in one's foot.
119
+
Following the path of localization, what is a localized application
120
+
worth if the documentation is still an impediment? In this idea, at
121
+
the beginning of this year, I've started an effort to translate the
122
+
manual pages in French and to propose the translation framework put
123
+
in place for this purpose to other languages.
124
+
125
+
So far, only two languages have translated content, but I expect to
126
+
have some more soon. The pages are already available at
127
+
http://git-scm.com/docs/ . What is still missing is the packaging
128
+
for other distributions of Git. Maybe when we have more content to
129
+
provide.
130
+
131
+
* If you could get a team of expert developers to work full time on
132
+
something in Git for a full year, what would it be?
133
+
134
+
Functionally, we've been bitten by some wrong merges of concurrent
135
+
branches, and I wish Git could have some knowledge in patch algebra
136
+
to better handle these corner cases. I know that it would be quite
137
+
orthogonal to the present design, but even just detecting and
138
+
showing warnings that something nasty is happening would prevent
139
+
surprises (to say the least) of the users in complex histories.
140
+
141
+
From a translator's stand point, a project that would not require a
142
+
big expertise while still being useful would be to introduce rules
143
+
and factorize internationalization. This part of Git is still the
144
+
wild west by some aspects with a lot of freedom left to developers
145
+
to choose their own formatting. A sizeable part of these strings are
146
+
almost identical: with or without an ending period, with quoted or
147
+
unquoted `%s`, with uppercase or not. Some strings are very similar:
148
+
"foo and bar are mutually exclusive", and so on. In the end, the
149
+
number of segments to translate in Git amounts to 4674 for v2.23.0,
150
+
which basically bars the entry to new translations.
151
+
152
+
As an aside, providing a `po` file for core strings and another one
153
+
for less used strings would also help kickstart translations by
154
+
focusing on more productive work for translators of new languages. I
155
+
understand this kind of task would be Sisyphos' work, but that would
156
+
really help the community grow by giving access to Git to users less
157
+
educated in computer science.
158
+
159
+
* If you could remove something from Git without worrying about
160
+
backwards compatibility, what would it be?
161
+
162
+
Translating Git and the manpages gives a good overview of what's
163
+
available and what is being introduced. So far, I haven't
164
+
experienced anything strinkingly bad about a particular feature. At
165
+
the limit, I would make rebasing require a more advanced knowledge
166
+
of Git's internals by not providing such an easy way to shoot in
167
+
one's foot.
115
168
116
169
* What is your favorite Git-related tool/library, outside of Git itself?
117
170
118
-
In fact, in my daily work with Git, I don't use the command line that much. I'm an emacs fan, and Magit is really a miraculous tool when it comes to interacting with a Git repository from my favorite editor.
171
+
In fact, in my daily work with Git, I don't use the command line
172
+
that much. I'm an emacs fan, and Magit is really a miraculous tool
173
+
when it comes to interacting with a Git repository from my favorite
0 commit comments