On Tue, 2017-03-21 at 21:55 +0530, Anurag Malyala wrote: > Firstly sorry for the off topic post, but I had to post it here as its > specifically written with this project in mind. > > 1. I've read up about dsadm and the dsconf tools from the website and > have an idea about their working, the question is what types of > administrative tools are going to be made/modified in the project? We are looking mainly at dsconf to be able to alter plugin configurations. DS provides most of it's functionality via plugins, and we need a way to expose this for CLI tools. > > 2. Are there any other tools that'll be involved in the project? No, just dsconf and plugin management. > > 3. Can someone also provide some more detailed info on the project which > extends beyond the description on the ideas page and the dsconf/adm > pages? any link/text will suffice. At the moment that's the most detail, there have been a number of other write ups about this on this list. I think this is a good example: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/PSHQYKSSTXSYSN2RUNLIABZRYYOMNVDR/#BGDSZVUJJMJGVLUKLEKLNBRXQSDEOZR6 > Ah alright, I'm pretty good with Django as well, might be able to help > out there as well after the GSoC has ended. We don't use django in the project sorry, we use python and in the future, flask. :) Hope that helps, -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
