pidgin/nest
+6
-0
+5
-0
+19
-3
+11
-2
+36
-0
+4
-0
+46
-0
+84
-0
+1
-1
+5
-0
+11
-0
+++ b/config.toml Tue Jan 15 21:55:18 2019 +0000
@@ -10,3 +10,9 @@
+++ b/content/_index.es.md Tue Jan 15 21:55:18 2019 +0000
@@ -0,0 +1,5 @@
+++ b/content/_index.md Tue Jan 15 21:55:18 2019 +0000
@@ -1,6 +1,22 @@
+Pidgin is a chat program which lets you log in to accounts on multiple chat networks simultaneously. This means that you can be chatting with friends on MSN, talking to a friend on Google Talk, and sitting in a Yahoo chat room all at the same time.
+Pidgin runs on Windows, Linux, and other UNIX operating systems. Looking for Pidgin for OS X? Try [Adium](https://adium.im)!
+Pidgin is compatible with the following chat networks out of the box: ICQ, Google Talk, Jabber/XMPP, Bonjour, Gadu-Gadu, IRC, Novell GroupWise Messenger, Lotus Sametime, SILC, SIMPLE, and Zephyr. It can support many more with [plugins](/plugins).
+Pidgin supports many features of these chat networks, such as file transfers, away messages, buddy icons, custom smilies, and typing notifications. Numerous plugins also extend Pidgin's functionality above and beyond the standard features.
+Pidgin is under constant development. Releases are usually frequent and driven by user contributions, such as [bug reports](https://pidgin.im/support/) and [patches](https://developer.pidgin.im/).
+Pidgin is free and contains no ads. All our code is open source and licensed under the GNU General Public License. This means you can get Pidgin's underlying code and modify it to suit your needs, as long as you publish the changes you make for everyone to benefit from as well.
+++ b/content/gsoc/_index.md Tue Jan 15 21:55:18 2019 +0000
@@ -2,7 +2,6 @@
@@ -10,7 +9,17 @@
+++ b/content/gsoc/instructions.md Tue Jan 15 21:55:18 2019 +0000
@@ -0,0 +1,36 @@
+Our project has historically allowed a wide variety of applications on topics both solicited and unsolicited, and we do not intend to change this policy. However, every application must meet some criteria, which we have set out here, to be considered.
+The application should demonstrate (by reference to previous projects, completed coursework, job experience, description, etc.) that the applicant possesses the following skills:
+ * Competence in programming in the applicable language for the task at hand. For Pidgin, Finch, or libpurple themselves this means C.
+ * An ability to effectively communicate, via written language, technical topics and precise thoughts.
+Every application must describe the project the applicant intends to pursue. While this may *contain* information from our ideas page or other online sources, it must *primarily* consist of the applicant's own words and plans. It should include:
+ * The applicant's estimate of the skills required to complete the task, particularly noting those skills that will need to be developed during the course of the project. Note that *it is absolutely fine* if the applicant, for example, is unfamiliar with a library or protocol necessary to complete the project, if they can demonstrate that they understand what needs to be learned and how that learning will be approached.
+ * A general timeline of the project as envisioned, with a breakdown including major milestones (e.g., "necessary UI infrastructure", "supporting changes to protocol X", "draft specification for Y").
+Note that project applications **need not be for projects from our ideaspage**. If you have a great idea for a project, that's fine, propose it! Just be sure to describe what it is, why you can do it, and how you plan to accomplish it within the summer.
+If a project or applicant has any external factors that the project should be aware of, those must be spelled out explicitly along with an explanation of how the project will be affected if those factors fail to come through or otherwise interfere. For example, if a project depends on a third-party library that is known to have limitations that may affect the success of the project, the application should describe those limitations and how they will be mitigated if they get in the way. Something like this would be appropriate:
+> I plan to use libfoo 3.1 to implement a foo protocol plugin, but it doesn't yet support a pluggable main loop, which libpurple requires. The libfoo developers intend to address that, but if they do not address it by midsummer, I will implement it myself and submit a patch upstream. If this happens, I probably will not be able to complete the extended frobnicator API in libpurple, but the project will still successfully speak the foo protocol by the end of the summer.
+Any potential major demands on the student's time MUST be included, such as: finals (we know that not all school schedules line up with SoC precisely, and this will absolutely not disqualify an application!), scheduled vacations or holidays, existing summer commitments for work or school, potentially conflicting job applications, etc.
+After submitting a great proposal, PLEASE join us on IRC (irc.freenode.net #pidgin) or XMPP MUC (devel@conference.pidgin.im) and discuss your ideas with the community. Experience has shown that students who are involved before the Summer of Code starts are more likely to stick with it and make good progress during the summer. In addition, this provides us more and better information about how you work with other developers and what your skill set is. You can greatly improve your chances of selection by engaging with the community early.
+++ b/content/i18n/_index.md Tue Jan 15 21:55:18 2019 +0000
@@ -0,0 +1,4 @@
+++ b/content/i18n/tips.md Tue Jan 15 21:55:18 2019 +0000
@@ -0,0 +1,46 @@
+Yes! Our translations are provided by volunteers. To improve consistency and quality we prefer to have a designated person or group of people maintain each translation.
+If Pidgin already has a translation for your language, please contact the designated translator(s) and ask if you can help. It's possible they are looking for someone to take over. You can find their email address in Pidgin's Help→Translator Information window. Or, for some languages you can try contacting the translator(s) via [Transifex](https://www.transifex.com/projects/p/pidgin/).
+If you're unable to contact the designated translator(s) or if Pidgin does not yet have a translation for your language, email the [translators mailing list](https://pidgin.im/cgi-bin/mailman/listinfo/translators) and ask if anyone is already working on translating that language.
+The translations are shipped with each Pidgin release, so there is no great advantage to submitting a translation multiple times during a release cycle. We announce a string freeze on the [translators mailing list](https://pidgin.im/cgi-bin/mailman/listinfo/translators) before each release. This is a promise to you that we will not add any new strings or change any existing ones. During this time you should finish translating any new strings and submit a new translation to us.
+The preferred method for submitting updated translations is via [Transifex](https://www.transifex.com/projects/p/pidgin/). If you're the designated translator for your language then you can request to create a new language team for your language in Transifex (and please also send an email to the [translators mailing list](https://pidgin.im/cgi-bin/mailman/listinfo/translators) and let us know!).
+If you're opposed to using Transifex there are two other methods you could use to send us translations. These cause slightly more overhead for us, so we try to avoid them.
+ 1. By [creating a new ticket](https://developer.pidgin.im/newticket) and attaching your translation file. Please provide your full name, a contact email address, and the language and country code for your translation.
+ 1. Or you can ask a Pidgin developer to give you commit access directly to our version control system, then commit the translation yourself. Before you commit a translation update, please strip line numbers from the .po file by running `XGETTEXT_ARGS=--no-location intltool-update LL`. This makes the diff smaller and more human-friendly.
+You can see the current translation statistics at https://developer.pidgin.im/l10n/. There is also a link to the nightly version of the pidgin.pot at the bottom of the page. The .pot file includes the strings from our Windows installer. Providing a full translation of this file automatically ensures that Windows users will be able to have a translated installer for their convenience.
+ * Current translators are always listed in Pidgin's About dialog (Help → About from Pidgin's Buddy List window) by name, and each translator's e-mail address is included. Because of this, we need current translators to inform us if their e-mail address changes.
+ * Translation updates for each language are accepted ***only*** from its current translator, except when:
+ * The current translator has not submitted an update for at least one year and does not respond to inquiries.
+ * The current translator tells us to accept the update and/or treat a new translator as a co-maintainer of the translation.
+In short, this means that if you are not the current translator for a specific language, we will not normally accept the translation update from you, except as described above. We do this to minimize confusion among users--we've found over time that some translators will choose different ways to translate a given word or phrase, which inevitably confuses users. We apologize for any inconvenience this may cause, but we believe that following these rules makes translations better for everyone.
+++ b/data/i18n_languages.json Tue Jan 15 21:55:18 2019 +0000
@@ -0,0 +1,84 @@
+++ b/layouts/partials/logo.html Tue Jan 15 21:55:18 2019 +0000
@@ -1,1 +1,1 @@
+++ b/layouts/shortcodes/i18n-languages.html Tue Jan 15 21:55:18 2019 +0000
@@ -0,0 +1,5 @@
+++ b/themes/learn/static/css/custom.css Tue Jan 15 21:55:18 2019 +0000
@@ -2,3 +2,14 @@