> Please understand that you force Windows developer completely change > environment. Not many developers will be ready to do that.
IMHO, there are two tiers of possible firmware contributions: 1. Stuff that is pure Java. This would include the built-in Android applications and a reasonable chunk of the SDK (particularly the portions that do not need JNI). 2. Stuff that is below the Java layer, perhaps extending into Java classes inextricably tied to the C code via JNI. I can definitely see a gap to be filled in providing assistance for Windows developers interested in #1. As with Mr. Hodges and Mr. Turner, though, I remain unconvinced that changing version control systems is necessarily part of the solution. Let's focus on the "business objective" (making things easier for Windows-only developers to contribute to Java code) rather than dictating a specific technical solution up front. In terms of #2...I would sincerely hope that anybody planning on doing development of a Linux-based OS would be amenable to using a Linux-centric build environment. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
