David, Just throwing these thoughts out there...
In order to raise interest we need to reach out to more people who have Cocoa software on Mac OS X and help them realize that GNUstep is a viable environment for porting their software. We have a number of examples of modern Mac OS X Cocoa applications which have been ported: Bean, Flexisheet, GNUspeech so there is no doubt that GNUstep is maturing. One thing I will say, from experience, is that we do need further improvement to pbxbuild (which I have been working on). It now does an almost perfect job of translating .xcodeproj to PC projects at this point, but there are still a few gotchas. The ability for Mac OS X developers to come over and be able to build their apps with no changes or, at least, very minimal ones is something that is very close, but not entirely working. It does work in most cases for simple projects, but for complex ones it's a problem. We also have to start appealing to more people in the GNU/Linux world who are interested in Objective-C and a Mac-like experience, but don't necessarily want a Mac. There seem to be plenty of them around. :) I want GNUstep to be seen as a full development environment as well as conduit for people to bring their Cocoa applications to a wider audience. In my experience reaching out to companies, individuals and other open source projects who might be willing to help us are several good ways to bring attention to GNUstep. :) Later, GC Gregory Casamento -- Principal Consultant - OLC, Inc # GNUstep Chief Maintainer ________________________________ From: David Chisnall <thera...@sucs.org> To: Adam Fedor <fe...@qwestoffice.net> Cc: Developer GNUstep <gnustep-dev@gnu.org> Sent: Tuesday, January 13, 2009 6:36:09 AM Subject: Re: our Devroom - what do we want to do there - call for papers On 13 Jan 2009, at 03:14, Adam Fedor wrote: > We had three. One dropped out before the start even, I think due to family > problems. This one looked very promising at the start, but unfortunately someone else thought so too and he was offered an internship that looked more appealing than spending the summer working on GNUstep. > One basically did not submit code that was anywhere near done. Basically > just a skeleton. This was mine. Two things to take away from this: 1) Due to the way the SoC is set up, we should favour students in the USA. I don't really like this, but the dates are fixed according to US term dates - there is no flexibility and most other countries have quite different summer holiday times. This student should probably have failed in the middle, but I passed him because his term dates meant that he had to start several weeks late. 2) Make absolutely sure the student has no outside commitments. Mine had an internship that was meant to have finished but kept calling him back. Unfortunately, GNUstep did not really have enough applicants to be able to turn away any that looked even vaguely promising. I don't know how we can go about raising the profile of the projects this year so that we will get more applicants. David _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
_______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
