Thank you guys for the positive feedback! I hadn't realized the complexity
of the process originally but your messages got me thinking about it.
We need a simple mechanism that will use potential from the whole world.
Otherwise, if we go directly for a perfect solution, we may never launch it.
Here are the objectives I see and how to accomplish them:
1. How to collect a large number of RPMs
We have to allow everyone to create a free account and to upload RPMs.
2. How to protect download users from bad RPMs
We have to maintain a download count and user comments for each RPM. That
way download users will know what risk they are taking by installing an RPM
for the first time or without a positive comment. Yes, we'll also rely on
the downloaders' good faith to provide good comments.
3. How to protect the host from being flooded
We can have a few people who authorize uploads bigger than a certain size.
To distribute the workload among the authorizers, we can create multiple
brackets, e.g. 1MB, 10MB, 100MB. We can also maintain a quota per user to
avoid flooding through many small files.
All those things are easy to implement through the wiki. If some problems
occur later, we'll act on them as we go. We'll learn how to maintain the
repository while it's growing.
I also thought of recruiting "trusted builders" but that would be a too
formal yet too slow process and the initiative will lose momentum.
Let me know what y'all think.
Thanks,
Zlatko
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
