20 Sep 2012 06:50
A proposed goal for the Sea Sprint
Hey sprinters (and other plone-developers)! So I've been poking at the current state of Deco a little bit in preparation for the sprint, and wanted to send some thoughts and get some discussion going about where we should focus our efforts. Here's what I suggest as an overall sprint goal: as a Plone site administrator, after the sprint, I can install plone.app.deco and use it to create a reasonable home page and/or landing page for my site, without worrying about it breaking things in my site. There are certainly plenty of more ambitious goals related to deco that we should keep in mind (such as using it to build layouts for custom content types, replacing tinymce, or moving all of Plone's UI into overlays), but we also need to be realistic about the fact that we'll only have 2 full days (and nights) of sprinting, and we have received generous support from numerous donors to whom we should deliver something in a usable state. I think getting the homepage/landing page story right is a focused goal that we can achieve in our short sprint. To that end, I think we should be working with the "deco-1.0.cfg" variant of the buildout.deco buildout. (You have already cloned and built this, right? If not, now's the time, so that we don't waste the first part of the sprint waiting for eggs.) If you don't know, the only difference between deco-1.0.cfg and deco-2.0.cfg is that the latter uses a newer branch of plone.app.toolbar that loads everything linked in the toolbar in overlays. That's a good thing for us to work on, but it doesn't seem ready (links in the contents and site setup views don't work, for example) and in general it seems like a distraction from the main focus of the sprint (getting something that works and is not risky to install). Rok, please correct me if I've misinterpreted the current state of things and using p.a.toolbar 1.x won't work for some reason.(Continue reading)
> my personal views on some comments I read on the thread:
>
> 1. please kill the portlet history right now; we only need tiles and tiles
> are easy to write
> 2. I'm not really sure about replicating the functionality of a collection
> inside a tile; maybe I misunderstood the idea of this tile, but I think that
> can be solved having a collection and a tile that displays its results
In the "full Deco" vision, there would be no Collection content type.
Instead, you'd add a Page to your site where you wanted to display a
listing of content, add a Listing tile to it (and other tiles, for
content around the listing), configure it (much like the new
collections are configured now), and that would be that.
I don't think it's terribly user friendly to have to create a "secret"
collection somewhere in content space that you don't expect your users
to see, and then create a secondary content object (a page ala
collective.cover) to render it in situ.
> all of our code base and ideas are yours; use it. if we can move anything
> away from collective.cover to Deco we will be very happy; we will refactor
> our package after that.
>
> last thing I want to say: Chris Calloway told me that maybe the Sea Sprint
> wouldn't be happening without the Cafecito Sprint.
Oh, I'm very sure. Anything to drive this story forward is important.
And, crucially, we need to solve people's real-world problems today to
evolve a vision, not set some grand vision for the far-future and do
nothing until we've got it perfectly built. I think we do need a bit
of a vision, though, even if it changes over time.
> I've been working with the people behind this project for over a year and I
> feel like a very privileged guy.
>
> you probably don't know many of them; most of them are pretty young, but
> they are very skilled and professional: we have, together, more than 30
> years of Plone development experience in different areas.
The code looked really good, certainly.
> for me it has been difficult to make some of them understand the importance
> of being known and the imperative of participate on the discussions of this
> list about the future of Plone.
I think "being known" doesn't mean you're part of some clique. It
means that you've contributed code, documentation, support on the
forums etc.
> this is the first time Gonzalo is going to be with you and he's very excited
> about that; please talk to him: teach and learn.
Welcome 
RSS Feed