Summary: | New project for 'realmd' | ||
---|---|---|---|
Product: | freedesktop.org | Reporter: | Stef Walter <stefw> |
Component: | Project Creation Requests | Assignee: | fd.o Admin Massive <sitewranglers> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Stef Walter
2012-06-11 04:35:46 UTC
Hi Stef, I'm a bit reluctant to create this project. Is there buy-in from non-gnome participants? Does this tie in to the system-tools-backends stuff, or could it? Cheers, (In reply to comment #1) > I'm a bit reluctant to create this project. Is there buy-in from non-gnome > participants? Yes. So far there's buy in or positive discussion with Fedora [1], OpenSUSE, Ubuntu, anaconda/firstboot, kickstart, authconfig, LightDM. But I'd like to help integrate with other projects and desktops too. In addition the DBus interfaces are designed in such a way that people can implement all or part of it outside of realmd and are not limited to its default implementation. > Does this tie in to the system-tools-backends stuff, or could > it? realmd has multiple ways to connect to the realms. One of them is Winbind. In theory the Winbind-realmd code could theoretically use SMBConfig to read/write the samba config ... if SMBConfig was greatly extended to support many more attributes. realmd does far more than just configure config files. It implements discovery, keytab setup, and manages package installation, many other bits. If refused hosting here, I guess I would go for gitorious.org. Many of the contributors to realmd are those who would contribute to other FDO projects. So living on gitorious.org would fragment the bug reporting, accounts, and other things that contributors to realmd are familiar with. realmd is a real project that will be shipped and integrated into the default install (with multiple participants) in the next version(s) of distros. [1] https://fedoraproject.org/wiki/Features/ActiveDirectory Moving to NEW so I see it on the next sweep. Thanks Tollef. Is there any chance you would have time to do this before GUADEC? I'm giving a talk about this stuff there, and it would really be nice if we had the hosting for realmd worked out. In addition, I'd like to request a second repository for this. This is a dependency of realmd. I've been asked to split this out from the main project so others can use it: Repository name: 'adcli' Repository Description: Library of routines for joining a machine to Active Directory (without samba) and managing machine accounts there. Will probably expand to cover other AD related tasks as well. Should we have a different project name? Perhaps 'Directory Support' with realmd and adcli under it? If you have suggestions on how you prefer things to be organized, I'd be happy to adapt to them. And lastly, if there's anything I can do to help get this done, let me know. I realize that all this admin stuff takes time, so if there's anything I can do to make life easier for you, or return the favor, I'd be happy to. Project created. File upload space at /srv/www.freedesktop.org/www/software/realmd with the pretty obviously corresponding URL. Both git repos and bugzilla set up, please test. Enjoy GUADEC, and sorry for the delay. Thanks :) Any idea why realmd and adcli don't show up here: http://cgit.freedesktop.org/ I've pushed stuff to both of those repositories, and waited several hours? Do I have to wait until tomorrow? In addition: $ git clone git://git.freedesktop.org/realmd/adcli.git Cloning into 'adcli'... fatal: The remote end hung up unexpectedly (In reply to comment #6) > Any idea why realmd and adcli don't show up here: > > http://cgit.freedesktop.org/ Fixed. > In addition: > > $ git clone git://git.freedesktop.org/realmd/adcli.git > Cloning into 'adcli'... > fatal: The remote end hung up unexpectedly Try anongit.fdo (as per cgit.fdo :-) Thanks. All working now. Much appreciated. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.