[CentralOH] COhPy website

[yanovich.1 at osu.edu]

I am more for the option of a static site. Especially if it is brief and
contains this:

* Who we are
* What we do
* Why we care about Python
* How to sign up for the mailing list
* Link to our meetup page
* List of upcoming long term events (something that won't need updated
on a weekly/monthly basis, a good example would be PyOhio)

I favour the static site because it would allow those who are new to
easily figure out how to get involved without having to figure out the
layout/requirements for using meetup.com.

Another nifty idea about having a website for the group would be to
demonstrate the power of Python, and also link to the source code of the
website on Github so others can see how it is done and can
contribute/learn from whatever is eventually set up.

On 04/23/2013 12:10 PM, Brandon wrote:
> I disagree with the philosophy of a static site for COhPy.  The
> static site, while performant, is a different approach how how you
> implement and deploy augmenting features and components.  The core
> demographic and anticipated traffic of COhPy would not benefit from
> the performance and be hindered by the deployment process, in my
> opinion.
> 
> At the forthcoming meeting, we should discuss the stack and vitals
> of this site.  There is an abundance of greenfield work and feature
> set to be done.  Let's ensure that the solution is sensible for us as
> COhPy and develop a strategy first.
> 
> I suggest COhPy create a public git repo on GitHub or Bitbucket where
> a core maintainer(s) can monitor pull requests.  This endeavor should
> be an open source accomplishment in the truest spirit of the Python
> community.
> 
> -Brandon
> 
> On Apr 22, 2013, at 6:09 PM, John Santiago <jdsantiagojr at gmail.com 
> <mailto:jdsantiagojr at gmail.com>> wrote:
> 
>> Yes I am def. interested in helping with development. Or getting 
>> started. Just need some direction. -john
>> 
>> Austin: congrats on the move. I lived in Arizona for a few years. 
>> Really liked it.
>> 
>> 
>> On Mon, Apr 22, 2013 at 4:45 PM, Brian Costlow 
>> <brian.costlow at gmail.com <mailto:brian.costlow at gmail.com>> wrote:
>> 
>> Eric, Austin,
>> 
>> I know John Santiago was interested in doing some work on the COhPy
>> website.
>> 
>> If he doesn't notice this and speak up, grab his info from 
>> meetup.com <http://meetup.com>.
>> 
>> Pretty sure he RSVPd for the next COhPy.
>> 
>> 
>> 
>> 
>> On Mon, Apr 22, 2013 at 4:03 PM, Eric Floehr 
>> <eric at intellovations.com <mailto:eric at intellovations.com>> wrote:
>> 
>> Right now, COhPy.org <http://COhPy.org> redirects to the meetup
>> page. There was some talk at a few of the previous meetings about
>> building an actual web app (in Python of course :-). I just wanted
>> to share something from the Python group organizers link that might
>> be of interest.
>> 
>> The Kansas City group is still using meetup, but is using the API
>> and hosting on gondor.io <http://gondor.io> (same place used by
>> PyOhio.org <http://PyOhio.org>) a custom web app. Here is the
>> original newsgroup email:
>> 
>> -------------------------------
>> 
>> I'm Juan from Kansas City and you're right that we do use the 
>> meetup API to pull information from meetup.com <http://meetup.com/>
>> and display it in our website.
>> 
>> You can take a look at our website here: http://pythonkc.com/
>> 
>> and the source code for the website is here:
>> https://github.com/pythonkc/__pythonkc.com 
>> <https://github.com/pythonkc/pythonkc.com>
>> 
>> We host the website on Gondor (https://gondor.io/) so there's some
>> Gondor specific stuff in the code, but you can modify it to re-use
>> it on any hosting provider.
>> 
>> Hope this help and I'd be glad to answer any other questions you
>> might have.
>> 
>> -------------------------------
>> 
>> 
>> _______________________________________________ CentralOH mailing
>> list CentralOH at python.org <mailto:CentralOH at python.org> 
>> http://mail.python.org/mailman/listinfo/centraloh
>> 
>> 
>> 
>> _______________________________________________ CentralOH mailing
>> list CentralOH at python.org <mailto:CentralOH at python.org> 
>> http://mail.python.org/mailman/listinfo/centraloh
>> 
>> 
>> 
>> 
>> -- This electronic message is intended to be for the use only of
>> the named recipient, and may contain information that is
>> confidential or privileged.  If you are not the intended recipient,
>> you are hereby notified that any disclosure, copying, distribution
>> or use of the contents of this message is strictly prohibited.  If
>> you have received this message in error or are not the named
>> recipient, please notify us immediately by contacting the sender at
>> the electronic mail address noted above, and delete and destroy all
>> copies of this message.  Thank you. 
>> _______________________________________________ CentralOH mailing
>> list CentralOH at python.org <mailto:CentralOH at python.org> 
>> http://mail.python.org/mailman/listinfo/centraloh
> 
> 
> _______________________________________________ CentralOH mailing
> list CentralOH at python.org 
> http://mail.python.org/mailman/listinfo/centraloh
> 

-- 
Michael Yanovich

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/centraloh/attachments/20130423/e10f3016/attachment-0001.pgp>