Re: [sabayon] Starting to map out a roadmap for sabayon.

["Job Cacka" <job ccbox com>]

Scott,
    I like the suggestions you have made. Am I correct in assuming that the
changes that have made Sabayon function correctly have not been backported
to older versions of gnome? This is the typical case with FOSS. I will need
to check it out again to give better feedback.
    Docbook is great. Often it is beneficial to have plain text
documentation as well. Especially, when you are in the heat of the battle.
    Logging ought to be as unix/linux like as possible. If my distro uses
/var/log that is where I want to see verbose logs kept when I am
troubleshooting. This is a reason I gave up on Sabayon in my Ubuntu+LTSP
install. It was impossible for me to troubleshoot in the time frame I had
for development.
    Whenever you deal with ownership issues I think that modules for the
primary authentication scheme should be used. Case in point, we use an
OpenLDAP implementation. One of the most frustrating things in the
Linux/Unix realm is every service seems to authenticate/establish ownership
in a different way. My Samba server wants to use smbpasswd, Dovecot on my
internal mail server has a special method for changing authentication, and
the one method that works the best is Linux' own PAM. Probably, because it
was broken at one point and much time has been spent to "fix" it. My users
do not want to "remember" forty-eleven passwords and I do not want to manage
that many accounts. Whenever possible do not reinvent the wheel. But then
you know this.


Job Cacka
IT Manager
Columbia Corrugated Box Co.

.

-----Original Message-----
From: sabayon-list-bounces gnome org [mailto:sabayon-list-bounces gnome org]
On Behalf Of Scott Balneaves
Sent: Monday, November 02, 2009 8:39 AM
To: sabayon-list gnome org
Subject: [sabayon] Starting to map out a roadmap for sabayon.

Hello all lovers of edited profiles,

I'm starting to think a bit ahead to what we can accomplish for sabayon in
the
next 6 months.  Now that we've got something that (all feedback appears to
indicate) is functioning, we can start blue-sky dreaming.

Here's what I've got on my hitlist:

1) Group apply.  Federico's already integrated those patches into the git
tree,
so we should have that when the next release comes out.
2) Updated documentation.  I'd like to re-vamp and bring the doco up to
date,
in docbook format.  I need to have a look at what gnome's doing for docs
these
days, but IDEALLY, we'd have a "help" menu off the editor screen with a
bog-standard fully-translated gnome help entry.  this would be ideal, in my
mind, but I'm interested in other people's thoughts.
3) re-vamping the debuglog architechture.  Because of the way sabayon does
logging, by default, the logs are... not very helpful.  Then we run into the
old problem of trying to step a (potentially inexperienced) user through
creating a sabayon-debug-log.conf file in ~root, etc.  My FIRST idea would
be
to turn on all logging by default, but we log to a ring buffer in memory.
if
we get an error of any kind, we then cut an actual log file.  But if the
session exits normally, we do the "unix" thing and exit silently.  Again,
thoughts?
4) Better storage handling.  We need to start fully handling things like
perms,
ownership, etc, in the zip file.  we'll have to start storing more info in
the
metadata file.  Some kind of voodoo magic's going to be needed for
sabayon-apply, seeing as how it runs as the user, but an admin might want to
put root-owned file in a users home dir.
5) A nice code cleanup.  We could handle more exceptions gracefully, and
there's some room for general code-cleanup and documentation.

That's what's bleeping on my radar.  Any other bugaboos out there for
people?

Scott

-- 
Scott L. Balneaves | I don't have any solution,
Systems Department | but I certainly admire the problem.
Legal Aid Manitoba |     -- Ashleigh Brilliant
_______________________________________________
sabayon-list mailing list
sabayon-list gnome org
http://mail.gnome.org/mailman/listinfo/sabayon-list