|
|
|
Posted
7 days
ago
Hi there, while we've been working very hard on the next Amarok feature release, the 2.8, we also haven't forgot the majority of our users using the stable versions. Welcome Amarok 2.7.1, a very close relative of 2.7.0 with just a couple of
... [More]
very important bug fixes. The 2.7.1 is also an opportunity for Arch Linux to package it correctly. :-)
Don't fear that we've made just 8 commits since 2.7.0. In fact, we've made over 300 by 25 different people! Look forward for better transcoding, ASX playlist and Opus audio format support, improved MusicBrainz tag guessing and improvements of existing features all over the place for Amarok 2.8.0. [Less]
|
|
Posted
7 days
ago
by
myriam_rs
The Amarok Team has discovered a very unpleasant bug in QtWebkit ↔ GStreamer interaction that made continuous playing almost impossible, due to frequent crashing. We decided to work around it in our code and take it as an opportunity to release a
... [More]
bugfix version. It contains a couple of other fixes we deemed important.
This version only contains some very essential fixes and changes compared to 2.7.0:
A modification in handling MusicBrainz ID tags was needed to avoid problems with falsely duplicate tracks.
We fixed a weird behaviour when the "Use Music Location?" question is answered "Yes" on the first run.
We now have worked around the QtWebkit ↔ GStreamer bug that caused frequent crashes on track start; this happened if the Wikipedia applet tried to load a page containing an audio tag.
The database is now also created if the home directory contains non-ASCII characters.
The Nepomuk Collection now also shows track numbers.
Note that this is just a very small subset of bug fixes that already went to upcoming Amarok 2.8, which is being baked behind the scenes and which will improve many existing features. We kept 2.7.1 as minimal as possible (with just 8 commits on top of 2.7.0) so that it is a safe and pleasant update for everyone. If you want to get a taste of what Amarok 2.8 will be, you are encouraged to use our development version.
As usual we welcome as many testers as possible so this version will make its entry as fast as possible in the distributions updates. See the full article for download options and a full change log.
Weiterlesen [Less]
|
|
Posted
26 days
ago
by
The Amarok Team
It took some time, but it is finally here: the brand new Windows build of Amarok 2.7.0 The KDE on Windows developers worked hard to publish KDE 4.10.2, so we delayed this release to make sure you can get the newest KDE as well. This
... [More]
should work on XP, Vista, Windows 7 and Windows 8.
Since there are a few limitations in a Windows build, some features you know from the Linux version are not available:
the Nepomuk Collection plug-in is not available
no CD playback support
the features requiring Gstreamer (Equalizer, Moodbar) are not available as this version uses the VLC backend
Since we can't ship ffmpeg on that build, there is no transcoding either
Disclaimer: since most of our developers don't even have a Windows installation to test this build, we rely on you, dear Amarok lover, to help us testing and to report any bugs you might find. Please report them to our bugtracker and don't forget to specify the version and the exact Windows platform.
If you have filed bugs for the previous versions on Windows, please check if you can reproduce them with the 2.7.0 version as well, we would be very grateful for your help with that:)
Weiterlesen [Less]
|
|
Posted
about 1 month
ago
… then here are some tips Show us you are bright… and do your homework: Read the documentation We can’t be there for you 24/7, so don’t expect to be spoon-fed information you can look up in
... [More]
documentation available online. While you will probably never hear a RTFM from us (we are polite), we do expect coders to be able to document themselves. You will be given a lot of links to documentation to read in the welcoming mail, so please do that: read and learn!
Use your search engines and try to look up things on your own before asking.
In general, not doing some search on your own before asking questions is frowned upon, as it shows lazyness on your behalf.
Don’t send private mail to potential mentors, use the mailing list
KDE is a community and we work on our projects in a collaborative effort. While there is usually one mentor assigned to an idea, there are co-mentors and we do coordinate our work in the mailing list. If you want to work with us, please do use the right channels for that. It also greatly enhances the probability to get an answer, as there are more eyes to see your mail. Private mails from unknown people can easily get lost in a filter, especially if they are badly formatted and sometimes not even have a subject line… *cough*
Don’t ping people in IRC, and don’t open Queries without even asking if it is OK
There are some basic rules in IRC, all of which you can find online (search for “IRC Guidelines KDE”), so randomly pinging people you have never met or opening queries without asking beforehand are considered rude and are frowned upon. If you have an urgent matter, use the mailing list, not everybody is online all the time and not necessarily in your timezone. And if you ask a question on IRC, stick around so we can actually answer, don’t just leave after a few minutes. IRC is not for the impatient:
Be patient!
We are usually very much occupied with our every day work and life and simply can’t be at your service just because you are there NOW. We do our best to answer your requests and questions in a timely fashion, but don’t be impatient, that is not making things go faster. Your request is usually not as urgent as YOU might think it is. Did you try to search online and in the documentation on your own? No? Why not?
Remember: there is life out there, and that is often in the way of answering your requests as fast as you would like it to happen.
Know what you are going to work on
You want to be a GSoC student but you don’t know your basic 101 of coding? Sorry, that is not for you, then. Consider applying for SoK instead. You need to at least have some basic knowledge of the business you want to get involved in. So if you want to participate, show us you know what you are talking about. The best way to show us is to do some coding beforehand, we have plenty of junior jobs with low hanging fruits.
You can’t choose what project is the best for you?
We can’t do that either, sorry, as we usually only just met you. Just telling us what coding language you know about is not helping either, as we assume that to be part of your 101 skills box. You are the one who needs to decide what to work on, how and in what time frame. You want to participate, then make your mind up, study, read, use the software you are planning to work on, that is the best way to find out if it is suitable for you. And do look at the proposals made by other students in previous years, Lydia did send a nice mail to the kde-soc@kde.org mailing list detailing that. You are not on that list? Well then what are you waiting for?
I am NOT detailing links here on purpose: the various mailing lists of KDE can easily be found online, and there have been dozens of mails from me or Lydia or other people with links and instructions that can all be looked up in the archives, most of that in the last 2 months which will help you narrow the search. These mails contain all you need to know
All of the above applies mainly to GSoC, but also to OPW and SoK to some extend. Don’t recognize these terms? Are you sure you read the kde-soc@kde.org mailing list? [Less]
|
|
Posted
about 1 month
ago
I’m happy to announce that KDE has been accepted as a mentoring organization in Google Summer of Code 2013. This is our 9th consecutive year. Congrats to all accepted organizations, and a big thanks to everyone who helped to make this happen
... [More]
for KDE!
This year KDE will also participate in the Free and Open Source Outreach Program for Women, an internship opportunity running almost simultaneously with Google Summer of Code, from June to September. Please note that while the Outreach Program for Women shares many goals and methods with Google Summer of Code, the two programs are not related. Unlike Google Summer of Code, the Outreach Program for Women also allows non-coding contributions. For more information about applying, see KDE’s Outreach Program for Women wiki page.
KDE will also be hosting Season of KDE 2013, with more information to come in the following weeks. Season of KDE is expected to start later in the summer, around the Google Summer of Code midterm.
Students. Now that you have a list of accepted organizations, it’s time to start working on your proposal. The KDE community maintains an ideas page which is an excellent starting point, and don’t forget to check our student guidelines. Also, last year I published an article with some tips on how to structure your proposal, you might find it useful.
You can come up with your own idea or base your proposal on something from the ideas page, but either way it’s very important that you get feedback from the team you wish to work with well before the submissions deadline. If you have general questions about getting involved with KDE as a Google Summer of Code student you’re welcome to ask on our IRC channel #kde-soc on Freenode, or join the mailing list kde-soc@kde.org. For questions about a specific idea please contact the relevant team (subproject) directly.
Finally, make sure to keep an eye on the official Google Summer of Code timeline – those deadlines are always closer than they seem
Mentors. Now that we know that KDE has been accepted, it’s time to get ready to mentor some students. If you wish to be a mentor your next steps should be:
subscribe to kde-soc-mentor@kde.org,
sign up on http://www.google-melange.com and apply as a mentor for KDE,
contact one of the admins to approve your requests.
For questions you can reach the admin team in #kde-soc on Freenode or at kde-soc-mentor-owner@kde.org.
And most importantly, in the following weeks you’ll be contacted by prospective students with questions and feedback requests for their proposals. It might take a bit of time and you might get questions with very obvious answers. Please be patient and keep an eye on the timeline
[Less]
|
|
Posted
2 months
ago
Outreach Program For Women Logo. CC-BY-SA - artists: Máirín Duffy, Liansu Yu, Hylke Bons KDE will – for the first time this year – participate in the “Outreach Program for Women”. This was originally
... [More]
started by GNOME, but has also other participating organisations like Wikimedia, Mozilla, Fedora and others.
With KDAB as our sponsor we will be offering one internship. This is in no way only limited to coding, but includes user experience design, graphic design, documentation, web development, marketing, translation and other types of tasks needed to sustain a Free Software project.
The deadline for task submission is March 27. Please all in the KDE Community, suggest suitable tasks on our wiki page and volunteer to mentor. Feel free to contact me or Lydia for more information.
Prerequisites for application: Any woman who has not previously participated in an Outreach Program for Women or Google Summer of Code internship is welcome to apply, provided she is available for a full-time internship during this time period. This program is open to anyone who identifies as a woman regardless of gender presentation or assigned sex at birth. Genderqueer and genderfluid people are welcome to apply.
The application deadline for candidates is already on May 1st, while the program runs from June 17 to September 23. [Less]
|
|
Posted
3 months
ago
It’s this time of the year again, where we express our love for what and whom we like: This year I want to express my personal thanks to the kmail developers for the awesome work during the last year, the KDE sysadmins
... [More]
for being so fast and efficient,
the Amarok team for their love and dedication,
the Sconcho developer for being so responsive and making my knitting pattern editing so easy,
the whole FSFE team for their hard work on protecting our Freedom!
Keep up the good work, folks [Less]
|
|
Posted
4 months
ago
It was a very busy End of Year again: Amarok 2.7 is out! While the code-name “A Minor Tune” would suggest it to be an average release, it is in fact one of the most polished we ever did. 473 bugs closed, 17 feature requests
... [More]
granted and not less than 100 commits that fixed bugs directly. Rock On!
We also ship a fully updated handbook for this version, with new screenshots. For that we had some help from the Google Code-In students who helped updating the handbook. Amarok also moved it’s wikis to the KDE infrastructure with the help of several students, you can now find the Amarok wiki at http://community.kde.org/Amarok
Google Code-In also saw several students doing some quality work for Amarok, testing the 2.7 beta release as well as with the current git source, and updating the testing instructions on the wiki while doing so. A new Team page also has seen the light thanks to Code-In work: http://amarok.kde.org/en/team
Over all: great work from the Amarok Team and the Google Code-In students, thank you!
PS: the color theme is ‘Evening Lilac’
[Less]
|
|
Posted
4 months
ago
by
The Amarok Team
A New Year, a new Amarok! The Amarok Team is proud to present the new Amarok 2.7, codenamed "A Minor Tune". This version comes with the following brand new major features, developed during last year's Google Summer of
... [More]
Code:
Preliminary version of the Nepomuk Collection plug-in
Statistics Synchronization between collections and with Last.fm
While originally scheduled before the end of 2012, our code monkeys started to enjoy fixing bugs much more during the holiday period, so we gave them a few weeks more to let them shine. It turned out great:
The File Browser's behavior and appearance was greatly improved
Audio CD playback was resurrected (at least with recent phonon-gstreamer)
We haven't been lazy even before this, as this release also comes with an impressive amount of other bug fixes: a total of over 470 bugs were closed since the 2.6 release, of which exactly 100 are direct bug fixes (with a commit link). Over 15 feature requests were granted directly or indirectly as well.
We are also proud to ship a completely updated handbook, with updated screenshots and help pages for the new features. In this context our thanks goes to the Google Code-In students who helped in updating the handbook. Several Code-In students also helped to test Amarok extensively, both with the 2.7 beta1 release and the development version. The students also helped in moving two old wiki instances to a new server, verifying articles were currently relevant with working links. In total, 10 students worked on a total of 47 tasks for Amarok: great work indeed!
-
See full article for download options
Weiterlesen [Less]
|
|
Posted
4 months
ago
In case you don't know it yet, we've just released Amarok 2.7! This release is called A Minor Tune, partially because the list of new features isn't pages-long (but you still get statistics synchronization and preliminary Nepomuk integration). But I
... [More]
believe it will be remembered for its level of polish and stability - many components like audio CD playback and file browser have been made much more solid, and the number of user-reported problems that were closed since 2.6 approaches stunning 500.
On the other hand, due to the lack of manpower there are still components that deserve much more love than they currently get. One such example is the MTP player plug-in, but don't fear, we (or I) have plans with it. Contributions in any form (patches being best) are of course more than welcome. [Less]
|
Copyright
©
2013
Black Duck Software, Inc.
and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a
Creative Commons Attribution 3.0 Unported License
. Ohloh
®
and the Ohloh logo are trademarks of
Black Duck Software, Inc.
in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.