Re: [Musicpd-dev-team] libcue licensing problem
Hi Max, Max Kellermann wrote: Avuton forwarded a mail from Svend Sorensen to me: On Wed, Apr 22, 2009 at 10:53 AM, Svend Sorensen sv...@ciffer.net wrote: Did you give permission to change the license to libcue[1]? I did not. Jochen Keil sent me an email asking if he could relicense parts of cuetools under a BSD license, but I never got around to replying. That's nice that he found the time to answer Avuton.. Until today (23.04.09) i did not receive *any* mail from Svend. What's wrong with the old license? While this is basically your own personal problem GPL is to restrictive *imho*. http://www.freebsd.org/doc/en/articles/bsdl-gpl/article.html You didn't respond to my former questions regarding that license change Honestly, i can't recall those.. code from MPD on 30th of April (7 days from now), unless you can convince me that your code is legal. I'm tempted to say go for it, then take down everything on sf and leave everyone else in the dust. I've got my stuff here, why should i care to share it? I'm really upset about this. What is going on here behind my back? However, there is a modified COPYRIGHT notice as well as some updated copyright notifications in several files in the git repo on sf.net. Please have a look and tell me if you are fine with it. Jochen signature.asc Description: OpenPGP digital signature -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
Re: [Musicpd-dev-team] libcue licensing problem
On 2009/04/23 14:47, Jochen Keil jochen.k...@gmail.com wrote: I'm tempted to say go for it, then take down everything on sf and leave everyone else in the dust. I've got my stuff here, why should i care to share it? I'm really upset about this. What is going on here behind my back? Nothing is going on behind your back. I asked you half a dozen of times on IRC to clean up your licensing problem, and others also pointed out that you're violating Svend's copyright. Since you didn't respond to any of those, Avuton asked Svend instead. Please understand that you must not change the license of somebody else's work without his permission. Getting no response simply means no! That's not a valid excuse. However, there is a modified COPYRIGHT notice as well as some updated copyright notifications in several files in the git repo on sf.net. Please have a look and tell me if you are fine with it. 'Copyright (c) 2009, Jochen Keil' marks code which is released as 2-clause BSD license You added your name to all source files, even those which you didn't touch at all (e.g. time.c). The license of those files isn't obvious, but it should be. Suggestion: add the full BSD license to all files which you created (e.g. rem.c), and all others stay 100% GPL according to COPYING, even if you modified them. Max -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
Re: [Musicpd-dev-team] libcue licensing problem
Hi Max, Max Kellermann wrote: Nothing is going on behind your back. I asked you half a dozen of times on IRC to clean up your licensing problem, and others also pointed out that you're violating Svend's copyright. Since you didn't respond to any of those, Avuton asked Svend instead. i don't want to argue about that with you but i told everyone that i sent an email and never got a reply. I don't understand why Svend replied to Avuton instead of me, doesn't he like my email address? Please understand that you must not change the license of somebody else's work without his permission. Getting no response simply means no! That's not a valid excuse. Since the copyright hasn't been updated for almost two years now, i felt more like this is abandoned code. What this implies legally is of my scope as i'm not a lawyer. It might well have been a mistake to just relicence it to BSD but i had to make a decision. What's more important: i never ever wanted to steal someones work nor label it as mine. That's why i imported the whole cuetools repo, made the work to transparently move every source file and keep all the copyright notices where appropriate. 'Copyright (c) 2009, Jochen Keil' marks code which is released as 2-clause BSD license You added your name to all source files, even those which you didn't That's why i added this: (and only with this notice alone, if there is an additional copyright notice about Svend Sorensen, GPL applies!) touch at all (e.g. time.c). That's been a careless copy and paste error. I fixed it now, thanks for your remark. Suggestion: add the full BSD license to all files which you created (e.g. rem.c), and all others stay 100% GPL according to COPYING, even if you modified them. That's a good idea and i applied it. One last thing i'd like to add. There have been a lot of modifications done by me. Some may be trivial but some are quite under the hood and fixed severe mistakes. If it weren't for the lexer (tokenizer) or the parser (grammar) i might have written this as well myself. Unfortunately there is not much room left for writing the tokenizer/grammar in a different way in lex/yacc. All in all i'm not happy with GPL. I don't want to make a fuss here though since i think that it's more important to share the work so that everyone can benefit from it. All the updated copyright notices are now on git at sf.net. If there are no objections anymore i'll repackage the latest release asap. Jochen signature.asc Description: OpenPGP digital signature -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
Re: [Musicpd-dev-team] mpd patch | mpd discussion about stickers
On Tue, Apr 14, 2009 at 3:05 PM, Max Kellermann m...@duempel.org wrote: On 2009/04/14 15:38, Sébastien Houzé sebastien.ho...@gmail.com wrote: Ok, but I run many mpd processes, this implies running many mpdscribble too... is a playlog_file option in mpd.conf better ? Think about some analogy with Apache accesslog and errorlog. Logging can be optionnal this way, and why not loggin format configurable (data, IP, song) like in Apache. Hmm, I'm not comfortable with that idea, because this is a very specific feature request which can be solved with a client. Might be more difficult for you because you're running multiple MPD instances, but you can use the same init script for starting one mpdscribble per MPD instance. Any other opinions on the mailing list? My very late two cents. If I'm way off about something, just correct me - these are just thoughts. I'm not really sure whether it's best for this feature to end up in a client or in MPD. Good to keep MPD slim, but also good to not have to make sure a client is running to get your statistics. (I realize there's a wiki page that states that MPD is not a statistics server.) In any case, it seems like the most basic thing we'd be looking for out of this is play counts, and maybe a last played and skip count sort of thing. Note that none of these require full logging anyway - just some incrementing and such. They also wouldn't require a huge amount of code to implement, so it's not entirely unreasonable to think about putting them into MPD. Either way, assume that we're going to get some statistics generated. But how are they stored and accessed? This seems like a great use for the sticker database to me. There are already suggestions in the documentation to store ratings; why not these basic statistics? This makes them easily available to multiple clients (important! don't want to add mpdscribble-client communication), and also makes them easier to backup/transfer. If we go the client route, I don't see a huge problem with requiring one instance of mpdscribble per instance of mpd, though of course it's less convenient. In any case, avoiding the logging method seems good - it's overkill, and only available locally. Besides, the idle commands give a great way to get just the information you need. (Incidentally, I've been wondering about suppressing status commands from clients in the logfile - I'd like to run in verbose all the time just in case a bug crops up, but the vast majority of the content is just ncmpc asking for status. I know I can kludge it locally, and also that idle commands will decrease command volume, but that's not trivial.) As long as we're talking about improving the sticker database functionality, and clients are beginning to use it, I think there's one thing that needs to be considered: how do you preserve stickers when moving/renaming files? I know we don't want mpd to actually manage the files, but maybe there should be some way to let it know about a rename? Or do clients have to do a sticker list for the original then several sticker sets for the new? The world would of course be a better place if tagging were standardized and this information could just go along with the file, but we've got to make do somehow. Jeffrey -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
