On Thu, Mar 12, 2009 at 2:40 AM, Jorge Vargas <[email protected]> wrote:
>
> On Tue, Mar 10, 2009 at 10:09 AM, Florent Aide <[email protected]> wrote:
>>
>> On Tue, Mar 10, 2009 at 2:46 PM, Mark Ramm <[email protected]> 
>> wrote:
>>
>>> http://docs.turbogears.org/GSoC/Ideas2009
>>>
>>
>> I added an idea and a bare minimum formatting in rst for the page.
>>
>> Florent.
>>
> I'll be willing to mentor someone this year. I have been cooking a
> mercurial frontend project which I'll post with more details later.
>
> What is exactly needed for the "administrator" position? I may be able
> to fill that in, although I prefer to be the last candidate as I'm
> already into way too many things.


I would like to see 2 projects:

1. Continuation of a buildbot. Give it some kind of interface and
connect autosetup, auto install , auto epydoc generation to tg and its
requirements and those software requirements. I would like to have
every single package that is pulled for tg to have its own epydoc for
each version that was generated; all on one page.

2. Design turbogears apps online. Similar to web2py. It is an
interface for running and changing apps online. Right now the
turbogears is installed, generated and modified via command line. This
web interface would run commands like "paster quickstart" "paster
setup-app" and "paster serv". After that a user would start modifying
the root.py, model.py, etc via a web interface. This would allow web
designers to go straight to designing the apps instead of command
line.
Web interface:
- "create new tg app"
- "setup database "
- start project
- browse the files
 - modify root.py

Thanks,
Lucas

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to