Fri, 30 Aug 2024 19:33:36 -0500
Update the plugins page for the new process
This includes defining the process and providing a template for a new issue to
add new plugins. I did go through and audit `No IRC /WHO` so we had at least
one validated entry.
Testing Done:
Ran `npm run hugo:server` locally and verified the page worked and checked the new links.
Bugs closed: NEST-53
Reviewed at https://reviews.imfreedom.org/r/3450/
--- title: Philosophy and Goals date: 2019-08-22T03:45:43.000Z weight: 200 replaces: [] lastmod: 2019-08-22T03:45:43.000Z --- ## Philosophy Pidgin has a number of design goals that we consider our philosophy. For example: ### Protocol/Service Agnosticism We believe that once all your accounts are configured in Pidgin, it shouldn't matter what protocol or service is being used when messaging a contact. The purpose of using Pidgin is to communicate; the communication itself is more important than the gritty details of how it's happening. This is exemplified as "I want to talk to John" versus "I want to talk to John on his XMPP account at jabber.org." It's our belief that "I want to talk to John" is our users' expectation, and we aim to make Pidgin that simple. ## Project Goals Pidgin, as a project, has overarching goals for the future of the project: ### Protocols/Services The main protocol-related goal for the Pidgin project is to remove support for the proprietary services from the libpurple source code and have them as separate plugins. This protects the core project from some legal issues and allows much faster response to protocol-level changes if the owners of a given service make changes that break the plugin. There is no specific timeline to do this; we simply aim to do it at some point in the future.