Package submission process

[Robert Marcano]

On Fri, 2005-10-14 at 17:08 -0400, Jeff Spaleta wrote:
> On 10/14/05, Ian MacGregor <contact at ardchoille.org> wrote:
> >   My name is Ian MacGregor and I have been using Fedora since FC1.
> > Fedora is the best distro available and I thank those involved for its
> > creation. I create packages for apps when I find an app that I like
> > which is not on Fedora Extras or Livna - I enjoy building packages. I
> > have been trying to become a Fedora Extras contributor but I cannot
> > understand the 20-step process here:
> > http://fedoraproject.org/wiki/Extras/Contributors
> 
> 
> Sorry you feel this way. But I think you have greatly over-simplified
> what is actually necessary. In your six step world.. how do you gain
> access to the cvs system? Who creates the cvs account for you? steps
> 8-13 in the Extras process detail exactly how you gain access to the
> cvs system so you can actually import the package. If you dont have
> access to the cvs system... how exactly do you import the package?   I
> don't see you addressing this issue.

It looks than Ian just do not want to do the CVS job, the maintenance of
the RPM in the repository, take care of the compatibility with each
Fedora release. Maybe a Wiki page can be created where people can
register the location of the RPMs they have created in order to give
some help to people looking for something to package and mantain.

> 
> In your six step world.. how do you specify which fedora release you
> want to build a package for in the build system? Fc3? Fc4?
> development? how do you pick which branch to build for?
> Its not so simple as saying "build for all"..dependancies can change
> from Core release to Core release so some packages won't build or work
> correctly on fc3 but may for fc4. Istanbul for example.. only works
> for fedora development because of a dependancy that is only available
> in fedora development right now. Steps 16-19 give the details on how
> to pick which release branches to build for.  I dont see you
> addressing this issue.
> 
> In your six step world.. how do you automate the creation of a
> bugzilla component so users of that package have a place to report
> bugs?  Step 15 details how this is done in the Extras process. It is
> important to make sure that users have a place to file bugs. I don't
> see you addressing this issue.
> 
> None of these issues can just be ignored..there must be a process by
> which people gain cvs access, create release branches and generate a
> bugzilla listing for the package. If you have serious thoughts on how
> to streamline the process in a way that still makes sure those items
> get dealt with feel free to elaborate on your ideas.
> 
> 
> -jef
> 
________________________________________
Robert Marcano
マルカノ・ロバート。にほんごのがくせい。

web: http://www.marcanoonline.com/
gpg --keyserver hkp://pgp.mit.edu/ --recv-key 72A0DCFD