I think it would be a good exercise to start from there. I do know if sachmo has this but we it would be nice to a web service layer so that users can develop frontends in html (the default) or Flex (via standard APIs provided by the system).
On Jul 10, 4:11 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > I think for a CMS, defining what to do, how it would look initially, and > it's structure could take some time to review the "best" (or most used) > CMS's and what they offer. The basic structure should not be too hard to > start (Massimo has started several times). > > A wiki is probably a core component of this, so considering the components > of a CMS might spawn several projects. > > I'd just want to be sure to start with something that will work, will show > how to work in sprint teams, and will produce results rather quickly. Then > more ambitious projects will have a way to gain traction. > > On Fri, Jul 10, 2009 at 3:56 PM, eric cs <eeri...@gmail.com> wrote: > > > We have to beat them...hehehe > > Rails for Spree and Magento for Php/Zend. > > At least Magento for inspiration. > > > On Jul 10, 4:49 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > > > Those are bigger, more ambitious projects. > > > > We could start with something shorter, just to work out the task force > > > processes.... > > > > Perhaps a web2py resources site, an update to the appliances app could be > > > the first part of that (and an update to it). > > > This will give us relatively little to do, and we can work out what will > > > work: > > > > I would like to see "regular" meetings (IRC), and _real_ distance, > > on-line > > > code sprints... so that a 2 hour session will find everyone coding a > > piece, > > > and a leader merging and running it live for all to review, update, etc. > > > (leader to push up to a launchpad, or mercurial). > > > > One of the process things to work out: stay launchpad, or move > > > code.google.com / mercurial. > > > > The latter would give us (if they've worked it out) a code review site, > > > which would be a great way for task force to work asynchronously (e.g. in > > > between code-sprint meetings). > > > > Code sprints would be useful - if the balance on a team was 3 / 2 or so > > of > > > experienced python-web2py-ers, vs people wanting to learn, stretch it > > would > > > be a great way to regularly have a place to join in --- real "community" > > > stuff. > > > > How does this sound? A simpler job to work out the basics of the > > working > > > process, find what will work for starters. > > > > - Yarko > > > > On Fri, Jul 10, 2009 at 3:37 PM, eric cs <eeri...@gmail.com> wrote: > > > > > I am in...but no knowledge, just wanna help and learn on the process > > > > if that is possible, count with me. > > > > > On Jul 10, 4:32 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > I think we need to build two task forces. > > > > > > 1) to build a CMS > > > > > > 2) to build a eStore > > > > > > the more overlap the better. We need two project leaders and > > > > > volunteers. I also suggest starting by creating google docs to gather > > > > > requirements. > > > > > > Lots of people needs these, including me. > > > > > > Massimo- Hide quoted text - > > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
