Subject: Re: [Ows_solutions] [NYCGA-IWG] Re: Project Proposal: Occupy Wall St The App (iOS/Android)
From: plntry.io@nym.hush.com
Date: Sat, 12 Nov 2011 17:33:57 -0800
To: internet_working_group@googlegroups.com, dallas.t.carter@gmail.com
CC: ows_solutions@freenetworkfoundation.org

(NOTE LINK CORRECTION to hotline svc.)

Right now we are experimenting with a couple of baseline peer 
configurations & dial plans for an Asterisk implementation of this 
"PEOPLE'S PBX" concept. For those who have heard about this before, 
here is some additional detail on the work plan as it stands today. 

What we would like to do is set up each occupation with the ability 
to configure:

- A hosted / owned instance of the "PEOPLE'S PBX" SW chassis 
(LAMP/Asterisk 1.6 over Ubuntu/Debian}
- A shared version of same to house smaller occupations (think: 
large cities ---> regional encampments)
- Inter-occupation links probably via IAX (inter-Asterisk optimized 
signaling protocol)

We would provide configuration files, instructions, & designs for:
- Intra-Occupation Dial Plans (e.g. Fixed Stations like Media, a 
roaming "On-Call" rep)
- Inter-Occupation Dial Plans via IAX Switching (OccupyNYC dials 
*7+ext to reach OccupyLA contacts)
- Public Hotline Menuing Interface (as depicted CORRECTED LINK: 
http://www.plntry.net/ppbx-publichotline-plntry.jpg
- Internal Hotline Admin System (allowing folks at particular 
stations to directly record msgs for the 'needs' queue, add events, 
etc.)

See a high-level routing concept for such an interoccupation system 
here:
http://www.plntry.net/ppbx-hlrouting-plntry.jpg

We'd also distribute preferred softphone clients & other optimal 
configurations @ terminal end.  Have been testing every SIP client 
known to man. 

If we had the resources (hint), we could do deep documentation, a 
premade distro, setup scripts, and more.  
ideally a custom PHP admin interface on the FGA drupal chassis...?

We are looking for more experienced Asterisk or other FLO PBX 
system folks who can help streamline our ugly little dial plans. Do 
e-mail us and we can include you in drafts of conf files.

We have some servers here & there & DIDs that we can lend to 
testing or even production deployment of the PPBX, too, in both 
eastern & western US.  And a few other places, but first things 
first.  

On Sat, 12 Nov 2011 15:07:17 -0800 Dallas Carter 
<dallas.t.carter@gmail.com> wrote:
Excellent point with regard to placing priority on "dumbphone" and 
voice
based solutions ahead of those that require more costly voice/data 
plans
and handsets.

The basic outline you've provided is great, and I can think of a 
couple of
possible added features/tweaks offhand.

At this point, considering how much discussion there has been of 
difficulty
in getting our message directly to the public and facilitation of 
real-time
intra- + inter-Occupy communications, I'd say a basic phone tree &
VM-to-email setup is a definite need. A regularly updated info 
line (maybe
even toll free?) for each Occupy would reach a lot of people that 
don't
have or aren't in the habit of using portable data services as 
well.


On Sat, Nov 12, 2011 at 5:27 PM, <plntry.io@nym.hush.com> wrote:

The reach into mobile is critical, however we caution you 
against
leading with smartphones, a strategy which will tend to exclude
those without the economic means to buy the devices / plans - 
often
those without the time or personal freedom to participate in OWS
events in - person.  That would tend to disadvantage those most 
in
need of the tool, we think.

We would instead recommend a mobile roadmap that starts from the
most widely available, data plan-friendly, and interoperable
services first.

Universal Dumbphone Solution:

1) Voice Portal: we are developing a prototype of a voice portal
system for #Occupy* as part of our Peoples' PBX project.  We 
have
done an initial use case/system mockup here:

http://www.plntry.net/ppbx-publichotline-plntry.jpg

Another alternative is SMS, though reliable & performative 
systems
tend to be have high variable costs relative to the cost to the
host of serving voice or a low-bandwidth xHTML site to users 
with
entry-level data plans.


High End Feature Phone Solution (eg. Brew Devices):

2) xHTML Web Site: since ~2007, if a device supports mobile Web, 
it
supports ~xHTML 1.0(ish).


Smartphones:

3) Webkit (/ HTML5-ish) lowest common denominator Site (cross-
smartphone solution: iOS, Android, RIM, W7, Palm...)

4) Hybrid Application: using the Webkit core site, develop 
native
app shells for iOS, Android, RIM, etc as needed; majority of app
simply renders Webkit views, 'shell' takes advantage of native
capabilities like local storage, notifications, add'l security,
voting client, etc.

Even over time as the mobile sln gets more refined, we believe 
many
use cases / features will still more logically live in the 
lighter
weight, more easily updated & maintained, & independent of 
client
update Web hybrid zone.

So...

As mentioned we are already working the voice portal concept in
Peoples' PBX.

We would be willing to contribute to systems design, UX, 
testing,
potentially server space & even devices. We may also be able to
rally a few folks to get their hands dirty code-wise but no
guarantees.

We hope you'll consider a modest / incremental / mass approach 
like
this - given who #Occupy* claims to be & represent, we at 
Planetary
think it's very important to place extraordinary priority 
attached
to those users most impacted by the greed and oppression we have
united to combat.

yours in solidarity,
@planetary_io
http://plntry.net





On Fri, 11 Nov 2011 23:27:38 -0800 Matthew Lepacek
<pursuitofliberty@gmail.com> wrote:
Tech ops is currently seeking mobile platform developers to 
begin
development of such an application.  There is a wealth of ideas
and methods
of implentation available but a first step is collecting actual
developer
resources so we can determine a platform for development, with 
the
hope of
creating one framework-product that will work on most
android/iphone/blackberry devices.  After we have gathered a 
list
of
development-programmer resources we will conveign a series of
meetings to
hash out the best platform solution.  After a universal 
platform
is chosen
we can engage in the idea exchange of features and advisories.
The goal at
this time is not to change a single thing about GA process, but 
to
compliment it 1:1 for our beta app.

I'm attaching an example concept mock-up of a system proposed
utilizing
professional voting keypads at a cost of $13/ea.  We are 
getting a
demo
system of a few commercial audience polling systems from
replysystems.com,
enjoy-ars.com, powervote.com, and clickapad.com but we are 
seeking
to also
develop our own unique smartphone solution using WIFI for the 
long-
term.
Part of this smartphone platform is ensuring that we have 
enough
devices
for everyone to participate, which will involve donations of 
older
smartphones from the public.  Our hope is that the publics
generocity will
be suplimented by donations from manufacturers/retailers.  
Those
that have
a compatible smartphone will be able to use it, but whose who 
do
not--we wil make them readily available.  At this time there is 
no
discussion as to whether this will be adopted by the GA, we 
merely
want to
present the option and develop it with the hopes of it being
accepted.
There are no guarantees.

Anyone who has experience developing mobile applications please
email me
mattl@nycga.net

Thanks,

Matthew Lepacek
mattl@nycga.net
347-684-7285

On Wed, Oct 26, 2011 at 2:06 AM, Naqeeb Memon
<naqeeb@108production.com>wrote:

Everyone -
I would like to propose that we build an iOS / Android app 
that
will allow
Occupy Wall St (OWS) to be directly connected to the people 
and
help grow
the movement.  Facebook is a great tool but a Facebook Post /
Event don't
have the same reach as an app installed on a user's phone and
tweets are
lost in the stream. Please review and provide any
feedback/requests/comments:

*Features*

   1. Allow Users to follow/participate in OWS events in 
their
   prospective cities.  We will begin with NY and expand to
other cities.
   2. Notify Users of the next OWS planned protest through
notifications,
   events etc.
   3. Notify OWS of arrests during the protest.  The user 
will
be able to
   report an individual arrest or their own arrest
   4. Allow OWS to share latest updates/content/requests with
users in
   their prospective cities.


*Next Steps*

   1. Reach out to the Media Work Group to get their feedback
and feature
   requests
   2. Prototype iOS / Android functionality and look and feel
with OWS
   Design.
   3. Find developers


Thanks,
Naqeeb

_______________________________________________
Ows_solutions mailing list
Ows_solutions@freenetworkfoundation.org



http://freenetworkfoundation.org/mailman/listinfo/ows_solutions_fr
e
enetworkfoundation.org






-- 
Thanks,
Dallas Carter
< PREV INDEX SEARCH NEXT >