[Product-Developers] Modifying existing product in the collective

[Tim Knapp]

Hi,

There was some conversation[1] recently on the Plone Enterprise list re.
etiquette (is this the right term :) to follow when proposing an update
to a product in the collective. I was just wanting to send a message to
the list for feedback in the case where a developer has attempted to
contact the product maintainer a reasonable number of times (see
forwarded messages below) but hasn't had a reply - what to do then? Do
products just stagnate or can they be taken over if the original product
maintainer is longer actively maintaining it? How would I/someone else
get access to the product page on plone.org to update it?

The code change I propose has been tested in a production environment
(and is still being used successfully on a couple of sites).

Thanks in advance,
Tim

[1] http://www.nabble.com/collective.solr--tt15908099.html#a16028706

-------- Forwarded Message --------
> From: Tim Knapp - Emerge Technology <tim at emergetec.com>
> To: Mikko Ohtamaa <mikko at redinnovation.com>
> Subject: [Fwd: Implemented DisplayField in customsearch]
> Date: Tue, 22 Jan 2008 11:06:34 +1300
> 
> Hello again Mikko,
> 
> Just following up on this email below. The updated customsearch (with
> the DisplayField option is now being used in a production site[1] and
> I'm just about to implement it on another site as they require this
> feature there too. So I was just wondering if you'd had a chance to
> consider whether you wanted this included in the trunk/main product?
> 
> Thanks again,
> Tim
> 
> [1] http://www.payrollamsterdam.nl/
> -------- Forwarded Message --------
> > From: Tim Knapp - Emerge Technology <tim at emergetec.com>
> > To: Mikko Ohtamaa <mikko at redinnovation.com>
> > Subject: Implemented DisplayField in customsearch
> > Date: Tue, 25 Dec 2007 16:11:34 +1300
> > 
> > Hi Mikko,
> > 
> > How are you? For a customer, I've just implemented an update to
> > customsearch on a branch[1] to allow a site manager to select a field
> > that will only be displayed in the results of the customsearch, i.e.
> > it won't be used in the search itself but only when rendering the
> > results (it's based on the ImageSearchField implementation). The
> > branch was just cut today (25/12/2007 NZ Time) based on trunk and I
> > was wondering if you felt this worthy of merging into trunk and
> > perhaps putting a new release up on plone.org (e.g. 0.5.3)? I've
> > tested it against Plone 2.5.3/Zope 2.9.8 and it's still pending
> > production testing by the customer so we can obviously wait till after
> > that.
> > 
> > Basically the way you use it is you create a new field under the
> > 'Fields' section in your customsearch content and select 'A field to
> > be displayed' as the 'Search type' and the relevant 'Catalog index'
> > that indexes your text field (as well as enter a 'Friendly Name' as
> > per standard practise). The 'Default value', 'Visibility' and 'Mode'
> > dropdowns can be ignored.
> > 
> > If you've got any questions, please let me know.
> > 
> > Thanks,
> > Tim
> > 
> > 
> > [1]
> > https://svn.plone.org/svn/collective/customsearch/branches/duffyd-displayonlyfield