Slashdot videos: Now with more Slashdot!
BerliOS was founded 10 years ago as one of the first repositories in Europe. It was
developed and maintained by Fraunhofer FOKUS. As an European, non-proprietary
project BerliOS pursued the goal to support the various open-source players and provide
a neutral mediator function. In 2011 over 4710 projects have been hosted on BerliOS,
with 50,000 registered users and over 2.6 million file downloads each month. We are
proud that with BerliOS we have brought the idea of an OSS repository to Europe.
Meanwhile, the concept has prevailed and there are many good alternatives.
Unfortunately, as a research institute Fraunhofer FOKUS has only few opportunities to
operate a repository like BerliOS. Such a project will only work with a follow-up financing,
or with sponsors or partners taking over the repository. In the field of OSS this is a
difficult undertaking. In a recent survey the community indicated some support in funds
and manpower which we would like to thank you for. Unfortunately, the result is not
enough to put the project on a sustainable financial basis. In addition the search for
sponsors or partners was unsuccessful.
Open Source is understood by Fraunhofer FOKUS as a paradigm for future-oriented
intelligent use of IT. It hurts us all the more that we are forced to discontinue the hosting
for BerliOS by 31.12.2011.
* As a developer, you should export your BerliOS project into another repository.
* On our site you will find a guide on how to get your project data out of the portal and
migrate it in a different platform, see
Fraunhofer FOKUS has a strong commitment to open source and interoperability, and is
involved in numerous successful OSS projects. The institute focuses on the development
of quality standards for open source software and in particular on the technical, semantic
and organizational interoperability between open source software components and
between open source and closed source software. Example of our OSS activities including
our management of the German Competence Center QualiPSo.
We thank all who have used BerliOS over the years.
This email was sent from developer.berlios.de.
To change your email receipt preferences,
please visit the site and edit your account via the
"Account Maintenance" link.
Direct any questions to email@example.com, or reply to this email."
Link to Original Source
(This message may be seen as inflammatory, but I assure you that it is just my opinion and not particularly anybody else---I don't speak for the projects on which I participate).
I am not a developer of VLC, but I am part of the LAME team (that MP3 encoder that a good amount of people use). I see similar problems regarding LAME as those described by the VLC team: lack of continuous power and resources.
Some users just magically think that "oh, this program won't exist anymore, so let's use this other one". The sad thing here is that they are shortsighted in the fact that they, by doing nothing (just receiving the programs), are not giving the incentive for the projects.
What about if the proposed alternative dies a few days from now? The amount of alternatives is finite.
Not only that, but the major players out there all share the same codebase: there are "incestuous" (in a good sene of the word) relations with VLC, xine, and mplayer: the all use, to some extent or another (well, in some cases, to the full extent) some common libraries: ffmpeg, libmp3lame, theora, vorbis, dirac, x264 and so on.
Usually, also, the players also send some feedback to the people writing the libraries and, without them, the libraries would not be as good as they are. And the feedback that developers provide is, not infrequently, in form of patches, or constructive suggestions. Some users, like the one above, just cares less and, honestly, where would you just "grab the extra codec" if they all, come, essentially, from the first place?
If you didn't know, perhaps it is a good reminder to put here that people from the VLC project developed the nice libdvdcss library, which benefited xine and mplayer, while people in the other projects have directly or indirectly benefited the others.
I would not like to have the "Linux desktop" mainstream with a "community" with a person that doesn't want a community. For people that are more altruistic (and that show it, instead of just playing in slashdot all day), I am open to a more open talk.
[Gee, from what I wrote the above, it seems like if I only saw Linux---I actually value the other Unix-like operating systems as much].
I guess that what I meant to say here is: "Talk is cheap. Show me the code. Don't wish the death of what you may proudly use and not even know".
Regards, Rogério Brito.
The current JPEG format, widely used by almost every page to show "potographic" images (and many other applications) shows poor compression rates while a given "quality ratio" is specified. Also, it performs poorly when low "quality ratios" are selected.
The JPEG2000 format is a more efficient format based on Wavelet Transforms rather than Discrete Cosine Transforms to compress data. The "quality ratios" can be selected very low and the images still show good quality, among many other features that JPEG does not have (like being a lossy compression format with support for transparency).
(As a side note, you can check which image formats your browser supports at browserspy.dk).
There are implementations of the JPEG2000 format that are Free/Libre Open Souce but not widely used. The perceived reason for this has the nature of a "chicken-and-egg" problem: no browsers support it (apart from Apple's Safari, with the use of Quicktime), and no users have still employed it, leading to little support in browsers.
There is a very long-lived bug in Mozilla's bugzilla system (almost a decade ago) that asked support for the "new" file format to be supported.
Yesterday, this long-standing feature request was closed with the "WONTFIX" tag, citing the the "chicken-and-egg" problem. This has caused many replies from both the developer and user community, and even a comment from Mark Shuttleworth stating "We'd consider a patch for the Ubuntu builds of Firefox." and Mike Hommey, one of the principal maintainers of Iceweasel for Debian."
Link to Original Source