My mind immediately JUMPED at JohnMc's suggestion of a calendar - Useful everywhere; useful in CMS, in community sites, even in eStore where you sign up for events (as opposed to shippable products - e.g. seminars, haircut appts, etc.)
Massimo's like just gives the front end - all that's left to do is a base backend (I would guess).... This seems simple enough to do little more than flush processe, but yet result in a useful module. Who'd like to sign up for an on-line IRC coordinated series of sessions & code sprints? They will seem boring, as working out the mercurial push/merge/pull run cycles, and getting them short enough so that things actually feel and act like sprints may at first be a distraction. 3 of 4 hearty souls? I would guess 2 or 3 sessions; product would be a web2py calendar scheduling module AND a guidesheet for online sprinting / projects. - Yarko On Sat, Jul 11, 2009 at 5:07 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > I like this very much. About your calendar project: > > http://www.bytecyclist.com/SourceCode/jMonthCalendar/1.3.0-beta/Demo.html > > massimo > > On Jul 11, 4:48 pm, JohnMc <maruadventu...@gmail.com> wrote: > > Joe -- > > > > I disagree as well. Even though I have said more than once docs are a > > weak point. But it is being addressed. Might I suggest, Massimo > > released 3 chapters of the new book. Have you reviewed them and > > possibly sent in corrections? Proof's in the pudding. > > > > Yarko, rest -- > > > > Want something focused, gets out the kinks on process and has > > something to show for it in the end process? > > > > Why not turn the editorial proofing of the V2 of the book into a > > series of sprints? If nothing else it will validate the 'process' for > > everything else going forward. If Massimo approves, its his IP. > > > > As to projects to tackle. I see nothing wrong with either CMS, Wiki, > > or eStore. If you ran these suggestions thru a UML you will end up > > with some constituent subcomponents. > > > > * editor come tag tool. Ends up being common to all three. > > * intelligent storage. A means to properly categorize content, filter > > it, sort it in a common way. Maybe an XPath like metaphor higher level > > than the DAL for most common searches? DAL directly for more > > sophisticated queries. Common to CMS, Wiki, Blog and catalog > > descriptions in an eStore. > > * Calendar function. An iCal based engine plus a base level class for > > display. Common to CMS, Wiki, Blog. > > * Workflow engine. Leverage off the cron functionality but extend it > > to trigger tasks in sequence and in parallel as the work flow > > dictates. Tasks would validate predecessors are complete. Common in > > CMS, eStore. > > > > With those subcomponents in hand tackling the higher level projects > > start with around 50% of the work already done -- once. This also > > gives those interested exposure to these tools before launching a > > larger project. > > > > JohnMc > > > > On Jul 11, 11:34 am, Joe Barnhart <joe.barnh...@gmail.com> wrote: > > > > > I think its a complete diversion of effort and a waste of time. > > > > > The reason we don't have meaningful apps on web2py is because nobody > > > can figure out how to use it. The documentation SUCKS. Hello??!? > > > Haven't we had this discussion endless times already? > > > > > We are the same group who couldn't create our own WIKI in web2py so we > > > could have a PLACE for documentation. Instead of fixing the wiki > > > we're going to hike the banners and storm the walls of other platforms > > > by doing our own CMS? > > > > > We need cohesive documentation so we can grow the pool of web2py > > > users. Useful meaningful applications will come if we have a user > > > community with depth. Which we DON'T at present. > > > > > -- Joe Barnhart > > > > > On Jul 10, 1: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 > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
