Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Jan 17, 2007, 8:46:54 PM (17 years ago)
- Author:
-
seanegan
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v11
|
v12
|
|
| 14 | 14 | |
| 15 | 15 | * Do these groups accurately represent the expected audience of the site? |
| | 16 | >[wiki:seanegan]: Yes, and in order of importance too. At each level, the audience both drops to perhaps under 5% of the group above it, and is likely to already have other outside resources. |
| 16 | 17 | * Is there anything that should be added to this list? |
| 17 | 18 | * Other questions/comments? |
| … |
… |
|
| 40 | 41 | |
| 41 | 42 | * What's the best way to describe Pidgin in the shortest amount of text? We want to tell people what Pidgin is in a compelling way in as few words as possible. (Users will often gloss over long descriptions). |
| | 43 | >[wiki:seanegan]: I think your description is pretty spot-on. I think including the list of supported protocols is a huge selling point that immediately adds a ton of relevance over just a description. Good idea. |
| 42 | 44 | * Any good taglines for Pidgin? |
| | 45 | > Gaim's tagline is "The Penguin Pimpin' IM client that's good for the soul." I don't know if Pidgin has/needs/wants a tagline ;) |
| 43 | 46 | * Other questions/comments? |
| 44 | 47 | > [wiki:sgarrity]: "The current site has "A multi-protocol instant messaging (IM) client" - Not too exciting, but it works. |
| 45 | | |
| | 48 | > [wiki:seanegan]: It would be fun to change the screenshot on a very regular basis. The silhouette is obviously of the buddy list and a conversation window. It would be fun to be able to change the conversation text frequently to in-jokes/obscure 80s pop culture references/current events. Clearly not a huge priority. |
| | 49 | >[wiki:seanegan]: It might be nice to have the full text of the latest news post on there instead of just a headline. |
| 46 | 50 | ---- |
| 47 | 51 | |
| … |
… |
|
| 56 | 60 | |
| 57 | 61 | * Will there be repositories for systems like yum and apt? |
| 58 | | >[wiki:lschiere]: I had not considered this. I think I'm a fan of the idea though. |
| | 62 | >>[wiki:lschiere]: I had not considered this. I think I'm a fan of the idea though. |
| | 63 | > Yeah, that's not a bad idea at all, especially for yum and apt-rpm. I still doubt we'll need to package for Debian. Perhaps we may want to offer nightly builds (which might be useful if we switch to mtn which has a high initial pull cost). |
| 59 | 64 | |
| 60 | 65 | * Are there volunteers available to maintain installation instructions for their favorite distros? |
| 61 | | >[wiki:lschiere]: We have some notes, particularly about getting ssl/tls to work with gaim on various distros. In the past, there have been some patches providing additional information for various distros, but not much. |
| | 66 | >>[wiki:lschiere]: We have some notes, particularly about getting ssl/tls to work with gaim on various distros. In the past, there have been some patches providing additional information for various distros, but not much. |
| | 67 | >[wiki:seanegan]: It's mostly straightforward anyway. We only offer rpm's; there are few weird dependencies that ever need to be tracked down---most of what we have is common. But if worse comes to worse, we can bug the packagers for tips. |
| 62 | 68 | |
| 63 | 69 | * Other questions/comments? |
| 64 | | |
| | 70 | >[wiki:seanegan]: Where does the user actually click to download the package? Is it possible to download the package directly from the homepage, or do you have to go to this page first? From this page, where is the link to download? For UNIX distros, it would be nice if the home page contained two links, one for the binaries and one for the source... but in a way not to confuse the 15 year old Ubuntu livecd users. ;) |
| 65 | 71 | ---- |
| 66 | 72 | |
| … |
… |
|
| 72 | 78 | |
| 73 | 79 | * What are the features of Pidgin that should be highlighted to prospective users? |
| 74 | | > |
| 75 | | |
| | 80 | >>[wiki:lschiere]: the status stuff needs a section either here or in support. |
| | 81 | >[wiki:seanegan]: The screenshots on our current screenshot page are dated, but are a good start. Something like NetworkManager integration probably isn't too good because it's not visual, but there are plenty of UI things to show off. |
| 76 | 82 | * Should the official organization (IMF) that's now behind Pidgin be explained? |
| | 83 | >[wiki:seanegan]: This should probably just be a link to [imfreedom.org], which would just be a simple static HTML page with everything we need to disclose. |
| 77 | 84 | * Where and how can we explain that Pidgin was formerly Gaim, and the reasons for the change? |
| | 85 | >[wiki:seanegan]: Luke asked if the settlement even allows us to mention this. I think it does; it says we can use Gaim as it refers to "it's past use as a technical term" or some such. In either case, I don't expect any resistance from AOL about doing this. That said, I think the best place would be on the homepage, in the description (labeled 4) and in one of the transient areas. We would then phase these out over a couple of months. Perhaps phase out the alert after a week or so, and the description later. This would ease the initial confusion of people getting redirected from gaim.sf.net. |
| 78 | 86 | * Other questions/comments? |
| | 87 | >[wiki:seanegan]: It would be great if selecting screenshots refreshed on the page without a reload. |
| 79 | 88 | |
| 80 | 89 | ---- |
| … |
… |
|
| 88 | 97 | * What are all of the support resources that are available to users having problems? |
| 89 | 98 | >[wiki:lschiere]: there are definitely going to be mailing lists, and a FAQ. The wiki here at developer.pidgin.im will also have information on figuring out what is going wrong. My hope is to have pages here that are useful to users, but which can help point users interested in doing more in the right direction towards submitting a patch. In the past, we have written various page length articles on various things, protocol descriptions, things like our reaction to skins, plain text passwords, so on. These could remain static pages, or could be pages here with links to them from a Documentation page. I do not know which approach is best. A good search would be awesome regardless. |
| 90 | | |
| 91 | 99 | * What else should be added to the Support section? |
| 92 | 100 | * Other questions/comments? |
| … |
… |
|
| 101 | 109 | |
| 102 | 110 | * Does this seem like a good method to handle bug reports? |
| 103 | | > |
| 104 | | |
| | 111 | >>[wiki:lschiere]: this is utterly awesome. |
| | 112 | >[wiki:seanegan]: seconded |
| 105 | 113 | * Any other resources that should be searched for solutions? |
| 106 | 114 | * Other questions/comments? |
| … |
… |
|
| 115 | 123 | |
| 116 | 124 | * Are there any other ways to contribute that should be highlighted? |
| 117 | | >> |
| 118 | | > |
| 119 | | |
| | 125 | >>>[wiki:lschiere]: we are going to be using monotone, [wiki:elb] had mentioned that it might be worthwhile to have a snapshot of the monotone database posted in an automated fashion so that those interested in contributing can get a jump start, rather than the half-hour to an hour initial monotone checkout. I do not know how hard/easy it would be to do this. |
| | 126 | >> [wiki:elb] The generation of the database itself is trivial; mtn pull to an existing, dedicated database to update it (which takes care of not having to lock anything), copy it alongside the current download database, and mv it overtop. A new version will be atomically available to fresh downloaders. |
| | 127 | >>[wiki:seanegan]: That would live within developer.pidgin.im, not on this page. A lot of people have asked if we have "buttons" that they could include on their webpage. Perhaps this sort of thing could be considered a form of contribution. |
| 120 | 128 | * Other questions/comments? |
| 121 | 129 | |
| … |
… |
|
| 129 | 137 | |
| 130 | 138 | * Should the 'official' news remain separate from the blogs? |
| 131 | | > |
| 132 | | |
| | 139 | >>[wiki:lschiere]: I expect official news would remain separate yes. |
| | 140 | >[wiki:seanegan]: agreed |
| 133 | 141 | * Should we attach author names to official posts? |
| 134 | | * Other questions/comments? |
| 135 | | |
| 136 | | |
| 137 | | |
| | 142 | >[wiki:seanegan]: Doesn't matter to me. |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!
