[00:30] <crimsun> stgraber: please try to reproduce issues with latest PA (1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu1) first
[00:31] <crimsun> sbalneav: interesting ideas all (just read backscroll). I do think books, maps, alphabets are interesting (and also am concerned with my or other suggestions perhaps walking the line of being "Western hemisphere-centric")
[13:20] <dgroos> Good Morning
[13:21] <dgroos> I'm trying to run a piece of software, a beta version that is a port of a commercial product to ubuntu--still commercial I think though not sure.
[13:23] <dgroos> This software allows you to connect an interface box with all kinds of probes eg temp, air pressure, O2 and CO2 concentration, heart rate monitor, force, acceleration, and many dozens more, to a computer.
[13:24] <dgroos> It allows students to easily design data collection and run it.  Very cool.  I'd like to run it with LTSP, but get this error:
[13:25] <dgroos> dgroos@gcos2:~$ loggerpro
[13:25] <dgroos> main.cc main(156) : Ubuntu 9.04: 2.6.28-17-generic
[13:25] <dgroos> Working dir /home/dgroos
[13:25] <dgroos> Top Level Folder: '/usr/local/share/LoggerPro/'
[13:25] <dgroos> Our runtime support folder is: /tmp/VST_Support_rLmpwh/
[13:25] <dgroos> terminate called after throwing an instance of 'std::logic_error'
[13:25] <dgroos>   what():  basic_string::_S_construct NULL not valid
[13:25] <dgroos> Aborted
[13:25] <dgroos> Is there some kernal of wisdom ;) I could pass on to the developers to make it work on thin clients?
[13:26] <dgroos> Should I ask this at #ltsp instead?
[13:33] <highvoltage> dgroos: I guess I would run it through strace, it might give them some useful feedback
[13:35] <dgroos> highvoltage: thanks, I'll google that and give it a try.
[13:38] <highvoltage> dgroos: you basically just install strace and type strace before the command, it will then spew lots and lots of information you could use for debugging
[13:40] <dgroos> Cool, I'm just seeing that (your explanation was understandable as opposed to this line from the wiki: "strace -Ff -tt <program> <arguments> 2>&1 | tee strace-<program>.log" :)
[13:41]  * stgraber waves
[13:43] <dgroos> I know there's a way to get the output to print to a file and I need to do that since the output is way more than can be shown in a terminal window.  How do I do this?
[13:43] <dgroos> Good (early) morning stgraber
[13:43] <moldy> dgroos: some_command > some_file
[13:44] <dgroos> thanks moldy!
[13:44] <moldy> np
[13:47] <dgroos> moldy: I only get this in the file using the command you mentioned:
[13:47] <dgroos> Working dir /home/dgroos
[13:47] <dgroos> Top Level Folder: '/usr/local/share/LoggerPro/'
[13:47] <dgroos> Our runtime support folder is: /tmp/VST_Support_Wyt4AP/
[13:48] <moldy> dgroos: sorry, try this: some_command 2>&1 > some_file
[13:49] <moldy> dgroos: no, sorry. this way: some_command > some_file 2>&1
[13:49] <moldy> dgroos: otherwise, you only get standard output in the file... you probably want standard error output, too
[13:51] <dgroos> that did the trick! :)
[13:52] <moldy> dgroos: also see http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-3.html for background information
[14:19] <mhall119|work> morning
[14:45] <sbalneav> Morning all
[14:46] <mhall119|work> morning
[14:46] <highvoltage> morning mhall119|work, sbalneav
[14:48] <alkisg> Morning mhall119|work, sbalneav, highvoltage :)
[14:50] <highvoltage> morning alkisg
[16:12] <LaserJock> alkisg: yo
[16:12] <alkisg> Hi LaserJock :)
[16:12] <LaserJock> one sec, brb
[16:15] <sbalneav> alkisg: put on your users-admin thinking cap
[16:15] <alkisg> Wow
[16:15]  * alkisg puts a donkey hat whatsyamacallit
[16:15] <highvoltage> omg, it's LaserJock!
[16:15] <mhall119|work> the Dr. is in
[16:16] <sbalneav> alkisg: have you looked at the new users-admin tool in Lucid yet?
[16:16] <alkisg> sbalneav: yes, it looks like someone put some work on it
[16:16] <sbalneav> right.
[16:17] <sbalneav> In your professional opinion as an educator, is it useful?
[16:17] <sbalneav> And, what do we want to do about bulk import?
[16:17] <highvoltage> sbalneav: does it have bulk import?
[16:17] <sbalneav> No
[16:17] <alkisg> Well, for a school, where one wants to manage a lot of students, the previous list-type-interface was much better
[16:18] <alkisg> (it couldn't even sort by columns, but you know, the idea)
[16:18] <sbalneav> alkisg: laserjock came up with a patch for the sorting
[16:18] <sbalneav> then discovered the tool changed completely
[16:18] <alkisg> I think the current users-admin is oriented towards desktop systems, with only a handful of users
[16:18] <sbalneav> right.
[16:19] <sbalneav> So, we have a few choices.
[16:19] <highvoltage> it would be nice if you could list by group
[16:19] <highvoltage> or in a school environment, by classroom or grade
[16:19] <alkisg> Right. kuser does a lot of those things
[16:20] <highvoltage> I just looked at the new users-admin and it seems to have the same old problems in terms of usability
[16:20] <sbalneav> highvoltage: How do you store classroom/grade info?  In the gecos field?
[16:20] <alkisg> Or even fedora's users management GUI (but that's also to be abandoned)
[16:21] <sbalneav> So, here's the question.  Do we:
[16:22] <sbalneav> 1) try to add functionality to users-admin? (probably hard)
[16:22] <sbalneav> 2) ship something that's closer (kusers)
[16:22] <sbalneav> 3) Write our own tool that's uniquely designed for managing classrooms?
[16:23] <alkisg> 1 => yeah, and a python-based tool would also be more maintainable
[16:23] <alkisg> 2 => well we could use that for Lucid, as I don't think we'll have time for (3),
[16:24] <alkisg> 3 => you're de man!
[16:24] <sbalneav> We could distribute 3 via the edubuntu-ppa's after release.
[16:24] <alkisg> If (3) also allowed plugins (=actions) for the selected users, it would be much more helpfull for classrooms
[16:25] <sbalneav> alkisg: ok, you're the sole educator among us.
[16:25] <sbalneav> Could I ask you to create a wiki page with all the design features you'd like to see for a user management tool?
[16:26] <sbalneav> I'd be willing to take this on, and solve it for us once and for all.
[16:26] <alkisg> sbalneav: sure, but the plugins I'll mention there will only scratch the surface. If you did the plugin system, then the teachers themselves would come up with the needed plugins.
[16:27] <sbalneav> alkisg: sure, but I need to know what kind of things you want the plugin system to accomplish
[16:27] <sbalneav> scratch that
[16:27] <alkisg> Sure
[16:27] <sbalneav> interface of the plugin system
[16:27] <alkisg> sbalneav: do we want this to be LTSP oriented?
[16:27] <sbalneav> i.e. what do you want passed to the plugin?  I.e. userid, home dir. etc.
[16:28] <sbalneav> alkisg: well, for now, lets just assume it's a general user admin tool.
[16:28] <alkisg> I mean, suppose a teacher has 12 standalone workstations with students on them. What does users admin do for him?
[16:28] <sbalneav> if there's ltsp specific things, maybe we handle those with plugins.
[16:28] <sbalneav> alkisg: handle ldap maybe
[16:28] <sbalneav> or pam-sshauth
[16:28] <alkisg> Right, or pamssh... that
[16:29] <alkisg> Could the plugin show him who's logged on?
[16:29]  * LaserJock is back
[16:29] <alkisg> Eeeerr... the tool
[16:29] <alkisg> Because different actions are needed if the users are logged on, and different if they aren't
[16:29] <sbalneav> well, I'd say "no" since now you're making it a monitoring tool as well.
[16:29] <sbalneav> No, the actions are no different.
[16:29] <alkisg> Or maybe we could leave that for italc or a similar tool :)
[16:29] <LaserJock> I think it might be wise to separate the idea of managing the system's user information (name, password, etc.) from performing actions on the user
[16:30] <sbalneav> I'd say so yes.
[16:30] <sbalneav> LaserJock++
[16:30] <sbalneav> right, lets solve a smaller problem.
[16:30] <sbalneav> managing the user database
[16:30] <alkisg> LaserJock: if you already have the users there, why not allow the sysadmin to execute some actions upon them?
[16:31] <LaserJock> because it may well prevent us from having the tool in the first place
[16:31] <sbalneav> alkisg: that would be your plugin thing
[16:31] <sbalneav> right click on the user drops down list of plugins
[16:31] <LaserJock> what I think would be a good target would be to get something in upstream GNOME
[16:31] <sbalneav> click on plugin, plugin gets called for that users
[16:31] <LaserJock> in the Admin section
[16:31] <alkisg> Yes, if the tool was designed with plugins in mind...
[16:32] <sbalneav> Gee, if only there were a gnome developer amongst us who has git.gnome.org access....
[16:32] <alkisg> heh :D
[16:32] <alkisg> LaserJock: so... take kuser for example. Would you need anything more, for the admin section?
[16:32] <LaserJock> I don't know
[16:33] <LaserJock> what I'd like to see is educators/enterprise users get together and list what is needed
[16:33] <LaserJock> but not too pie in the sky
[16:33] <alkisg> It has ldap management, import/export from .csv etc
[16:33] <sbalneav> LaserJock: I asked alkisg to create a wiki page with requirements
[16:33] <alkisg> It's fine for enterprise usage
[16:34] <alkisg> I wouldn't need anything else for account management.
[16:34] <alkisg> But for *user* management, I'd need more
[16:34] <ogra> you and your endless requirements, tsk
[16:34] <LaserJock> ok, but we need account management first :-)
[16:34] <ogra> one user per PC is enough !
[16:34] <ogra> :)
[16:34] <alkisg> ogra: well, give us a good offer for arm netbooks :) We're waiting!
[16:34] <ogra> hey LaserJock
[16:35] <LaserJock> ogra: hi!
[16:35] <sbalneav> yeah, and they sit on the console.
[16:35] <alkisg> So, if we want an account management tool, I'd say kuser is fine. Not gnome, but in edubuntu, we don't care much as we already have all the KDE stuff.
[16:35] <LaserJock> right, I'm concerned about GNOME though
[16:35] <alkisg> For a user management tool, a plugin approach would be needed.
[16:36] <alkisg> LaserJock: I don't think edubuntu should be concerned about account management. It's more of an enterprise concern, let them do it, they have more resources :D
[16:36] <LaserJock> ok, but account management is sort of a prerequisite to a lot of other things
[16:37] <LaserJock> i.e. sabayon, etc.
[16:37] <LaserJock> effective use of account management could be a very useful thing
[16:37] <LaserJock> I think it could be a paradigm changer
[16:38] <LaserJock> how we think of users affects a whole lot of other decisions
[16:38] <LaserJock> including things like user managment
[16:39] <LaserJock> if it was trivial to import/export users, change groups on the fly, etc. do you think it would change how educators do user management?
[16:40] <alkisg> I've given this a lot of thought. I know exactly what I was as a computer teacher (=also sysadmin): an all-in-one tool. To be able to send 10 files to class A or put a firefox bookmark in class B from the same UI.
[16:40] <alkisg> It's not something enterprise admins would like, though :)
[16:41] <LaserJock> maybe, maybe not
[16:41] <alkisg> In other words: the user management tools in windows are sophisticated
[16:41] <alkisg> They allow for group changes, policy changes etc
[16:41] <LaserJock> but the foundation of either is account management I'd think
[16:41] <alkisg> They 're NOT suitable for educators
[16:41] <LaserJock> why not?
[16:42] <highvoltage> sbalneav: well. even if you could put them in a unix group
[16:42] <alkisg> Because they're enterprise oriented
[16:42] <highvoltage> sbalneav: well. even if you could put them in a unix group 'grade7' and display by that it would help, but gecos could be useful as well for more taggy things
[16:42] <LaserJock> how so?
[16:42] <alkisg> You cannot expect a teacher to understand about "resultand set of policies"... :)
[16:42] <LaserJock> that why we make the tool!!!
[16:43] <LaserJock> the idea is to abstract the nuts and bolts to something that teachers find useful
[16:43] <alkisg> That's why I'm saying that I don't really care about an account management tool
[16:44] <alkisg> I'd like a users management tool. In all the existing tools, windows, kde, fedora's etc, I don't see any actions to do on users
[16:44] <LaserJock> ok, but it sounds to me like you're saying that you don't want an account management tool because account management tools suck
[16:44] <alkisg> No, they're doing their job fine
[16:44] <sbalneav> You guys are making this over complicated.  With your plugin idea, we don't have to worry about that right off the bat.
[16:44] <sbalneav> All you need to do is:
[16:45] <sbalneav> 1) create an account management tool that handles account management fine.
[16:45] <sbalneav> 2) have 2 sets of plugin dirs: one for user actions, one for group actions.
[16:45] <sbalneav> you alow multi-select on the user and group lists
[16:46] <sbalneav> when you right-click on a selected set of users, then you get a dropdown menu with the available plugins (i.e. list of files in /usr/share/foo-manager/user-plugins
[16:46] <sbalneav> you select the plugin
[16:46] <sbalneav> plugin is passed a list of user or group id's that have been selected.
[16:47] <sbalneav> so if you want a plugin that copies bookmarks, or whatever, you just write one.
[16:47] <alkisg> Right. Perfect.
[16:47] <sbalneav> that won't be OUR problem to solve
[16:47] <alkisg> The teachers themselves can solve this, if the mechanism is there.
[16:47] <sbalneav> then as people write plugins, we can either:
[16:48] <sbalneav> 1) package these up as either individual or groups of plugins
[16:48] <sbalneav> or
[16:48] <sbalneav> 2) simply provide a place where people can advertise plugins they've written (wiki, or what have you)
[16:49] <LaserJock> so the question is, can this be done in users-admin, and if not how can we get it upstream?
[16:49] <ogra> sbalneav, but but ... then we wouldnt have the fun to explain garymc the .desktop file copying every month in #ltsp ... that would automate everything
[16:50] <alkisg> Hehehehe
[16:50] <ogra> sbalneav, that makes us jobless !!!!
[16:50] <alkisg> Don't worry, we'll hire you as a plugin writer :)
[16:50] <sbalneav> pffft :)
[16:50] <alkisg> I don't think users-admin is suitable for plugins
[16:50] <sbalneav> So, really, what we need is:
[16:51] <alkisg> Python is better for that instead of C
[16:51] <sbalneav> 1) something like the old users-admin in terms of interface
[16:51] <sbalneav> 2) written in python
[16:51] <sbalneav> 3) need a plugin architecture for "user supplied plugins"
[16:51] <sbalneav> that's not that hard.
[16:51] <LaserJock> well
[16:51] <milanbv> hey guys
[16:51] <LaserJock> technically *no*
[16:51] <milanbv> I'm users-admin's maintainer
[16:51] <LaserJock> but socially?
[16:52] <LaserJock> milanbv!!!
[16:52] <LaserJock> milanbv: awesome to see you
[16:52] <sbalneav> Hello milanbv
[16:52] <milanbv> hi! :-)
[16:52] <LaserJock> milanbv: I've been talking to Edubuntu folks in order to know how to respond to your email
[16:52] <milanbv> it's arer to see so much enthusiasm for the gnome-system-tools
[16:53] <milanbv> s/arer/rare/
[16:53] <milanbv> if you're going to write a new app, I'd suggest you to base on the new work by mclasen rather than on the system tools backends
[16:53] <alkisg> Hi!!!
[16:54] <LaserJock> milanbv: is that from Red Hat?
[16:54] <milanbv> yeah
[16:54] <milanbv> http://cgit.freedesktop.org/accountsservice/tree/
[16:54] <milanbv> http://blogs.fedoraproject.org/wp/mclasen/2010/01/15/old-promises/
[16:54] <LaserJock> thanks
[16:55] <LaserJock> the thing that concerns me is if it would be hard to get another tool into GNOME
[16:55] <LaserJock> I can see where the new users-admin is a nicer UI for the "typical" users
[16:55] <milanbv> n, it's already in: http://git.gnome.org/browse/accounts-dialog/
[16:55] <LaserJock> but is there enough of a distinction between home users and educational/enterprise users that a separate project is worth while?
[16:56] <milanbv> what separate project? yours?
[16:56] <LaserJock> good grief
[16:56] <LaserJock> everybody needs to get together and come up with a single set of tools
[16:56] <LaserJock> :-)
[16:56] <milanbv> (that was a real question :-p )
[16:57] <alkisg> About the UI, I think kuser has a lot of good ideas. The dbus backend also sounds sexy...
[16:57] <ogra> milanbv, all existing tools are lacking multi user management
[16:57] <alkisg> ogra: kuser supports multi user management (I think)
[16:57] <milanbv> what do you mean by that?
[16:57] <ogra> milanbv, and the UI simplification going on, while its beautiful doesnt make it easier
[16:57] <ogra> milanbv, imagine you manage 500 users on one server
[16:57] <ogra> you want to be able to group and sort in the UI
[16:57] <milanbv> OK, multi = many
[16:58] <milanbv> yes, that's why I was wondering
[16:58] <ogra> or to apply the same set of changes to a certain set etc
[16:58] <milanbv> sorting is rather trivial
[16:58] <alkisg> milanbv: not only that. Suppose you want to change the groups on 100 users simultaneously
[16:58] <alkisg> I.e. remove them from "audio" and put them on "sambashare"
[16:58] <LaserJock> or you want to just throw a .csv at the tool and have everything synced
[16:59] <milanbv> hmm, that's not on our scope, sadly
[16:59] <LaserJock> right
[16:59] <milanbv> that would need a separate tool
[16:59] <alkisg> kuser supports that
[16:59] <ogra> all existing user management apps lack such features and the focus of future improvements seems to always be on single desktop systems with in max 10 users or so
[16:59] <LaserJock> milanbv: so do you think there would be support within GNOME for such a tool?
[16:59] <milanbv> I'm not sure
[16:59] <ogra> (/me talking about gnome desktops here)
[16:59] <milanbv> the question is not really whether it would enter GNOME
[16:59] <milanbv> you need somebody to work on it
[17:00] <LaserJock> well
[17:00] <LaserJock> I'm willing to put my code time to something like that
[17:00] <LaserJock> little as it is
[17:00] <milanbv> that may not be too hard, yes
[17:00] <LaserJock> but I don't want to work on something that has no chance of getting upstream
[17:00] <milanbv> do you really need it to go upstream? why?
[17:01] <LaserJock> because I want GNOME to work for educators
[17:01] <milanbv> that could stay a separate tool shipped with distributions like Edubuntu
[17:01] <LaserJock> it's part of my secret plot to make GNOME rule the world, one school at a time .... mwhuahahahahahahaaha
[17:02] <LaserJock> ok, so maybe not ;-)
[17:02] <LaserJock> but I have issues with tools that just stay within a single distro
[17:02] <LaserJock> I think it should be more broadly useful
[17:02] <milanbv> agreedù
[17:03] <milanbv> but the first step is to make it work ;-)
[17:03] <LaserJock> sure
[17:03] <alkisg> milanbv: are there thoughts to make the dbus-based backend a "global" solution? I.e. thoughts for it to manage LDAP users? Or to be used by other DEs as well?
[17:03] <ogra> and you could get it into something like fifth toe ...
[17:03] <LaserJock> the fatal flaw in my world domination plans, drat
[17:03] <ogra> doesnt need to be 100% upstream that way, but would be available through upstream
[17:03] <milanbv> alkisg: the system tools backends are not really maintained actually
[17:04] <milanbv> I was the only person working on it
[17:04] <alkisg> milanbv: I mean the new one, that uses dbus
[17:04] <alkisg> http://cgit.freedesktop.org/accountsservice/tree/
[17:04] <milanbv> and now mclasen seems to want to create a better D-Bus service
[17:04] <milanbv> that one would support LDAP
[17:04] <milanbv> so yes :-)
[17:04] <milanbv> that's the plan, but it's only starting
[17:04] <alkisg> So maybe we could use it as a backend too, and only design a suitable front end
[17:05] <milanbv> sure, avoiding duplication is always good
[17:05] <alkisg> Maybe it's worth waiting then, and not start the project now.
[17:05] <milanbv> you should discuss with him what you need
[17:05] <milanbv> basic support is here ATM
[17:05] <ogra> ++
[17:05] <milanbv> http://cgit.freedesktop.org/accountsservice/tree/data/org.freedesktop.Accounts.xml
[17:05] <ogra> communication helps sometimes :)
[17:05] <milanbv> http://cgit.freedesktop.org/accountsservice/tree/data/org.freedesktop.Accounts.User.xml
[17:06] <milanbv> what do you need actually?
[17:08] <alkisg> Personally, I'd like something like kuser (https://help.ubuntu.com/5.10/kubuntu/images/C/kubuntu-kuser.png) with multiple select / edit and with a plugins architecture
[17:09] <alkisg> So that I could select 10 users and put them in group A or invoke the plugin "set a firefox bookmark" on them.
[17:09] <milanbv> but that's the GUI's job
[17:09] <alkisg> Yes
[17:09] <milanbv> I meant: what do you need from the backend?
[17:09] <alkisg> Oh
[17:09] <alkisg> The information on the .xml seems enough, but is it going to be stable?
[17:10] <milanbv> no
[17:10] <milanbv> :-)
[17:10] <alkisg> That's why I said maybe we should wait :)
[17:10] <milanbv> but I'm not sure that's a great problem
[17:11] <milanbv> the hard work will be the interface parts
[17:11] <milanbv> you could also start with the system tools backends, and switch when it's ready
[17:11] <milanbv> if the backend is abstracted enough, that won't be hard
[17:12] <alkisg> Well if we're going to do our own user "abstraction" then we won't mind the backend changing, but if we're going to use the same structures as the backend, we'll need a lot of changes in the code for e.g. s-t-b => new stuff migration
[17:12] <milanbv> for you, the base structure is only following /etc/passwd an /etc/group
[17:12] <milanbv> so those fields are not going to change much
[17:12] <milanbv> (if at all)
[17:13] <alkisg> I'm not sure that's the case
[17:13] <alkisg> E.g. consolekit has info on who's logged on. That may be useful for some plugins
[17:13] <alkisg> Or, the "Desktop" / "Επιφάνεια εργασίας" xdg dirs could also be useful
[17:14] <milanbv> hmm, that's another issues
[17:14] <milanbv> who's logged in is not a problem, even the GUI can do that
[17:15] <milanbv> liboobs is doing it for users-admin, it's not in the system tools backends
[17:15] <alkisg> So if we're going to "pass" users around to plugins, we'll need those as fields of the objects/structures...
[17:15] <milanbv> are there other "special" settings other than XDG that you may need?
[17:16] <alkisg> At some point "special" settings it the responsibility of the plugin (e.g. where's the firefox dir?)
[17:16] <milanbv> that would be more complex
[17:16] <milanbv> plugins on the backend side would really make it harder
[17:17] <milanbv> you'd need another system
[17:17] <alkisg> I agree, those should be frontend-plugins
[17:17] <sbalneav> Sorry, was afk for a bit, workping
[17:17]  * sbalneav reads scrollback
[17:18] <milanbv> but on the frontend side, you wouldn't be able to install files into Firefox's dir
[17:19] <milanbv> maybe you should combine two backends: the user management one, and another custom one, allowing to install some files and things like that
[17:22]  * alkisg doesn't know how PolicyKit works behind the scenes, so has now clue on how to design that 
[17:23] <alkisg> s/now/no
[17:23] <milanbv> not very hard
[17:23] <milanbv> the backend runs as root, and asks PolicyKit when a frontend wants to do something
[17:23] <milanbv> it's either yes or no, PK takes care of authentication
[17:24] <sbalneav> I'm having to learn pk for sabayon, so I might end up knowing something more about it soon than I know now.
[17:24] <sbalneav> Which is nothing
[17:27] <alkisg> Well the plugins would contain arbitrary commands. So I guess the backend should be able to take the scripts as a parameter, and execute them... Will need extra checks for security :)
[17:27] <milanbv> for that, simply use gksu from the frontend, then
[17:28] <alkisg> E.g. "put a firefox bookmark for the selected users"
[17:29] <alkisg> The frontend shows a dialog, gets the bookmark, notifies the backend to run "addbookmark $selected_users"
[17:30] <milanbv> so use libgksu to run the plugin from the frontend
[17:30] <alkisg> The backend should then invoke that (python?) plugin, pass it the selected users info, and let it add the bookmark...
[17:30] <milanbv> you don't need PolicyKit to run arbitrary commands
[17:30] <milanbv> that's cheating :-)
[17:30] <alkisg> So for each action a gksu dialog would be displayed? Wouldn't that be annoying?
[17:31] <milanbv> no idea
[17:31] <alkisg> Or should the whole frontend run with gksu?
[17:31] <milanbv> no
[17:31] <milanbv> never run GUI as root
[17:31] <LaserJock> well, that might be something to consider further down the road
[17:31] <milanbv> there's another
[17:32] <milanbv> otion
[17:32] <LaserJock> perhaps to start with you just want to limit what scripts can do
[17:32] <LaserJock> and not let them be arbitrary
[17:32] <milanbv> you could install plugins in a dir where your custom backends knows about them
[17:32]  * alkisg looks at /usr/share/applications/sabayon.desktop... "gksu sabayon" :P :D
[17:32] <milanbv> and then use a generic command that runs the plugin with some arguments
[17:33] <milanbv> for example, you could send to the backend "run firefox_bookmark (["user1", "user2"], "bookmark file")"
[17:34] <milanbv> and the PolicyKit action would either be "run any plugin", or "run firefox bookmark plugin"
[17:34] <alkisg> That's what I meant above with "notifies the backend to run "addbookmark $selected_users""...
[17:35] <alkisg> The plugins would be python modules or something like that, in standard dirs
[17:35] <alkisg> And the whole users objects would need to be passed, not just the user names...
[17:35] <milanbv> yeah
[17:36] <milanbv> you'd need to restrict scripts that you run to a special folder where the plugins are installed
[17:36] <milanbv> and you would define a user struct that you would pass to the plugins, of which they would do what they want
[17:36] <milanbv> but this has to be independent from the general user management backend
[17:37] <milanbv> so you need to choose your struct anyway
[17:38] <milanbv> gtg
[17:38] <alkisg> milanbv: so... if we did a tool like kuser (multiple selection/editing etc), which depended on the new dbus backend for user management,
[17:38] <alkisg> and also a plugin mechanism (frontend/backend),
[17:38] <alkisg> could the tool (without the plugins) be integrated to gnome?
[17:38] <alkisg> (or with the plugins...) Or should it remain an edu* project?
[17:39] <milanbv> hey, I'm not the GNOME release team :-)
[17:39] <milanbv> you could ask on #release-team
[17:39] <milanbv> they will give you an insight
[17:39] <milanbv> anyway I'm going
[17:39] <alkisg> :) thanks a lot man
[17:39] <alkisg> Bye..
[17:40] <milanbv> if you want to grab me, I'm on #ubuntu-desktop, or on #gst (on irc.gimp.net)
[17:40] <milanbv> and file reports in Launchpad if some minor bugs could help you
[17:40] <alkisg> Thanks!
[17:43]  * sbalneav has been in and out of the office on work matters
[17:43] <sbalneav> so what was the end result?  Are we adding things to the new users admin?
[17:47] <alkisg> sbalneav: well YOU SHOULD BE HERE to ask that :D
[17:48] <LaserJock> well
[17:48] <alkisg> I think he said "hmm, that's not on our scope, sadly" about multiple selection etc
[17:48] <sbalneav> Yeah, well, I have this thing called a JOB which allows me to do all this other stuff, and they kinda needed me :)
[17:48] <LaserJock> it seemed fairly clear to me that users-admin is not where mass-user is going
[17:48] <sbalneav> So, a separate project.
[17:49] <alkisg> We could use their backend, though
[17:49] <sbalneav> but, maybe we can use their PK backends
[17:49] <LaserJock> I asked rick spencer (Desktop Team manager) about the Red Hat tool and if Ubuntu had any plans
[17:49] <sbalneav> right
[17:49] <LaserJock> he basically said they didn't but they'd likely just use whatever was the GNOME default tool
[17:52] <LaserJock> so ....
[17:54] <sbalneav> So, we'll use their pk backend for adding the users and getting auth
[17:54] <sbalneav> have a more "large # of users" frontend
[17:54] <sbalneav> and a plugin system.
[17:55] <sbalneav> It'll be an Edubuntu sponsored project, and be something unique that we add to the process.
[17:55] <sbalneav> Unfortunately, Ahmuk-jr's not here to see it :)
[17:58] <alkisg> A good user manager is a much needed tool. But I don't think it's my first priority at this point. E.g. I think fat clients are a lot more important...
[17:58] <alkisg> Maybe we could propose kuser for some time, and see how that goes?
[17:59] <alkisg> I don't know why, but I have the feeling that for the next LTS some new tools or backends will be there.
[17:59] <sbalneav> alkisg: Sure, I wasn't even going think about looking at this until after we got close to lucid release.
[18:00]  * alkisg also started his phd and is already behind schedule, so after lucid is released will devote most time in it
[18:00] <sbalneav> I've got enough on my plate ATM.  But post lucid, it could be a "killer feature" for edubuntu, and we could still give it to lucidusers via the edubuntu-ppa's
[19:04] <sbalneav> So over my lunchtime walk, I solved the most important problem with this user manager we're talking about.
[19:04] <sbalneav> The name.
[19:04] <sbalneav> See'um
[19:04] <sbalneav> Simple, Elegant, Extensible User Manager
[19:04] <sbalneav> Now that I've solved the hard part, the rest should be easy ;)
[19:06] <alkisg> Heh... I'll do the icon
[19:06] <alkisg> Now with the most 2 difficult parts done, we just need a humble programmer to do the monkey typing thing
[19:07] <sbalneav> Like I say, I'll take that one on.  Post lucid.
[19:08]  * alkisg will help, do most of the plugins
[19:10] <sbalneav> I'll start a wiki page tonight, point you at it in the morning.
[19:12] <sbalneav> What I mapped out in my mind over lunch is that we do *very little* natively in the gui.  Very simple: add, delete, modify users & groups
[19:12] <sbalneav> most functionality will come from plugins.
[19:12] <sbalneav> I'll put my thoughts in order tonight, get 'em on a wiki page.
[19:15] <alkisg> bbiab
[19:22] <LaserJock> sbalneav: are you putting this on the Gnome wiki or Edubuntu wiki?
[19:24] <sbalneav> LaserJock: edubuntu wiki for the momen
[19:24] <sbalneav> t
[19:25] <LaserJock> so is the idea to use accountservice (new DBUS thingy from red hat) or system-tools-backend?
[19:27] <LaserJock> it's not clear to me how plugins will be implemented in the UI
[19:28] <LaserJock> I would think a really good plugin framework might be a bit difficult to do
[19:29] <sbalneav> LaserJock: Well, I'd have to look at accountservice, see what it does.
[19:29] <sbalneav> as for the ui....
[19:30] <sbalneav> right-click context menu brings up list of plugins avaialble
[19:30] <LaserJock> you sure that's that'll work?
[19:30] <LaserJock> what if I want to extend in different ways
[19:30] <LaserJock> what happens if you end up with 50 scripts
[19:31] <LaserJock> so if I write a .csv import/export plugin
[19:31] <LaserJock> I'd want it to show up in a "Add" dialog
[19:31] <sbalneav> LaserJock: Then you have a looooong context menu :)
[19:31] <LaserJock> I really think there should be limits on plugins
[19:32] <LaserJock> maybe it's paranoia about other apps I've seen with "plugin mania"
[19:32] <sbalneav> There are.  Screen resolution :)
[19:32] <LaserJock> one could classify plugins
[19:32] <LaserJock> an app I've worked on before, Avogadro, has like 3-4 different plugin types
[19:33] <LaserJock> depending on what they do
[19:33] <LaserJock> some go in a menu, some get added to the toolbar, etc.
[19:33] <LaserJock> so user/group manipulation scripts sound good for right-click context menus
[19:33] <sbalneav> right
[19:34] <LaserJock> import/export scripts could show up in a central "Add/Remove" dialog
[19:34] <LaserJock> maybe there could be searching/grepping plugins?
[19:34] <LaserJock> this is where I'd really like to know what kinds of things people actually do with users
[19:35] <sbalneav> Possibly.  Like I say, I'll get my thoughts down on the wiki tonight, then we can start kicking 'em around.
[19:36] <LaserJock> it'd be awesome to make this usable for sabayon and dynamics menus
[19:37] <LaserJock> sbalneav: can sabayon be launched straight from the edit button?
[19:38] <sbalneav> Sabayon isn't account management
[19:38] <sbalneav> it's profile management.
[19:38] <sbalneav> lets not write a kitchen sink here.
[19:38] <LaserJock> no, no
[19:39] <LaserJock> what I was thinking
[19:39] <LaserJock> was you have 2 possibilities
[19:39] <LaserJock> 1) a user script that runs "edit the profile for this user" from the user management
[19:39] <LaserJock> 2) a option in sabayon that launches the user management to do user shuffling, etc.
[19:40] <LaserJock> so making them a bit integrated so that the whole user management landscape is a bit more cohesive
[19:42] <sbalneav> Well, we can talk about that.
[19:43] <LaserJock> heh
[19:43] <LaserJock> you know
[19:44] <LaserJock> it might be possible to use a simple python backend until this accountservice thing is stable/packaged for Ubuntu
[19:45] <sbalneav> Probably first implementation will just use gksu
[19:45] <LaserJock> it might be easier than trying to use system-tools-backends
[19:45] <sbalneav> ignore pk alltogether.
[19:45] <LaserJock> well, yeah
[19:45] <LaserJock> I'm just talking about doing the actual user/group manipulation
[19:48] <LaserJock> then when a newer/better backend arrives we can just swap out
[19:51] <alkisg> Well, for starters, the python passwd bindings seem to work fine
[19:52] <alkisg> #import pwd, spwd, grp, csv
[19:54] <LaserJock> right
[21:29] <sbalneav> dgroos: ping
[22:56] <dgroos> sbalneav: pong
[22:56] <dgroos> (I've always loved ping pong)
[22:59] <dgroos> Further question about using that data collection software on thin clients--they responded to my post this morning, and said that they are interested, but that they've had a hard time getting it to work.  They referred me to a web page...
[22:59] <dgroos> which had this comment: "If you are using USB, make sure the environment is set up so the clients address local USB ports rather than those on the server."  Is this the way it would work with using their software as a local app?
[23:02] <dgroos> sbalneav: I've been reading today's irc--lots of important talking about account/user management.
[23:03] <dgroos> I've got some opinions--am looking forward to the wiki page that alkisg puts out--I hope I can add profitably (metaphorically speaking) to it.
[23:04] <dgroos> I'm heading home, will be back on this evening, adios.