About remove nfs filesharing support

[Kevin Krammer]

On Tuesday, 2010-12-28, Raphael Kubo da Costa wrote:
> On Tuesday 28 December 2010 12:56:01 Rodrigo Belém wrote:
> > On Tue, Dec 28, 2010 at 10:12 AM, Alex Fiestas <alex at eyeos.org> wrote:
> > > On 12/28/2010 03:06 PM, Rodrigo Belém wrote:
> > >> Hello everybody,
> > >> 
> > >> I've been working on kubuntu team to update the samba file sharing
> > >> code and code is already in trunk :-) I have another patch that
> > >> updates the kdenetwork/filesharing, but it removes all the nfs code,
> > >> which needs root privileges. Are you ok with this change or do you
> > >> want keep the nfs support?
> > > 
> > > Well, we should not remove any feature imho, but maybe we can improve
> > > it.
> > > 
> > > If the code needs root maybe we can port the current code to KAuth so
> > > we have a modern way of doing it.
> > 
> > I think remove features is not very good too, but worth keep nfs
> > support and update it? Users really uses this feature?
> 
> Does that mean making KDE completely oblivious to NFS at all?

I think the main idea of this thread is to agree to a change without knowing 
what it exactly changes.

Unfortunately we don't have any of the following things at our disposal:

- web based system for reviewing patches (you know like a reviewboard)
- messaging system with attachment capabilities (you know like email)
- remote file access based ion some universal addressing scheme (you know like 
HTTP)

Since, as we already have established, have neither at our disposal I suggest 
we jsut go ahead and blindly argue about scope, necessity and any other 
details people can come up with.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20101228/2b799d7d/attachment.sig>