[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Help/sponsorship needed in upstreaming multiple elpa/melpa packages to debian



Welcome Sławomir!

Sean, please see my subjective comments below (with one DFSG point
you'll be interested in):

Sławomir Wójcik <valdaer@gmail.com> writes:

> Hello,
>
> I've recently packaged a lot of emacs elpa/melpa packages for personal 
> use and
> I would like upstream some/most of these to Debian by joining Debian Emacsen
> team on salsa(or if it's not possible then at least getting repositories 
> there).
>
> For now it's a couple packages(one orphaned for adoption, 3 which were 
> RFP for
> rest I've created ITP issues), the repos are on salsa under my 
> user(links below)
> and I've built and uploaded packages to debian mentors.
>
> scala-mode-el/emacs-scala-mode:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766441
> https://salsa.debian.org/Valdaer/emacs-scala-mode
> https://mentors.debian.net/package/emacs-scala-mode
>

Scala-mode is high priority for me, because it has been blocking
"906259: ITP: smartparens -- auto insertion, wrapping, and navigation of
()s, delimiters, and tags for Emacs" for ages.  I've replied to the bug
directly and am willing to review, mentor, and comaintain this one.

> dockerfile-mode:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929291
> https://salsa.debian.org/Valdaer/dockerfile-mode
> https://mentors.debian.net/package/dockerfile-mode
>

Normal.

> docker-compose-mode:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961046
> https://salsa.debian.org/Valdaer/docker-compose-mode
> https://mentors.debian.net/package/docker-compose-mode
>

Normal.

> emacs-ansible:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941246
> https://salsa.debian.org/Valdaer/emacs-ansible
> https://mentors.debian.net/package/emacs-ansible
>

Normal.

> company-ansible:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961047
> https://salsa.debian.org/Valdaer/company-ansible
> https://mentors.debian.net/package/company-ansible
>

Wishlist.

> groovy-emacs-modes:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961048
> https://salsa.debian.org/Valdaer/groovy-emacs-modes
> https://mentors.debian.net/package/groovy-emacs-modes
>

Minor.

> nginx-mode:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961050
> https://salsa.debian.org/Valdaer/nginx-mode
> https://mentors.debian.net/package/nginx-mode
>

High, because nginx is popular and because we have a mode for Apache, so
we ought to have one for nginx.

> all-the-icons.el:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893983
> https://salsa.debian.org/Valdaer/all-the-icons.el
> https://mentors.debian.net/package/all-the-icons-el
>

I do not believe this one meets our high standards, which is why I gave
up on the ITP.  Namely, I investigated the standards of the Font Team,
saw how they were generating fonts, saw this was not possible with
all-the-icons.el.  I believe I also filed some bugs and/or attempted to
contact our Font Team, but sadly never received a reply.  At any rate,
while I think font icons are a cool hack, others have expressed strong
opinions about how font icons are an abomination that should DIAF.

Supposing we did go ahead with uploading this, my concerns are:  1)
trademarked images that are removed from the font-foo packages for DFSG
reasons.  2) Conflicts with the system-wide font-foo packages and
associated bug potential.

I just noticed I never provided my rationale to #893983, so I'm doing
that now.

[snip]
> There is one issue with adopted package scala-mode-el: I've created the 
> repo from
> scratch because package was very outdated compared to upstream and 
> according to
> Addons packaging policy in here: https://wiki.debian.org/EmacsenTeam the 
> package
> name should be changed. I can try to recreate a new repo for it using
> gbp-import-dsc if it's really necessary but frankly I don't see the 
> point/value
> in it. More info in: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766441
>

Are two people's contributions to this package over the course of three
years meaningless?  I've replied to the bug directly and am willing to
review, mentor, and comaintain this one.

[snip]
> Please tell me what's the process for joining the team or at least the
> best way to upstream these packages.

Have you subscribed to this mailing list, and have you requested
membership in our Salsa group?

> Do I need a sponsor for these?(I've read that if the package is
> released through a team it doesn't need a sponsor? Is that true?)  It
> seems to me the most logical thing to do first is to get these package
> repos under https://salsa.debian.org/emacsen-team because all/most
> emacs elpa/melpa packages are there, right?
>

Yes, you will need a sponsor.  When the package is ready, your sponsor
will sign your source package's foo.changes file and upload it to the
archive.  I suspect what you've read about "released through a team" is
that team members may sponsor from git without asking the new
contributor to file a formal RFS (request for sponsorship).

> Sorry for long email.
>

I don't mind, because I prefer comprehensive to laconic ;-)  Brevity is
very important to other Debian members though, and you'll figure out
when to use which :-)


Regards,
Nicholas

Attachment: signature.asc
Description: PGP signature


Reply to: