зеркало из https://github.com/mono/mail-archives.git
196 строки
9.0 KiB
HTML
196 строки
9.0 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE> [Mono-list] Surveys: Mono 1.0 and Mono Conference.
|
|
</TITLE>
|
|
<LINK REL="Index" HREF="index.html" >
|
|
<LINK REL="made" HREF="mailto:Nick.Pavlica%40echostar.com">
|
|
<META NAME="robots" CONTENT="index,nofollow">
|
|
|
|
<LINK REL="Previous" HREF="016220.html">
|
|
<LINK REL="Next" HREF="016229.html">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#ffffff">
|
|
<H1>[Mono-list] Surveys: Mono 1.0 and Mono Conference.
|
|
</H1>
|
|
<B>Pavlica, Nick
|
|
</B>
|
|
<A HREF="mailto:Nick.Pavlica%40echostar.com"
|
|
TITLE="[Mono-list] Surveys: Mono 1.0 and Mono Conference.">Nick.Pavlica@echostar.com
|
|
</A><BR>
|
|
<I>Thu, 09 Oct 2003 13:15:04 -0600</I>
|
|
<P><UL>
|
|
<LI> Previous message: <A HREF="016220.html">[Mono-list] Surveys: Mono 1.0 and Mono Conference.
|
|
</A></li>
|
|
<LI> Next message: <A HREF="016229.html">[Mono-list] Surveys: Mono 1.0 and Mono Conference.
|
|
</A></li>
|
|
<LI> <B>Messages sorted by:</B>
|
|
<a href="date.html#16227">[ date ]</a>
|
|
<a href="thread.html#16227">[ thread ]</a>
|
|
<a href="subject.html#16227">[ subject ]</a>
|
|
<a href="author.html#16227">[ author ]</a>
|
|
</LI>
|
|
</UL>
|
|
<HR>
|
|
<!--beginarticle-->
|
|
<PRE>On Wed, 2003-10-08 at 20:24, Miguel de Icaza wrote:
|
|
><i> Hey guys,
|
|
</I>><i>
|
|
</I>><i> I want to query the community, and find out about two things:
|
|
</I>><i>
|
|
</I>><i> * What should Mono 1.0 be?
|
|
</I>
|
|
|
|
I believe a 1.0 release of Mono should, at a minimum, encompass the
|
|
following:
|
|
|
|
- At least one complete development paradigm.
|
|
- Top notch documentation, packaging, etc.
|
|
- Embody the performance and stability that is generally expected in
|
|
a 1.0 release.
|
|
- A clear definition of what Mono 1.0 is and is not.
|
|
- A "Road Map" to what can be expected in future releases.
|
|
|
|
><i>
|
|
</I>><i> * When and where should we do a Mono developer summit.
|
|
</I>
|
|
A developer summit would be great! I just hope that you try to make it
|
|
as accessible by normal people as possible. For years I have worked for
|
|
companies, and organizations that DO NOT PAY for these types of events,
|
|
which means it would have to come out of my pocket. It's very difficult
|
|
to justify spending $2-3000(Travel, etc.) of my own money for this type
|
|
of activity.
|
|
|
|
[IMHO] The Java One, and similar conferences are examples of what not to
|
|
do for a developers summit. Yes they are fun, but they are really just
|
|
a huge interactive commercial for whomever is tying to sell there
|
|
product to Engineers, CTO's, etc. I believe that most people that would
|
|
attend this conference would all ready understand what Mono can do for
|
|
them and would rather have technical and brainstorming sessions. Coding
|
|
sprints/competitions and the like are other good activities as well.
|
|
|
|
It would be fun/possible to visit Vancouver B.C.
|
|
|
|
|
|
><i>
|
|
</I>><i> * Mono 1.0
|
|
</I>><i>
|
|
</I>><i> Mono is rapidly approaching maturity in various of its class
|
|
</I>><i> libraries, the question in everyone's minds is: is it worth
|
|
</I>><i> waiting for the full .net framework implementation to be ready
|
|
</I>><i> to publish 1.0, or is a subset fine?
|
|
</I>><i>
|
|
</I>><i> Mono 1.0 so far is going to be a subset, and my current thinking
|
|
</I>><i> is `.NET 1.0 minus two major pieces: EnterpriseServices and
|
|
</I>><i> Windows.Forms'.
|
|
</I>><i>
|
|
</I>><i> But today some people suggested that we might want to have a
|
|
</I>><i> Mono 1.0 release earlier by committing to less than that,
|
|
</I>><i> something like:
|
|
</I>><i>
|
|
</I>><i> Mono 1.0:
|
|
</I>><i> C# compiler
|
|
</I>><i> Toolchain (ilasm, ildasm, al, etc)
|
|
</I>><i> corlib, System, System.XML, System.Security.
|
|
</I>><i> ADO.NET (System.Data and providers)
|
|
</I>><i> ASP.NET (System.Web.Services and System.Web)
|
|
</I>><i>
|
|
</I>><i> Anything else that is robust by the time the other components
|
|
</I>><i> are deemed "stable" would also make it. So if for example
|
|
</I>><i> "System.Wasabinator" is of 1.0 quality by the time the rest is
|
|
</I>><i> done, we can also include it.
|
|
</I>><i>
|
|
</I>><i> We would later publish the other components in upcoming
|
|
</I>><i> releases:
|
|
</I>><i>
|
|
</I>><i> JScript, VB.NET (compiler and runtimes)
|
|
</I>><i> System.DirectoryServices
|
|
</I>><i> System.EnterpriseServices
|
|
</I>><i> System.Windows.Forms
|
|
</I>><i>
|
|
</I>><i> * Mono Conference (Code name: Mono Summit of Love).
|
|
</I>><i>
|
|
</I>><i> Gnome has been fairly successful at running yearly conferences
|
|
</I>><i> for users and developers. And these face to face meetings are
|
|
</I>><i> fantastic to improve the collaboration between the various parts
|
|
</I>><i> of the project, and help to go over development bumps rather
|
|
</I>><i> quickly.
|
|
</I>><i>
|
|
</I>><i> Also, it is great to put faces and voices to nicknames and email
|
|
</I>><i> addresses.
|
|
</I>><i>
|
|
</I>><i> So am thinking that we need to have a such a summit. There are
|
|
</I>><i> two questions: what is the audience for this summit and where
|
|
</I>><i> should we base it.
|
|
</I>><i>
|
|
</I>><i> Audience:
|
|
</I>><i>
|
|
</I>><i> We can certainly make this a hacker-only conference, but
|
|
</I>><i> given the amount of projects, companies and developers
|
|
</I>><i> using Mono, it might make sense to have something with a
|
|
</I>><i> larger scope.
|
|
</I>><i>
|
|
</I>><i> In one extreme we have the `big room with internet
|
|
</I>><i> access, printers and laptops' and in the other we have
|
|
</I>><i> something more formal including presentations on
|
|
</I>><i> specific technologies, tutorials and workshops.
|
|
</I>><i>
|
|
</I>><i> I know active Mono developers would like to come (and am
|
|
</I>><i> working on getting the funding to pay for airfares and
|
|
</I>><i> hotels for those who can not afford a trip to the other
|
|
</I>><i> end of the world).
|
|
</I>><i>
|
|
</I>><i> Location:
|
|
</I>><i>
|
|
</I>><i> I suggested Cancun during summer break, but Nat quickly
|
|
</I>><i> pointed out that if you are working for a company, there
|
|
</I>><i> was no way your boss would authorize such a thing.
|
|
</I>><i>
|
|
</I>><i> So here are the parameters:
|
|
</I>><i>
|
|
</I>><i> * If we are getting many latin-americans/asians,
|
|
</I>><i> we should do it in a country that does not
|
|
</I>><i> require VISAs, so that rules out the US and
|
|
</I>><i> Brasil.
|
|
</I>><i>
|
|
</I>><i> * If we are getting mostly US citizens,
|
|
</I>><i> Europeans that are under the VISA waiver
|
|
</I>><i> program and just a few foreigners, we might
|
|
</I>><i> consider the US.
|
|
</I>><i>
|
|
</I>><i> My choice would be to pick a cheap city, rather than an
|
|
</I>><i> expensive one, and one that has good airport
|
|
</I>><i> connectivity to minimize airfare cost, for case A we
|
|
</I>><i> have:
|
|
</I>><i>
|
|
</I>><i> * Cancun, Mexico.
|
|
</I>><i>
|
|
</I>><i> * Barcelona, Spain
|
|
</I>><i>
|
|
</I>><i> For case B we could probably do Boston, unless some
|
|
</I>><i> University wants to step up and provide some facilities.
|
|
</I>><i>
|
|
</I>><i> Love, Love, Love,
|
|
</I>><i> Miguel.
|
|
</I>><i> _______________________________________________
|
|
</I>><i> Mono-list maillist - <A HREF="mailto:Mono-list@lists.ximian.com">Mono-list@lists.ximian.com</A>
|
|
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/mono-list">http://lists.ximian.com/mailman/listinfo/mono-list</A>
|
|
</I>
|
|
</PRE>
|
|
<!--endarticle-->
|
|
<HR>
|
|
<P><UL>
|
|
<!--threads-->
|
|
<LI> Previous message: <A HREF="016220.html">[Mono-list] Surveys: Mono 1.0 and Mono Conference.
|
|
</A></li>
|
|
<LI> Next message: <A HREF="016229.html">[Mono-list] Surveys: Mono 1.0 and Mono Conference.
|
|
</A></li>
|
|
<LI> <B>Messages sorted by:</B>
|
|
<a href="date.html#16227">[ date ]</a>
|
|
<a href="thread.html#16227">[ thread ]</a>
|
|
<a href="subject.html#16227">[ subject ]</a>
|
|
<a href="author.html#16227">[ author ]</a>
|
|
</LI>
|
|
</UL>
|
|
</body></html>
|