Hi all, so I've been thinking about this for a while - we should drop the default set of assistants. There's not enough manpower to put all the features that we like into all assistants that we have in default assistant set (sometimes we don't even have time to maintain the default set to work flawlessly with what's already there). So, let's drop it and leverage the central assistant index (after we actually have it of course). Essentially, DA should be a tool/framework that users will install without assistants. Then they'll get their assistants from the central index with command like "da get someassistant" and then they'll be able to use these assistants. I'm CCing Miro, who is working on the packaging side of things and on the index - Miro, could you sum up your progress and provide us with the links to repos, etc., so that we all know what's going on? Comments/thoughts?
Thanks, Slavek.
Dne 24.2.2014 10:28, Bohuslav Kabrda napsal(a):
I'm CCing Miro, who is working on the packaging side of things and on the index - Miro, could you sum up your progress and provide us with the links to repos, etc., so that we all know what's going on?
Hi, currently there is a "somehow defined standard" for a DevAssistant module - called dap. The standard may still be changed (in backwards incompatible way), depending on the implementation of dap index.
The standard is defined in README of daploader:
https://github.com/hroncok/python-daploader https://pypi.python.org/pypi/daploader
Daploader is a Python module that can load metadata of a dap for further processing. It can perform sanity checks on the metadata and files in the dap. Later, sanity/validity checks for the assistants inside are planed as well (as well as for DevAssistant itself).
Daploader comes with daplint "binary" user/developer can use to check his/hers daps.
The dap index (name is not final) will allow any logged user (via Github or FAS (or potentially other services)) to upload a dap file.
That file will be processed by daploader and if valid, added to the database. Daps can be updated in similar way.
Other users will have the opportunity to browse, search and rate assistants. Reporting of malware and legal issues will be possible as well.
API will be provided (for start, it will be read-only).
The dap index is currently in planing phase only, public pre-alpha with restricted write access will be available soon (probably withing no longer than a month, but no promises).
Several things we've decided with Slávek:
* daps in dap index will not be namespaced (as opposite of Copr or Github) and will have unique names * it will allow comaintainers in similar way as Fedora pkgdb * we want to avoid dependencies on other daps
devassistant@lists.fedoraproject.org
-
Bohuslav Kabrda -
Miro Hrončok