just joined
vonn...@gmail.com
I just heard about this project from a Fractured Atlas email.
I'm a Drupal developer and interested in learning more about ATHENA
Tix.
It sounds like a really useful project.
Ryan Price
One thing that concerns me from a technology angle is Athena's big-
brother relationship with the Kuali project - I don't have any
experience with it, but after digging in their wiki, I see they
require Java and Oracle ... I was shocked that something meant for
free use, by nonprofits would not use a dynamic language and an open
source software stack. There are some great options out there.
Then I saw the Oracle XE edition, which is free for individual or non-
profit use, and that made it a bit easier to swallow. Still, it's a
bit like saying Rupert Murdoch is giving out free copies of the Wall
Street Journal to homeless people.
Peace,
Ryan Price
rpr...@ryanpricemedia.com
@liberatr
407-484-8528
FloridaCreatives.com
3rd Anniversary Happy Hour: Dec 21st @ Crooked Bayou
Next Likemind: Jan 15th @ Drunken Monkey
FL DrupalCamp: Feb 20th + 21st
http://2010.fldrupalcamp.org -- @fldrupalcamp
Adam Huttler
Justin can weigh in on this with more details, but I just want to clarify
that we'll be using an entirely open source software stack.
The ATHENA platform will be developed in Java, using a service oriented
architecture and leveraging lots of existing open source modules. That
should make it exceedingly easy to integrate with other non-Java
components. We haven't committed to any single database yet, but I'm
confident we'll be able to make it work with any number of options,
including MySQL and PostgreSQL.
My own background includes lots of PHP and Rails development, so I'm more
than sympathetic to the appeal of light-weight, dynamic languages.
However, the long-term ambitions of the ATHENA project require a somewhat
more "enterprise-y" architecture. (Believe me, I fought this long and
hard, but was eventually persuaded that it's the only sane approach.)
There does indeed seem to be some early interest in integrating Drupal and
ATHENA Tix, which would be really interesting to explore. Not sure what
the next steps are, but perhaps we can begin by identifying the interested
parties...
Adam
David
I was wondering what featres of CRM Athena might have. If there is a
lot of interest in integrating with Drupal what is the likelihood of
the software integrating with something like CiviCRM, which is a free
donor management system that uses Drupal.
David
On Dec 9, 10:32 am, "Adam Huttler" <adam.hutt...@fracturedatlas.org>
wrote:
Vonn New
I'm in the process right now of implementing an event management system (conferences) using Ubercart, signup and uc_signup.
Peace,
Vonn
Vonn New - Raising consciousness, one eyebrow at a time.
Visit my websites:
http://www.vnew-tech.com <-- website design and audio services
http://www.vonnnew.com <-- Listening for Muses - music, art and musings.
http://hemingwayscat.com <-- eclectic homegrown music
Stjepan
interest to have mobile devices (e.g., running Android) interface with
ATHENA Tix?
Really cool - nice work, Fractured Atlas!
Best,
Stjepan
http://urbanstew.org
Adam Huttler
guess), so I'm sure we'll want to put some thought into integrating with
existing systems in the meantime. I've heard good things about CiviCRM, so
maybe that's a place to start, especially if the community's interested in
Drupal integration more generally. Salesforce (the free version for
non-profits) is also worth considering, along with Tessitura.
Justin Karr
I'll second what Adam said and also point out that so far our commitment
to depend on Kuali is for its middleware suite, Kuali/Rice. Kuali/Rice
includes MySQL as one of its supported DBs
(http://rice.kuali.org/documentation/1.0.1/IG/ - see "required database").
Also, it uses a JDBC architecture, so I am confident we can make it work
with any mainstream JDBC-friendly databases, including the most commonly
used open source ones.
In terms of the language and architecture choices, more fundamentally than
"what language are we using" is "what methodology are we using" and the
answer to that is SOA. We intend ATHENA Tix (and the other ATHENA
projects, as they appear) to be a system of components, some or all of
which organizations can chose to implement. This does two things.
1. It lets organizations integrate with their existing stuff and use only
what they need. Have a great Rails website you want to add ticketing to?
Deploy the ticketing engine as a service without a front-end. Use
pick-your-favorite-rpc-tech* to communicate with it directly from your
front end.
2. It lets organizations re-implement the components they need to
re-implement without making them re-implement the entire system. You
really need the price-setting-workflow* bit to be implemented in PHP?
Fine, re-implement that part and keep the rest.
This post raises a really important topic for me that I am going to start
in other post. Something that we didn't have time to do in the design
session is actually run through a list of what technologies organizations
want us to integrate with right away. (Drupal is an active, early
favorite.)
Justin
*We are still in the planning phase, please do not interpret this as a
promise to support XYZ rpc tech or have a component called ABC.
Adam Huttler
friendly to mobile browsers.
> -----Original Message-----
> From: athena-ti...@googlegroups.com [mailto:athena-tix-
> plan...@googlegroups.com] On Behalf Of Stjepan
> Sent: Wednesday, December 09, 2009 11:01 AM
> To: ATHENA Tix Planners
> Subject: [athena-tix-planning] Re: just joined
>
>
Justin Karr
all new messages about DB support there.
On Dec 9, 11:04 am, "Adam Huttler" <adam.hutt...@fracturedatlas.org>
wrote: