[knc1]

The one thing I would like to be handled by the repository software, rather than a human crew of repo gods, is file level access control.

For the Kindles, we have the situation where there are nearly as many authors as there are packages.

A system where we can implement the concept of file ownership and permissions would be best.

That is:
An 'owner' can update/add/delete/change/whatever their own files;
An 'owner' can create a new entry in the repo;
Otherwise, an 'owner' has only the same access rights as the general public.

Many of our contributors make one-time contributions.
They make something that solves a problem for themselves and want to share it.

Therefore, whatever client is provided or required needs to be simple to use, and generally available.
A client that is packaged to run on Kindles would meet the 'generally available' as far as our community is concerned.

WebDAV does not meet the above requirements as well as a Cloud Service does.
But it does serve the needs of a small, closely cooperative, group of people. A situation that does not require file-level access control, just common sense.

Since with the introduction by Amazon of this new device, we (the cooperating developers here) are not waiting for an end-user Jailbreak to be developed before "porting and testing" our existing packages.

Which is the reason for this thread and the "Release Candidates" repo.
It allows the few Kpw2 owners who have manually jailbroken their device to test and contribute packages for the new device.

Since this is a small and (hopefully) short lived repository -
It seems a good development ground for a more general public package repository.

The "general public" needing only to be able to download the most recent (Cloud Services do version control) package will not need any addition to their Kindle.

They can (or a script can for them) download using wget/curl/web browser - - distribution just looks like and acts like a URL.

Overall, a very interesting problem to be solved.