Changes between Version 8 and Version 9 of WebsiteWireframes

Timestamp:

Jan 17, 2007, 6:00:29 PM (17 years ago)

Author:

lschiere

Comment:

--

WebsiteWireframes

@@ -28 +28 @@
  * Other questions/comments?
 
->>[wiki:LSchiere]: In your site map, you have a section for developer blogs in both "About" and "latest news." Do we want this duplication?
+>>[wiki:lschiere]: In your site map, you have a section for developer blogs in both "About" and "latest news." Do we want this duplication?
 >joekepley: I was thinking of the Team page in the about section as something more akin to the 'contact info' page on the current site, perhaps with a bit more bio information. The 'Dev Blogs' page would be more like the current 'planet' site - an aggregation of articles from developers' blogs. So I don't think the duplication is a big deal. In one case it's part of the contact info, and in the other it's there to provide context to the posts.
 
@@ -52 +52 @@
 
  * What types of packages and binaries will be provided for Pidgin?
->[wiki:LSchiere]: The downloads section also looks good. I'm not sure we would have much in the way of alternates though beyond the source itself.  We typically have a collection of rpms, the source in .tar.gz and .tar.bz2, 3 win32 installers (with gtk, without gtk, and debug), and sometimes an autopackage.  We have not distributed debs ourselves in the past, mostly because the debian developers have done an excellent job providing packages for unstable.
+>[wiki:lschiere]: The downloads section also looks good. I'm not sure we would have much in the way of alternates though beyond the source itself.  We typically have a collection of rpms, the source in .tar.gz and .tar.bz2, 3 win32 installers (with gtk, without gtk, and debug), and sometimes an autopackage.  We have not distributed debs ourselves in the past, mostly because the debian developers have done an excellent job providing packages for unstable.
 
  * Will there be repositories for systems like yum and apt?
->[wiki:LSchiere]: I had not considered this.  I think I'm a fan of the idea though.
+>[wiki:lschiere]: I had not considered this.  I think I'm a fan of the idea though.
 
  * Are there volunteers available to maintain installation instructions for their favorite distros?
->[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.
+>[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.
 
  * Other questions/comments?
@@ -71 +71 @@
 
  * What are the features of Pidgin that should be highlighted to prospective users?
->[wiki:LSchiere]: the status stuff needs a section either here or in support.
+>[wiki:lschiere]: the status stuff needs a section either here or in support.
 
  * Should the official organization (IMF) that's now behind Pidgin be explained?
@@ -86 +86 @@
 
  * What are all of the support resources that are available to users having problems?
->[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.
+>[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.
 
  * What else should be added to the Support section?
@@ -100 +100 @@
 
  * Does this seem like a good method to handle bug reports?
->[wiki:LSchiere]: this is utterly awesome.
+>[wiki:lschiere]: this is utterly awesome.
 
  * Any other resources that should be searched for solutions?
@@ -114 +114 @@
 
  * Are there any other ways to contribute that should be highlighted?
->[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.
+>[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.
 
  * Other questions/comments?
@@ -127 +127 @@
 
  * Should the 'official' news remain separate from the blogs?
->[wiki:LSchiere]: I expect official news would remain separate yes.
+>[wiki:lschiere]: I expect official news would remain separate yes.
 
  * Should we attach author names to official posts?