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

Re: Bug#1004498: RFP: toml11 -- C++11 (or later) header-only toml parser/encoder

Hi Nilesh,

On Tuesday, February 1st, 2022 at 8:27 PM, Nilesh Patra <nilesh@tchncs.de> wrote:

> It is an RFP, just change it to ITP, assign it to yourself and go ahead, you don't have to wait :)

How would I go about doing this? I've seen a few ways to do this (emailing requests@debian.org with a command, for example) but I would like to learn the correct way.

Unfortunately, I already created the ITP, so do you think this would work:
(1) Re-title bug 1004498 to ITP?
(2) Merge my created ITP with 1004498? Close my ITP bug?
(3) Re-title bug to RFS once I finish the packaging

I would appreciate your help in knowing exactly how to do this. At a glance it makes sense but I don't know how to do it within Debian. It's a bit confusing for a new comer. Thank you for your good advice.

> > 

> > It would be great if a Debian Developer on this mailing list would be able to sponsor the package for me

> I/someone else will do so definitely.

Thank you! I will let you know when it is uploaded to mentors.

> > as well as create a repo on the debian med team salsa page.

> I'll add you to the team in a bit.

> However, that package doesn't look like a Medical software so maybe it should go to salsa.debian.org/debian namespace.

> But it's fine if you want it in med team, I wouldn't mind.

After working with the software, I think I would agree. This seems to be a general package and not medical specific. For now, I have hosted the repo on my personal salsa [1]

> > I will file an ITP bug and get started.

> No, rather retitle this bug report to an ITP.

> Thanks for taking this up.

No problem. I am happy to help and enjoy working with the Debian med team.

Lance Lin <lqi254@protonmail.com>
GPG Fingerprint:  8CAD 1250 8EE0 3A41 7223  03EC 7096 F91E D75D 028F

[1] https://salsa.debian.org/linqigang/toml11

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: