samba stuff

Given the ubiquity of networks and the need for their interoperability:

Let's take a look at all the samba proposals on blueprints and hammer-out essential priorities for the program.
Further, we need to colloquialize the vocabulary for the everdy idiot: "don't worry, you can create a samba share" means nothing to the uninitiated...he's just think "???...idiot".

I would put samba in a higher priority than medium/low positions: as evil as some think Windows is (not me), it's the duke: Linux needs to play nicely...even if it has to fight to. Novell seems to be working on this right now (oooo...the dirty traitor: I'm sorry I mentioned that name...ooo). Whether or not it made the best decision (who cares) it could become a valuable inroad for the OSS community...like it or not, it'll give insights.

Particulary, we need the interoperability for mixed environments: my campus is one of the first things that comes to mind; corporate environments follow (former business major--switched to biology though). : ) We don't just need a gui: we need service/protocol/port/etc. discovery, automation of everything possible, play-nice-with-firewall considerations, but more: anything and everything that won't requie the user to get scared-off with the labor of configuration. Windows already, often, doesn't play nice with itself: I can just imagine the linux-windows scenario's possibilities...could seem bleak; however, I'm aquainted with people who do just fine (after some long, arduous, painful configuration work and pouring over manuals: they use Red Hat, by the way...might be Fedora now), but they're also technical.

Basically, this is meant to be "do some brainstorming about Samba" post.