[Mono-list] Updating or Redoing go-mono.net
Mon, 12 Jan 2004 13:40:35 -0700
The point that I was trying to make is that the current site doesn't
clearly reflect the use of Mono/ASP.Net. This creates the perception of
the site that I tried to describe in my first email. When I have
directed others to the site, they responded with the same sentiment.
That's the contention that I was talking about, and not that the Mono
tools/developers/etc are incapable. This emphasizes the need for
(a,b,c), but wouldn't necessarily be required to change the tone of the
site a little to show more of it's roots.
Are you looking for members of the community to do (a,b,c) or are you
looking at resources within Novell?
On Fri, 2004-01-09 at 16:13, Miguel de Icaza wrote:
> > "Most ambitious would be to put the site entirely into ASP.NET, making
> > it a showcase for Mono software"
> > IMHO :)
> > This is absolutely critical, and has been a point of contention for some
> > time. By not using your own product, you are telling everyone that even
> > the developers can't get it to work on there production site. To start,
> > a basic port and a little cleanup shouldn't be an unrealistic project
> > for the talent that in floating around on this project.
> > "Please move the Mono site to Mono/ASP.NET!"
> No, that has not been the contention issue.
> The issue has been that we need:
> a. A new design that can serve the different needs that we have,
> starting with defining the audience, the layout and its goals.
> b. Design graphically a site that would include support for those
> audiences defined above, roughly: Installing Mono, Using Mono,
> Developing with Mono and The Development of Mono.
> c. Someone to oversee the integration of the few pieces of dynamic
> content that we have.
> In fact, today the Mono web site *uses* ASP.NET, just not on the front
> So you are wrong in that there is any issue using ASP.NET, we just have
> not had anyone who can do (a), (b) and (c) other than what I have done.