Independent developers contributing packages

[Lucas Albers]

Can someone explain how this new redhat project works with independent
developers?

Let's pick a really cool package that currently exists in redhat.
Severn currently includes spamasssassin 2.55.
Those crazy SA guys are coding up 2.6. When they release 2.6 they usually
release a rpm package.
So one of the SA developers will contact redhat and tell them to include
their rpm in the severn version of redhat?

Does this add potential security problems?
If an independent developer get's their machine hacked and their source
trojaned, will that package sneak into the redhat release?
Are independent developers responsible for security updates?
How does QA work with package developers?

This should speed up the dev cycle.

Does this have less QA built into the package release cycle?

I could not find any documentation concerning this subject.

It appears a developer has to submit their package as a bugzilla entry to
be included in the base release?

In Summary:
What are the steps for an independent developer to get their package into
redhat?

--Luke

[Michael Schwendt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 23 Jul 2003 00:37:54 -0600 (MDT), Lucas Albers wrote:

>  Can someone explain how this new redhat project works with
> independent
>  developers? 
- -snip-

Not to sound like a nerd, but while this mailing-lists deals with
the Red Hat Linux Beta version, the rhl-devel-list would be much
more appropriate for your question:

  Rhl-devel-list(a)redhat.com
  http://www.redhat.com/mailman/listinfo/rhl-devel-list

List-Help: <mailto:[e-mail]?subject=help>
List-Post: <mailto:[e-mail]>
List-Subscribe: <http://www.redhat.com/mailman/listinfo/rhl-devel-list>;,
<mailto:[e-mail]?subject=subscribe>
List-Id: For developers, developers, developers <rhl-devel-list.redhat.com>
List-Unsubscribe: <http://www.redhat.com/mailman/listinfo/rhl-devel-list>;,
<mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://www.redhat.com/archives/rhl-devel-list/>

- -- 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
>
> iD8DBQE/HjiQ0iMVcrivHFQRAs8SAJ9YyaCPhKsHT+bnpAaedBbGcse/9ACfaC5c
> DFnvdS/i5vjWo2maVPeROlc=
> =0Nap
> -----END PGP SIGNATURE-----

[Phillip Compton]

On Wed, 2003-07-23 at 02:37, Lucas Albers wrote:

>  In Summary:
>  What are the steps for an independent developer to get their package into
>  redhat? 
I believe these steps are still being worked out RedHat. 

At Fedora, the procedures are documented here:
http://www.fedora.us/wiki/PackageSubmissionQAPolicy

Personally, I think these are a good starting point when considering the
future submission policies of RHLP.


Phil

[Jos Vos]

>  Let's pick a really cool package that currently exists in
> redhat.
>  Severn currently includes spamasssassin 2.55.
>  Those crazy SA guys are coding up 2.6. When they release 2.6 they usually
>  release a rpm package.
>  So one of the SA developers will contact redhat and tell them to include
>  their rpm in the severn version of redhat? 
I can't give an authorative answer, but this is not the way it was
meant to work, AFAIK.  An external person should be *responsible*
for a package and has to comply with RH guidelines etc.  In my
experience, "standard" rpm's released by projects are in general
much different w.r.t. packaging style.

So, "contact redhat and tell them to include their rpm in ..." does
sound a bit different, as it doesn't sound like actively working with
RH standards and guidelines and/or continous responsiblity etc. (but
maybe you thought of something else).

-- 
--    Jos Vos <jos(a)xos.nl&gt;
--    X/OS Experts in Open Systems BV   |   Phone: [phone]
--    Amsterdam, The Netherlands        |     Fax: [phone]