Re: Brasero improvements over the 2.26 release cycle
Hi all, I thought it would be a good thing to recap all that was done to address the remaining issues that were raised regarding brasero. Libbrasero-media API was improved and should now be well documented. Most of all, Libbrasero-media was relicenced to GPL 2 + restrictions based on rhythmbox licence. There is still one file under GPL 2 which is the file providing an Open Solaris backend conditionally compiled. If someone can think of a better licence I can change it (only not GPL3). Nautilus extension was updated to match the progress of ncb (basically an image in the button and hints). All patches below were updated, and the one that adds a totem plugin was included. > [1]-http://bugzilla.gnome.org/show_bug.cgi?id=536732 > [2]-http://bugzilla.gnome.org/show_bug.cgi?id=565383 > [3]-http://bugzilla.gnome.org/show_bug.cgi?id=567286 Regards, Philippe ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
On Fri, 2009-01-16 at 18:38 +0100, Philippe Rouquier wrote: > - One last thing, if I want to relicence brasero as a whole what about > artwork (and translation, and documentation) that was submitted? > Should I require the permission from the people who did this (great) > work? Otherwise, I will of course at least warn the submitters. Documentation, at least, is a completely separate product, and its license has no bearing on the license of any applications or libraries. As a tangent, though, if the Libbrasero-media Reference Manual contains substantial code samples that you expect people to use in their own applications, you should add an exception to the FDL to allow this. Something along the lines of "Code samples in this document may be reused freely with no restrictions." Luis Villa could probably advise something better. It would be nice to have a standard FDL+exception in Gnome. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Philippe: As Luis said I'm not against relicencing the library (and even the whole of brasero). It's just I wasn't aware of the issue at stake since I don't care much about licencing (which turns out to be a mistake). Regarding libbrasero-media, it shouldn't take long as I wrote all of the code but the two backends for : - FreeBSD but the copyright holder agreed to the licence change - OpenSolaris and I'm waiting for the answer. Given the size of the latter file, I can easily rewrite it if need be but I don't think it'll be necessary. A few questions: - is using the same licence and wording as rhythmbox OK? If Brasero uses GStreamer plugins directly, then GPL+exception would be good for the the Brasero application. LGPL seems a better choice for libraries that are intended to be used by multiple applications. If you use LGPL, for such libraries an exception is not needed. Brian ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Le vendredi 16 janvier 2009 à 14:06 +0100, Vincent Untz a écrit : > Le vendredi 16 janvier 2009, à 12:25 +, Luis Medinas a écrit : > > Right now Brasero is currently re-licensing the library again, we > > already contacted the people involved asking about the change. There > > were some bits in the library that Philippe re-wrote (that used NCB > > code) to be compatible with SJ and RB. > > Awesome! > > Vincent > As Luis said I'm not against relicencing the library (and even the whole of brasero). It's just I wasn't aware of the issue at stake since I don't care much about licencing (which turns out to be a mistake). Regarding libbrasero-media, it shouldn't take long as I wrote all of the code but the two backends for : - FreeBSD but the copyright holder agreed to the licence change - OpenSolaris and I'm waiting for the answer. Given the size of the latter file, I can easily rewrite it if need be but I don't think it'll be necessary. A few questions: - is using the same licence and wording as rhythmbox OK? - should brasero remain GPL v2 (just temporarily of course I need to check who sent patches and there were not that many unfortunately/fortunately your choice) while libbrasero-media is GPL v2 + exceptions would it be a problem? If not, should I simply add the new licence to libbrasero-media for the time there is this discrepancy between brasero and the library? - One last thing, if I want to relicence brasero as a whole what about artwork (and translation, and documentation) that was submitted? Should I require the permission from the people who did this (great) work? Otherwise, I will of course at least warn the submitters. - still if I wanted to relicence brasero as a whole, do I need to ask for the permission of the people who submitted patches fixing problems (crash, things not working properly in general, ...) ? Thanks in advance. Regards, Philippe ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Le vendredi 16 janvier 2009, à 12:25 +, Luis Medinas a écrit : > Right now Brasero is currently re-licensing the library again, we > already contacted the people involved asking about the change. There > were some bits in the library that Philippe re-wrote (that used NCB > code) to be compatible with SJ and RB. Awesome! Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
On Fri, 2009-01-16 at 12:29 +0100, Vincent Untz wrote: > Le jeudi 15 janvier 2009, à 10:59 +0100, Josselin Mouette a écrit : > > Le lundi 12 janvier 2009 à 19:18 +, Bastien Nocera a écrit : > > > > - Split Brasero into a library (available on trunk) named > > > > libbrasero-media that is being documented (devhelp) and re-arranged so > > > > we can deliver a stable API. > > > > > > The library isn't usable in Rhythmbox or sound-juicer, as it conflicts > > > with their license (GPLv2 vs. GPLv2 + exception). > > > > Well, they are not incompatible per se, it’s just that the exception > > cannot apply if rhythmbox/sound-juicer links to this library. > > > > For the record, what is making this exception necessary? I don’t think > > any non-GPL-compatible GStreamer plugins are required for the normal > > operation of rb or s-j. > > Let's make it clear: from what I understand, it seems it's a blocker in > Bastien's mind. It is a blocker for me too. We can have some long > discussion about all that, but in the end, it might cause difficulties > that we don't have with the ncb library (eg, Bastien rejecting the > rhythmbox plugin). > Right now Brasero is currently re-licensing the library again, we already contacted the people involved asking about the change. There were some bits in the library that Philippe re-wrote (that used NCB code) to be compatible with SJ and RB. So we still expect to have all this done (of course with Bastien help to review our patches :) ) before the deadline. We have been working harder to accomplish all new features and deadlines. Luis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Le jeudi 15 janvier 2009, à 10:59 +0100, Josselin Mouette a écrit : > Le lundi 12 janvier 2009 à 19:18 +, Bastien Nocera a écrit : > > > - Split Brasero into a library (available on trunk) named > > > libbrasero-media that is being documented (devhelp) and re-arranged so > > > we can deliver a stable API. > > > > The library isn't usable in Rhythmbox or sound-juicer, as it conflicts > > with their license (GPLv2 vs. GPLv2 + exception). > > Well, they are not incompatible per se, it’s just that the exception > cannot apply if rhythmbox/sound-juicer links to this library. > > For the record, what is making this exception necessary? I don’t think > any non-GPL-compatible GStreamer plugins are required for the normal > operation of rb or s-j. Let's make it clear: from what I understand, it seems it's a blocker in Bastien's mind. It is a blocker for me too. We can have some long discussion about all that, but in the end, it might cause difficulties that we don't have with the ncb library (eg, Bastien rejecting the rhythmbox plugin). Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Josselin: Le jeudi 15 janvier 2009 à 11:12 -0600, Brian Cameron a écrit : No distribution can ship any popular non-free GStreamer codecs if the GStreamer based programs link in any GPL code without the exception. Well first of all, I find this interpretation of the GPL rather extreme. A GStreamer plugin is a derived work of GStreamer, but it is not a derived work of rhythmbox (unless rb as shipped actually requires it for normal operation, of course). However I understand that people want to be on the safe side and adopt the most conservative interpretation. I am not a lawyer, so I can't really say with any authority; but it seems unclear whether clause 7 of the GPL is in effect if the non-free code in question is a plugin and the application can be used without it. Clause 7 states: For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. Regardless, the GNOME community has spent a lot of time making sure that the licenses clearly avoid any confusion in this area by adding the GPL license exception. This seems a good thing and something we shouldn't just abandon without careful consideration. So, with the exception a distro or mobile device OS using GNOME/GStreamer could purchase a MP3 audio license and include that with their GStreamer based-engine. They could also purchase a patent license for a free MP3 implementation. It’s not as if there weren’t any such implementations. Right, although things get more complicated if the GPL is involved since it is a violation of the GPL use this license and distribute code which requires royalty fees. Even if, as you suggest, using a plugin framework like GStreamer works around this, it wouldn't solve the problem for other GPL'ed programs like VLC or mplayer that link such non-free code directly into the application. Considering how important mobile is to the GNOME community these days, and how important it is to play things like mp3 audio files or YouTube videos on mobile devices, I would think this would be pretty important issue and concern. I don’t like spreading statements implying the assumption that free software-based h264 or MP3 playback is illegal. This is what Fraunhoffer and the MPEG consortium would like to be true, but please don’t assume they are right. It's not inappropriate as long as the free license being used doesn't disallow such usage. Clause 7 of the GPL makes it (at the very least) complicated to use this license to distribute such non-free code. Note that the GPL restrictions are only concerning distribution. I don't believe there is any problem with a person who owns a media license building their own code to play non-free media. However, such free and non-free code may not be distributable together without violating the terms of the GPL. You are right, though, that we shouldn't assume. Perhaps it would be good to get some authoritative opinion about this, so that we don't waste time bickering, adding license exceptions if they are needless, etc. Brian ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Le jeudi 15 janvier 2009 à 11:12 -0600, Brian Cameron a écrit : > No distribution can ship any popular non-free GStreamer codecs if > the GStreamer based programs link in any GPL code without the exception. Well first of all, I find this interpretation of the GPL rather extreme. A GStreamer plugin is a derived work of GStreamer, but it is not a derived work of rhythmbox (unless rb as shipped actually requires it for normal operation, of course). However I understand that people want to be on the safe side and adopt the most conservative interpretation. > So, with the exception a distro or mobile device OS using > GNOME/GStreamer could purchase a MP3 audio license and include that with > their GStreamer based-engine. They could also purchase a patent license for a free MP3 implementation. It’s not as if there weren’t any such implementations. > Considering how important mobile is to the GNOME community these days, > and how important it is to play things like mp3 audio files or YouTube > videos on mobile devices, I would think this would be pretty important > issue and concern. I don’t like spreading statements implying the assumption that free software-based h264 or MP3 playback is illegal. This is what Fraunhoffer and the MPEG consortium would like to be true, but please don’t assume they are right. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Josselin: Le lundi 12 janvier 2009 à 19:18 +, Bastien Nocera a écrit : - Split Brasero into a library (available on trunk) named libbrasero-media that is being documented (devhelp) and re-arranged so we can deliver a stable API. The library isn't usable in Rhythmbox or sound-juicer, as it conflicts with their license (GPLv2 vs. GPLv2 + exception). Well, they are not incompatible per se, it’s just that the exception cannot apply if rhythmbox/sound-juicer links to this library. Considering how much work has gone into adding this exception to rhythmbox, totem, and songbird; it would be a shame to toss that work out. I don't believe sound-juicer yet has the exception. I believe the upstream community is working on it. http://bugzilla.gnome.org/show_bug.cgi?id=513615 http://live.gnome.org/SoundJuicerRelicense For the record, what is making this exception necessary? I don’t think any non-GPL-compatible GStreamer plugins are required for the normal operation of rb or s-j. No distribution can ship any popular non-free GStreamer codecs if the GStreamer based programs link in any GPL code without the exception. So, with the exception a distro or mobile device OS using GNOME/GStreamer could purchase a MP3 audio license and include that with their GStreamer based-engine. If we link in code which removes that exception, then distros lose this ability. This drives people towards using other operating systems where they can distribute with popular non-free support built in. Considering how important mobile is to the GNOME community these days, and how important it is to play things like mp3 audio files or YouTube videos on mobile devices, I would think this would be pretty important issue and concern. Brian ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Le lundi 12 janvier 2009 à 19:18 +, Bastien Nocera a écrit : > > - Split Brasero into a library (available on trunk) named > > libbrasero-media that is being documented (devhelp) and re-arranged so > > we can deliver a stable API. > > The library isn't usable in Rhythmbox or sound-juicer, as it conflicts > with their license (GPLv2 vs. GPLv2 + exception). Well, they are not incompatible per se, it’s just that the exception cannot apply if rhythmbox/sound-juicer links to this library. For the record, what is making this exception necessary? I don’t think any non-GPL-compatible GStreamer plugins are required for the normal operation of rb or s-j. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
2009/1/13 Philippe Rouquier : > > Le lundi 12 janvier 2009 à 19:18 +, Bastien Nocera a écrit : > > On Sun, 2009-01-11 at 01:19 +, Luis Medinas wrote: >> Hi! >> >> After the previous discussion about proposing Brasero for GNOME 2.26 the >> Brasero has made lot's of improvements based on some feedback from the >> community. >> >> So right now we released two releases during the 2.25 cycle and added >> this important features: >> >> - Nautilus extension (based on the current ncb), there are some >> applications that put the files on burn:/// with this extension Brasero >> replaces ncb and Burn the media. > > You copied some old code, you have no icons, or hints. > > Yes indeed; it turns out I missed the hint addition to have the brasero > 'version' uptodate. > As for the icon, the problem is going to be fixed. You probably didn't > install brasero in /usr/ or /usr/local which I admit shouldn't be a reason > to miss the icons. > >> - Split Brasero into a library (available on trunk) named >> libbrasero-media that is being documented (devhelp) and re-arranged so >> we can deliver a stable API. > > The library isn't usable in Rhythmbox or sound-juicer, as it conflicts > with their license (GPLv2 vs. GPLv2 + exception). > > As I commented in the bug, I'll rewrite the bits that didn't come from > brasero and then I'll relicence the whole of it. But it seems that this was > the case for nautilus-cd-burner and sound-juicer/rhythmbox so it doesn't > worsen things here. > >> - Lot's of bug fixes (Can be seen on NEWS and Changelog) >> - Submitted a Totem[1] plugin, Rhythmbox[2] plugin and Sound-Juicer[3] >> work to replace ncb by brasero using the new library in addiction to >> other applications already using Brasero (Banshee, exaile etc...). > > The Rhythmbox plugin isn't good enough to replace the current ncb based > one, as it lacks integration (it writes a playlist file, and launches > brasero itself). > > yes, but on the other hand it does the job just like the previous plugin did > and reduces the code size of the plugin as brasero handles transcoding of > audio all by himself which allows on the fly burning. (Note: it's not a > regular playlist but a brasero project that is written). > I would like to congrat the Brasero supporters for their work during the proposal of the module, they did a big amount of work to adapt things towards the GNOME standards. With such a vibrant community behind it (which I don't think is being the case for the rest of our current burning related code), I would like to express a big +1 for inclusion even if their work is not quite there yet. > Cheers, > > Philippe > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > -- Un saludo, Alberto Ruiz ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Le lundi 12 janvier 2009 à 19:18 +, Bastien Nocera a écrit : > On Sun, 2009-01-11 at 01:19 +, Luis Medinas wrote: > > Hi! > > > > After the previous discussion about proposing Brasero for GNOME 2.26 the > > Brasero has made lot's of improvements based on some feedback from the > > community. > > > > So right now we released two releases during the 2.25 cycle and added > > this important features: > > > > - Nautilus extension (based on the current ncb), there are some > > applications that put the files on burn:/// with this extension Brasero > > replaces ncb and Burn the media. > > You copied some old code, you have no icons, or hints. Yes indeed; it turns out I missed the hint addition to have the brasero 'version' uptodate. As for the icon, the problem is going to be fixed. You probably didn't install brasero in /usr/ or /usr/local which I admit shouldn't be a reason to miss the icons. > > - Split Brasero into a library (available on trunk) named > > libbrasero-media that is being documented (devhelp) and re-arranged so > > we can deliver a stable API. > > The library isn't usable in Rhythmbox or sound-juicer, as it conflicts > with their license (GPLv2 vs. GPLv2 + exception). > As I commented in the bug, I'll rewrite the bits that didn't come from brasero and then I'll relicence the whole of it. But it seems that this was the case for nautilus-cd-burner and sound-juicer/rhythmbox so it doesn't worsen things here. > > - Lot's of bug fixes (Can be seen on NEWS and Changelog) > > - Submitted a Totem[1] plugin, Rhythmbox[2] plugin and Sound-Juicer[3] > > work to replace ncb by brasero using the new library in addiction to > > other applications already using Brasero (Banshee, exaile etc...). > > The Rhythmbox plugin isn't good enough to replace the current ncb based > one, as it lacks integration (it writes a playlist file, and launches > brasero itself). > yes, but on the other hand it does the job just like the previous plugin did and reduces the code size of the plugin as brasero handles transcoding of audio all by himself which allows on the fly burning. (Note: it's not a regular playlist but a brasero project that is written). Cheers, Philippe ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
On Sun, Jan 11, 2009 at 3:19 AM, Luis Medinas wrote: [snip - nice things said about Brasero] I recently ran a poll [1] on debian-user mailing list, and the favourite disc burner was: * K3b (14 votes) * wodim/cdrecord (6 votes) * Brasero (4) * Gnomebaker (2) With this much goodness, K3b might finally be stopped from monopolising the GUI burner market. Thanks much for your work. [1] http://lists.debian.org/debian-user/2008/12/msg00031.html -- my place on the web: floss-and-misc.blogspot.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
On Sun, 2009-01-11 at 01:19 +, Luis Medinas wrote: > Hi! > > After the previous discussion about proposing Brasero for GNOME 2.26 the > Brasero has made lot's of improvements based on some feedback from the > community. > > So right now we released two releases during the 2.25 cycle and added > this important features: > > - Nautilus extension (based on the current ncb), there are some > applications that put the files on burn:/// with this extension Brasero > replaces ncb and Burn the media. You copied some old code, you have no icons, or hints. > - Split Brasero into a library (available on trunk) named > libbrasero-media that is being documented (devhelp) and re-arranged so > we can deliver a stable API. The library isn't usable in Rhythmbox or sound-juicer, as it conflicts with their license (GPLv2 vs. GPLv2 + exception). > - Lot's of bug fixes (Can be seen on NEWS and Changelog) > - Submitted a Totem[1] plugin, Rhythmbox[2] plugin and Sound-Juicer[3] > work to replace ncb by brasero using the new library in addiction to > other applications already using Brasero (Banshee, exaile etc...). The Rhythmbox plugin isn't good enough to replace the current ncb based one, as it lacks integration (it writes a playlist file, and launches brasero itself). > - Followed and completed Gnome Goals in time. > - Consistent releases with the current unstable release cycle. > > With this we archived almost all feedback made by the community we > always expect to improve GNOME and would be glad to help. > In the future we expect to make the library better documented, add > language bindings, support for more formats etc... > Thanks for all the people involved on the feedback, help tested, > submitted bugs and translate. The Rhythmbox plugin isn't integrated enough to replace the original one. The Totem will probably be merged after the last round of updates. I'm still concerned about the reasons why brasero didn't use libnautilus-burn and extend on top of it, instead of starting their own library. Cheers ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
On Sun, 2009-01-11 at 11:35 +0100, Josselin Mouette wrote: > > - Lot's of bug fixes (Can be seen on NEWS and Changelog) > > - Submitted a Totem[1] plugin, Rhythmbox[2] plugin and Sound-Juicer[3] > > work to replace ncb by brasero using the new library in addiction to > > other applications already using Brasero (Banshee, exaile etc...). > > This way we can completely deprecate libnautilus-burn, I guess. The only > remaining thing will be the python bindings. We have two applications > using them: pybackpack and serpentine. > Yes we are planning the bindings too, it seems almost every application using ncb is patched so we can safely now replace ncb. > Thanks a lot for the work. I doubted that brasero could replace n-c-b > that soon, and you proved me wrong. > Thanks for your feedback too, it helped to archive all this goals. Luis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Hi, Le samedi 10 janvier 2009 à 21:04 -0500, Martin Meyer a écrit : > A couple question: > > Will the refactoring into library and app (the separation) be ready > and stable for the 2.28 release? libbrasero-media which probes for, retrieves information about drives/media and provides locking,... will be ready for 2.26. I will complete the API before the 19th of January (with doc hopefully). The said API will be quite similar to the one of NCB plus some more functions needed for some specific advanced task (multisession in particular, session/track information, CD-TEXT reading). It also provides an additional widget to select media (not drives) which is more useful in some situations. The burning part is still in brasero and needs some more work; it should be split for 2.28 (if brasero gets included of course). In the mean time our lastest work on brasero allows it to be quite flexible when spawed (especially through the use of projects) so at the moment this solution should cover all the needs. Of course an exposed burning backend will allow for more things. > What are the plans for versioning? Will you jump to a 2.28 release, or > stay with your current version scheme for a while? > I think we would stick to GNOME one which means that 0.9.x would become 2.26. Regards, Philippe ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Le dimanche 11 janvier 2009 à 01:19 +, Luis Medinas a écrit : > - Nautilus extension (based on the current ncb), there are some > applications that put the files on burn:/// with this extension Brasero > replaces ncb and Burn the media. Very nice! Do you have a screenshot? > - Split Brasero into a library (available on trunk) named > libbrasero-media that is being documented (devhelp) and re-arranged so > we can deliver a stable API. > - Lot's of bug fixes (Can be seen on NEWS and Changelog) > - Submitted a Totem[1] plugin, Rhythmbox[2] plugin and Sound-Juicer[3] > work to replace ncb by brasero using the new library in addiction to > other applications already using Brasero (Banshee, exaile etc...). This way we can completely deprecate libnautilus-burn, I guess. The only remaining thing will be the python bindings. We have two applications using them: pybackpack and serpentine. Thanks a lot for the work. I doubted that brasero could replace n-c-b that soon, and you proved me wrong. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
Sorry, I did mean 2.26 there... On Sat, Jan 10, 2009 at 9:04 PM, Martin Meyer wrote: > It sounds like you're aiming to make Brasero a pretty all-encompassing > burning library/system. That sounds awesome - I really like the idea > of having just one library responsible for that desktop-wide. > > A couple question: > > Will the refactoring into library and app (the separation) be ready > and stable for the 2.28 release? > > What are the plans for versioning? Will you jump to a 2.28 release, or > stay with your current version scheme for a while? > > I've used Brasero a few times now and it seemed pretty nice to me. > Thanks for all the work you guys put into it! > > Cheers, > Martin > > On Sat, Jan 10, 2009 at 8:19 PM, Luis Medinas wrote: >> Hi! >> >> After the previous discussion about proposing Brasero for GNOME 2.26 the >> Brasero has made lot's of improvements based on some feedback from the >> community. >> >> So right now we released two releases during the 2.25 cycle and added >> this important features: >> >> - Nautilus extension (based on the current ncb), there are some >> applications that put the files on burn:/// with this extension Brasero >> replaces ncb and Burn the media. >> - Split Brasero into a library (available on trunk) named >> libbrasero-media that is being documented (devhelp) and re-arranged so >> we can deliver a stable API. >> - Lot's of bug fixes (Can be seen on NEWS and Changelog) >> - Submitted a Totem[1] plugin, Rhythmbox[2] plugin and Sound-Juicer[3] >> work to replace ncb by brasero using the new library in addiction to >> other applications already using Brasero (Banshee, exaile etc...). >> - Followed and completed Gnome Goals in time. >> - Consistent releases with the current unstable release cycle. >> >> With this we archived almost all feedback made by the community we >> always expect to improve GNOME and would be glad to help. >> In the future we expect to make the library better documented, add >> language bindings, support for more formats etc... >> Thanks for all the people involved on the feedback, help tested, >> submitted bugs and translate. >> >> Cheers >> Luis >> >> >> [1]-http://bugzilla.gnome.org/show_bug.cgi?id=536732 >> [2]-http://bugzilla.gnome.org/show_bug.cgi?id=565383 >> [3]-http://bugzilla.gnome.org/show_bug.cgi?id=567286 >> >> ___ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/desktop-devel-list >> > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Brasero improvements over the 2.26 release cycle
It sounds like you're aiming to make Brasero a pretty all-encompassing burning library/system. That sounds awesome - I really like the idea of having just one library responsible for that desktop-wide. A couple question: Will the refactoring into library and app (the separation) be ready and stable for the 2.28 release? What are the plans for versioning? Will you jump to a 2.28 release, or stay with your current version scheme for a while? I've used Brasero a few times now and it seemed pretty nice to me. Thanks for all the work you guys put into it! Cheers, Martin On Sat, Jan 10, 2009 at 8:19 PM, Luis Medinas wrote: > Hi! > > After the previous discussion about proposing Brasero for GNOME 2.26 the > Brasero has made lot's of improvements based on some feedback from the > community. > > So right now we released two releases during the 2.25 cycle and added > this important features: > > - Nautilus extension (based on the current ncb), there are some > applications that put the files on burn:/// with this extension Brasero > replaces ncb and Burn the media. > - Split Brasero into a library (available on trunk) named > libbrasero-media that is being documented (devhelp) and re-arranged so > we can deliver a stable API. > - Lot's of bug fixes (Can be seen on NEWS and Changelog) > - Submitted a Totem[1] plugin, Rhythmbox[2] plugin and Sound-Juicer[3] > work to replace ncb by brasero using the new library in addiction to > other applications already using Brasero (Banshee, exaile etc...). > - Followed and completed Gnome Goals in time. > - Consistent releases with the current unstable release cycle. > > With this we archived almost all feedback made by the community we > always expect to improve GNOME and would be glad to help. > In the future we expect to make the library better documented, add > language bindings, support for more formats etc... > Thanks for all the people involved on the feedback, help tested, > submitted bugs and translate. > > Cheers > Luis > > > [1]-http://bugzilla.gnome.org/show_bug.cgi?id=536732 > [2]-http://bugzilla.gnome.org/show_bug.cgi?id=565383 > [3]-http://bugzilla.gnome.org/show_bug.cgi?id=567286 > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
