Brian, Sounds like a good plan. So far, it's been hard to know what people are working on, what code is being changed, what needs testing, etc. A lot of people are doing different things and it's possible that their contributions will be lost or work duplicated. This list, and the changes you outline in your email should help a lot.
A few suggestions: Communication: Can we try to concentrate discussion about development, patches, testing, etc. on this list? The committers (you, Marcelo, anyone else?) could help by discussing what you're working on here. (My open source experience is in the Apache world where there's a cultural norm against doing any substantive discussion off-list.) Perhaps people could submit patches here, or at least CC: this list along with the patches address. More frequent commits: To me, frequent commits are more important than frequent builds. This is because I can build myself, and I'd rather just "repo sync" than apply patches all over the place, then worry about merges when they finally get committed. I realize that others' mileage may vary :-) Is there any way to get a feed of git commits? The RSS/Atom feed at git.koolu.com seems to only show merges from the Google tree. Even though I can see your commits when browsing, I don't see them in the feed. More frequent kernel merges: I understand that you probably have concerns about stability, but my experience with running a patched andy-tracking kernel is pretty good. The do seem to be fixing a number of worthwhile bugs these days, and I think it would make help to have the merged kernel available so that userspace could adapt and benefit from changes they make. BTW, is there any reason your changes can't be pushed back upstream, so that we could build an Android kernel by simply changing some config settings? Some sort of road map and/or to-do list: I'd like to contribute to the project. I'm a skilled Java developer with some experience with the Android SDK. My C skills are a bit rusty, I'm still getting the hang of git and repo, but I do have a working build environment and I can troubleshoot problems. I'd love to have a list of tasks, preferably one that indicates which items you and Koolu are planning on tackling first, so that I can avoid those and concentrate on ones where I might be of help and am less likely to duplicate effort. Again, thanks for your efforts so far and I look forward to contributing in some way going forward. I look forward to hearing more from you soon. Jim On Fri, Jan 23, 2009 at 10:42 AM, Brian Code <brian.c...@koolu.com> wrote: > All, > > Although it might not be the most speedy method of development, I would like > to suggest having Koolu as the main repository. I have talked with Michael > Trimarchi and am in the process of devising a streamlined way to submit > patches so that they can be integrated into the tree. I will post the > process to this list a little bit later today. > > To date, the Koolu releases have been slower to come out that some of the > other individuals in the community. This was in part due to getting some of > the infrastructure set up to facilitate this project, however, now that the > infrastructure is in place, I expect that there will be more frequent > releases. With that being said, it's important that each release gets tested > to determine what works and what doesn't. In my opinion, daily builds on > some of the Openmoko derived distributions fragments the QA process and > testing. > > I would encourage everyone to look at the test list at > http://freerunner.android.koolu.com/test-plans-and-results . It gives an > idea of the type of rigorous testing that I would like to see of Android on > Freerunner. There will be more tests added to the list (and I would > recommend people submit them to this list) moving forward. It's a start, but > by no means exhaustive. > > Also, I would ask that people submit bugs against the different releases in > the trac at trac.koolu.com. That way we will have a central place to catalog > all the open issues with Android on Freerunner, and start to close them out. > I will be working on that as well today to ensure that the different > subsystems and releases are available to file tickets against. > > Lastly, thanks to everyone in the community that has shown interest in this > project, and especially those that have contributed to help move it forward. > > Best Regards, > Brian Code > > _______________________________________________ > android-freerunner mailing list > android-freerunner@android.koolu.org > http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org > _______________________________________________ android-freerunner mailing list android-freerunner@android.koolu.org http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
