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.

Changes between Version 27 and Version 28 of PidginWebsite


Ignore:
Timestamp:
Nov 3, 2006, 4:39:41 PM (17 years ago)
Author:
datallah
Comment:

Testing Server time

Legend:

Unmodified
Added
Removed
Modified
  • PidginWebsite

    v27 v28  
    3434 * '''Documentation''' - still need this? if so, merge with Support page
    3535 * '''FAQ''' - Merge with Support page
    36  * '''Screnshots''' - Merge with About Pidgin page
     36 * '''Screenshots''' - Merge with About Pidgin page
    3737 * '''Downloads''' - Prominent Windows download on home page, link to download page with all other formats
    3838 * '''Windows Port''' - Does this need it's own page? Is it really a "port'?  In a lot of senses it is, there is a lot of win32 specific information on the existing win32 page, and many bugs win32 users report are specific to that platform.
     
    4848>> That's what I was thinking when I suggested a support page ["seanegan"]
    4949> That sounds great to me, I'm in complete support (pun intended) of that! support.pidgin.im, anyone?  Bug reports will probably have to be linked back to developer.pidgin.im in some fashion, but users should be able to find them without thinking "oh, I'm a developer".  [wiki:elb]
    50 >> support.pidgin.im exists, but is currently empty.  One of the reasons we chose trac was for the integration between tracker, VCS, and wiki.  So we definitally do not want to actually *move* the tracker to support.pidgin.im, but I am definitally a fan of providing easy links there. --[wiki:lschiere]
     50>> support.pidgin.im exists, but is currently empty.  One of the reasons we chose trac was for the integration between tracker, VCS, and wiki.  So we definitely do not want to actually *move* the tracker to support.pidgin.im, but I am definitally a fan of providing easy links there. --[wiki:lschiere]
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!