Re: [Framework-Team] plone products leaders (v2)

[Hanno Schlichting]

Hi,

Tom Lazar wrote:
 On Mar 17, 2007, at 8:35 AM, Thierry Benita wrote:
 
 What do you think of this idea ? Do you think that it is
 possible/affordable ?
 
 + 100 and thanks for the nice writeup, i think this initiative comes at
 a very good time, because on the one hand we definitely need to lighten
 the load of responsibility that currently is divided among the very few
 shoulders of our 'rock stars'.

Personally I would love to divide some of the load on more shoulders.
Especially mine are getting busier with other responsibilities and I
want to avoid to become a bottleneck...

 take hanno's `statusmessages` product for instance, a super small
 product all in itself. just yesterday i found a bug in it and given the
 fact, that the entire functionality is just a few lines of (isoltaed)
 code i was (surprisingly) easily able to come up with a patch.
 
 however, now that i'm fairly familiar with this product's inner workings
 i already would feel confident taking over maintainership of it, while
 hannosch still remains 'mentor' of it.

Consider yourself the new official maintainer of it ;) I'll do one last
release tomorrow so you start with a clean state :)

 so, perhaps, to ease the transition the current de facto maintainer of a
 package could offer 'mentorship' (i.e. provide support for the
 maintainer, as opposed to everybody).

I'm willing to do that for all the packages I'm currently maintaining.
There are some where I don't understand enough about the inner workings
to mentor anybody though, but I shouldn't maintain those in the first
place... one example being ATReferenceBrowserWidget which constantly
breaks due to the sheer amount of configuration options in conjunction
with exactly zero tests.

Hanno

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

[Framework-Team] The big 3.0 ;)

[Alexander Limi]

Hi team,

I'm in the process of entering stuff in the issue tracker this weekend  
(that thing needs a thorough scrubbing, let me tell you ;), and this is  
how my current list looks like.


I'd appreciate feedback, especially on what needs to be resolved before  
beta/RCs. I just wanted you to see the list I currently have, I'll make  
sure all of them are handled in a proper manner (ie. get issues in the  
tracker). Hopefully people at the Sorrento sprint can take a shot at  
fixing these as well.


Time is tight these days, and I just recovered from a fever/cold, but I'd  
rather overcommunicate than be too silent. No panicking about the list. ;)


Fix before beta:

- KSS vs. CMF errors
- Kupu doesn't work either at the moment, probably related to the
  KSS/CMF issue

Fix before RCs:

- KSS:
- Reduce file size, it's currently way too heavy
- Get a basic UI on ÜberSelectionWidget

- Archetypes
- After we removed JS from checkboxes, they no longer stick
  (really!). Might have to put that back, even though it sucks
- There's something strange going on with enabling comments, it
  only works on the initial view of the page after saving,
  possibly related

- NuPlone theme
- Be complete and functional by RCs, tested in IE6 too
- Be the default in RCs if the above is the case ;)

- Kupu
- Make sure the control panel removes stuff that is no longer
  relevant with the HTML Filtering control panel
- Make sure you can't insert images that are bigger than
  Preview size by default
- Include additional default styles (highlight, table
  variations)

- Wicked
- Needs to use createObject?type_name=Document — the way it is
  set up now, anything spidering the site with credentials will
  create objects, and any object clicked will create objects
  (this change will make it invoke portal_factory)
- Support both (()) and [[]] syntax by default, so we can
  remove this preference from the control panel (exclusively
  using either is still supported behind the scenes, of course
  — just not in the standard control panel)
- Wiki control panel can be removed, only needs wiki syntax
  on/off switch in the control panel

- Fieldsets
- Do we still support fieldsets that require something on
  fieldset #1 to be filled out before you can access fieldset
  #4?
- Next button shows up in the Save/Cancel area when using the
  inline fieldsets?
- Fieldset code: if more than N (N=6?) fieldsets, turn into
  pulldown

- Sensible defaults:
- Make sure the WFs are sensible and default WF decided
- Members folder gets created even though it's turned off?
- Only HTML available as format by default, everything else
  assumes knowledge of markup
- But make sure it supports loading existing documents that
  are in other formats already
- Enable wiki support by default on most types? it's unlikely
  to trigger accidentally anyway
- Both the Navigation and Search control panel does not show
  the Friendly types list, but uses the full list instead,
  should be fixed (user does not know what a ChangeSet or
  Relative Path Criterion type is ;)
- Remove personal prefs from the global prefs section
- Don't install the following by default:
- Content Rules
- Can the old-style Add-on products support TITLE.txt to match
  the new style products' ability to have a friendly name?
- Preferrably move the Collections (Smart Folder) control panel
  to a ZMI version, since it is very complex and not something
  site admins are likely to need
- Put back autofocus behaviour now that we have ondomload (make
  sure tabindex is correct)
- Move sendto/print/whatever to bottom of page, use text
  representation
- Combine delete confirmation page with integrity checking
  (having to say yes/no on two separate pages sucks :)
- Only show the Display/Add/WF pulldowns on the View screen
- Possibly remove the border on initial creation forms (ie.
  keep the actual green border, but remove everything
  clickable on it, since it causes errors)

- Other
- Get rid of all the deprecation warnings in the core
- Why is Members folder showing up even if that is disabled by
  default now?
- Is there any way to get formlib to support our
  checkbox-before-label UI policy? (see control panels for  
examples)

- Users seem to be listed twice in the control panel
- You are adjusting the sharing privileges for a default view, to
  adjust them for the entire