I'm forwarding this to the public mailing list, sry for the late reply but the original responses got caught up on a gmail filter.
Hi, I just realized that this project could be done as a gsoc.
main goal: upgrade the site to be a TG application, showcasing most of the technology around TG2.0.
my original idea was to build a job-seeking website for TG, but it can be molded into being merge with the main site.
high overview of features.
People -- some general info about himself. he can create Jobs, apply for Jobs own Sites and belong to one or more Companies,orgs,etc. Jobs -- a description, TTL, public or private replies to it, maybe a bid thingy? Sites -- url, description, screenshot?, info about it in general. Companies,groups,organizations -- same as the site, just info.
so I'll add to my original idea the following. redo the cogbin, redo the news part. and maintain "two fronts" one that will be pretty much what we have now (for developers) and the other for people seeking developers (mostly oriented around the jobs part)
as a plus I'm thinking of having a "how I did it" for each page that is relevant, that will explain the code behind each mayor part of the site, so it could work as both documentation and a tool, although I'm not sure if this will be too much work for the timeframe.
the whole thing will be ajaxy-web2.0y to throw in some buzzwords, but the general idea is for the site to be super easy to use and demonstrate the best aspect of the framework.
components I plan on using (so far) SQLAlchemy - maybe elixir tosca widgets mako new tg2.0 auth layer (i'm not 100% sure of the stability of that one)
PS: sry for coming up too late with this, I wasn't aware of the dates, but I still got the rest of the week to apply. PS2: if this project isn't accepted I'm still willing to work on the system.
On Fri, Mar 28, 2008 at 1:31 PM, Jorge Vargas <jorge.var...@gmail.com> 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?
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 <jorge.var...@gmail.com> 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?
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.
On Fri, Mar 28, 2008 at 6:41 PM, iain duncan <iaindun...@telus.net> wrote:
> 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? ;-)
Any help will be appreciated of course :) I need to get the basic framework of the app up and running first though.
For JS I prefer Mootools but I wouldn't complain too much if jQuery were used, it's still a really nice library.
> 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 <jorge.var...@gmail.com> 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?
> 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 was intending to write the gigboard anyway, GSoC or not. I'll move any discussion about it away from this thread for the time being though so as not to clutter Jorge's thread any more than required =)
On Fri, 2008-28-03 at 18:49 +0000, Lee McFadden wrote: > On Fri, Mar 28, 2008 at 6:41 PM, iain duncan <iaindun...@telus.net> wrote:
> > 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? ;-)
> Any help will be appreciated of course :) I need to get the basic > framework of the app up and running first though.
> For JS I prefer Mootools but I wouldn't complain too much if jQuery > were used, it's still a really nice library.
My main objection ( actually deal-killer ) for mootools was that the devs stated that they didn't care a niff about making it play well with others, while jQuery took the opposite approach. I've had no problems using jQuery plus mochikit, but Mootools was an all-or-nothing. To me that doesn't jive with the TG philosphy. ymmv!
> On Fri, 2008-28-03 at 18:49 +0000, Lee McFadden wrote:
> > On Fri, Mar 28, 2008 at 6:41 PM, iain duncan <iaindun...@telus.net> wrote:
> > > 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? ;-)
> > Any help will be appreciated of course :) I need to get the basic
> > framework of the app up and running first though.
> > For JS I prefer Mootools but I wouldn't complain too much if jQuery
> > were used, it's still a really nice library.
> My main objection ( actually deal-killer ) for mootools was that the
> devs stated that they didn't care a niff about making it play well with
> others, while jQuery took the opposite approach. I've had no problems
> using jQuery plus mochikit, but Mootools was an all-or-nothing. To me
> that doesn't jive with the TG philosphy. ymmv!
On Fri, Mar 28, 2008 at 12:58 PM, Christopher Arndt <chris.ar...@web.de> 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 <jorge.var...@gmail.com> 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?
> > 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.
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 <jorge.var...@gmail.com> wrote:
> On Fri, Mar 28, 2008 at 12:58 PM, Christopher Arndt <chris.ar...@web.de> 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 <jorge.var...@gmail.com> 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?
> > > 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.
> 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.
Why don't add a security related section into the turbogears
website? ;)
Don't you think that there is a lack of security informations related
to the turbogears development and deployment?
