Re: Sprint: clean up Plone day [was: A few suggestions]
David Glick <davidglick-PRw/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
On Nov 27, 2008, at 11:26 PM, Dylan Jay wrote: > Thanks so much for the info David. I suspected that there was a lot > of these > simplifications going on. > > I think the stuff that's being rethought is already being taken care > of > well. So is there anything left over that doesn't need completely > new design > but rather just recoding? Same functionality, same api just remove the > obsolete technology. There probably are some. However, one problem is that we don't really have a well-defined API. Anything that doesn't begin with an underscore is kind of fair game. And another problem is that choice of technology usually has implications for the API by which an item is used. e.g. you specify form actions one way with CMFFormController forms, and a completely different way with formlib and z3c.form. > The two you brought up are good examples, user registration and > commenting. > > I don't think it needs a sprint by core devs to identify these but a > sprint > or tune up day might be a good place to harness new volunteers to > refactor > this code. It would love a public list of core components that I could > refactor if I had a spare weekend or better yet could do in a remote > sprint > in conjunction with a team headed by a core developer. > > Only someone with more of an architectural overview than me could > answer if > that is possible or even wise. Jon Stahl proposed a similar thing a few months back, see the discussion in this thread: http://www.mail-archive.com/[email protected]/msg01848.html We recently added a "feature request" ticket type to Plone trac, which IMHO is a good place for core developers to record cleanup/refactoring sorts of tasks as they come to mind (and then follow-up discussion of consequences and implementation details). Regardless of size of the task or whether it will end up being PLIPped. > And yes as you point out the process would have to result in new > code + more > api documentation + more unit tests. > > Dylan Jay > Technical Solutions Manager, PretaWeb.com David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidglick-PRw/[email protected] work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/