Hi Richard. I double checked and Sean is already an admin for the Emacs group on Savannah.
Please let me know if something else is needed. Corwin 612-217-1742 612-695-4276 (signal) [email protected] On Fri, Jan 16, 2026 at 9:22 PM Richard Stallman <[email protected]> wrote: > > If you get this email, would you please ack? > And please add him as an Emacs maintainer. > > ------- Start of forwarded message ------- > Content-Type: text/plain; charset=Utf-8 > From: Richard Stallman <[email protected]> > To: Sean Whitton <[email protected]> > In-Reply-To: <[email protected]> (message from Sean > Whitton on Thu, 25 Dec 2025 11:06:46 +0000) > Subject: I hereby appoint you one of the maintainers of GNU Emacs > Reply-To: [email protected] > Message-Id: <[email protected]> > Date: Fri, 26 Dec 2025 23:52:11 -0500 > > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > I hereby appoint you as a comaintainer of GNU Emacs. > Thanks for volunteering. > > Being a package maintainer is a relationship between you personally > and the GNU Project. The maintainer or maintainers are the ones who > take the overall responsibility for the work done on the package, on > behalf of the GNU Project. The maintainers generally make the specific > decisions about the package, following the project's general standards > and principles. Once in a rare while, perhaps once every few years, > the GNU Project may make a concrete decision about the package -- > about features or implementation methods for the code, or about text > in accompanying files -- which you as maintainer should implement. > > If you recruit others to contribute to the package (and some packages > have hundreds of contributors), they work under your supervision. You > can delegate some of your authority to them, but you can also take it > back. Please make sure they don't come to think that you have ceded > your authority to them and that they no longer have to follow your > directions. > > The GNU Project will sometimes need to talk with you, sometimes > privately, so please make sure we know a personal email address which > you read frequently. We normally publish these email addresses in the > Free Software Directory. We would also like to know other ways to get > in touch with you if email fails; we do not give them out. > > If you ever want to step down as maintainer, or would like someone > else to replace you, please talk with [email protected] about it. > When a package has no maintainer, we need to know about the problem so > we can look for a new one. The program remains a GNU package > unless/until the GNU project decides to drop ties with it. > > Likewise, if you think someone else should join you as co-maintainer > or take over from you as maintainer, please suggest that to us, since > we will need to establish a relationship with that person. A person > cannot become a GNU package maintainer except by being appointed by > the GNU Project. > > Your appointment as maintainer is provisional at first. We'll make > your appointment full and permanent when we see that you're doing the > job. Usually that means we see that you've made a release properly, > with the changes that the next release ought to have. However, if > making a proper release involves a lot of work, and will therefore > take a long time, we could appoint you full maintainer when we see you > have made a good start on the job. > > Please tell us the first time you're about to make a release, so we > can guide you on doing it properly following our conventions. > > The GNU maintainer information in https://www.gnu.org/prep/maintain/ > describes a lot of procedures for GNU maintainers. It also > describes who you can ask for various kinds of support or advice. If > you encounter a situation where it isn't clear what to do, you can > also ask [email protected], which is a list of a few other GNU > maintainers who have offered to answer questions for new maintainers. > > We will add you to the gnu-prog mailing list, a moderated list for > announcements to GNU maintainers. We will also add you to the > gnu-prog-discuss list, which can be used for discussion among GNU > maintainers, but whether to stay on the list is up to you. > > We strongly recommend using ftp.gnu.org to make distributions > available. Please see the GNU maintainers guide for the procedure, > https://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html. > When that is set up, you'll be able to do uploads yourself. If you > want to also distribute the package from a site of your own, that is > fine. To use some other site instead of ftp.gnu.org is acceptable, > provided it allows connections from anyone anywhere. > > Please write or update the web pages about the program, to put in > https://www.gnu.org/software/PROGNAME. These pages should be the > main web site for the program, and they should really have the > information for users, not just a link to another site; please use > https://www.gnu.org/software/PROGNAME whenever you give out the URL > for the home page of the program. Please don't set up a "site for the > program" anywhere else--if you want to do work on additional web pages > about the program, please put them on www.gnu.org. > > (It is ok to put pages that address developers-only topics on another > site, and likewise for pages that access databases.) > > In writing the web pages, please follow the style guidelines in > https://www.gnu.org/server/fsf-html-style-sheet.html. See also > https://www.gnu.org/prep/maintain/html_node/Web-Pages.html. > > We ask that you register your package on Savannah, at least to maintain > your package's web pages. This is independent of where the actual > program sources are hosted (although we encourage you to use Savannah > for that too). This makes it easy to update the web pages, since you > will have access to a CVS repository for the web pages and can update it > as you like. Using Savannah will help the GNU Project in other ways, > too. To set this up, visit https://savannah.gnu.org/. > > Please also write an entry or a change for the page > https://www.gnu.org/people/people.html, and mail that to > [email protected]. Note that we don't want to talk about > proprietary software, so if you have worked on any, please don't > mention it here. Your entry can include a link to your home page > provided it fits our usual criteria for what we link to. > > Please update the program's entry in our Free Software Directory. See > https://www.gnu.org/help/directory.html#adding-entries for help. > > Mailing lists: Your package should already have a mailing list > [email protected] for reporting bugs. If not, please create it--see > https://www.gnu.org/prep/maintain/html_node/Mail.html for the details of > creating mailing lists. > > Some GNU programs with many users have another mailing list, > [email protected], for people to ask other users for help. If > your program has many users, you should create such a list for it. > For a fairly new program, which doesn't have a large user base yet, it > is better not to bother with this. > > Please post announcements of new releases of the program to > [email protected]. Include a brief description of the program so people > can tell whether they are interested in using it. The announcement > should mention the web pages on www.gnu.org, and say where to get > releases, normally ftp.gnu.org. > > You can also send announcements to a special list [email protected] > for your program if you think that is warranted. (This list should be > moderated.) > > Please also mention release announcements in the news feed of the > savannah project site, <https://savannah.gnu.org/projects/PROGNAME>. > The news feeds from the GNU project are aggregated at > <https://planet.gnu.org/>. > > For more details about writing and publicizing announcements, please see > https://www.gnu.org/prep/maintain/html_node/Announcements.html. > > For details on all policies and recommendations for GNU packages, > please see the GNU maintainers information, at > https://www.gnu.org/prep/maintain/, and GNU coding standards, at > https://www.gnu.org/prep/standards/. > > For the basic ideas of GNU and free software, please read these essays: > http://www.gnu.org/gnu/the-gnu-project.html > http://www.gnu.org/philosophy/free-sw.html > http://www.gnu.org/philosophy/categories.html > http://www.gnu.org/philosophy/compromise.html > http://www.gnu.org/philosophy/words-to-avoid.html > http://www.gnu.org/gnu/linux-and-gnu.html > http://www.gnu.org/gnu/gnu-linux-faq.html > http://www.gnu.org/philosophy/open-source-misses-the-point.html > > new-gnu people, could you please enter Sean Whitton in > gnuorg/maintainers and add him to the gnu-prog lists? > > Savannah hackers, could you please ensure that Sean Whitton is an > administrator > of the project on Savannah (if there is one)? > > - -- > Dr Richard Stallman (https://stallman.org) > Chief GNUisance of the GNU Project (https://gnu.org) > Founder, Free Software Foundation (https://fsf.org) > Internet Hall-of-Famer (https://internethalloffame.org) > ------- End of forwarded message ------- > > -- > Dr Richard Stallman (https://stallman.org) > Chief GNUisance of the GNU Project (https://gnu.org) > Founder, Free Software Foundation (https://fsf.org) > Internet Hall-of-Famer (https://internethalloffame.org) > > >
