[Mono-list] Surveys: Mono 1.0 and Mono Conference.
Bob Smith
bob@thestuff.net
Fri, 10 Oct 2003 14:24:41 -0700
--=-VG9q6R8Id2z44i3KWoIf
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Wed, 2003-10-08 at 19:24, Miguel de Icaza wrote:
> Hey guys,
>=20
> I want to query the community, and find out about two things:
>=20
> * What should Mono 1.0 be?
>=20
> * When and where should we do a Mono developer summit.
>=20
> * Mono 1.0
>=20
My 1.5 cents. :)
Why a monolithic release?
We have some very different types of technology in mono. As such, why
not release a few different packages. Maybe at the same time for a
general 1.0 release or possibly separately as they mature. For example,
if the mono core is done but asp.net is not, why wait for asp.net?
1. The core stuff. The JIT, meta data libs, and class libraries.
This is really the heart of mono and will be needed for everything else.
2. ASP.NET (Web stuff)
Not necessary for non web builders. What percentage of machines have
apache on them? I don't think Microsoft is going to go after mono over
asp, but if they do, it would be good for them to target the asp stuff
directly rather then all of mono.
3. GTK# (Gui stuff)
Why install GTK# on your web server? I know my web servers don't have X
on them, so I'd rather not download it on that system.
4. mcs, mbas, monodis, ilasm, etc (Development stuff)
These tools are only useful to developers. Most users wont ever need
them, so why have them install them?
Bob
> Mono is rapidly approaching maturity in various of its class
> libraries, the question in everyone's minds is: is it worth
> waiting for the full .net framework implementation to be ready
> to publish 1.0, or is a subset fine?
> =20
> Mono 1.0 so far is going to be a subset, and my current thinking
> is `.NET 1.0 minus two major pieces: EnterpriseServices and
> Windows.Forms'.
> =20
> But today some people suggested that we might want to have a
> Mono 1.0 release earlier by committing to less than that,
> something like:=20
> =20
> Mono 1.0:=20
> C# compiler
> Toolchain (ilasm, ildasm, al, etc)
> corlib, System, System.XML, System.Security.
> ADO.NET (System.Data and providers)
> ASP.NET (System.Web.Services and System.Web)
> =20
> Anything else that is robust by the time the other components
> are deemed "stable" would also make it. So if for example
> "System.Wasabinator" is of 1.0 quality by the time the rest is
> done, we can also include it.=20
> =20
> We would later publish the other components in upcoming
> releases:
> =20
> JScript, VB.NET (compiler and runtimes)
> System.DirectoryServices
> System.EnterpriseServices
> System.Windows.Forms
> =20
> * Mono Conference (Code name: Mono Summit of Love).
>=20
> Gnome has been fairly successful at running yearly conferences
> for users and developers. And these face to face meetings are
> fantastic to improve the collaboration between the various parts
> of the project, and help to go over development bumps rather
> quickly.
> =20
> Also, it is great to put faces and voices to nicknames and email
> addresses.=20
> =20
> So am thinking that we need to have a such a summit. There are
> two questions: what is the audience for this summit and where
> should we base it.
> =20
> Audience:
> =20
> We can certainly make this a hacker-only conference, but
> given the amount of projects, companies and developers
> using Mono, it might make sense to have something with a
> larger scope.
> =20
> In one extreme we have the `big room with internet
> access, printers and laptops' and in the other we have
> something more formal including presentations on
> specific technologies, tutorials and workshops.=20
> =20
> I know active Mono developers would like to come (and am
> working on getting the funding to pay for airfares and
> hotels for those who can not afford a trip to the other
> end of the world).
> =20
> Location:
> =20
> I suggested Cancun during summer break, but Nat quickly
> pointed out that if you are working for a company, there
> was no way your boss would authorize such a thing.
> =20
> So here are the parameters:
> =20
> * If we are getting many latin-americans/asians,
> we should do it in a country that does not
> require VISAs, so that rules out the US and
> Brasil.
> =20
> * If we are getting mostly US citizens,
> Europeans that are under the VISA waiver
> program and just a few foreigners, we might
> consider the US.
> =20
> My choice would be to pick a cheap city, rather than an
> expensive one, and one that has good airport
> connectivity to minimize airfare cost, for case A we
> have:
> =20
> * Cancun, Mexico.
> =20
> * Barcelona, Spain
> =20
> For case B we could probably do Boston, unless some
> University wants to step up and provide some facilities.
> =20
> Love, Love, Love,
> Miguel.
> _______________________________________________
> Mono-list maillist - Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
--=20
Bob Smith <bob@thestuff.net>
--=-VG9q6R8Id2z44i3KWoIf
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQA/hyOP5f+eZB67+RMRAgDrAJ0ekz78xvT890fs5DzUrSCxOHkv3ACgiw7+
Rkd08YANBVoK3zTQG1Q1TUk=
=AGKQ
-----END PGP SIGNATURE-----
--=-VG9q6R8Id2z44i3KWoIf--