Hello Dave, See my comments inline.
>>Overall this is very ambitious, and there is lots of stuff here to keep >>us going for a couple of years - one thing I missed was a priority >>associated with each functionality Yes I agree. That is something we need to work on now that we have a good overview of the ideas. >In addition, I would like to formalise the process for getting new >developers and contributors involved in the project. I would like people >to know what is involved in getting Subversion commit access, how to get >access to modify tickets in the trac, how to get a blog on >openwengo.org, how we can include the community in the governance of the >project, getting an openwengo.org email address, etc. These processes need to be written to see what we can settle upon. >> ## restructuring the source tree ## >> Will this involve removing modules from the source tree? Yes. It will at least clarify the usage of 3rdparty libs. >> ## split some subprojects into separate trac instances ## >>Is there a risk of having too many entry points into the project for >>outsides with this? Yes there is a high risk. This is why it should only be done very carefully. Restructuring the source tree seems to be a higher priority. >> ## rebranding entry points ## >>I'm not sure I understand this - do you mean, make it easy for third >>parties to provide a branding bundle which will remove the wengophone >>and openwengo names, like Mozilla does? Something like that yes. >> ## packaging ## >>Even more - I would like to make sure that the wengophone gets included >>in all of the major community based distributions - Ubuntu, Debian, >>Fedora, Mandrake Cooker, OpenSuse (I know that we're already in some of >>those in the community repositories - I'd like to see us get into the >>main repositories). I agree >> ## port glib to a WindowsCE target ## >>Perhaps people at GNOME are working on this already? what are the issues? If you could find information on this it could be nice. >From what I heard, no one is interested on the subject and there may be problems related to some low level APIs used in the GLIB. On the compiler side, there are 2 issues : - either you need to be able to compile with Visual Studio - or your need the windows mobile header files for MingW (they do not exist as far as I know) >> ## get rid of openssl ## >>While there may be technical reasons to avoid OpenSSL, I don't think >>there are any licence issues. Interesting. There was a debate on this on the list. I don't think there really is a technical reason apart maybe from the payload of this library. This is not a high priority _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
