Re: What are the rules about submitting beta projects to Debian?
Shawn Sörbom <shawn@sorbom.com> writes:
> I found a project I would like to work on for inclusion into Debian as
> a package, but it is in beta status.
The question to ask about that is: Would the package *now* be stable and
maintainable enough, so that it can be in Debian in its current state?
If the answer – honestly, without wishful thinking – is “no”, then this
is not yet a candidate for upload to Debian.
> Would it be possible to submit it to Sid anyway so that there is a
> clear path for inclusion when it is complete? I ask because I know
> that approval can sometimes take a while.
It's not quite addressing the same issue, but it is closely related:
You shouldn't be generating a first package "just to get it in
Debian". The archive is already well-stocked with poorly-maintained
vanity packages. […]
It is important to remember that an upload isn't a one-off thing
[…]. It's like having a child - a big responsibility.
<URL:https://wiki.debian.org/DebianMentorsFaq#But_why_should_I_waste_time_packaging_if_there.27s_no_guarantee_it.27s_going_to_be_uploaded.3F>
You are free to work on the packaging with an eye toward proposing the
package for Debian, once it is good enough to actually be part of
Debian.
In fact, doing this work correctly will greatly reduce the work that
needs to be done by a prospective sponsor of the package, and thereby
reduce the time before entry into Debian.
Before the work as a whole is ready to be part of Debian and placed in
front of all Debian users, though, do not ask for it to be uploaded.
--
\ “Sane people have an appropriate perspective on the relative |
`\ importance of foodstuffs and human beings. Crazy people can't |
_o__) tell the difference.” —Paul Z. Myers, 2010-04-18 |
Ben Finney
Reply to: