English sottotitoli

← meetings-archive.debian.net/.../Newcomer_experience_in_debian_packaging_by_Sindhu_Sundar.webm

Ottieni il codice di inserimento
1 Language

Mostrare Revisione 1 creata 07/22/2016 da DrZaius.

  1. Hi, my name is Sindhu
  2. and I'm gonna talk about
  3. "Newcomer experience in Debian packaging"
  4. "Who? Where? Why?"
  5. From 2006 to 2009
  6. were my first few years using
  7. GNU/Linux systems and
  8. I was majorly just distro hopping
  9. kind of get the latest desktop and ??? everyone of them
  10. and when I couldn't find the latest
  11. packages I would install
  12. things from the testing repositories
  13. and it didn't make much of a difference, you know?
  14. I would have the latest packages
  15. and I soon learnt that testing and
  16. devel package repositories where
  17. really testing and that would be unstable and
  18. break my system.
  19. So I went back to fix my system
  20. and for the next three years
  21. this is what I was doing
  22. you know... ???
  23. Later I was looking for a career change
  24. and a friend came along to teach me how to make a patch
  25. this is about the time when Outreach Program for Women
  26. was announced and
  27. I became a Documentation Intern for GNOME
  28. and I also went on to Google Summer of Code internship
  29. with Gnome I contributed code to gitg project
  30. and I'm now a mentor for Documentation interns
  31. at the Outreach Program.
  32. "What?"
  33. My first failed attempt at packaging
  34. was when I tried to package a
  35. a ??? called cnetworkmanager
  36. which is a command line
  37. application to access network manager
  38. and looking at the ??? documentation then
  39. pretty overwhelming and
  40. in retrospect I think that
  41. I abandoned my efforts quickly
  42. because I wasn't experienced in using GNU/Linux systems
  43. and because there was a lot of documentation, truly.
  44. My second failed attempt was as recent as last year
  45. and I just wanted to package something for Fedora
  46. and looking at the specs files and so many things to
  47. do about it, I was quick to just dismiss it.
  48. Other commitments came along
  49. but this was a ???
  50. "So then?"
  51. My first job ??? two years
  52. when I was contributing to GNOME, was
  53. not just about learning for myself
  54. but also teaching other newcomers
  55. and helping people get into the community
  56. Soon I was speaking to many newcomers on mailing lists
  57. and in person teaching at local colleges
  58. and events on how to contribute to GNOME
  59. and subliminally
  60. you know, you tend to summarise in your head
  61. telling the same things to many different people
  62. It's just really four steps to
  63. start, to really start contributing to any project.
  64. And that would be to go to the official website and
  65. read the pages about how to help Project X
  66. or "Get Involved" or "Help us" pages
  67. and next step would be to set up the developement environment
  68. and do your ground work
  69. and find a willing mentor
  70. who will be able to take you from there.
  71. So, where's Debian in the picture?
  72. "Enter Debian"
  73. I have used Ubuntu extensively
  74. and I knew my way around apt-get
  75. but this is all I knew about Debian
  76. and Debian based distributions
  77. but learning about Debian MiniConf
  78. made me realise that this is my opportunity to
  79. change the memories I had about failing
  80. something and it would be a great way to get a headstart
  81. in such vibrant community
  82. and start packaging.
  83. "Choosing your tools"
  84. Choosing your tools.
  85. My first step to contributing to
  86. Debian would be to get Debian!
  87. I was an Arch Linux user and
  88. there are a couple of things to keep in mind when you
  89. try to contribute to a distribution.
  90. For example, the time it takes to set up
  91. and the time it takes to
  92. transfer your work over this new distribution
  93. and the disk space it would require
  94. and whether or not your device...
  95. ...you can set up this distribution easily on your device
  96. Not to mention the bandwidth required for
  97. the Internet bandwidth required for
  98. downloading and upgrading packages.
  99. In GNOME, to make this transition easier
  100. to have this quickstart with newcomers, we have
  101. a virtual machine image preloaded
  102. with our build system, so they can try it out and setup
  103. they don't have to setup stuff from scratch
  104. and when they're confident they can go set it up on disk
  105. Debian didn't offer me any
  106. such - you know - instant noodle like
  107. VM image but, it wasn't hard to set up
  108. so I went about using another fast project called Vagrant
  109. and I made a Debian box
  110. which I pre-filled with packaging tools
  111. ???
  112. I also learned about another project called Docker
  113. which is an even more elegant solution
  114. to have newcomers try out different environments in a GNU/Linux system.
  115. So what happened after this?
  116. "So..."
  117. My first experience when I was contributing to GNOME
  118. was trying to understand how ???
  119. and after learning how to make a patch I realized
  120. the meaning of the word "upstream", you know,
  121. realizing concepts about stable and unstable stages
  122. releases, and what kind of ???
  123. and all this information was pieced together
  124. over time of reading GNOME wiki pages
  125. including the content of GNOME Love,
  126. and interacting with my mentor
  127. and also from this knowledge I had
  128. from previously distro hopping
  129. I also made a upstream release myself
  130. and become the maintainer of
  131. one of the projects I was contributing
  132. a user documentation tool.
  133. So, doing all of this peripheral work
  134. made me a nice picture, a visualization in my head
  135. of how software development in facts takes place.
  136. So when I started with Debian
  137. I navigated to the Debian website
  138. read the introductory page about packaging
  139. I went to the Developer's Corner
  140. and the landing page for Documentation
  141. and I clicked on everything that was related to packagin.
  142. Since I knew that GNOME had a wiki
  143. it was likely that Debian also maintained a wiki
  144. and there was also a really helpful Teams page
  145. which made me realize
  146. how Debian is separated in terms of
  147. division of labour
  148. And I started doing all the things
  149. that were required for packaging
  150. and I kind of get stuck.
  151. "Hello, I am..."
  152. In my excitement of wanting to generate a deb file
  153. and at this point thinking that this was
  154. all that was to packaging
  155. I went through #debian-devel, #debian-gnome, #debian-mentors
  156. and #debian-women
  157. to told them that I was stuck because
  158. my deb file was empty
  159. and lot of them suggested in good intentions
  160. they suggested do this, do that but
  161. nothing made sense because...
  162. I had no idea what they were talking about
  163. So even though I was talking in English
  164. I was not able to communicate
  165. and it was quite frustrating because
  166. they did not know where I was coming from.
  167. So I went back to
  168. #debian-bcn2014 and Ana
  169. who first helped me put together
  170. my talk for this conference
  171. said "calm down and
  172. I'm gonna lead you through the steps"
  173. and she went by this ideology of learn
  174. to package first, and then making the package
  175. so this was fine
  176. this suited me fine because that's the way I learnt.
  177. I guess the most important thing that
  178. we can take away from this episode
  179. is to be a good mentor, you have to
  180. assume a very little baseline
  181. knowledge with the person ???
  182. be clear with instructions
  183. and don't expect them to have
  184. done XYZ
  185. because they may not
  186. know about it, but they may know ABC
  187. Ask if they have done XYZ
  188. and - you know - take it from there.
  189. So, what exactly did I do?
  190. "Actual work"
  191. I'm currently packaging GNOME Code Assistance
  192. and Gedit Code Assistance modules
  193. for GNOME.
  194. The former gives code assistance services for GNOME
  195. Basically if you have an IDE
  196. or any text editor
  197. in GNOME that you want to
  198. putting syntax error checking features
  199. for a particular language,
  200. then this is the package that does it.
  201. While the latter is a package
  202. that emits the dbus signal
  203. in Gedit text editor
  204. back to GNOME Code Assistance
  205. so when the correct backend is enabled
  206. this two packages interact with each other
  207. to give syntax validation features
  208. So far these are the things I've done
  209. I've gotten past in generating
  210. a working deb file
  211. but it can be improved
  212. and I really understood
  213. what dependencies meant.
  214. And that how autotools work
  215. and I started seen
  216. I really started paying attention
  217. and ??? how autotools
  218. are related to configuration files
  219. and I also patched our own build system called jhbuild
  220. to build these two modules in GNOME
  221. My next immediate concerns
  222. are getting the upstream author to
  223. bring it to a...
  224. usable position, because it works for some people
  225. and for some it doesn't: it works for the upstream author
  226. it works for him...
  227. and Ana suggested that I
  228. update a package
  229. that it is in QA and I think
  230. that's a small contribution
  231. for me to start from and then she
  232. sponsor it, so that's my next task.
  233. I want to document it
  234. for end users
  235. So one of the bugs that ??? against all of these packages are
  236. that there is no user documention so nobody knows
  237. how to use it, it's all magic
  238. So, packaging has also made
  239. these things my priority
  240. and I have few ideas
  241. that come from GNOME love
  242. A few ideas I feel
  243. Debian can benefit
  244. and to have a greater newcomers engage in the community
  245. or having the concept of GNOME Love like
  246. in packaging
  247. For example, tagging packages
  248. that are orphaned or are in QA
  249. that can be updated by anyone and this would make a great
  250. beginner contribution
  251. Specifically having a tutorial to do this
  252. would be nice
  253. And wiki pages about
  254. packaging that could reutilize videos
  255. and BoF sessions from previous Debian conferences
  256. For example there was a wiki page about
  257. Debtags, which uses a 2007 video to
  258. talk about what Debtags is, and what it does
  259. and there are some great videos
  260. I found in the archives of Debian conferences
  261. the first one is "Documentation in Debian"
  262. another one is "How contribute and get involved"
  263. and there's another great video about how other FLOSS communities mentor
  264. and the last idea is
  265. it's some ??? an idea is something ???
  266. Vincent Untz conducted
  267. an interesting session in FOSDEM 2010
  268. where they discussed what would be a good move
  269. to make life of packagers downstream easier
  270. So from the point of view of GNOME
  271. what should we be doing in order to make their life easier
  272. A reverse session
  273. ??? developers on how to say in Debian
  274. packaging and you know, make them interact
  275. and learn how packaging...
  276. how upstream changes affect packaging
  277. and what they can or cannot do
  278. to make our life easier would be great
  279. And a newcomers IRC channel or mailing list specifically
  280. for dealing with newcomers
  281. issues would be great
  282. and even local packaging workshops,
  283. BoFs, and parties
  284. if this hasn't already been done it would be nice.
  285. And all the links to the resources I'm talking about
  286. are there in my blogpost
  287. you can go it's sindhus.bitbucket.org
  288. I'd like to thank Tassia and Ana for having
  289. giving me this opportunity to present remotely, thank you very much!
  290. "Thank you"
  291. Thank you for listening so far
  292. and I hope I've given some interesting insights on how
  293. we make newcomers experience
  294. easy in GNOME and I hope
  295. to stick around in the Debian community and meet
  296. you all in the next Debian conference
  297. Thank you so much Tassia and Ana
  298. for helping me put this together
  299. and I hope to see you soon!
  300. "Thank you"
  301. Thank you so much for listening this far
  302. it's a shame I cannot be there
  303. in person to say this
  304. Thank you Tassia and Ana for
  305. helping me put this together
  306. I hope to stay involved in Debian
  307. in the packaging scene, contributing to it
  308. and all the things that I've spoken about
  309. in this talk is available on my blog
  310. it's sindhus.bitbucket.org
  311. So if you have any feedback, please do email me
  312. it will be good to hear from you
  313. I hope you guys enjoy your time at this conference, thank you bye bye!