Submission Tool (Re: Submission process (was: Re:Self-Introduction: Michael Tiemann))

[Erik LaBianca]

> 
> Are some people interested in developing such a tool ? I am, for one.
> I think Zope/Plone could do a good job, since it already has a good
> workflow
> system, but it is known by fewer people that PHP for example.
> What we need at the core is mainly a workflow system
(states/transitions),
> a
> system to track dependancies, ... What else ?
> 
> Is anybody interested ? Is there a real need for it ? (I think so)
> 

The discussion could be interesting, although I'm pretty confident I
won't have time to write much code. As far as platforms, I'm not real
sold on zope, just because it's such a heavy framework.
Python/xml/mod_python would be my tools of choice, but that's immaterial
atm.

I think the first thing to do is do decide what we don't like about the
current bugzilla-based system. 

Some of the things I've heard / thought up:

- Easier, automated submission. This is covered with ESR's tool, I
think.

- A place to upload packages for build tests. IMO this is best handled
with an easily duplicated build environment on the client. Think mach.
An official place to upload submitted packages, rather than having to
host them yourself would be good. 

- Easier startup for new packagers / QA people. This is a policy /
documentation / training problem IMO. A new tool isn't going to make
anything better. Bugzilla queries work pretty good when you know the
keywords to use etc.

- Standardized QA procedures. This is what a few of us have been working
on wrt qa-assistant and fedora-startqa. There is lots yet to do but the
tools we have are pretty cool, too.

- Better turn around time. People want to submit a package, and see
results. This is a personnel / policy problem. If we have a secure
autobuilder, we could automatically build submissions and deploy them in
some sort of "bleeding" repository where packagers could get their
builds back immediately. This would keep lots of third party packagers
(ESR?) happy, I bet. Then, when someone takes an interest in the package
and QA's it, it can be moved to stable and it's original publisher
"trusted" to make updates to it.

- Nebulous future of Fedora Extras. Blame redhat. Do I need to bet a
dollar again to get a response from somebody at redhat about this?

I guess in my opinion, most of the systemic problems we have now aren't
solvable programmatically yet. We need to solve a lot of these people /
policy problems before we're in a position to even know what the next
generation system looks like.

Just $0.02.

--erik