Dear subscribers, recently, I packaged `markdownlint`,[1] a syntax checker for markdown implemented in Ruby, for Debian as `ruby-mdl`. Thanks to a sponsor, there was an initial upload to Debian's package tracker,[2] too. A new upload (source-only upload) was prepared[3] and as Bastian Germann suggests, it possibly were better to move the relevant data from
https://salsa.debian.org/nbehrnd/ruby-mdl to an address like e.g., https://salsa.debian.org/ruby-team/ruby-mdl With the manual about packaging Ruby gems for Debian[4] and gem2deb,[5] I request advice how to proceed for such an adjustment, i.e. a merge into your git repository? Or, does it suffice to share the knowledge with you that there is a .deb `ruby-mdl` to prevent an other of you prepares a .deb of this name, and then to continue hosting the relevant data in the salsa instance under my name? In retrospect, there equally are two questions: * Because `ruby-mdl` is my first contribution leading to a .deb on Debian, I'm an uploader. Does assembling the necessary data equate that a maintainer of this .deb, i.e. should I/should I equally adjust this entry for the Debian package tracker? * GitHub's project page about `markdownlint` counts 52 contributors to `markdownlint`. To extract their names and the first year of contribution, I wrote two small scripts to assist the adjustment of file `/debian/copyright`. Now, though `gem2deb` creates the three git branches of `master`, `pristine-tar`, and `upstream`, does the creation of an extra branch interfere badly with the intended layout of Ruby gem packages for Debian? Because it does not change the source code of the Ruby code (compared to what `gem2deb` fetches from the rubygems database) it does not appear like a bug fix `upstream` should include before merging the results into `master`. On the other hand, I would welcome if the repository to package `markdownlint` as `ruby-mdl` for Debian would include these two short extra codes (e.g., an other user might be interested to build the package when `markdownlint` on rubygems has been updated). What would be your advise on this point? With regards, Norwid Behrnd [1] https://github.com/markdownlint/markdownlint/ [2] https://tracker.debian.org/pkg/ruby-mdl [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029033 [4] https://wiki.debian.org/Teams/Ruby/Packaging#Packaging_new_gems_from_scratch [4]https://wiki.debian.org/Teams/Ruby/Packaging/gem2deb
