How about we get together on IRC, tomorrow (Sunday) please suggest a time. So everyone can op-in his point of view, I really want to get this going (Gsoc or not) but I don't want to start working on something and then find out it's not going to go or someone else already did it. The way I see it we have several opinions, in no particular order.
a- make tg.org a comunity gathering site, where people can post their bio, their proyects, companies and job offers. b- the same but without the jobs c- make tg.org a "tutorial site" showcasing lots of tg technology but none of the above. d- make a as a separate site with a different URL. e- make 2 separate websites, b | c & d how about it? PS: sry for the late reply, but I had a virus issue on my laptop, which turned into a reinstalll issue, which turned into a partition table issue, which turned into a full backup and full restore issue, which turned into not having several installers, which turned into lots of wasted time. On Fri, Mar 28, 2008 at 11:50 PM, Jorge Vargas <[EMAIL PROTECTED]> wrote: > > On Fri, Mar 28, 2008 at 12:58 PM, Christopher Arndt <[EMAIL PROTECTED]> wrote: > > > > iain duncan schrieb: > > > > > On Fri, 2008-28-03 at 16:43 +0000, Lee McFadden wrote: > > >> Hi Jorge, > > >> > > >> On Fri, Mar 28, 2008 at 1:31 PM, Jorge Vargas <[EMAIL PROTECTED]> > wrote: > > >>> my original idea was to build a job-seeking website for TG, but it > can > > >>> be molded into being merge with the main site. > > >>> > > >> I actually already started a repository for this[1], although I am yet > > >> to upload any code. I will be coming out of my current heavy workload > > >> very soon and look to start making this gigboard app then. Maybe we > > >> could work together on this task? > > >> > > >> [1]: http://code.google.com/p/gigboard > > > > > > I'd be happy to kick in some templating/CSS'ing if that would help. I've > > > been doing a lot of nit-picky front end lately and have all the major > > > platforms set up at home for testing. I assume we'll use Genshi? Had you > > > thought of what the javascript will be based on? jQuery anyone? ;-) > > > > > > Maybe we could even make sure the site (eventually) uses the layouts/css > > > strategies that we were brainstorming including as examples or > > > something. > > > > > > Guys, before you delve too deep into the technical aspects of a future > > turbogears.org site, we need some kind of marketing / public relations / > > web site strategy first. It makes no sense developing new features for > > the site before we know what we want from it and what the goals are. > > > > To be honest, the proposal in it's current form will probably not get my > > support. > I'm open to your suggestions. if we end up making two websites then so > be it. But I'll really like to go for the community site instead of > just a bunch of tutorials, I believe we'll get more tracks on TG if we > have an enfasis on real life applications, hence the jobs, > companies,etc. components. > > As for Lee's proposition it was briefly discuss a while ago, and I'm > interested too, although if this doesn't gets accepted by soc we'll > need to work out the sharp edges and see if our visions of the app are > compatible or not. > > > > > > Chris > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
