On Mon, 12 Nov 2012 22:28:23 -0700
Tim Flink <tflink(a)redhat.com> wrote:
We've been talking a little bit on an internal list (the
conversation spawned out of something unrelated) about getting the
image build service project from GSoC 2012 to the point where it can
be deployed and used. Since the project doesn't have a mailing list
of its own and it isn't all that unrelated to autoqa, we're moving the
conversation here.
I spent a little bit of time putting git and trac into a somewhat
usable shape and filed a few tickets for some of the work that needs
to be done. I'm going to continue doing so and would welcome any help
in this department
I've been filing more tickets as I think of things that either need to
be fixed or would be nice to have.
I've been organizing the tickets into milestones that break the work up
into four major sets right now.
* Initial deployment - The system is working but may not yet be ready
for other people to use. At this point, the system will mostly
likely be deployed in a non-public location for farther testing
* Semi-public deployment - The system is mostly working but still has
some rough edges. It is enough to deploy on public servers but
access to the system will be restricted until we have a better
handle on how it could potentially be abused and how we limit
resource usage.
* Public Deployment - Full deployment on a public server. It's not
clear if or how we'd restrict access at this point but it could be
as little as FCA completion and FAS account.
* Glorious Future - No specific deadline but stuff that we'd like to
see done even though there are no specific plans to get it done at
this point.
Even with some of this documentation and planning done, there are
still some questions remaining:
- What still needs to be done before the system can be deployed?
- What features would be most useful to add once the base system is
working?
- Are there any concerns about what code already exists or the plan
we're talking about?
Thoughts on this would be much appreciated - as would code and testing
as we get farther along.
Tim