Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(58) |
Oct
(128) |
Nov
(200) |
Dec
(67) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(75) |
Feb
(78) |
Mar
(24) |
Apr
(15) |
May
(31) |
Jun
(118) |
Jul
(34) |
Aug
(74) |
Sep
(52) |
Oct
(27) |
Nov
(33) |
Dec
(27) |
2002 |
Jan
(40) |
Feb
(75) |
Mar
(48) |
Apr
(63) |
May
(123) |
Jun
(140) |
Jul
(39) |
Aug
(89) |
Sep
(90) |
Oct
(98) |
Nov
(132) |
Dec
(98) |
2003 |
Jan
(74) |
Feb
(70) |
Mar
(71) |
Apr
(13) |
May
(47) |
Jun
(25) |
Jul
(74) |
Aug
(29) |
Sep
(46) |
Oct
(25) |
Nov
(36) |
Dec
(17) |
2004 |
Jan
(9) |
Feb
(45) |
Mar
(32) |
Apr
(19) |
May
(56) |
Jun
(20) |
Jul
(27) |
Aug
(3) |
Sep
(28) |
Oct
(5) |
Nov
(60) |
Dec
(22) |
2005 |
Jan
(29) |
Feb
(24) |
Mar
(10) |
Apr
(20) |
May
(14) |
Jun
(112) |
Jul
(22) |
Aug
(30) |
Sep
(16) |
Oct
(16) |
Nov
(14) |
Dec
(21) |
2006 |
Jan
(40) |
Feb
(6) |
Mar
(51) |
Apr
(62) |
May
(131) |
Jun
(39) |
Jul
(8) |
Aug
(30) |
Sep
(62) |
Oct
(31) |
Nov
(55) |
Dec
(21) |
2007 |
Jan
(111) |
Feb
(56) |
Mar
(123) |
Apr
(50) |
May
(111) |
Jun
(6) |
Jul
(35) |
Aug
(53) |
Sep
(20) |
Oct
(6) |
Nov
(68) |
Dec
(13) |
2008 |
Jan
(17) |
Feb
(24) |
Mar
(65) |
Apr
(153) |
May
(20) |
Jun
(58) |
Jul
(8) |
Aug
(3) |
Sep
(99) |
Oct
(32) |
Nov
(5) |
Dec
(20) |
2009 |
Jan
(9) |
Feb
(2) |
Mar
(18) |
Apr
(73) |
May
(10) |
Jun
(32) |
Jul
(108) |
Aug
(14) |
Sep
(23) |
Oct
(50) |
Nov
(33) |
Dec
(4) |
2010 |
Jan
(79) |
Feb
(63) |
Mar
(48) |
Apr
(35) |
May
(72) |
Jun
(132) |
Jul
(77) |
Aug
(58) |
Sep
(27) |
Oct
(18) |
Nov
(3) |
Dec
(5) |
2011 |
Jan
(24) |
Feb
(14) |
Mar
(25) |
Apr
(10) |
May
(75) |
Jun
(19) |
Jul
(9) |
Aug
(29) |
Sep
(2) |
Oct
(76) |
Nov
(104) |
Dec
(43) |
2012 |
Jan
(38) |
Feb
(42) |
Mar
(8) |
Apr
(55) |
May
(14) |
Jun
(33) |
Jul
(47) |
Aug
(58) |
Sep
(66) |
Oct
(33) |
Nov
(1) |
Dec
|
2013 |
Jan
(58) |
Feb
(65) |
Mar
(112) |
Apr
(71) |
May
(6) |
Jun
(3) |
Jul
(12) |
Aug
(14) |
Sep
(11) |
Oct
(14) |
Nov
(1) |
Dec
(7) |
2014 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(2) |
Oct
(5) |
Nov
(11) |
Dec
(2) |
2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(1) |
Dec
(7) |
2016 |
Jan
(22) |
Feb
|
Mar
(5) |
Apr
|
May
(9) |
Jun
(9) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(10) |
2017 |
Jan
(14) |
Feb
(6) |
Mar
(7) |
Apr
(12) |
May
(16) |
Jun
(7) |
Jul
(5) |
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
1
|
2
|
3
|
4
|
5
|
6
(3) |
7
(3) |
8
(1) |
9
(1) |
10
|
11
(4) |
12
|
13
(5) |
14
(5) |
15
(4) |
16
(9) |
17
(4) |
18
(7) |
19
(6) |
20
(5) |
21
(18) |
22
(5) |
23
|
24
(3) |
25
(8) |
26
(5) |
27
(6) |
28
(12) |
29
(6) |
30
(3) |
31
|
From: Julien Lecomte <julien@fa...> - 2007-03-22 16:38:32
|
Earnie Boyd wrote: > Quoting Julien Lecomte <julien@...>: >> Earnie Boyd wrote: >>> Quoting Julien Lecomte <julien@...>: >>> Currently we have two pieces of content, the main site and the phpwiki >>> data. My main concern at the moment is the main site. >> I was thinking about merging both since what is on the main site can be >> in a wiki. > Eventually over a length of time, maybe. The data on the main site is the easiest to replicate, there's more work to be done when replicating the phpwiki. >>>> I'll just point out that MediaWiki had it's pros/cons. (...) >>>> AFAIK, I don't believe a MediaWiki plugin for auto-importing feeds exist. >>> This might be troublesome. >> I've just solved the problem of auto-import of the latest releases/news >> from sourceforge.net >> A brief reminder of the problem: the blue 'news box' on the main page >> was edited by hand and would require an user to update the page when a >> new release is done. >> >> I've just solved this problem by hacking the mediawiki '<iframe>' >> extension to include via php's 'fopen' >> http://sourceforge.net/export/projnews.php?group_id=2435&limit=10&flat=0 > > Is this screen scrape method so that if SF changes its HTML UI you > would need to change the data pieces? Not interested in that. You > could use the RSS feed and use the XML data. Yes I know SF can change > the layout of the XML. I just download the page and include it verbatim since my host allows cross-site http inclusion which is by default unsafe and probably disallowed on SF. On SF I was thinking we could fcron a wget on the url, and then include the local copy of it; much simpler than 'news-update.sh' on the shell server. We could parse a RSS or an XML feed and create a page for inclusion if we wish to. It would, in any case, work just like it currently works on mingw.org. In any case, if SF wishes to change something, they'll change it without telling us before hand, and change it to something that breaks the most things possible. >> http://www.amanitamuscaria.org/MinGWiki/Main_Page now has the correct >> latest news and releases. >> >> Maybe, after all, MediaWiki might be a good choice. > > I will admit that your three column template looks good. The credit really goes out to gpwiki.org. > It is too bad > that there isn't more control on the template overall. We can offer > the user a choice of template to view the data with Drupal. In my > opinion a wiki look for the front landing page cheapens the impression > of a project unless you're actually the one producing the wiki or your > name is wikipedia. Some talented users have created skins for their own projects. Some of these projects don't look at all like a Wikipedia. Some examples are listed on this page: http://meta.wikimedia.org/wiki/Gallery_of_user_styles I've tried your DNKWIWD method to try to make a skin for the MinGWiki sandbox. It "kinda" looks like http://www.mingw.org now (but with some css bugs) Julien |
From: <jacraig@so...> - 2007-03-22 16:36:20
|
Earnie Boyd writes: >> Earnie Boyd wrote: > > Is this screen scrape method so that if SF changes its HTML UI you > would need to change the data pieces? Not interested in that. You > could use the RSS feed and use the XML data. Yes I know SF can change > the layout of the XML. > Agreed. It would be fairly easy to create an XSLT stylesheet and simply transform the RSS data into inline HTML with PHP, so it shouldn't too hard to get a fairly maintainable method of displaying live sourceforge data. I've done this before in PHP. > In my > opinion a wiki look for the front landing page cheapens the impression > of a project unless you're actually the one producing the wiki or your > name is wikipedia. > Agree 100%. --Jason A. Craig |
From: Earnie Boyd <earnie@us...> - 2007-03-22 11:53:40
|
Quoting Julien Lecomte <julien@...>: > Earnie Boyd wrote: >> Quoting Julien Lecomte <julien@...>: >> Currently we have two pieces of content, the main site and the phpwiki >> data. My main concern at the moment is the main site. > > I was thinking about merging both since what is on the main site can be > in a wiki. > Eventually over a length of time, maybe. >> If I remember correctly what you had in your sand box included the >> wiki data. > Not much of it actually. I took some pages verbatim or wikified them. > >>> I'll just point out that MediaWiki had it's pros/cons. (...) >>> AFAIK, I don't believe a MediaWiki plugin for auto-importing feeds exist. >> This might be troublesome. > > I've just solved the problem of auto-import of the latest releases/news > from sourceforge.net > A brief reminder of the problem: the blue 'news box' on the main page > was edited by hand and would require an user to update the page when a > new release is done. > > I've just solved this problem by hacking the mediawiki '<iframe>' > extension to include via php's 'fopen' > http://sourceforge.net/export/projnews.php?group_id=2435&limit=10&flat=0 > Is this screen scrape method so that if SF changes its HTML UI you would need to change the data pieces? Not interested in that. You could use the RSS feed and use the XML data. Yes I know SF can change the layout of the XML. > http://www.amanitamuscaria.org/MinGWiki/Main_Page now has the correct > latest news and releases. > > Maybe, after all, MediaWiki might be a good choice. I will admit that your three column template looks good. It is too bad that there isn't more control on the template overall. We can offer the user a choice of template to view the data with Drupal. In my opinion a wiki look for the front landing page cheapens the impression of a project unless you're actually the one producing the wiki or your name is wikipedia. Earnie |
From: Earnie Boyd <earnie@us...> - 2007-03-22 11:34:46
|
Quoting techtonik <techtonik@...>: > > If you do not trust me then point any database driven project on > SourceForge to see your name on its main page. > http://www.google.com/search?hl=en&q=techtonik&btnG=Google+Search You see, I am not concerned with my name being used by others because I used the SF site. I do not store personally liable information on a public interface. It has nothing to do with trusting you, it has to do with trusting that 100s of 1000s of projects are using SF for its infrastructure. It is therefore not a concern. Earnie |
From: Earnie Boyd <earnie@us...> - 2007-03-22 11:22:00
|
Quoting jacraig@...: > Earnie Boyd writes: > >>> 3. Tune Drupal. >> >> This includes a template design. Drupal works best with phptemplate >> but can use smarty; I'm don't know what template engines Joomla >> supports. If someone wants to design a template for MinGW based on >> phptemplate using Drupal see http://drupal.org/node/509 for >> documentation from the http://drupal.org/handbooks section. > > Well since Drupal is the choice, perhaps I will get started on templates. > Are there any requirements for the design? Is there a pre-existing comp for > a design? Should the design be like the current site? > The design of the site we have now is simplistic because I DNKWIWD. I do not care if you apply some artistic ability to the template. The main goal is ease of navigation and interaction between SF and any other third party package we may interoperate with. There are modules that allow a different template for different pages and/or functions. In Drupal core with version 5.0 and above you can apply a separate template for administration UI than for the site UI. We could even enable more than one template and let the authenticated visitor choose which template she desires. Earnie |