Re: goodbye
On Wed, Sep 21, 2011 at 19:11, John Tapsell wrote: > Reindl, > > Sorry to see you go. I don't know why Aseigo is being childish - I > think this is all just taking its toll on him. This is one of the > advantages that companies have and we don't have - we can't pay people > to fix the essential things that are boring to do. John you are not helping here at all. We need to stick together in situations like this. Had we done that we'd not be where we are with this right now. Cheers Lydia -- Lydia Pintscher KDE Community Working Group member http://kde.org - http://about.me/lydia.pintscher >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Notice of moderation
- Ursprüngliche Mitteilung - > On 09/21/2011 07:19 PM, Ingo Malchow wrote: > > Hello all, > > > > due to recent activities and as being requested, this mailinglist is > > now set to full moderation, which means anyone will get moderated. > > This is not to make you uncomfortable, even the opposite. > > But don't worry, we are taking steps to have enough moderators to be > > in time and you don't need to wait days before your mail really gets > > on this list;) > > So please still enjoy this place, have fun and be nice (no, that is > > not incompatible). > > Moderation isn't good, and I hope that this change is reverted. I > understand that posts may be unhelpful and even unpleasant, but there is > something fundamentally wrong with the idea that some people must waste > their time censoring a communication medium and it less efficient just > because some users have a hard time ignoring some posts. It took me about half an hour to read through the thread yesterday and I cannot put a number on the lost motivation due to the thread - especially seeing the discussion going on after Lydia's mail. Moderation might not be nice, but it is better than developers going away because of their users. Cheers Martin >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
invest money in free software?
On Wednesday, September 21, 2011 06:11:09 PM John Tapsell wrote: > I would really like to see bounties being raised for bugs. There > are a lot of problems with having bounties, and in the past such an > idea has been shot down, but maybe it's worth revisiting. If users > care about a bug being fixed, perhaps they would be willing to put up > a small amount of money towards it being fixed. If enough users do > that, it entices developers to fix the bug. Hi John! As I am thinking about creating a platform for exactly this purpose, you made me curious. Could you point me to the thread where this was discussed or maybe some could highlight the basic reasons why this idea was shot down? Because if nobody thinks this would be a good idea, I maybe should invest my time in other stuff. I think putting money in the game could in some areas be a real boost to free software. After all, people spend huge amounts of money for proprietary software, although they don't really own it after-wards. I think it makes a lot more sense to invest money, in more valuable, free software. I am really curious about the reasons, any hints are welcome. I don't want to restart any old discussions, so if this was already discussed in detail, please just point me to the thread of interest ;-) Best regards, Robert >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
i would be the first to spent some amount of money for fixing things that making me personally tired if no one is interested elsewhere if someone says "pay me 50,- € and i fix it" i am the first saying "thanks here the money" as long i do not need a creditcard or paypal (why: because i don't have both) and support my desktop is a personal thing, server-software on the other hand will be possibly supported from my company if there are good reasons our company paid some thousand € the last years for free software to get some changes in several free server-software (as example help the netatalk project a short time ago), anyways this is limited because as SMALL company you can only support few projects each year but we are open to help real improvements this are all things people can talk about but a no-go is "why do you not fix it yourself?", "why have you not learend C/C++ in the last months", "if you was not willing to learn fix it this can not be important enough for you" - this is a destructive answer and only the right if someone want to start a flamewar or show users that they are not welcome Am 22.09.2011 11:04, schrieb Robert Klotzner: > On Wednesday, September 21, 2011 06:11:09 PM John Tapsell wrote: > >> I would really like to see bounties being raised for bugs. There >> are a lot of problems with having bounties, and in the past such an >> idea has been shot down, but maybe it's worth revisiting. If users >> care about a bug being fixed, perhaps they would be willing to put up >> a small amount of money towards it being fixed. If enough users do >> that, it entices developers to fix the bug. signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
2011/9/22 Reindl Harald : > i would be the first to spent some amount of money for fixing things that > making me personally tired if no one is interested elsewhere > > if someone says "pay me 50,- € and i fix it" i am the first saying "thanks > here > the money" as long i do not need a creditcard or paypal (why: because i don't > have both) and support my desktop is a personal thing, server-software on the > other hand will be possibly supported from my company if there are good > reasons > > our company paid some thousand € the last years for free software to get some > changes in several free server-software (as example help the netatalk project > a short time ago), anyways this is limited because as SMALL company you can > only support few projects each year but we are open to help real improvements > > this are all things people can talk about > > but a no-go is "why do you not fix it yourself?", "why have you not learend > C/C++ in the last months", "if you was not willing to learn fix it this can > not > be important enough for you" - this is a destructive answer and only the right > if someone want to start a flamewar or show users that they are not welcome This is not constructive. Feel free to discuss that NEW topic, which is quite interesting. But please stop references to a flame thread that was one of the reasons this list is now moderated. Keep trying to get stuff done and we all are more happy. That is a global statement :) Cheerio, Ingo Malchow >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
Hi Robert, A very recent opportunity was at at Sebastian Trueg's blog ( read from this post onwards http://trueg.wordpress.com/2011/09/13/nepomuk-fundraiser/ ) Regards, Shantanu Tushar(UTC +0530) http://www.shantanutushar.com On Thu, Sep 22, 2011 at 2:34 PM, Robert Klotzner wrote: > On Wednesday, September 21, 2011 06:11:09 PM John Tapsell wrote: > > > I would really like to see bounties being raised for bugs. There > > are a lot of problems with having bounties, and in the past such an > > idea has been shot down, but maybe it's worth revisiting. If users > > care about a bug being fixed, perhaps they would be willing to put up > > a small amount of money towards it being fixed. If enough users do > > that, it entices developers to fix the bug. > > Hi John! > > As I am thinking about creating a platform for exactly this purpose, you > made > me curious. Could you point me to the thread where this was discussed or > maybe > some could highlight the basic reasons why this idea was shot down? > > Because if nobody thinks this would be a good idea, I maybe should invest > my > time in other stuff. I think putting money in the game could in some areas > be > a real boost to free software. After all, people spend huge amounts of > money > for proprietary software, although they don't really own it after-wards. I > think it makes a lot more sense to invest money, in more valuable, free > software. > > I am really curious about the reasons, any hints are welcome. I don't want > to > restart any old discussions, so if this was already discussed in detail, > please just point me to the thread of interest ;-) > > Best regards, > > Robert > > > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > unsubscribe << > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
Hmmm. Isn't there already a place to make donations? If not it could be a way to go. Donate towards the cause of this bug. Or donations for bug fixes accepted On Sep 22, 2011 5:09 AM, "Robert Klotzner" wrote: > On Wednesday, September 21, 2011 06:11:09 PM John Tapsell wrote: > >> I would really like to see bounties being raised for bugs. There >> are a lot of problems with having bounties, and in the past such an >> idea has been shot down, but maybe it's worth revisiting. If users >> care about a bug being fixed, perhaps they would be willing to put up >> a small amount of money towards it being fixed. If enough users do >> that, it entices developers to fix the bug. > > Hi John! > > As I am thinking about creating a platform for exactly this purpose, you made > me curious. Could you point me to the thread where this was discussed or maybe > some could highlight the basic reasons why this idea was shot down? > > Because if nobody thinks this would be a good idea, I maybe should invest my > time in other stuff. I think putting money in the game could in some areas be > a real boost to free software. After all, people spend huge amounts of money > for proprietary software, although they don't really own it after-wards. I > think it makes a lot more sense to invest money, in more valuable, free > software. > > I am really curious about the reasons, any hints are welcome. I don't want to > restart any old discussions, so if this was already discussed in detail, > please just point me to the thread of interest ;-) > > Best regards, > > Robert > > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Allow users to donate money towards bugs
Hi all, I think it would really help with bug reports if we let people donate money towards getting bugs fixed. If there are lots of users annoyed by a bug, and there's no longer a maintainer for that code, then it makes a lot of sense to let those users contribute money towards the bug fix until the financial incentive is large enough for someone to step up and fix it. John >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
On 22 September 2011 10:04, Robert Klotzner wrote: > As I am thinking about creating a platform for exactly this purpose, you made > me curious. Could you point me to the thread where this was discussed or maybe > some could highlight the basic reasons why this idea was shot down? Have a google around for old threads, but the objections are usually along the lines of that: 1. It might de-motivate the developers that code for free. 2. What to do if someone commits a bad fix that another developer then has to go in and fix. Who then gets the money? 3. It might create a situation where someone writes a feature for money but won't maintain it. Do we want more unmaintained half-broken features? 4. What to do when a bug fix requires changes done by lots of people, who gets the actual money? Will it cause resentment to those who helped but didn't get the money? This has been tried before. An ubuntu brainstorm on it: http://brainstorm.ubuntu.com/item/1295/ Read the comments there and duplicates for more info and a list of existing websites: http://www.cofundos.org/ http://bountycounty.org/ http://www.opensourcexperts.com/bountylist.html https://www.bountysource.com/ John >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: goodbye
Am Donnerstag, 22. September 2011, 10:01:47 schrieb Lydia Pintscher: > On Wed, Sep 21, 2011 at 19:11, John Tapsell wrote: > > Reindl, > > > > Sorry to see you go. I don't know why Aseigo is being childish - I > > think this is all just taking its toll on him. This is one of the > > advantages that companies have and we don't have - we can't pay people > > to fix the essential things that are boring to do. > > John you are not helping here at all. We need to stick together in > situations like this. Had we done that we'd not be where we are with > this right now. Please do not take this too far! It's generally bad to just shut people up since it can lead to group think and hides real issues. Sticking together is good and I think I know that your intent is positive but it looks like you want to repress valid criticism as well. In the latter case "sticking together" is bad - really bad because it mediates that not everybody is treated with the same set of rules within KDE's community. Problems have to be spoken out, in a constructive and adult way. Same thing regarding unacceptable behaviour and a wrong style of communication. If sticking together means that one must not do that anymore you are doing a disservice to the KDE project and its openness. Sven >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: goodbye
On Thu, September 22, 2011 9:01 am, Lydia Pintscher wrote: > On Wed, Sep 21, 2011 at 19:11, John Tapsell wrote: >> Reindl, >> >> Â Sorry to see you go. Â I don't know why Aseigo is being childish - I >> think this is all just taking its toll on him. Â This is one of the >> advantages that companies have and we don't have - we can't pay people >> to fix the essential things that are boring to do. > > John you are not helping here at all. We need to stick together in > situations like this. Had we done that we'd not be where we are with > this right now. I concur with John. It seems to me that there has been some over-reaction on both sides of this argument - while the initial posting didn't properly recognise the way that free software works, I think that some of the responses, especially threats to revert a fix which a lot of other users would also benefit from, were also to a greater or lesser degree unreasonable. While we can stick together on the basic principles in the argument, KDE is surely about being free to (respectfully) question other people's ideas and statements. It's not about adhering 100% to some 'official' line (which is undefined anyway). -- David Jarvie. KDE developer. KAlarm author - http://www.astrojar.org.uk/kalarm >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Allow users to donate money towards bugs
Am 22.09.2011 10:29, schrieb John Tapsell: > I think it would really help with bug reports if we let people > donate money towards getting bugs fixed. If there are lots of users > annoyed by a bug, and there's no longer a maintainer for that code, > then it makes a lot of sense to let those users contribute money > towards the bug fix until the financial incentive is large enough for > someone to step up and fix it i agree but it would be very important that orphaned code is noticed somewhere automatically - what about bugreports ignored over months because the maintainer has left, does ignore mails from bugtracker and nobody notice that there something goes wrong? exactly this would be candidates for pay a small amount of money for takeover this code from someone else - but how should bugreporters take notice if this is they case or they maintainer(s) simply not interested to fix a concrete problem? signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Notice from moderators
Hi, The "goodbye" and the "why are bugs ignored..." threads are officially closed. _No_ more answers to these threads will be allowed. Please take this as a reminder to keep things civil and polite. A disagreement does not have to be unpleasant. /Regards The kde-devel moderators signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: goodbye
On Thu, Sep 22, 2011 at 11:08, Sven Burmeister wrote: > Am Donnerstag, 22. September 2011, 10:01:47 schrieb Lydia Pintscher: >> On Wed, Sep 21, 2011 at 19:11, John Tapsell wrote: >> > Reindl, >> > >> > Sorry to see you go. I don't know why Aseigo is being childish - I >> > think this is all just taking its toll on him. This is one of the >> > advantages that companies have and we don't have - we can't pay people >> > to fix the essential things that are boring to do. >> >> John you are not helping here at all. We need to stick together in >> situations like this. Had we done that we'd not be where we are with >> this right now. > > Please do not take this too far! It's generally bad to just shut people up > since it can lead to group think and hides real issues. Sticking together is > good and I think I know that your intent is positive but it looks like you > want to repress valid criticism as well. In the latter case "sticking > together" is bad - really bad because it mediates that not everybody is > treated with the same set of rules within KDE's community. > > Problems have to be spoken out, in a constructive and adult way. Same thing > regarding unacceptable behaviour and a wrong style of communication. If > sticking together means that one must not do that anymore you are doing a > disservice to the KDE project and its openness. Ok let me clarify that then. John calling Aaron childish was not helpful and not valid criticism especially not in this situation. I explained the details of it again on IRC. I am all for discussing problems but there are ways to do that without at the same time hurting your team mates. Cheers Lydia -- Lydia Pintscher KDE Community Working Group member http://kde.org - http://about.me/lydia.pintscher >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
Am 22.09.2011 11:46, schrieb John Tapsell: On 22 September 2011 10:04, Robert Klotzner wrote: As I am thinking about creating a platform for exactly this purpose, you made me curious. Could you point me to the thread where this was discussed or maybe some could highlight the basic reasons why this idea was shot down? Have a google around for old threads, but the objections are usually along the lines of that: 1. It might de-motivate the developers that code for free. There are already devs who are on the payroll of companies for working for KDE. And envy is always bad manners and a sign of immaturity. 2. What to do if someone commits a bad fix that another developer then has to go in and fix. Who then gets the money? 3. It might create a situation where someone writes a feature for money but won't maintain it. Do we want more unmaintained half-broken features? 4. What to do when a bug fix requires changes done by lots of people, who gets the actual money? Will it cause resentment to those who helped but didn't get the money? All of this could be resolved by simply feeding each donation into a pool to be used by the whole project. I admit, that putting money in the game does raise new workload for the project. Especially if it is not that much money but effectively more than nothing. But in the end money can always be helpful ;-) This has been tried before. And there is at least one big project living on donations from users: http:// ardour.org so it can be done methinks. An ubuntu brainstorm on it: http://brainstorm.ubuntu.com/item/1295/ Read the comments there and duplicates for more info and a list of existing websites: http://www.cofundos.org/ http://bountycounty.org/ http://www.opensourcexperts.com/bountylist.html https://www.bountysource.com/ John Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe<< Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
Am Donnerstag, 22. September 2011, 10:46:10 schrieb John Tapsell: > On 22 September 2011 10:04, Robert Klotzner wrote: > > As I am thinking about creating a platform for exactly this purpose, you > > made me curious. Could you point me to the thread where this was > > discussed or maybe some could highlight the basic reasons why this idea > > was shot down? > Have a google around for old threads, but the objections are usually > along the lines of that: > > 1. It might de-motivate the developers that code for free. It's not like users will pay for bugs/features that developers will work on anyway but rather those issues that nobody wants to work on without any additional incentive. Further, there are payed devs already, be it by donations or some company. Hence other than the source of money nothing changes. I did not read anything about e.g. the nepomuk devs complaining that Sebastian gets money because of working on a project they contribute to for free. > 2. What to do if someone commits a bad fix that another developer then > has to go in and fix. Who then gets the money? Good question. How is it solved with the commits of the currently payed devs? Regressions are introduced all the time, so there would be nothing new here. But of course the money should only be payed after the code was proven to be worth it. Maybe one minor release without any major bugs. Or what about giving x% to some reviewer who then takes responsibility for that commit as well. Those reviewers could be KDE devs who are known to be reliable. The reviewboard does already handle a lot of commits that way. > 3. It might create a situation where someone writes a feature for > money but won't maintain it. Do we want more unmaintained half-broken > features? This happens all the time without paying people. The folder-view was one of those examples. Yet with a bounty there would be an incentive for people to take over maintainership/fix bugs for something unsexy that nobody else wants to take care of. > 4. What to do when a bug fix requires changes done by lots of people, > who gets the actual money? Will it cause resentment to those who > helped but didn't get the money? As I stated already, there is this notion of payed vs unpayed developers already. > This has been tried before. An ubuntu brainstorm on it: > http://brainstorm.ubuntu.com/item/1295/ > > Read the comments there and duplicates for more info and a list of > existing websites: > > http://www.cofundos.org/ > http://bountycounty.org/ > http://www.opensourcexperts.com/bountylist.html > https://www.bountysource.com/ Thanks for the links, I'll read through them. :-) Sven >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
On Fri, Sep 23, 2011 at 8:49 AM, Sven Burmeister wrote: > > http://www.cofundos.org/ > > http://bountycounty.org/ > > http://www.opensourcexperts.com/bountylist.html > > https://www.bountysource.com/ > > Thanks for the links, I'll read through them. :-) Hi, just wanted to add this link with an interesting (and valid?) point of view http://threatpost.com/en_us/blogs/how-bug-bounties-are-rat-farming-092011 David E. Narváez >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
On Thu, Sep 22, 2011 at 4:13 PM, David Narvaez wrote: > Hi, just wanted to add this link with an interesting (and valid?) point of > view > > http://threatpost.com/en_us/blogs/how-bug-bounties-are-rat-farming-092011 Yes, allowing uncontrolled personal bug bounties would a) open the door to various moral hazards: - incentive for "rat farming" (as you mentioned) - incentive for working alone (or even in secret) rather that collaborating - etc., and b) introduce lots of destructive petty conflicts of interest into an environment otherwise based on mutual constructive collaboration: - Who gets the money, the one who completes the last 1% of the work? - How are disagreements handled about by whom, when or if a bug was fixed? - etc. To handle all those possible issues, lots of bureaucracy and conflict-management would be needed, which would probably do the project more harm than good. However, I still wouldn't discard the concept of allowing users to invest money into bug fixes completely. It could potentially work if the bounties are not paid to any individual developer, but go to towards a common cause that benefits KDE (or the individual project the bug belongs to) as a whole, like for example: - money is donated to KDE ev. - money goes towards providing free beer (or food or whatever) at the next developer sprint - money goes towards financing a new automatic unit testing server for the project - money goes towards financing Nnvidia cards for testing purposes (in the case of the KWin team ;-) And even bounties paid to individual developers could *possibly* be made to work in a very *controlled* (semi-automated) environment, like such: - The project maintainer must explicitly mark a bug as "yes, this seems to be a nasty, not-so-fun bug to solve and motivation to do so is low among our team" before bounties may be placed on it (maintainers have to be trusted not to abuse this). - A developer wishing to collect the bounty for a specific bug must announce his/her commitment to do so *beforehand*, and is then obliged to fix it within a specified time frame (within which no other developer can collect the bounty). - Each developer may only take on *one* "bounty bug" at a time. - Failing to complete a "bounty bug" as promised within the specified time frame bans the developer from the bounty system for a month, and opens up the bug again for other developers to take it. But even then, the principal problems I listed at the top of this mail would only be reduced, not eliminated completely. So before serious discussion is even possible, I guess a thoroughly worked-out proposal that addresses all those issues (and probably many others) would be needed. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
On Thu, Sep 22, 2011 at 11:29 AM, Harri Porten wrote: > Don Sanders, one of the former KMail maintainers, had such a system set up > many years ago btw. I couldn't find anything about it anymore online. But > iirc it didn't work out too well... > > Harri. Just to clarify, I'm not strictly against bug bounties, I just remembered I read that article recently and wanted to bring it to the table. Now, here's an idea, I don't know if essentially different from previous ones but we could discuss: What about funding bug squashing parties and stabilization sprints? That's not exactly a "pay per fix" model, but a way to sustain these activities which are very time consuming. The main reason why I think this is a better approach than plain "pay per fix" is that any given developer in the KDE project, or any large FOSS project whatsoever, is not able to cope with the size of bug lists and individual bugs (that is: some bug lists are larger than life and some bugs are extremely hard to reproduce - and that all comes before the fix) so I truly believe that if we don't attack theses collaboratively, there's no way we can really try killing the backlog. So what I'd love to see (and that's just me) are lots of distributed bug squashing and stabilization sprints "Sponsored By SomeMediumSized Co.", where funds can probably be managed through KDE e.V. or something, but can ultimately be distributed by the organizer of the sprint in the way she finds more useful. Notice that this is probably already happening, so I'm just maybe pointing to an existing idea, because this seems to me like https://sprints.kde.org/ with sponsors logos in each sprint box. David E. Narváez >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Allow users to donate money towards bugs
On Thursday 22 September 2011 10:29:16 John Tapsell wrote: > > I think it would really help with bug reports if we let people > donate money towards getting bugs fixed. If there are lots of users > annoyed by a bug, and there's no longer a maintainer for that code, > then it makes a lot of sense to let those users contribute money > towards the bug fix until the financial incentive is large enough for > someone to step up and fix it. As Harri already pointed out Don Sanders tried that a couple of years ago. It didn't work out. There are mainly two reasons for that. The first is that serious software development costs serious money. Getting enough money together from individual donators to actually competitively pay for the development is really difficult, because it's by far not done by two or three people pledging 50 EUR. So making a living from this kind of system would require massive numbers of supporters who continuously put in significant sums of money. This is really hard to achieve and certainly won't work for many developers. The second reason is that money is a horrible motivator. Of course everybody needs a certain amount of money to fulfill basic and some non-basic needs. But what motivates us is not getting money, but doing something that matters, doing something we are capable of doing well, having the freedom to do it in a way we feel is good and right. Money introduces a dangerous dynamics into this. It values extrinsic rewards over intrinsic rewards, opens the can of worms of fair distribution of money, and it requires a new level of administration, which is hard to get right. Doing free software because you love it works much better. Enjoy the technical challenges, enjoy being part of a wonderful community, enjoy the feeling of accomplishment, when you get something great done. This pays much better than money for fixing bugs. It pays in happiness, but it also pays materially. Successful involvement in free software projects is a booster for many carreers. This will put you into a situation where you can earn the serious money, and if you are a bit lucky even with something you really love. -- Cornelius Schumacher >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
CMake 2.8.6-rc4 ready for testing!
The CMake 2.8.6 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D This email is also available on the Kitware blog at http://www.kitware.com/blog/home/post/170 This is the last rc before the final release, unless somebody finds a showstopper issue between now and next Thursday. This release candidate we do not have pre-built binaries for the SunOS anymore. As mentioned on the CMake mailing list recently, our Sun hardware has bitten the proverbial dust. However, we are now providing two sets of installers for the Mac. The "Darwin" versions are for Mac OSX 10.4 and later, and are "ppc;i386" universal binaries. The "Darwin64" versions are for 10.6 and later, and are "x86_64;i386" universal binaries. Following is the list of changes in this release. Since we switched to git, this list is now the 'git log' one line summary written by the named CMake developers. Please try this version of CMake on your projects and report any issues to the list or the bug tracker. Happy building! -Dave Changes in CMake 2.8.6-rc4 (since 2.8.6-rc3) Alex Neundorf (3): FindFLEX.cmake: also search the include dir Fix typos in FeatureSummary.cmake (#12462) Don't warn when setting a property multiple times to the same value #12464 Bill Hoffman (2): For VS Intel Fortran IDE builds, add a check to find the Fortran library PATH. Enable Fortran tests for IDE builds. Brad King (5): FortranCInterface: Compile separate Fortran lib in VerifyC[XX] Move IntelVSImplicitPath project to better location Simplify IntelVSImplicitPath detection project libarchive: Fix ssize_t detection with mingwrt 3.20 Make file(DOWNLOAD) fail on http error David Cole (8): Tests: Add a KWStyle test, equivalent to the make StyleCheck target KWStyle Test: Activate by default if KWStyle is found Xcode: Use EFFECTIVE_PLATFORM_NAME reference in ComputeOutputDir Xcode: Add test to demonstrate iOS project in Xcode CMake: Reference test targets only when BUILD_TESTING is ON Tests: Add the more modern Mac64 nightly build Release Scripts: Use Qt 4.7.4 on dashmacmini5 (#12460) Revert "FindThreads: Try pthreads with no special option first (#11333)" Eric NOULARD (4): CPack fix #12449 doc mispelled CPack fix template too CPackDeb fix #10325 automagically use fakeroot for DEB if fakeroot is found CPackRPM authorize per-component pre/post-[un]install scripts (#0012063) Marcus D. Hanwell (4): Just code style changes. Don't warn when nothing to do in visibility function. Made ADD_COMPILER_EXPORT_FLAGS into a macro. Make add_compiler_export_flags a function again. Rolf Eike Beer (1): remove stray brace in CPackDeb documentation >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: invest money in free software?
Thanks for the links, your opinions and knowledge about this topic. This was really helpful, thanks a lot! Best regards, Robert >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Help fixing Lokalize & generic development questions
Hi Albert, > At the moment I am unemployed so if you are really interested drop me a mail > in private and we can have a chat. Thanks, Albert > Thank you for the quick reply. I have sent a proposal to my manager however think he has found another piece of software which seems to do the job we require. It's not as nice as Lokalize from my perspective so I will continue to push for this to be fixed but I think unfortunately I took too long to trying to fix the bug and should have signed up to the list sooner. Kind regards Andrew >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
