[Pidgin] FutureSOCProjects modified
Pidgin
trac at pidgin.im
Sun Mar 25 03:33:27 EDT 2012
Changed page "FutureSOCProjects" by MarkDoliner from 24.7.24.31*
Page URL: <http://developer.pidgin.im/wiki/FutureSOCProjects>
Diff URL: <http://developer.pidgin.im/wiki/FutureSOCProjects?action=diff&version=73>
Revision 73
Comment: Add stats reporting project
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FutureSOCProjects
=========================================================================
--- FutureSOCProjects (version: 72)
+++ FutureSOCProjects (version: 73)
@@ -50,8 +50,15 @@
* Grouped by contact (person), so if I have "markdoliner" on AIM and "mark.doliner at gmail.com" on XMPP combined into a contact/person, the logs show up as being for one person, with some differentiation for me to tell which IM account was used.
* Optionally propose an external log viewer. This has been requested a few times and we have historically ignored these requests.
+== Automated usage statistic collection ==
+It would be useful if Pidgin included functionality to automatically collect various statistics from users and aggregate these statistics into a viewable form on the Pidgin website. This would be useful in determining which features are popular and which are not, and could allow us to remove unused features and preferences. Google Chrome and possibly Adium could be used as references for how to implement this. Some requirements:
+ * The information must be anonymous, and not include usernames or passwords.
+ * Users must be able to opt-out. It's not clear whether reporting would be enable or disabled by default.
+ * Information must be easily viewable (so this project includes the client-side changes as well as possibly a server... but definitely investigate whether an existing solution could be used before creating a new one). It's not clear whether it would be public or private.
+ * Could also include automated crash reporting.
+
== Migrate our code from Monotone to Mercurial ==
-We'd like to switch using the Mercurial version control system, because it has wider adoption and would be a lower barrier to entry for casual developers. There are a few requirements for this project to be successful:
+(Note: There is some concern that this project does not include enough coding to qualify for Summer of Code.) We'd like to switch using the Mercurial version control system, because it has wider adoption and would be a lower barrier to entry for casual developers. There are a few requirements for this project to be successful:
* Complete history
* All tags and branches
* Configuration/installation of Mercurial on our boxes
-------8<------8<------8<------8<------8<------8<------8<------8<--------
* The IP shown here might not mean anything if the user or the server is
behind a proxy.
--
Pidgin <http://pidgin.im>
Pidgin
This is an automated message. Someone at http://pidgin.im added your email
address to be notified of changes on FutureSOCProjects. If it was not you, please
report to .
More information about the Wikiedit
mailing list