Review Request: include KolorManager in kdegraphics

Lamarque V. Souza lamarque at kde.org
Thu Mar 15 11:06:16 GMT 2012


Em Thursday 15 March 2012, Daniel Nicoletti escreveu:
> >Like I also help with Wicd support in KDE, Kopete, and other areas of
> >interests for KDE users. I do not use Wicd, but I help KDE users of Wicd
> >even before I was the Network Management maintainer. By the way, I am not
> >driven by FDO interests. We are using upower/udisks because there is no
> >other choice in Linux, hal is unmaintained as you probably know. That is
> >why I think we should have a community to maintain the software we depend
> >upon.
> 
> Right so which community you are talking about, because
> Kai likes KDE, it seems that you are putting FDO/Gnome as things we should
> get away, instead of actually looking at how maintainable these two
> things are and yet share code which is really important.

	The community that develops and maintains the software in question. In 
the sentence above it was hal's community, in this thread are the oyranos and 
colord's communities.
 
> >> First you need to build the software or use the packaged version, see
> >> how things work, now I started a replacement for system-config-printer
> >> because it has authentication problems and is written in python. when I
> >> go to Oyranos I found a bunch of tech I don't like, not just I don't
> >> like but many developers don't, so who will maintain those technologies
> >> if few people like/use it?
> >
> > 
> >That's too personal oppinion and you sound like nobody likes oyranos.
> 
> It's a personal opinion indeed but this doesn't mean nobody likes Oyranos,
> it simply means that looking at the code there won't be much devs willing
> to maintain that. The deps speak for themselves. 

	Maybe, that is something that needs to be discussed with oyranos' 
community. By what I read in this thread elektra is still maintained and is 
optional, not sure about fltk.
 
> >> I don't want to kill Oyranos but I do think the choices based on wrong
> >> use cases might lead to an end, a good project done with a wrong design
> >> won't succeed. Take smart for example, PackageKit in a few years was
> >> able to do what they tried for many years, and stop saying that Gnome
> >> or Red Hat is pushing it, you can have Gnome without it, FDO also plays
> >> by it's own rules, let's focus on what really matters which is the
> >> code. No user will help you maintain a line of code, they will use what
> >> we best choose to them.
> >
> > 
> >If it is about Gnome without colord I am not sure if that is possible,
> >anyway, why would they patch cups to add support to colord if it is not
> >going to be used in the desktops?
> 
> Gnome works pretty much the same way as KDE we have modules, so the do,
> you can just remove/disable and Gnome will run without it, but why remove
> a cool feature? It's non sense, it's obvious that every distro would push
> because they want the missing feature, if Oyranos was there first maybe
> colord didn't had to exist.

	Maybe, maybe not.
 
> >I have never used PackageKit and said nothing about it. Are you talking
> >about PakcageKit or colord here? Users can help with patches from time to
> >time, that is important, and I was only a Knetworkmanager user before I
> >started to contribute. Your statement is completely wrong in an
> >opensource world.
> 
> You don't get it, I'm giving an example of how good projects dies because
> from a technical point of view they become unmaintainable.
> Sure, pretty much everyone is first an user then a developer but this
> doesn't mean you can expect from users of a software to maintain that,
> otherwise most of these projects wouldn't go into an end.

	You mean the oppositte in the last sentense, right? I still disagree, 
users can do a lot to help maintaining a software, that's called community. 
For extremelly technical parts there will be less users able to help, but 
still if you are not a user of the software why would you bother to help 
maintaining it? Sure the most experient users take the technical decisions, 
that is what we are do here in k-c-d for KDE for example.

-- 
Lamarque V. Souza
KDE's Network Management maintainer
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20120315/076955c7/attachment.htm>


More information about the kde-core-devel mailing list