This week the Free Software Foundation's board announced that for the first time in the organization's 37-year-history, its 5,000-plus associate members will now be able to nominate and evaluate candidates for its board of directors. Under new procedures adopted by the FSF board on January 17 and summarized here, the organization will proactively engage associate members with a sufficient history of association with the FSF in the recruiting process by inviting them to suggest board nominees and then research collectively those nominees' suitability for a position on the board, including most importantly their record of commitment to free software ideals.... Following the new procedures, voting members (which include all current directors and are listed here) can start a process to recruit new directors, or a modified process to reconsider existing directors... The FSF intends to first add several new directors in 2022, utilizing these new procedures, and then begin a review of existing directors. The FSF staff and board have made this expanded engagement process a high priority and are working together to put in place the necessary infrastructure to support it, with a target to activate it within the first quarter of 2022... Voting members will review the community's nominations. A nominee may be removed from consideration if at least two voting members vote to do so without opposition from other voting members. The voting members will discuss the candidates and decide which should move forward in the process next. The FSF's associate members will then review each nominee's application, then evaluate and comment on those nominees in a private, staff-moderated discussion forum. Voting members will review this input and privately interview the finalists to assess their candidacy, ideals, and commitment to free software, then vote on their appointment.... The process is designed such that new iterations for both recruiting new directors and reviewing existing directors can be run whenever the need arises in the future. "Opening the director recruitment process to our associate members is a historic and welcome milestone for the FSF," said FSF president Geoffrey Knauth. "We are pleased to engage the free software community in attracting new talent to our leadership who will keep the freedoms.... We have worked hard to strengthen governance standards at the FSF and to create a transparent leadership recruitment process. We look forward to tackling new challenges and opportunities this year." The FSF's announcement calls the new "community engagement process" a "key result of a six-month consultant-led review designed to help make FSF governance and recruitment practices more transparent and participatory, while more systematically ensuring their commitment to the FSF's values and principles."

Read more of this story at Slashdot.

This summer the Free Software Foundation campaigns manager said that while they'll never stop aiming to be a "lighthouse" for others, "we recognize that a stance like ours can sometimes be a deterrent to people making important incremental improvements in their practices." So while they'll continue holding up the principled finish line, "Now, we're developing a clear set of steps to help support individuals in making the step-by-step improvements that they can." By supporting them in taking a step at a time, we're confident that we can help bring more people to a fully free setup than ever before. We're calling this campaign the "freedom ladder," and we need your support to help others begin climbing it. This week the Free Software Foundation's program manager explained that "Free software can only be a sustainable idea if we are continuously bringing new people into the free software community," and provided an update on their Freedom Ladder campaign: Since we recognized the need for community input at every step of the way, we started off the campaign by holding four interactive Internet Relay Chat (IRC) community meetings... In the community meetings, we once again confirmed that the "typical" free software user does not exist. It's not "one size fits all," and there are as many particular use cases as there are free software users. How do you create one single message for people that range from absolute beginners to lifelong programmers, and who span all walks of life? The answer is: you don't... As everyone's steps will be different, we need to meet people where they are. Our goal, and something important to keep in mind, is to explain the steps on the path forward in a way that allows one to step in from anywhere. We want to recognize the progress they've made so far, while still motivating them to strive towards full freedom... A clear result from our first conversations about the new campaign was the need for educational resources... We believe people's stories about the use cases of free software, much like the free software stories we collected for the thirtieth birthday of the FSF about how people got into free software, as well as on the difficulties that sometimes need to be overcome, will help us better represent and address the multitude of audiences we want to speak to. It will show that free software really is for everyone, and for everyone there is a step forward. The goal of the Freedom Ladder campaign is to deliver an ever-expanding journey towards free software. The ideal result would be a combination of resources, information, connections, and motivation for the future. This is a major undertaking and the campaigns team's main goal at present: delivering a framework we can accelerate building upon that will help people in their journey to freedom. We need to help people identify with other members of the community by delivering these stories, and letting them know that it's more than acceptable to move towards freedom gradually and incrementally... We're interested in both written statements and videos, and we would love to receive yours. You can add them to the Freedom Ladder pages in the wiki, or you can email [email protected] with your ideas. In the meantime, we will work on the infrastructure to start building this initiative and be able to integrate any information and resources we need. But we need your help... Our work on the Freedom Ladder campaign so far has been inspiring; the community meetings were fun and everything in this post is a result of the interactive, open, and welcoming nature of those events.

Read more of this story at Slashdot.

"Do you need a last-minute gift these upcoming holidays," asks the Free Software Foundation, "one that will keep on giving for the rest of the year? "Free your own digital life and the ones of those you love by opting to give them a gift that will raise their social consciousness, create more lasting cheer, and defend #UserFreedom: Gift a Free Software Foundation (FSF) associate membership!" After donating, you'll receive a code and a printable page so that you can present your gift as a physical object, if you like. The membership is valid for one year, and includes the many benefits that come with an FSF associate membership, including a USB member card [16GB and pre-loaded with the fully free GNU/Linux distribution Trisquel Live], email forwarding, access to our Jitsi Meet videoconferencing server and member forum, discounts in the FSF shop and on ThinkPenguin hardware, and many more. Looking for more gifts? You can also check out the latest FSF Giving Guide, or have a look at the great list of potential gifts our operations assistant Davis Remmel made for this very purpose! "If you're unsure what to get that special someone, or just want to treat yourself," Remmel writes, "consider our Emacs de Luxe Bundle: it has manuals, tutorials, references, mugs, shirts, and just like Emacs it includes the kitchen sink stickers. "For privacy lovers (or those who have ever uttered the word, "cryptography"), we have a NeuG USB True Random Number Generator (RNG). Your cryptographic keys will be stronger than an ox, without any need to trust your CPU's definition of "random." I recommend this RNG in conjunction with our anti-surveillance webcam stickers, which don't leave residue and can also cover microphone holes."

Read more of this story at Slashdot.

The Free Software Foundation's board "has approved and implemented two new measures designed to help make FSF governance more transparent, accountable, ethical, and responsible," according to an FSF announcement. First a Board Member Agreement "enumerates the responsibilities of board members." And there's also a Code of Ethics "that lays out principles to guide their decision-making and activities." The new measures are the first products of a six-month, consultant-led review. They formalize crucial aspects of the FSF's governance, and will guide board members to understand and embrace their responsibilities to the nonprofit's worldwide mission to promote computer user freedom. The new Board Member Agreement spells out nineteen duties and responsibilities, including minimum expectations for organizational and financial oversight, participation in board activities, the recruitment of associate members, and annual performance reviews. The Code of Ethics details thirteen specific provisions establishing how the board of directors will conduct the business affairs of the organization in good faith and with honesty, integrity, due diligence, and competence. All current board members have signed and committed to upholding the new governance standards. The agreement clarifies that Board members "do not have individual direct authority over FSF staff. Individual board members will not try to give staff instructions about what to do in their FSF work, nor try to pressure them about what to do." Board members also agree not to participate in discussions and votes where they might have a conflict of interest. "In signing this document, I understand that no quotas are being set, that no rigid standards of measurement or achievement are being formed. I have confidence that other board members will operate in good faith to carry out these agreements to the best of their ability." "The FSF has always been a steady beacon for freedom and against the widespread mistreatment of computer users," says FSF president Geoffrey Knauth in the announcement. "In the last year, the board realized that we faced a challenge and opportunity to improve our governance practices and recruit new leaders to the FSF board. I'm proud of this important step in that ongoing work."

Read more of this story at Slashdot.

"October 5 marks the official release of Windows 11, a new version of the operating system that doesn't do anything at all to counteract Windows' long history of depriving users of freedom and digital autonomy," writes Free Software Foundation campaigns manager Greg Farough. "While we might have been encouraged by Microsoft's vague, aspirational slogans about community and togetherness, Windows 11 takes important steps in the wrong direction when it comes to user freedom." Microsoft claims that "life's better together" in their advertising for this latest Windows version, but when it comes to technology, there is no surer way of keeping users divided and powerless than nonfree softwarechoosing to create an unjust power structure, in which a developer knowingly keeps users powerless and dependent by withholding information. Increasingly, this involves not only withholding the source code itself, but even basic information on how the software works: what it's really doing, what it's collecting, and how often it's snitching on users. "Snitching" may sound dramatic, but Windows 11 will now require a Microsoft account to be connected to every user account, granting them the ability to correlate user behavior with one's personal identity. Even those who think they have nothing to hide should be wary of sharing potentially all of their computing activity with any company, much less one with a track record of abuse like Microsoft... We expect Microsoft to use its tighter control on cryptography that happens in Windows as a way to impose more severe Digital Restrictions Management (DRM) onto media and applications, and as a way to ensure that no application can run in Windows without Microsoft's approval. In cases like these, it's no longer appropriate to call a machine running Windows a "personal" computer, as it obeys Microsoft more than it does its user. Indeed, it's bitterly ironic that Microsoft is calling the program that verifies a system's compatibility with Windows 11 a "PC Health Check." We counter that a healthy PC is one that respects its user's wishes, runs free software, and doesn't purposefully restrict them through treacherous computing. It would also never send the user's encryption keys back to its corporate overlords. Intrepid users will likely find a way around this requirement, yet it doesn't change the fact that the majority of Windows users will be forced into a treacherous computing scheme... Sometimes, Microsoft realizes that it can't be quite so overtly antisocial. We've commented many times before on the hypocrisy involved in saying that Microsoft "loves open source" and "loves Linux," two ways of mentioning free software without reference to freedom. At the same time, Microsoft employees do make contributions to free software, contributions which benefit many others. Yet they do not extend this philosophy to their operating system, and in the last few years, they've made an attempt to impair the ways free software makes "life better together" further by making critical functions of Microsoft GitHub rely on nonfree JavaScript and directing users toward Service as a Software Substitute (SaaSS) platforms. By attacking user freedom through Windows, and the free software community directly by means of nonfree JavaScript, Microsoft proves that it has no plans to loosen its grip on users. No program that you're forbidden to copy, modify, or share can truly bring people "together" in the way that Microsoft claims. Thankfully, and right outside the window, there's a true community of users you and your loved ones can join... Let's stop falling for the trap of chasing short-term, superficial improvements in proprietary software that may seem to make life better, and instead opt for free software, the only software that can support the best versions of ourselves. The post urges readers to sign (or renew!) their pledge not to use Windows and to help a friend install GNU/Linux, "sending Microsoft the strong message that software that subjugates its users has no place in Windows.... If you don't feel ready to take the plunge and switch entirely, you can use our resources like the Free Software Directory to find programs you can use as starting points for your free software journey." The post also has harsh words for TPM, warning that "when it's deployed by a proprietary software company, its relationship to the user isn't one based on trust, but based on treachery. When fully controlled by the user, TPM can be a useful way to strengthen encryption and user privacy, but when it's in the hands of Microsoft, we're not optimistic." And when it comes to Microsoft teams, "it seems that no Windows user can avoid it any longer.... we hope Teams' unpopularity and its newfound, unwanted place in Windows will encourage users to seek out conferencing programs that they themselves can control."

Read more of this story at Slashdot.

This week the Free Software Foundation (FSF) announced JShelter, "an anti-malware Web browser extension to mitigate potential threats from JavaScript, including fingerprinting, tracking, and data collection." The browser add-on — supported by NLnet Foundation's Next Generation Internet (NGI) Zero Privacy & Trust Enhancing Technologies fund — is currently "in development and the first release is available." This browser add-on will limit the potential for JavaScript programs to do harmful actions by restricting default behavior and adding a layer of control... Accessing cookies, performing fingerprinting to track users across multiple sites, revealing the local network address, or capturing the user's input before they submit a form are some examples of JavaScript's capabilities that can be used in harmful ways. JShelter adds a safety layer that allows the user to choose if a certain action should be forbidden on a site, or if it should be allowed with restrictions, such as reducing the accuracy of geolocation to the city area. This layer can also aid as a countermeasure against attacks targeting the browser, operating system, or hardware levels... [The extension] will ask — globally or per site — if specific native functions provided by the JavaScript engine and the Document Object Model (DOM) are allowed by the user. It will also link to an explanatory page for each function, to raise awareness of related threats. Depending on the function being addressed, the user will have the option to allow it, block it, or have it return a custom value... "Our browsers have become perhaps the most critical of tools we depend on, and yet the browser environment is far from healthy," says Michiel Leenaars, director of strategy at NLnet Foundation and coordinator of NGI Zero. "Dominant corporate behavior from a small amount of actors has been aggressively reshaping the evolution of the Web, and that is starting to wreak havoc. Despite an enormous systemic dependency, we as users have very little control over what browsers allow and share — leading to significant risk as the most powerful tools in the shed are essentially left unprotected for every casual Web site to abuse. JShelter is a great initiative to help empower us all, to help us gain better understanding and to better safeguard ourselves from obvious and otherwise unavoidable harm." The effort is part of a larger, multi-year campaign from FSF on JavaScript on the Web started in 2013, which among others includes the development of GNU LibreJS and outreach to users and developers about nonfree software inside the browser. The GNU LibreJS extension detects JavaScript web labels and assists users with running only JavaScript distributed under a free software license, according to their ethical convictions and individual preferences. "JShelter will help protect users from critical threats now, and contribute significantly to progress on the necessary longer-term cultural shift of moving away from nonfree JavaScript," said Ruben Rodriguez, former FSF chief technology officer. "This is a project I've been looking forward to for years, tired of dealing with all kinds of potential antifeatures in the browsers I use and distribute, and having to figure out some countermeasure for them with configuration changes, patches or extensions. Being able to wrap the JavaScript engine in a layer of protection is a game changer."

Read more of this story at Slashdot.

destinyland writes: A newly-released video at GNU.org shows an hour-long talk given by free software advocate Richard Stallman for the BigBlueBotton open source conference (which was held online last July). After a 14-minute clip from an earlier speech, Stallman answers questions from the audience — and the first question asked Stallman for his opinion about the AI Copilot [automated pair programming tool] developed for Microsoft's GitHub in collaboration with AI research and deployment company OpenAI. Stallman's response? There are many legal questions about Copilot whose answers I don't know, and maybe nobody knows. And it's likely some of theo depend on the country you're in [because of the copyright laws in those countries.] In the U.S. we won't be able to have reliable answers until there are court cases about it, and who knows how many years it'll take for those court cases to arise and be finally decided. So basically what we have is a gigantic amount of uncertainty. Now the next thing is, what about morally? What can I say morally about Copilot? Well the basic idea seems okay. Why shouldn't a program be able to give you hints like that? But there is one pitfall, which is that if you follow those hints, you might end up putting a substantial block of code copied from a GPL-covered program, written by someone else, or one hint after another after another after another — it adds up to a substantial amount of code, perhaps, with very little change, perhaps. And then you've infringed the GPL by releasing that code, unless your program is covered by the same versions — plural — of the GPL, in which case it would be permitted. But you might not even know that. Copilot might not tell you — it doesn't endeavor to inform you. So you're likely not to know. Which means Copilot is leading users — some of its users — into a pitfall. Well, they should fix it so it doesn't do that. But basically, what can you expect from GitHub? GitHub gives people inadequate advice about what it means to choose a license. They tell you you can choose GPL version 2 or GPL version 3. I think they don't tell you that really you could choose GPL version 2 only, or GPL version 2 or later, or GPL version 3 only, or GPL version 3 or later — and those are four different choices. They give users different permissions over the future. So it's important to make each program say clearly which choice covers it. And GitHub doesn't tell you how to do that. It doesn't tell you that you need to do that. Because the way you do that is with a licensed notice that is supposed to be in every source file. It's unreliable to put just one statement in a free program and say "This program is covered by such-and-such license." What happens if somebody copies one of the files into some other program which says it's covered by a different license? Now that program has been inaccurately mis-licensed, which is illegal and is going to mislead users. So any self-respecting — any repository that wants to be honest has to explain these things, not just tell people to make the licensing of each piece of code clear, but help users do so — make it easy. So GitHub has had this enormous problem for all of its existence, and Copilot has the similar — a basically, vaguely similar sort of problem, in the same area. It's not exactly the same problem. I don't think that copying a snippet of a few lines of code infringes any license. I think it's de minimus. But I'm not a lawyer.

Read more of this story at Slashdot.

Since most ebook readers run some version of the kernel Linux (with some even run the GNU/Linux operating system), "This puts ebook readers a few steps closer to freedom than other devices," notes a recent call-to-action in the Free Software Foundation Bulletin. But with e-ink screens and DRM-laden ebooks, "closing the gap will still require a significant amount of work." Accordingly, as we announced at the LibrePlanet 2021 conference, we've decided this year to prioritize facilitating the process for an ebook reader to reach the high standards of our Respects Your Freedom (RYF) hardware certification program, whether this means adapting an existing one from a manufacturer, or even contracting its production ourselves... The free software community has made some good strides in the area of freeing ebooks. Denis "GNUToo" Carikli has composed a page on the LibrePlanet wiki documenting the components of ebook readers and other single-board computers; this has laid the groundwork for our investigation into releasing an ebook reader, and is one of the wiki's more active projects. Also, earlier in the year, a user on the libreplanet-discuss mailing list documented their project to port Parabola GNU/Linux to the reMarkable tablet, thereby creating a free ebook reader at the same time. It's steps like these that make us feel confident that we can bring an ebook reader that respects its user's freedom to the public, both in terms of hardware and the software that's shipped with the device... If the FSF is successful in landing RYF certification on an ebook reader, which I fully believe we will be, we can ensure that users will have the ability to read digitally while retaining their freedom. It's up to all of us to make sure we have the right to read, by avoiding ebook DRM in each and every case, and celebrating free (as in freedom) resources like Wikibooks and the Internet Archive, bridging the divide between the movement for free software and the movement for free culture, empowering both readers and computer users around the globe. The article also warns that ebook DRM has gotten more restrictive over the years. "It's common for textbooks to now require a constant and uninterrupted Internet connection, and that they load only a discrete number of pages at a time... Even libraries fell victim to 'lending' services like Canopy, putting an artificial lock on digital copies of books, the last place it makes sense for them to be."

Read more of this story at Slashdot.

Version 9.4 of the GNU Compiler Collection "encompasses more than 190 bug fixes for GCC 9.3, which has been available since March 2020," reports DevClass. But they add that in addition, "Developers who want to contribute to the GNU Compiler Collection but don't feel like signing over copyright to the Free Software Foundation can get busy committing now." GCC Steering Committee member David Edelsohn informed contributors via the mailing list that the committee "decided to relax the requirement to assign copyright for all changes" to the FSF. Speaking for the committee, he wrote that the GCC project "will now accept contributions with or without an FSF copyright assignment", a practice thought of as consistent with that "of many other major Free Software projects, such as the Linux kernel". GCC "will continue to be developed, distributed and licensed" under the GPLv3, so nothing should change for those adding to the project under the old assumptions. There are those who have had troubles with that arrangement before, with Apple often cited as a popular example. They are now free to contribute utilising the Developer Certificate of Origin instead of agreeing to an FSF Copyright Assignment. A reason was not given, though the last sentence of the statement, which affirms the principles of Free Software, might give a clue. In March 2021, the committee commented on the removal of Richard Stallman from the project's steering committee website with a similar declaration... [T]hey felt like an association with Stallman was not serving the best interests of the GCC developers and user community, given that the "GCC Steering Committee is committed to providing a friendly, safe and welcoming environment for all." The Register notes that Red Hat senior principal engineer Mark Wielaard asked why there was no public discussion before making the change.

Read more of this story at Slashdot.

John Sullivan became the Free Software Foundation's Executive Director back in 2003 (at the age of 26). But now after 18 years, "I've decided to resign my position..." he tweeted Friday, "effective at the end of a transition period." "We'll be sharing further details, including information about that transition, and a few more words, in the coming days." Meanwhile, the Free Software Foundation announced Thursday that it's seeking "a principled, compassionate, and capable leader" to be its new executive director, working remotely out of their Boston office with the Foundation's current staff and board of directors. "The executive director, working with the president, is the public face of the Foundation." The FSF faces many challenges as software becomes increasingly central in the exercise of all fundamental human freedoms, including speech, association, privacy, and movement, and as software owners seek to exploit their control over us to profit at the expense of those freedoms. The executive director has a vital role in enabling the FSF to continue meeting these challenges, starting from the strong base that has been built in the last thirty-five years. The Foundation has recently reached record-high membership numbers and was awarded a perfect score from Charity Navigator, as well as its eighth consecutive four-star rating. Efforts to improve the Foundation's governance are underway. The executive director is the FSF's chief employed officer. The position reports to the president/CEO and the board of directors, and is responsible for management of all other staff, all day-to-day operations, and oversight of the Boston physical office. The successful candidate will have the opportunity to hire for additional key positions in the management team. One interesting item on their list of job responsibilities: Mentor, inspire, coordinate, and manage all FSF staff, building a culture that upholds the FSF's ideological principles and includes accountability, empathy, efficiency, and excellence A blog post on the FSF site also notes that the last month saw 11 new GNU releases. "A number of GNU packages, as well as the GNU operating system as a whole, are looking for maintainers and other assistance: please see https://www.gnu.org/server/takeaction.html#unmaint if you'd like to help."

Read more of this story at Slashdot.

Friday the Free Software Foundation awarded their coveted "Respects Your Freedom" (RYF) certification to another new product: the Free Software Wireless-N Mini Router v3 (TPE-R1300) from ThinkPenguin, Inc. Just 45 products currently hold the FSF's certification "that these products meet the FSF's standards in regard to users' freedom, control over the product, and privacy." (That is to say, they run on 100% free software, allow the installation of modified software, and are free from DRM, spyware and tracking.) The FSF writes: As with previous routers from ThinkPenguin, the Free Software Wireless-N Mini Router v3 ships with an FSF-endorsed fully free embedded GNU/Linux distribution called libreCMC. It also comes with a custom flavor of the U-Boot boot loader, assembled by Robert Call, who is the maintainer of libreCMC and a former FSF intern. The router enables users to run multiple devices on a network through a VPN service, helping to simplify the process of keeping their communications secure and private. While ThinkPenguin offers a VPN service, users are not required to purchase a subscription to their service in order to use the router, and the device comes with detailed instructions on how to use the router with a wide variety of VPN providers... "ThinkPenguin once again demonstrates a long-standing commitment to protecting the rights of their users. With the latest iteration of the Wireless-N Mini Router, users know that they'll have up to date hardware they can trust for years to come," said the FSF's licensing and compliance manager, Donald Robertson, III. Phoronix points its readers to the device's page at ThinkPenguin.com "should you be looking to build out your wireless network using the decade old 802.11n standard."

Read more of this story at Slashdot.

Long-time Slashdot reader destinyland writes: This week the Free Software Foundation posted some new answers to frequently-asked questions "as the FSF board sets about the work of strengthening the Foundation's governance structure." The FAQ notes that most of their financial support comes from individuals, and that "At this moment, the FSF has more associate members than at any time in its history," adding that it's in good financial health. (And the FAQ also reminds readers that all board members are uncompensated volunteers.) But it also confirms that a seat on the board was created for union staff "in the aftermath of the March 2021 controversy over the election of Richard Stallman to the board." And apparently in light of Stallman's return, the first question is "What are the responsibilities of a member of the FSF board?" Answer: The board of directors does not usually deal with the everyday work of the FSF, focusing instead on the long-term direction and financial stability of the Foundation, as well as the appointment of the officers. In addition, members of the board do not speak for the board or for the FSF. Outside of the deliberations of the board, they are private citizens. The right to speak for the Foundation is reserved to the president of the FSF and other FSF officers, such as the executive director. When the board does make statements, each statement is carefully deliberated. No one member has this individual authority. The FAQ also clarifies that while Stallman is also a voting board member, "Voting member meetings normally discuss only who should be on the board. They do not take up the issues that come before the board itself... When the Foundation was formed in 1985, the founders were advised that, to qualify for a tax exemption, board members should not be chosen solely by other board members. Legal counsel advised the founders that there should be two bodies with some overlap, one being the active board and the other being a body that appointed the active board. "Governance standards have since changed, and this structure is no longer required. As part of the effort to improve FSF governance, the board can consider possible changes to this overall structure." It also adds that "There is no formal term limit for a board member. Board members are evaluated by the voting members at regular intervals, and occasionally by the other directors." The last question on the list? "In addition to holding a board seat, what other role or roles does Richard Stallman play in the FSF?" The answer? "Richard Stallman frequently gives talks on free software, in his personal capacity, and, when he does so, he sells merchandise from the FSF shop, recruits volunteers for FSF and GNU, and raises donations for FSF. He is the primary author and editor of two books sold by the FSF."

Read more of this story at Slashdot.

Friday on Richard Stallman's personal web site, he posed the question: Am I Doctor Stallman? He's received 15 doctorates honoris causa — doctorates "for honor" — in the company of others whose achievements impressed him... So I was shocked to read an article which describes this as a sleazy marketing scheme, and claims that recipients of these degrees are not supposed to call themselves "Doctor." The article says that universities hand out "honorary doctorates" readily to donors who have essentially bought them, and to performing artists so that they will entertain the students at graduation... But my experience is totally different. I am not an entertainer, except for a few minutes when I don the robe and halo of Saint iGNUcius, and that is comic relief for a long, serious talk. I never donated money to the universities that gave me doctorates, nor could they expect me to. What's more, I never saw such people receive degrees along with me. The other recipients, when there were others, were likewise being honored for their work, not as a quid-pro-quo. Why this difference? My doctorates come from universities in other countries, not in the US. I conjecture that buy-a-doctorate and sing-for-your-doctorate are found in the US only. (How sad for the US...!) [O]n reading that Florida Atlantic University explicitly says that recipients of doctorates honoris causa are not permitted the title of Doctor, I began to wonder about the policies of the universities which had given me degrees, so I asked people at some of those universities about their policies. The replies were quite disparate. One said, like Florida Atlantic, that it was not permitted. Another said I should write "Dr.(h.c.)." Another said it had no objection. So it seems that I am entitled to call myself Dr. Stallman. Why do I do that? The personal reason is that these doctorates recognize decades of work for an important cause, and I am proud of them. The reason that is beyond personal is so that people who know little or nothing of my career may decide, based on the title of "Doctor", to pay a little attention to that work and that cause, which is the free software movement. That may help us defeat the totalitarian control that today's digital technology is designed to impose.

Read more of this story at Slashdot.

Richard Stallman's name has now been taken off the official web page of the steering committee for GCC, reports IT Wire. But they also note new changes this week in the management team of the Free Software Foundation: A statement from [FSF executive director John] Sullivan, deputy director John Hsieh, and chief technology officer Ruben Rodriguez on 30 March said: "As members of FSF management, we have decided to resign, with specific end dates to be determined. We believe in the importance of the FSF's mission and feel a new team will be better placed to implement recent changes in governance..." The resignations come in the wake of FSF founder Richard Stallman announcing on 19 March, during the organisation's annual LibrePlanet conference this year that he was rejoining the board. "Some of our colleagues in the FSF have decided to resign," reads an official response from the FSF. "We are grateful for the good work they have done for so long, and we will miss them. We regret losing them; we regret the situation that has motivated them to leave." Another FSF board member also resigned last week. Meanwhile, Ars Technica reports the FSF has created a new seat on the board to be filled by someone from FSF union staff, with acting FSF President Geoffrey Knauth calling it "an important step in the FSF's effort to recognize and support new leadership, to connect that leadership to the community, to improve transparency and accountability, and to build trust. There is still considerable work to be done, and that work will continue." Ars Technica adds: The elephant in the room that the FSF's remaining board members seem determined to ignore is the continued presence of Stallman himself — who, along with the rest of the FSF board, will soon need to undergo its new "transparent, formal process for identifying [members] who are wise, capable, and committed to the FSF's mission."

Read more of this story at Slashdot.

Early Friday the principal author of GNU Privacy Guard (the free encryption software) warned that version 1.9.0 of its cryptographic library Libgcrypt, released January 19, had a "severe" security vulnerability and should not be used. A new version 1.9.1, which fixes the flaw, is available for download, Help Net Security reports: He also noted that Fedora 34 (scheduled to be released in April 2021) and Gentoo Linux are already using the vulnerable version... [I]t's a heap buffer overflow due to an incorrect assumption in the block buffer management code. Just decrypting some data can overflow a heap buffer with attacker controlled data, no verification or signature is validated before the vulnerability occurs. It was discovered and flagged by Google Project Zero researcher Tavis Ormandy and affects only Libgcrypt v1.9.0. "Exploiting this bug is simple and thus immediate action for 1.9.0 users is required..." Koch posted on the GnuPG mailing list. "The 1.9.0 tarballs on our FTP server have been renamed so that scripts won't be able to get this version anymore."

Read more of this story at Slashdot.

Long-time Slashdot reader lee1 shares his recent article from LWN: On November 26, version 6.1 of GNU Octave, a language and environment for numerical computing, was released. There are several new features and enhancements in the new version, including improvements to graphics output, better communication with web services, and over 40 new functions... In the words of its manual: GNU Octave is a high-level language primarily intended for numerical computations. It is typically used for such problems as solving linear and nonlinear equations, numerical linear algebra, statistical analysis, and for performing other numerical experiments. Octave is free software distributed under the GPLv3. The program was first publicly released in 1993; it began as a teaching tool for students in a chemical engineering class. The professors, James B. Rawlings and John G. Ekerdt, tried to have the students use Fortran, but found that they were spending too much time trying to get their programs to compile and run instead of working on the actual substance of their assignments... Octave became part of the GNU project in 1997... Octave, written in C, C++, and Fortran, soon adopted the goal and policy of being a fully compatible replacement for MATLAB. According to the Octave Wiki, any differences between Octave and MATLAB are considered to be bugs, "in general", and most existing MATLAB scripts will work unmodified when fed to Octave, and vice versa... When octave is started in the terminal it brings up an interactive prompt. The user can type in expressions, and the results are printed immediately.

Read more of this story at Slashdot.

All the videos have now appeared online for the talks at this year's virtual EmacsConf 2020, "the conference about the joy of Emacs, Emacs Lisp, and memorizing key sequences." And among them are an appearance by 67-year-old Richard Stallman, reminding the audience he'd created the first Emacs editor in 1976 "with some help from Guy Steele," then created GNU Emacs in 1984. Stallman was there to tell the history of the GNU Emacs Lisp Package Archive (and the licensing issues involved) — and how it's ultimately led to the creation of the NonGNU ELPA. "The fundamental plan of NonGNU ELPA is that we won't ask for copyright assignments for those packages, so we won't be able to put them into core Emacs, at least not easily — but we will have some control over how we distribute them. We can put any package into NonGNU ELPA as long as its free software. "If we like it, we can set up that way for users to get it. We can put the package in exactly as it is, if there's no problem at all with it. We can make an arrangement with the package's developers to work on it with us and maintain it directly for distribution by NonGNU ELPA. But if they are not interested, we can put it in ourselves, and if we need to make any changes we can do so. So NonGNU ELPA is not meant to be just a way that others can distribute their packages. Its meant at least in a minimal, technical sense to work with GNU Emacs, and we will make changes if necessary so that it works smoothly with GNU Emacs... "The idea is to have a single Git repository where you can download various packages, but they won't be maintained there. Each of those packages will be copied automatically from some other place, probably some other people have the right access to work on it. This way we can avoid giving a gigantic number of people access to it. "So far NonGNU ELPA is just a plan. We need people to implement the plan, so if you'd like to help, please write to me. I think this is a very important step for progress, and it's got to be implemented. Thanks, and happy hacking." Stallman provided a status update on NonGNU ELPA as part of the 46-minute Q&A that followed. "The creation of it has started. There's an archive and you can download packages. There's a repository to put it in... Still working out the procedures, how to make the arrangements with developers, etc." But he also answered questions on other topics. Some highlights: Q: Which distro of GNU/Linux do you use? guix? or something else? RMS: Trisquel. Q: If you knew that you would get hit by a bus tomorrow, say because of a fortune-teller, what would you leave behind in terms of advice for stewardship of Emacs and its future? RMS: Focus on keeping the community strong in defending freedom. If given the choice to have more people developing the software or defending the software, choose the latter. Guard your soul carefully... :P Q: Would you mind sharing your Emacs configuration files? RMS: Configuration files are personal and will not be shared.

Read more of this story at Slashdot.

"Today, on October 4th, the Free Software Foundation (FSF) celebrates its thirty-fifth year of fighting for software freedom," announces a blog post at FSF.org: Our work will not be finished until every computer user is able to do all of their digital tasks in complete freedom — whether that's on a desktop, laptop, or the computer in your pocket. The fight for free software continues, and we wouldn't be here without you. To celebrate, we have a full week of announcements and surprises planned starting today, and we will end in an online anniversary event featuring both live and prerecorded segments this Friday, October 9th, from 12:00 EDT (16:00 UTC) until 17:00 EDT (21:00 UTC). We'd love for you to join in celebration of this amazing community by submitting a short (two-minute) video sharing your favorite memory about free software or the FSF, and a wish for the future of software freedom. We'll be collecting the videos all week and airing a selection during the birthday event on October 9th... If you are able to, please make a donation of $35 or more to help keep the fight for user freedom going another 35 years, we'll send you a commemorative pin... We're another year older, but that doesn't mean we're slowing down our efforts to bring software freedom to users around the globe. Stay tuned for more information on how we plan to ring in the FSF's next year, and the vital role each one of us plays in ensuring free software's success for the future. We hope that you'll be able to take part in our festivities this week! The announcement suggests 10 different ways to celebrate, which include: Try a fully free distribution of GNU/Linux, which can be run "live" without making any permanent changes to your computer's hard drive. Take an hour to follow our Email Self-Defense Guide, and learn how to opt out of bulk surveillance . Download and experiment with one of the oldest parts of the GNU operating system, the GNU Emacs text editor. Try the tutorial by launching the editor and typing Ctrl-h + t (C-h t), or see if you can make it through some of the games included with Emacs, such as Alt-x (M-x) dunnet or M-x tetris. Make the commitment to replace one nonfree program that you use with one that respects your freedom, such as using LibreOffice instead of Microsoft Office. Petition the administrators of your favorite Web site to free the proprietary JavaScript lurking on their page that many users run and download without ever realizing it.

Read more of this story at Slashdot.

LWN.net re-visits the emacs-devel mailing list, where the Emacs 28 development cycle has revived discussions about how to make the text editor more "modern" and attractive to new users: A default dark theme may not be in the future, leading one to think that there may yet be hope for the world in general. But there does seem to be general agreement that Emacs could benefit from a better, more centralized approach to color themes, rather than having color names hard-coded throughout various Elisp packages. From that, a proper theme engine could be supported, making dark themes and such easily available to those who want them... Another area where Emacs is insufficiently "modern", it seems, has to do with keyboard and mouse bindings. On the keyboard side, users have come to expect certain actions from certain keystrokes; ^X to cut a selection, ^V to paste it, etc. These bindings are easily had by turning on the Cua mode, but new users tend not to know about this mode or how to enable it. Many participants in the discussion said that this mode should be on by default. That, of course, would break the finger memory of large numbers of existing Emacs users, who would be unlikely to appreciate the disruption. Or, as Richard Stallman put it: It is not an option to change these basic key bindings to imitate other, newer editors. It would create a different editor that we Emacs users would never switch to. It is unfortunate that the people who implemented the newer editors chose incompatibility with Emacs.... The situation with mouse behavior is similar; as several participants in the discussion pointed out, users of graphical interfaces have come to expect that a right-button click will produce a menu of available actions. In Emacs, instead, that button marks a region ("selection"), with a second click in the same spot yanking ("cutting") the selected text. Many experienced Emacs users have come to like this behavior, but it is surprising to newcomers. The right mouse button with the control key held down does produce a menu defined by the current major mode, but that is evidently not what is being requested here; that menu, some say, should present global actions rather mode-specific ones. Stallman suggested offering a "reshuffled mode" that would bring the context menu to an unadorned right-button click, and which would add some of the expected basic editing commands there as well. This would be relatively easy to do, he said, since mouse bindings are separate from everything else. Besides, as he noted, the current mouse behavior was derived from "what was the standard in X Windows around 1990"; while one wouldn't want to act in haste, it might just be about time for an update. Other proposed changes involved "discoverability," including the default enabling of various modes, although to incorporate them into GNU Emacs "would often require the author to sign copyrights over to the Free Software Foundation, which is not something all authors are willing to do..."

Read more of this story at Slashdot.