There is not a regular "Pylons" group but there are the front range
pythoneers that meet the third wednesday of every month.  There are a
few members there who use pylons.  Here is more information on the
sprint: http://docs.turbogears.org/SprintOrganization  You are of
course welcome to participate remotely.

cheers.
-chris



On Feb 12, 4:06 pm, Elisha Cook <[EMAIL PROTECTED]> wrote:
> Actually, I live near Boulder (Lafayette), but I will be in England
> that week. I'd love to participate remotely and definitely will be
> around for the next one.
>
> Is there a regular Pylons group in Boulder?
>
> On Feb 12, 4:00 pm, percious <[EMAIL PROTECTED]> wrote:
>
> > TG2 is largely based on pylons, and in fact the worldwide sprint is
> > going to be concentrating on both technologies.
>
> > Why don't you come down to Boulder on September 23rd and have at it!
> > I am sure that there are lots of things to work on.
>
> > cheers.
> > -chris
>
> > On Jan 26, 11:25 pm, Elisha Cook <[EMAIL PROTECTED]> wrote:
>
> > > Hi all,
>
> > > I am an experienced web developer and, until pylons, have always used
> > > my own frameworks/components rather than be restricted to someone
> > > else's idea of how I should design applications. So thanks for
> > > building a tool that is so helpful I pretty much forget it's there.
>
> > > I'd like to offer any help I can. I've dug through the archives of
> > > this list looking for obvious starting points but there are so many
> > > facets I thought it might be more effective to just ask if there are
> > > any particular areas in need of some attention. Perhaps some grueling
> > > drudge work no one else wants to do?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to