RE: admin or version control system? I think sprint-type activity would be better handled by distributed SCM and workgroups working on their own copies of app, and cross-pulling. That type of work model is not web2py dependent, and calls for a "task manager" who then merges, and pushes to a "master" place - that master can be a deployed site (after testing of course!).
I think any teamwork in web2py admin should be considered for small scale instances - collaborating on small changes. Any more "demand" on web2py admin would impose requirements on the admin which I think are (1) not in line with rapid web development (rather focus on team-ware use cases), and as such would be a distraction from the main goals of web2py, and (2) I don't believe they would be likely to serve a serious agile development team as well as alternatives (eg workgroup clouds, using local git/hg/bzr to coordinate). Those are just my current thoughts... and not immutable. Regards, Yarko On Mon, Mar 2, 2009 at 12:59 AM, aunger <alexander.unger.br...@gmail.com>wrote: > > I'm working with a team of 4 developers on a new web app. We are > evaluating web2py and are wondering how team based development works > in web2py and what is setup in the admin interface for that. > Thanks. > > -Alex > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
