Ah! I've finished reading Nate and Vince's replies. I think we are leaning in somewhat the
same direction. I'll clarify some thoughts I have again for the mix, and consideration
on Saturday.

I agree that we definitely do not want many different programs running that we cannot
maintain. So first regarding the blog aggregater, simplepie, as setup now its actually
just as simple as me providing the http of the blogs we want to aggregate. And one
simple include file (the simplepie one) and creating a cache directory. If we want something
branded, of course we would need a CSS. But other than that simplepie is basically done.
And as a result many of the issues related by Nate shouldnt be an issue with that.

Now regarding the issues of CMSes, Forums, Wikis, and so on all trying to integrate, I am
very much on exactly the same page here. A forum is a prime example. First I'll state that
I think we definitely need one, because, as mentioned in a previous email, we wont have
access to the Mysql data of our forum here at meetup.com. Unless they've created an API
in the last couple months, we'll have to copy and paste. So I want to eliminate that when
reasonably possible. But I also think we dont need anything very fancy in a forum. We just need
to be able to post topics inline just as meetup.com's does. We can add categories later if we
choose. (Or immediately..its actually pretty simple to code this). Next we need to store who
made what posts...also pretty simple. Then maybe allow some markup (maybe not) and
ability to link. Other than that I dont think we need much more in a forum. If we did this
we do get something usable fairly quickly, without either vendor lockin (in the case of
proprietary software) or project lockin (in the case of Free and Open Source Software).

I am totally on board with single sign in. In my work with the Joomla team, one of the things
I have noticed, is those wishing to build bridges into Joomla, are basically just seeking a
way to have Joomla users added to their system, so again there can be single sign in.
If we create are own software, we can follow a standard here as well.

Another important factor brought up several times, is that doing this can create a training
cycle for all of us.

Ok basically I am just stating what Vince and Nate have already stated. We get something very basic
up, nothing fancy. Determine our barest needs, set that in motion, but do so in such a fashion that
it allows us to grow the site and association in whatever direction we are hoping, and might
choose in the future...without lockin from ourselves, our those we get software (or content)
from.

All of these conversations that yall are bringing up are excellent ideas and definitely we should
consider all of these ideas at our meetup on Saturday.

Kind regards,
Joseph James Frantz