This is off topic, but important to open software developers & supporters
Brazil may be punished because government supports free software...
IIPA is willing to put Brazil in the black list of copyrights because
Federal & State governments support free software. According to IIPA, by
supporting free software it shows Brazil has an inadequate policy
against violations on intellectual property.
IIPA... & its gangster supporters must be denounced now. Not only to
local authorities but also to international organizations like the ICO.
Full article (in Portuguese) can be found here: http://bit.ly/cxbqJO
Whilst cleaning up some recently adopted orphans, I discovered that
perl-Nmap-Parser has been tagged with the wrong license since August
2008. Upstream changed the license from GPLv2+ to MIT sometime back in
2007 and I've just corrected it in rawhide (and will do on all
branches too in the near future). Presumably this isn't a problem for
anyone since it's less restrictive now.
for all maintainers of packages which BuildRequire qt4-devel (or qt-devel, but
the versioned virtual Provides is preferred): please, when you plan to push
updates for your packages, ALWAYS CHECK what version of Qt your package got
built against and DO NOT PUSH your update to stable before that version of Qt
goes stable! A package built against Qt 4.6 WILL NOT WORK AT ALL with Qt
4.5!!! (This is always the case, Qt is backwards- but not forwards-
Currently, buildroot overrides for Qt 4.6 are in effect (intermittently, as Qt
4.6 can and will be untagged from the buildroot on request to build updates
which need to go out soon, but we need it in the buildroot to build anything
related to KDE 4.4), so a package built now CANNOT go to stable before the big
Qt 4.6 / KDE 4.4 / SIP 4.10 update does. If you need to push an urgent update,
please ask Rex Dieter (rdieter on Freenode IRC) or another rel-eng member to
get the stuff out of the buildroot for a moment, and follow the instructions
given on IRC. If your update is not urgent, I recommend just not pushing it
out to stable before the big Qt/KDE/SIP update.
NOT FOLLOWING THOSE INSTRUCTIONS WILL LEAD TO YOUR PACKAGE BEING BROKEN IN THE
STABLE UPDATES!!! YOU HAVE BEEN WARNED!
I am sorry if I sound abrasive, but we already had at least 2 packages which
were broken due to this issue (just for 4.6, there were more such issues with
previous upgrades) and it looks like our previous devel-announce message was
not clear enough. Please double-check before you hit that "push to stable"
button! Thanks in advance.
We will look into using some less dangerous process (special build tags?) for
future Qt updates as this is just not working, but for now please be careful.
devel-announce mailing list
Talking points are key highlights of the new release. They should be
compelling, but they will not necessarily be comprehensive. There are
different types of talking points for different types of people:
general desktop users/everyone, developers, and sysadmins. For the
Fedora 13 cycle, we will also have talking points to address some of
the Spins. They are meant to provide a short, effective answer to the
question, "What cool stuff is in the latest release of Fedora?"
Each cycle, the Marketing team compiles a short list of approximately
three talking points for each of these audiences for the upcoming
release. For Fedora 13, they're found here:
If you have a talking point that you feel meets the criteria found on
the talking points SOP page at
https://fedoraproject.org/wiki/Talking_points_SOP, add it to the the
table on the F13 page with supporting information. Please make your
contributions and changes on the wiki page, so that the Marketing team
can efficiently capture and consider your input.
The Marketing team will make final adjustments to the list of talking
points at their meeting on February 23, which will be announced on the
marketing list and is open to everyone. If you are interested in
attending the meeting, the agenda, location, and time details can be
found at http://fedoraproject.org/wiki/Marketing_meetings. Following
the meeting, the finalized list of talking points will be announced,
and posted to https://fedoraproject.org/wiki/Fedora_13_Talking_Points.
We welcome you to participate in the process!
devel-announce mailing list