Spread to more platforms - Randa Meetings 2016 open for registration
Good morning everyone Please excuse this cross-posting but all the above mailing list fit quite well this year's topic of the Randa Meetings: multi-platform end-user application development. This includes stuff like improving KDE Frameworks 5 (KF5) on other platforms like MS Windows, Android or Apple’s MacOSX, presenting and discussing how software distribution works on other systems than GNU/Linux (Windows installers, app stores and application bundles) and learning from the experience projects like Krita, digiKam, Rkward, Kdenlive & Co collected. We’d like to bring this information to more KDE Applications and work on this during a full week. So if you're interested and can help please go to: https://sprints.kde.org/sprint/301 and add yourself. And spread this information and tell people that could be of great help. This email though is just an informational email and thus not to start a discussion. Thanks and cu soon Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Versioning of Frameworks
Am Dienstag, 05. Mai 2015, 13.46:16 schrieb Martin Gräßlin: Morning [snip] > > If master is always releasable, you should indeed only merge into master > > with a change of a version number. > > If you don't want to maintain different versions for whatever reason > > (and I think that's an entirely reasonable choice), > > you can continue to automate this version bump. As long as I can exclude > > my library from the automatic version bumping, > > I see no problem at all. Having an automatic version bump as a > > requirement to be a framework is the problem IMO. > > ok, I start to understand what you want to get: two different ways of > releasing frameworks. I think that's a very bad idea for obvious reasons I > hope I do not have to bring up here. Ok, they are not that obvious too me. Wouldn't it be possible to add something like maintainerManagesVersionOnItsOn=false to a file in all the frameworks (isn't there already a file in each frameworks for stuff like platforms, etc.?) and modify the release-scripts (David or anybody who knows these scripts) once so that these scripts check this variable. So if it's set to false and most current maintainer seem to prefer not to do version bumps on their own the release scripts would bump the version number and do all the stuff as they do now. If the variable was set to true these scripts wouldn't bump the version numbers and just use the version numbers as set by the maintainer? Or is this just naive thinking from my side that it's "that easy"? > So far I assumed that you want to change the way how *all* frameworks are > released which would imply a significant work load to the maintainers as > you just explained yourself. As I understood it Christian doesn't want it changed for all maintainers as that would almost be rude ;-). griits Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-CI IRC meeting - Your possible KDE contributions in non-C++
Am Samstag, 22. November 2014, 21.15:01 schrieb Mario Fux: Good morning So the date is set now: Tuesday, 2nd of December, 20.00 CET (UTC+1) For the meeting, its summary and other stuff I setup: https://notes.kde.org/p/CI_IRC_Meeting_01 Thanks and cu there Mario > [Disclaimer: this email is sent to kde-devel, kde-core-devel and kde- > frameworks-devel. Please just answer to kde-devel!] > > Morning ladies and gentlemen > > Oh and please scratch the "please" above ;-). This email is about another > possibility to contribute to KDE. It's about taking work off Ben's > shoulders and about fixing the bus factor for our great CI (Continuous > Integration) [1] system: http://build.kde.org > > I'd like to start a series of weekly or bi-weekly (to be decided) IRC > meetings to coordinate the work to understand, change and enhance our CI > system and therefore we need a first date. So if you're interested please > add yourself to this Doodle (think about different timezones!): > http://doodle.com/i5f4pppb2sq6u5ee > > Prospective agenda for the IRC meeting: > - Ben: Short introduction to KDE CI > - Everybody: Short introduction incl. their skills and wishes for KDE CI > - Ben: What needs to be changed > - Everybody: Work on a roadmap and distribute work till next meeting > - Everybody: Determine date for the next IRC meeting > > This is your chance to help KDE to enhance the code quality and spread to > even more platforms and thus bring our great software to even more > computers and people. > > [1] https://community.kde.org/Frameworks/Epics/Continuous_Integration > > Best regards > Mario > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > >> unsubscribe << ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
KDE-CI IRC meeting - Your possible KDE contributions in non-C++
[Disclaimer: this email is sent to kde-devel, kde-core-devel and kde- frameworks-devel. Please just answer to kde-devel!] Morning ladies and gentlemen Oh and please scratch the "please" above ;-). This email is about another possibility to contribute to KDE. It's about taking work off Ben's shoulders and about fixing the bus factor for our great CI (Continuous Integration) [1] system: http://build.kde.org I'd like to start a series of weekly or bi-weekly (to be decided) IRC meetings to coordinate the work to understand, change and enhance our CI system and therefore we need a first date. So if you're interested please add yourself to this Doodle (think about different timezones!): http://doodle.com/i5f4pppb2sq6u5ee Prospective agenda for the IRC meeting: - Ben: Short introduction to KDE CI - Everybody: Short introduction incl. their skills and wishes for KDE CI - Ben: What needs to be changed - Everybody: Work on a roadmap and distribute work till next meeting - Everybody: Determine date for the next IRC meeting This is your chance to help KDE to enhance the code quality and spread to even more platforms and thus bring our great software to even more computers and people. [1] https://community.kde.org/Frameworks/Epics/Continuous_Integration Best regards Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 Update Meeting Minutes 2014-w28
Am Dienstag, 08. Juli 2014, 19.27:52 schrieb John Layt: Morning John [snip] > > * he'd like to see a donation button in KDE apps based on KF5 > > (developers > > > > could opt-out); > > We already have a link to the donations page buried deep in the "About > KDE" dialog under the "Support KDE" tab where no-one ever sees it. A Indeed there is something ;-). > Help menu item for "Donate to KDE..." that pops up a dialog explaining > why would be far more visible, but easily disabled by distros who So what? It's still free software so everybody can patch it away. But we can present it prominently and try and see if it helps. And I mainly think about KDE apps on Windows, Mac and Android when I want to see this donate button as we're the distributors there ourselves. But it's exactly what I meant: A "Donate to KDE..." menu item under the Help menu. > object. We could also include a "Donate to KDE" tip in every > KTipDatabase and ensure it's the first tip shown by default on an apps > first run. As an admin note, whenever we do add a donate link > anywhere we should make it unique so that we can track how successful > each channel is. +1 > > * ervin hopes to see kdepimlibs bits getting in sooner rather than > > later; > > I asked on the PIM list the other day, Montel says the plan is not to > start on frameworks until after 4.15, so maybe March/April next year? There won't be a 4.15 and I talked with Montel about this. > I think he meant porting the PIM applications though, so I'm not sure > what that means for starting on pimlibs. I'll follow up. > > > My plans: > * Write proper docs for KUnitConversion > * Make KUnitConversion Tier 1 by switching to Qt translations > * In advanced planning for replacements for ISO codes and flag images, > even have some code, see > https://community.kde.org/KDE_Core/KDE_Open_Data > ** OpenCodes: repo of json files of ISO data auto-extracted from > Wikidata, CC-0, can be used by anyone > ** KCodes: Qt library which loads OpenCodes files > ** OpenFlags: repo of SVG flag images auto-extracted from Wikidata, > with icon set auto-generated from SVGs Very interesting stuff! > Here's a bit of bike-shedding for you: when creating completely new > Frameworks in Tier 1, do we name them with a Q or with a K or with > something completely neutral? > > Cheers! > > John. Thx Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 Update Meeting Minutes 2014-w28
Am Dienstag, 08. Juli 2014, 17.30:19 schrieb Kevin Ottens: > Hello everyone, Morning > This is the minutes of the Week 28 KF5 meeting. As usual it has been held > on #kde-devel at 4pm Paris time. [snip] > * unormal is looking forward to more mac CI results; > * the windows CI is a bit stuck; > * he'd like to see progress on the android CI; > * he'd like to see a donation button in KDE apps based on KF5 (developers > could opt-out); > * he's thinking we should ask third party developers if they want to send > us some information when they use a framework to create an app; There was a small misunderstanding (probably based on my fatigue brain atm). Of course this interpretation would be nice as well I meant apps based on KF5 and to get a channel to our users. Two way: - Get to them if we need (financial) support or want to tell them about new version or other stuff - They send us automatically and agreed upon data about their use of our apps. [snip] griits Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Added current release schedule to techbase
Am Sonntag, 29. Juni 2014, 12.42:37 schrieb Kevin Ottens: Morning Kevin > > > > And what about the future releases of KF5? Any decisions made? At > > > > least Plasma 5 has a tentative schedule now: > > > > http://techbase.kde.org/Schedules/Plasma_5 > > > > > > I think we should have this in a single place, or they'll get out of > > > sync. I'm not sure where that place should be, though. > > > > As all the other release schedules are on techbase I think this should be > > the place. But I'd like to have an ok (or ship it ;-) from Kevin or > > someone else first. > > Was just more convenient for me on community.kde.org. But if that matters > that much to have them together with the other schedules, I don't mind > having them on techbase. Ok. Moved. It's easier to have all schedules and roadmaps at the same place. > Our schedules aren't that complicated anyway so we probably won't need to > edit that much. :-) > > Regards. Thx Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Added current release schedule to techbase
Am Samstag, 28. Juni 2014, 13.05:09 schrieb Alex Merry: Morning Alex > > And what about the future releases of KF5? Any decisions made? At least > > Plasma 5 has a tentative schedule now: > > http://techbase.kde.org/Schedules/Plasma_5 > > I think we should have this in a single place, or they'll get out of > sync. I'm not sure where that place should be, though. As all the other release schedules are on techbase I think this should be the place. But I'd like to have an ok (or ship it ;-) from Kevin or someone else first. Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Added current release schedule to techbase
Morning As I was asked recently why the release schedule of KDE Frameworks 5 is not (yet) on techbase.kde.org I took the liberty to change this: http://techbase.kde.org/Schedules/Frameworks It's link to the main page as well: http://techbase.kde.org/Schedules The content is taken from: http://community.kde.org/Frameworks/Epics I hope that's ok for your guys. If you tell me I'll remove it from the community.kde.org wiki and set a link. And what about the future releases of KF5? Any decisions made? At least Plasma 5 has a tentative schedule now: http://techbase.kde.org/Schedules/Plasma_5 Best regards Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Randa Meetings 2014: Registration Deadline and Fundraising
Good morning gals and guys You get this email because you're either: - Already registered on http://sprints.kde.org/sprint/212. - You're subscribed to a mailing list of a group that participates this year. - I already asked you in one way or another to come to Randa and you're not yet sure. - Or there is another good reason why you get this email ;-). This email is mainly to tell you the registration deadline for the Randa Meetings 2014: Deadline: Sunday, 4th of May 2014, 23:59 UTC. After this day we'll calculate the budget and will start a fundraising campaign as KDE e.V. can't give us enough money. We already did a campaign in 2012 [1] and it was a success but it needs some work and energy and you can be of valueable help: spread the fundraising campaign when we give you the link and go. But now, please do this: - If you're already registered on sprints.kde.org please check your data and verify that everything is correct (we can't try to sponsor you if you forget to add the data ;-). - Please check your group, who is yet missing on sprints.kde.org/sprint/212 of your group and ping and poke these people. - If you bring you family: did you already get in contact with me (about your preferred room, the number of persons, if they are vegetarians, etc.)? - Check if anything is unclear and you've question and send me an email or ping me (unormal) on IRC. Topics this year are: - KDE Books about KDE Frameworks - Gluon - KDE Edu/GCompris - KDE SDK - Porting apps to KF5 and porting KF5 to other platforms - Kdenlive - Amarok/Phonon/Multimedia And one last thing: Do not yet order any tickets! I'll tell when the right time for this will be. Best regards Mario [1] https://pledgie.com/campaigns/18045 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Writing a Frameworks book at Randa
Am Mittwoch, 09. April 2014, 15.05:06 schrieb Kevin Funk: Morning Valorie, Kevin and Co Thanks for bringing this topic up again. > On Wednesday 09 April 2014 02:25:18 Valorie Zimmerman wrote: > > Hello folks, I know that August is months away, but if you want your > > Frameworks book, now is the time to step forward. > > > > Here are some things to think about: > > > > Most of this book is already written somewhere. When the words have > > already been written down, all we need do is gather and arrange them. > > When you think of such an email, dot story, blog post or have eloquent > > thoughts in your head, please make a note. > > > > If you are on this list, you are an expert. You know what the > > Frameworks will do for KDE, and you know what they *can* do for > > others. Our book will present that case. A good book will help grow > > the Frameworks team; I'm sure of it. And a good book will make your > > work more widely used. Oh, and you'll be a published author! > > > > While in Randa, none of us will be writing full-time. In fact, I hope > > that *all* of the Frameworks people will stop by the writing room, or > > log into Booki and review, add, re-arrange, correct, or make the text > > more graceful. > > > > To make this work a few people must volunteer to take on the writing > > of the book as their most important task at Randa. It will be mine, > > and our goal is to have a book by the end of the week. We've done it > > before, and I know we can do it again. This is a valuable work. > > > > We need to know the core members of this team, soon. Please step > > forward, and also add yourself to the Spints page for planning and > > funding. +1 from my side here ;-). About the book. I think the first one was quite a success and often used to direct new people, contributors to. And IIRC you (Valorie) and Co took care not to integrate information in the book that was in heavy flux and often changed. So it mostly a beginners guide for KDE Platform and soon KF5 users, a bigger brochure that helps to get a broad overview. For the frameworks people that already registered on sprints.kde.org/sprint/212 please put some time aside to get to Valorie and Co in Randa and have a look or two and a helping hand. > > Valorie > > Hey, > > I'm wondering if we should rather try spending the time in making our KF5 > apidocs shine. You could spend plenty of time on writing introductory parts > for the individual modules, writing tutorials and examples, and make sure > they're easy to reach and grasp for newcomers on apidocs.kde.org. This is > an integral part for the docs on qt-project.org, too. Just have a look at > the first hit for "qt docs": [1] > > There's a "Getting Started" section, with overviews [2] with examples and > tutorials [3]. That's *exactly* what we need for KF5, too. That's the best > place to point newcomers to whenever they want to get wet with KF5. But it > also takes time and people to get to this state. > > Personally, from a developer POV, I don't really see the need for a > separate "book". There will always be a discrepancy between the book and > the actual code (be it completeness, accuracy, its up-to-date-ness), and > for developers it's always an extra burden to make sure to amend the > contents of the book whenever they change something in source code. It's > much more straight-forward to make sure that at least the apidocs are > up-to-date. The apidocs being inline in the source code being is an > integral part in making sure they're amended alongside of source code > changes. > > Opinions? What do the frameworks devs think about it? There is one above. And about the apidocs and examples and online resources I agree. They are important, very important and probably sometimes even more important than a book. But I think both are valuable and both have target groups. The questions is probably more. Would a dedicated KF5 apidocs meeting or sprint be of value? Another idea from my side is to include the kde-doc people in this effort and discussion? > Greets > > [1] http://qt-project.org/doc/qt-5/index.html > [2] http://qt-project.org/doc/qt-5/overviews-main.html > [3] http://qt-project.org/doc/qt-5/qtexamplesandtutorials.html Thanks and best regards Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: libmm-qt/libnm-qt as KF5
Am Montag, 07. April 2014, 14.38:14 schrieb Lamarque Souza: > Hi all, Morning Lamarque > I have cloned ECM git repo and looked at it. I agree that it is small and > it has useful features for NMQt/MMQt. I like the fact that it provides a > FindNetworkManager.cmake. Ok, we can make ECM a hard dependency for > NMQt/MMQt. > > My only concern now is the kde-modules that Jan used in NMQt/MMQt's > framework branches. Is it necessary to have KF5 installed to use those Here still seems to be a misunderstanding about KDE Frameworks (KF5). The goal and idea was and is it to modularize kdelibs so that people can pick the frameworks (e.g. KConfig and Sonnet) they need for an app and don't need to use and install all of them. So for the case of our (KDE) apps a lot (or most) of them will depend on many or all of the Frameworks in KF5. But all other Qt apps and libs that want to use the KDE Frameworks can just pick the once they need. Hope that clarifies KF5 a bit Mario > modules? I am asking it because I did not find where in ECM repo the > macro _kde_add_platform_definitions is defined. > > Lamarque V. Souza > > KDE's Network Management maintainer > > http://planetkde.org/pt-br > > On Mon, Apr 7, 2014 at 5:31 AM, Martin Gräßlin wrote: > > On Monday 07 April 2014 10:14:12 David Faure wrote: > > > On Monday 07 April 2014 09:47:43 Jan Grulich wrote: > > > > You are still talking about users, but I'm sure that 99% of them will > > > > install it from distro repositories and because e-c-m is build > > > > dependency, > > > > > > they won't notice that. For remaining 1% of users you are talking > > > > about will be e-c-m available from distro repositories as well, so > > > > what's the problem? Now those libraries are compiled mostly because > > > > of Plasma NM, which requires unreleased versions (i.e. for > > > > frameworks version) and in this case they have already e-c- m > > > > installed. > > > > > > > > I don't want to have libnm-qt/libmm-qt as separated libraries, I > > > > think that > > > > a lot of distributions have them in their repositories, because they > > > > are > > > > > > as > > > > dependency for Plasma NM. I would be really interested how many > > > > distributions would have it without Plasma NM. It makes sense to me > > > > be part > > > > of KF5, don't be separated and be more visible and available for > > > > other developers and users and probably less confusing for > > > > packagers. > > > > > > I agree. ECM is a very tiny dependency to have, and in return it solves > > > a large number of issues for you (deployment, cmake config files, > > > qmake > > > > .pri > > > > > file, dependency handling for users of your libs, forwarding headers, > > > versioning, releasing, etc. etc.). > > > > This is IMHO the important point. Just look at what ECM provides and you > > will > > realize that it's extremely useful and that even if those libraries will > > not > > end up in KF5, they will use ECM. How can I do such a bold statement? > > Because > > ECM solves real world problems you want to have solved in your library, > > too. > > The developers using your library will expect a proper Config.cmake file > > and a > > proper Version.cmake file and ECM solves that for you. I'm using ECM in > > libraries not intended to ever be part of KF5 exactly for that and before > > I added that dependency it was just not possible to reliable use the > > library. > > > > Of course you can also write that CMake Foo all by yourself but I have > > the feeling that the knowledge to write proper CMake Foo is not wide > > spread among > > our developers. I personally prefer to use the CMake Foo written by > > people who > > know their stuff instead of doing my own. > > > > Cheers > > Martin ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
kde4support => kdelibs4support[Was: Re: Releasing Deprecated modules and Tier 4 Definition]
Am Montag, 17. März 2014, 18.15:09 schrieb Kevin Ottens: > Hello, Morning Kevin > Thanks for the feedback! Thanks for your coordination! [snip] > Now, the last point... What else do we want to move from KDE Frameworks to > KDE Porting Aids? Aleix and Aaron proposed the following content for KDE > Porting Aids: > * kde4support (obvious); Just that it doesn't get forgotten I'd like to second Aarons (or who it was) proposal to rename kde4support to kdelibs4support at this occasion if it's an easy rename! This might be the perfect opportunity. Makes it easier for us promo people to tell that there is no "KDE4" as well. > * khtml (planned for a long time); > * kjs (because of khtml I gather); > * kjsembed (ditto); > * krunner (because of upcoming sprinter, and only one user anyway); > * kmediaplayer (unused AFAIK). > > I think that list makes sense. Is there anyone who couldn't sleep at night > if those were in KDE Porting Aids? > > Regards. Thanks Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KCodecs - Quick Review
Am Dienstag, 04. März 2014, 16.58:11 schrieb John Layt: > Hi, Morning Just a short notice. It looks as if the description on projects.kde.org for KCodecs is wrong: Thx Mario > I know nothing about text codecs, but I've had a *very* quick look at > KCodecs: > > * Original code by Lars dated 1999! > * One method marked as deprecated to be removed for KDE4 > * "###FIXME KDE4: the name of the encodings should mostly be uppercase" > * Code generated by script generate_string_table.pl located in > kdesdk/scripts * Algorithms marked as copyright by RSA Data Security and > others, but no mention what the original licence was or real link to > original source * Encoding probers and lookup tables marked as copyright > Mozilla 1998, X11 license > * kentities.c is documented as generated by gperf from either > kentities.gperf and/or khtmlentities.gperf but neither are in kcodecs, > instead they are in khtml as is another copy of kentities.c. > * Public API using boolean parms > > This suggests it could do with some attention: > * Check still valid to remove deprecated code? > * Check if encoding names should be made uppercase? > * The generate_string_table.pl script should probably be moved into > KCodecs, unless it has more general use? > * The RSA and other algorithms may need checking for licensing issues, or > at least improve the license documentation? > * The probers may need to be checked they are still up to date with the > original Mozilla code and look-up tables? > * kentities.c needs investigation and I suspect moving all the files from > khtml to kcodecs, with khtml then using kcodecs? Or at least docs added > that this is where it comes from and should be kept in sync. > > I wonder how much of this functionality is now done in Qt5? Would it > benefit from a functional review by someone who knows what they're doing, > like Thiago or David? > > Cheers! > > John. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE 5 versioning in documentation
Am Dienstag, 25. Februar 2014, 22.47:51 schrieb Martin Klapetek: > Hey, Morning [snip] > > Will the "KDE Software Compilation" still be a thing in the KF5 era, > > complete with its own versioned releases? If that's the case, we'll > > probably just want to change "KDE" to "KDE SC" in the > > for frameworks-based apps and call it a day. > > Not in its current form afaik. There will be three big "modules" - > Frameworks, Plasma and Applications. Given the progress on their "5" > versions is different, there are also different release schedules for both, > so no more SC in the current sense (that name also got dropped couple years > ago, no?). Correct. The SC was just an engineering/technical term. It was never intended to us in promo communication or for end users (of our apps, not our libs). See all the recent release announcement. There we never used SC. > We'd like to put heavy accent on *not* using KDE anymore in around the > workspace releases, so no more KDE Plasma, but just "Plasma", possibly with > "by KDE" touch. It'd be awesome to get it away from apps to, so it would > become "Dolphin for Plasma" instead of "KDE Dolphin" etc. Dolphin for Plasma shouldn't be used as well, if I see it correctly, as Dolphin work on Gnome, razorqt and Co as well and not just on Plasma. So just "Dolphin" or "Dolphin by KDE". Plus what Luigi wrote! > > If we're instead going to release all applications on their own > > schedules, we'll instead probably just want to drop any mention of a > > KDE version in applications' documentation. (Or add "on KDE > > Frameworks 5" or something like that?) > > I'm not sure what's the plan for apps. Their "4" versions will just work > with Plasma and we expect to actually ship the first Plasma with > applications based on kdelibs (please correct me if I'm wrong). > > > I'm also going to submit a review request shortly adding entities for > > all this new nomenclature so we can refer to it consistently in > > documentation in KF5-based applications. People interested in this > > sort of thing please double-check it for accuracy.. > > Cool, make sure you add kdeframeworks group as reviewers. > > Cheers Best regards Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
KF5 at the Randa Meetings this year
Morning guys Just read and you should get the answer: http://randa-meetings.ch/2014/02/19/randa-meetings-2014-the-date-is-set- please-register/ Best regards Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Keep the Things You Forgot
Am Donnerstag, 24. Oktober 2013, 14.02:16 schrieb Mark: Morning [snip] > You probably mean dot.kde.org/2013/09/25/frameworks-5 And this: http://dot.kde.org/2013/09/04/kde-release-structure-evolves > That would work but not if that's it. This kind of change is one that has > to sink in over time so this has to be repeated from time to time. Of course. That's why there are some more stories in the tube. See promo list and co for hints. Best Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Keep the Things You Forgot
Am Mittwoch, 23. Oktober 2013, 21.49:27 schrieb Mark: Morning [snip] > A blog post that i'd very much like from you (Aaron) is about the next > big KDE version, the naming and how the complete collection is going > to be called or if there even will be a collection release (what KDE > SC is now). Press is still getting that wrong, i tend to get it wrong > and other people talking about KDE seem to get it wrong. Usually it's > just being referred to as "KDE 5" which is wrong. (Frameworks 5, > Plasma 2, ...). So if you have the time, a blog about that would be > wonderful and very educational ^_^ What about all the recent dot articles about KF5, Plasma 2 and Co? I think you won't get it clearer than that. Best Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Keep the Things You Forgot
Am Dienstag, 22. Oktober 2013, 22.27:18 schrieb Aaron J. Seigo: > hi :) Morning guys > (i stole the subject without shame. but it seemed appropriate given the > topic) > > we’ve all gotten out of the habit of communicating with the outside world, > with some notable exceptions. Martin, in particular, has become an > outstanding blogger. > > the rest of us have been overly quiet. i’m working on getting my > bloggerificness going again rather than just hiding on irc and g+ ... > > i’d like to invite all of you to blog at least once a week about the > amazing work everyone is doing with Frameworks 5 and Plasma 2. there is SO > MUCH ACTIVITY in the repositories and the progress is astounding. > > it is important that the rest of the KDE (and beyond!) community sees this > movement too so they know what we’re up to and that we’re still running > ahead at great speed. > > communicating is how we get more contributors, it’s how we get more users, > it’s how we find more partners, it’s how we remind others to believe as > much as we do in the things we’re doing. I'd like to add a big (HUGE) +1 here. I'm reading several mailing lists (some less to get less distracted from my diploma thesis ;-) and it's great to see what your doing and accomplishing atm. Please tell the world, blog as hell! > love ‘n hugs to you all ... Another hugger from Switzerland Mario PS: And cross your fingers that my two concepts get finally excepted so that I can start organizing the Randa Meetings 2014 edition. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Sonnet up for adoption
Morning frameworkers In the last one to two weeks I thought a lot about my old and new involvement in KDE and my new family and thus I need to make some hard (for me) decisions. I need to reduce my involvement in KDE and need to focus and some or better one task. Therefore I think it wouldn't be responsible to have myself as Sonnet maintainer if I'm not sure to find the time to do the necessary work and learning. Thus I removed myself from the wiki [1] as Sonnet maintainer. I got a frameworks development enviroment up and running but if I find some sporadic time now I won't find more from May on when my first baby arrives. Thanks for all your help and patience and all the best for the future of KF5. I'll keep an eye on it ;-). Currently I'll focus my KDE work on the Randa meetings [2] and to build a stable legal foundation for it. I hope to introduce more of you to my new family at the next occasion in Randa ;-). All the best and cu soon Mario [1] http://community.kde.org/Frameworks/Epics/Splitting_kdelibs#May_Iteration [2] http://community.kde.org/Sprints/Randa ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kdelibs split: February Iteration reminder
Am Montag 27 Februar 2012, 22.04:06 schrieb Kevin Ottens: > Hello, Morning > On Monday 06 February 2012 19:45:05 Kevin Ottens wrote: > > I'm sending this email today as you are the lucky few choosen to be in > > the february iteration. From the look of the relevant table, we're in a > > pretty good situation already for this month: > > http://community.kde.org/Frameworks/Epics/Splitting_kdelibs#February_Iter > > ati on > > > > Still, I'd like to make sure that everyone is aware of the goal of > > getting those frameworks done by the end of the month which will arrive > > quickly now. As I said the situation seems well engaged so far, I see > > only very minor issues with the february batch, but we need to make sure > > steady progress happens to hit the target. > > So, only a couple of days left. Any progresses people? Apart from one > module I don't think I heard much from most of the modules after my > reminder. > > It looks like most of you are then silently in need for help. Any > volunteers to give our framework maintainers a hand? Most of the tasks > needed to complete the modules should be rather simple as I pointed out in > my previous email. As I was quite busy I at least found the time to get the KF5 compiling and allocated this Friday (yes, already March but hey, at least my birthday ;-) for the work on Sonnet. Although I for sure will need help. I read most of the wiki packages about Frameworks and hope to start with some small tasks. I'm a bit behind on this mailinglist tough. griits Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kdelibs split: February Iteration reminder
Am Mittwoch 08 Februar 2012, 07.52:53 schrieb Mirko Boehm: > Good morning! Good morning as well > On Feb 7, 2012, at 20:08, Kevin Ottens wrote: > > On Tuesday 07 February 2012 09:29:49 Mirko Boehm wrote: > >> I realized I am surprisingly unaware of the current ongoings. Because of > >> that, I will reserve some time for weekend hacking (good to have an > >> excuse anyway), and bug you guys on IRC about what needs to get done. > > > > Sure. For Threadweaver the situations looks fairly good already though. > > It's likely to be just a bit of cmake-fu and renaming a few folders to > > go through the "done" check list for that one: > > http://community.kde.org/Frameworks/Epics/Splitting_kdelibs#Existing_fram > > eworks > > Okidoki. I have to focus on something else for now, looking forward to it > though :-) First. Could we please stop using CC:s after the first mail as I think most of us are subscribed to the list. Then about my Sonnet stuff. I've planned to start this weekend, latest next week to spend time on this and will then ask dfaure to mentor me. > Mirko. Thx Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: examples
Morning Sometimes it's not the best idea to offer all choices but probably this time. I think it makes sense to leave the examples in an examples directory in each frameworks as this example code normally doesn't build without the framework itself. On the other side there are quite some people who'd like to have an overview of different KDE technologies and thus would like to download a kdeexamples module or repository (and I'll do this myself in the next days ;-). So why not leaving the examples in examples directories in the frameworks and building some cmake or what magic to create a tarball or something with all examples collected. Probably together with the (new) KDE demo app done this summer of code? Just my 2 Rappen Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: version # in frameworks
Am Sonntag 04 Dezember 2011, 23.53:14 schrieb Aaron J. Seigo:
> hi..
Morning
> currently in the top level CMakeLists.txt file in frameworks we have this:
I've now idea if this is complete bullshit and not necessary at all but I dare
to mention it nonetheless...
> set (KDE_VERSION_MAJOR 4)
> set (KDE_VERSION_MINOR 7)
> set (KDE_VERSION_RELEASE 40)
> set (KDE_VERSION "${KDE_VERSION_MAJOR}.${KDE_VERSION_MINOR}.
> ${KDE_VERSION_RELEASE}" )
> set (KDE_VERSION_STRING "${KDE_VERSION} (4.7.40 (KDE 4.8 >= 20110623)")
>
> this should be bumped imho to reflect that this is the "5.0" version.
> should we do the usual "4.90"?
As there is no KDE (as in software, but as in community) which can be released
(or versioned) and as we want to underline this fact more and more shouldn't
we change this variables?
Or is it too much work for too less value?
Just my 2 Rappen
Mario
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Date for IRC meeting about
Am Freitag 25 November 2011, 21.14:15 schrieb Jeremy Whiting: Morning Jeremy > I wont be able to attend the meeting at that time (which is fine, I > probably don't have a lot to add to the discussion). But like others > could probably benefit from a log of the meeting getting posted. > Could someone do that after the meeting please? Of course we will but thanks for reminding. > thanks, > Jeremy Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Date for IRC meeting about
Am Sonntag 20 November 2011, 20.08:11 schrieb Alexander Neundorf: Morning First: I'm subscribed to both lists so no need to CC: me. > > According to our Doodle [1] we found a date which works for everybody, > > great! > > > > It's Sunday, the 4th of December at 20:00 (UTC). > > Just to make sure: that's 21:00 CET (german) time, right ? Yes that's right. For other time zones here is a link to a tz converter: http://www.timeanddate.com/worldclock/converter.html > Which channel, actually ? Sorry, forgot this: #kde-devel > Do we have/need something like an agenda ? I think there will be an more precise agenda but this is not done by me (who is just a helper) but by some frameworks developers. thx Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Date for IRC meeting about
Good morning According to our Doodle [1] we found a date which works for everybody, great! It's Sunday, the 4th of December at 20:00 (UTC). CU then Mario [1] http://www.doodle.com/tbndqqynre36ax9f#table ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: IRC meeting for KDE Frameworks 5
Am Freitag 18 November 2011, 14.07:22 schrieb Giorgos Tsiapaliwkas: > On 11 November 2011 17:45, Mario Fux wrote: Morning > > In the weeks after the 20th > > have you decided the time and date for the meeting? Not yet but it strongly looks as if Sunday, the 4th of December at 20:00 (UTC) will be the date of choice. So this is a last reminder to add you to the doodle: http://www.doodle.com/tbndqqynre36ax9f#table We'll announce the final date on Sunday. > thanks Thx for your question Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Doodle for the proposed IRC meeting
Good morning As everyday this morning I started with reading several kde mailing lists and read on k-c-d again about the problems with kdelibs 4.8 vs. frameworks 5. Then I started to talk with Aaron who reminded me in looking at kde-frameworks- devel and after reading all the archived mails and subscribing I set up a doodle for the proposed IRC meeting. I hope to have taken into consideration all your availabilities and time constraints. Thus please go to the following doodle page and indicate there when you would like to have this meeting (somewhen in the two weeks after the 20th of November): http://www.doodle.com/tbndqqynre36ax9f And what about spreading this doodle link to other places or the blogosphere? Thx and I hope to contribute in one or the other way to KF5 Mario ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
