Re: [Cdk-jchempaint] Some organizational issues regarding JChemPaint applet development

[Rajarshi G. <raj...@gm...>]

This is unfortunate news. I echo Jonathans' comments - while I'm not a  
developer of the JCP code, I certainly make use of the underlying  
components (such as the renderer).

If the main bottleneck that led to this fork is the merging of patches  
into the CDK - couldn't the review process be made simpler, if patches  
are localized to the renderer/controller packages?

As a CDK dev I'm happy to review patches, but for stuff related to JCP  
it's a little difficult since I do not know that portion of the code  
and my review would necessarily be cursory.

So wouldn't it be better for patches related to these two packages, to  
just let JCP devs check with each other and then commit?


On Nov 28, 2009, at 8:55 AM, Christoph Steinbeck wrote:

> Dear all,
>
> after revamping the JChemPaint applet completely and including it into
> our EBI chemistry database ChEBI (http://www.ebi.ac.uk/chebi) as  
> part of
> the production systems, we have decided to make some changes to our
> internal production process of the applet of which we would like to  
> make
> you aware:
>
> For development of the JChempaint applet, we have now decided to
> permanently fork the 'controller' and 'renderer' packages
>
> They now live in the JChemPaint svn repository on SourceForge and were
> renamed to org.openscience.jchempaint.* to avoid confusion and to  
> allow
> to provide a stable applet which works reliably with our production
> databases at EBI.

----------------------------------------------------
Rajarshi Guha        | NIH Chemical Genomics Center
http://www.rguha.net | http://ncgc.nih.gov
----------------------------------------------------
Entropy requires no maintenance.
	-- Markoff Chaney