Dear Maintainer,

I am looking for a sponsor for my package "noct":

 * Package name     : noct
   Version          : 1.0.16
   Upstream contact : Awe Morris <awe@noctvm.io>
 * URL              : https://github.com/awemorris/NoctLang
 * License          : zlib
 * Vcs              : https://salsa.debian.org/awemorris/noct/
   Section          : devel

The source builds the following binary packages:

  noct - tiny programming language for sandboxed scripting
  libnoct1 - core library for the Noct programming language
  libnoctapi1 - standard API library for the Noct programming language
  libnoct-dev -  development headers for the Noct programming language

To access further information about this package, please visit the following URL:

https://mentors.debian.net/package/hello/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/n/noct/noct_1.0.16-1.dsc

Changes since the last upload:

 - Initial Upload (Closes: #1135753)

[What led up to the situation?]

During the packaging review of "suika3" (ITP #1133308) on mentors.debian.net,
reviewers suggested that the embedded scripting runtime should be split into
an independent source package instead of being bundled within the game engine.

[What exactly did you do that was effective?]

I separated Noct from the suika3 source package and prepared it as an
independent Debian package with its own shared library, development package,
symbols tracking, autopkgtest integration, and standalone build system support.

I also cleaned up the packaging to follow Debian policy recommendations,
including multiarch-compatible library packaging, lintian fixes, and proper
dependency metadata.

[What was the outcome of this action?]

The package was reviewed on mentors.debian.net and received positive feedback
from reviewers, who indicated that the package quality was sufficient to
proceed with an RFS submission.

The separation also made the scripting runtime reusable by other applications
independently of suika3.

[What outcome did you expect instead?]

I initially expected Noct to remain an internal component of suika3.
However, the review process clarified that packaging it separately would better
align with Debian policy and improve reusability for the wider ecosystem.

Regards,
--
  Awe Morris