[Noisebridge-discuss] Noisedroid Meetup

[Joe LaPenna]

We will be meeting up at 4pm this Saturday to do a Noisedroid meetup
practice run... Feel free to join us. My plans are to get a general
feel for what pepole are interested in working on, Andy and I will be
at the space earlier in the day as well.


FWIW, there wasn't much warning so if you can't make it, feel free to
propose the next time/place.

Per Asheesh:
"""
I set up a bunch of checkboxes on the web to help us decide:
http://doodle.com/participation.html?pollId=tdpw3ybyp4vc57sm

Check the boxes to say when you can come, and then we'll know without
passing a huge number of emails around.

(You can administer those checkboxes here, if you want to change the
options or edit other people's answers or something:
http://doodle.com/administration.html?pollId=tdpw3ybyp4vc57sm&adminKey=dtcsn7ut
)
"""


On Thu, Apr 16, 2009 at 10:04 AM, Joe LaPenna <jlapenna at gmail.com> wrote:
> +more people who might be interested.
>
> I'll be around in the morning as well, probably be hanging out at NB
> most of the weekend actually. I'll ping noisebridge-discuss about this
> weekend.
>
> On Wed, Apr 15, 2009 at 11:57 AM, Andy Isaacson <adi at hexapodia.org> wrote:
>> On Wed, Apr 15, 2009 at 02:15:31AM -0700, Joe LaPenna wrote:
>>> So far, with the four of us who have added data, Saturday seems the
>>> best option for a meet-up. Anyone else care to comment?
>>
>> I can do Saturday, but I have a prior commitment starting approximately
>> 2PM.  I'll be at 83c in the morning in any case, so if people want to
>> come by and hack on Noisedroid I'm down with that.
>>
>> The particular things that need work right now are
>>
>> 1. reprising our build process for the post-merge upstream trees
>> (the build process in Noisedroid/FAQ is busted due to changes upstream,
>> last I checked -- 4/10 or thereabouts -- the upstream kernel tree didn't
>> build at all apparently due to a halfassed merge.)
>
> There have been two more merges since then. We can probably ping some
> of the community folk like JesusFreake for some getting-it-on-the-g1
> side or even some android folk that lurk around here.
>
>>
>> 2. understanding the contact sync and IM providers and starting to
>> implement non-google-specific ones
>
> This is the area that I'll probably focus on as I
>>
>> 3. collating apps we want to ship in the Noisedroid default build
>
> I think that is a bit far out, but we can start getting an idea about it. Yeah.
>>
>> 4. coming up with a credible plan for libc et al to address the working
>> set issue
>
> I'm not sure what you mean here.
>
>>
>> 5. figuring out what is wrong with the Noisedroid build such that some
>> keys don't work (Home, for example).
>
> This is a "provisioning" issue and is resolved by (android-developers:
> What happened to the HOME button in cupcake):
>
>  1. Edit "development/apps/SdkSetup/Android.mk" to include the
> "LOCAL_MODULE_TAGS := eng" line
>   2. Rebuild the system image with "mmm development/apps/SdkSetup
> snod"
>
>>
>> 6. figuring out what we're going to do for the Debian install and wire
>> it up to a usable terminal widget.  (We need a credible way to have
>> persistent TTY sessions so you can run, for example, a native Python
>> interpreter and be able to switch away from it without losing state.)
>
> "Spare Parts" has a terminal built in:
> .$SRC/development/apps/SpareParts which could lead us to a start,
> there is also jsharkey's connectbot which has terminal support with
> backgrounding support. Probably service based with a RemoteBinder
> between it and the foreground activity.
>
> I think this is a good list of things to start discussing. Where do
> people's interests lie regarding Noisedroid?
>
>
>
> --
> http://joelapenna.com
>



-- 
http://joelapenna.com