> Thx Sebastien Bacher to re-attach the bug to us. You are welcome
> I want to be clear on some of your "notes". nautilus-elementary is not a duplicated effort, it's a different implementation from upstream exactly like the patches you apply on your ubuntu version except it's a little larger. Right, the difference is that we don't like having to carry those changes and we think it benefit everybody when those go upstream that's why we do efforts to get all the changes submitted upstream for review > All theses changes were never proposed to upstream for a reason, nautilus-elementary is mostly patches, implementation rejected by upstream or implementation that never landed. How do you know they would not be accepted since you didn't try? One reason changes in bugzilla are often sitting there is that they need work and nobody is available to do the work. If you do pick those tasks and do the work there is no reason they wouldn't interest upstream as well. > So it would be a waste of time to publish all this patches a second time, bugzilla or nautilus mailing list is already full of theses patchs. It's not true. Bugzilla has high activity and most maintainer don't manage to follow things there but patches on the mailing list usually get reviewed. If you do changes on nautilus you should at least discuss them on their mailing list. You would get some code review which would help quality and help nautilus and be nice opensource citizens. > So there's really no duplication efforts. Having say that, nautilus- elementary and nautilus teams have talked together recently and there would be a collaboration between the two project on some points but each project would follows their road and their choices. Right. I'm following the nautilus mailing list and IRC channel for some years and I've been talking to Jorge Castro about the issues between teams recently since the nautilus team expressed concerned about your team doing changes and not contributing back to nautilus. > I just wanted to make this clear as i am sick of reading this duplication effort stuff... seriously if there was any duplication i wouldn't have wasted my time in nautilus-elementary project implementing stuff upstream didn't want to. That's a troll, you could suggest your changes and go your way if they are not interest. They are interested for changes like editable toolbars for years though, it didn't happen by lack of manpower, it seems that you guys picked on the task and there is no reason why you shouldn't do it with the nautilus team to get those change in the upstream code. > sorry for the spam. No worry, that's not spam but a constructive discussion to have (though maybe it should be take out of the bug tracker), your team seems to have a wrong perception of what nautilus upstream is wanting to work on and on the value of working with upstream on the sort of changes you are doing -- Nautilus Segmentation Fault 0x010719a5 in IA__gtk_range_set_value https://bugs.launchpad.net/bugs/589076 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
