Re: FirebirdSQL Backend - Wiki Access

For the rest of the list, I sent Rob the wiki signup key, my comments
are inline.

Hi Rob:

In message <[email protected]>,
Rob Kellock writes:
>Started to do a write up on my customisations of the Classic install and 
>realised I've made masses of them, so many... that cutting and pasting 
>the code changes into a document would be a mess. They include a 
>FirebirdSQL backend, internal vs external users, HTML signatures for 
>internal users, spam redirection to the dispatcher, activity by external 
>user, a fix for the query functionality which was broken and slight 
>improvements to the HTML rendering on the issues page.  From a visual 
>perspective my customised effort hardly looks any different from a 
>vanilla Classic, but lots of changes have happened under the hood.

The fix for query functionality should be posted as an issue at:

 http://issues.roundup-tracker.org/

so we can track it and make your patch obsolete (you may even have
fixed an outstanding bug).

Also the improvement for html rendering on the issues page should
probably be in the tracker.

>Perhaps it would be better to attach a Zip archive of all the pages that 
>have been affected and a discussion document to go with them? I want to 
>keep that on your Wiki, since when I was doing them, I referred to the 
>Wiki initially for inspiration. I think it would be counter-productive 
>to store them elsewhere with a link to them. But.., it seems you don't 
>have attachments on your Wiki.

We do support attachments you just need to be logged in to add them.

A zip works, but makes cutting/pasting tough. Also with all of the
changes on one page, it kind of breaks the indexing provided by the
individual pages.

E.G. Internal vs external users, Spam to dispatcher (and dispatcher
role I assume), Adding an html signatore to an email, Firebird support
...

should be separate pages. They certainly can point to another page
where the zip file is attached that describes your use for all of
these changes.

>I'm not sure that joining the developers list and posting my individual 
>files changes would help, since the whole customisation has to be 
>together to be useful.  The way I'd see my changes being used, is that 
>others look at what I've done and then use that as a pointer for their 
>own customisation effort.

I think your idea to put it on the wiki is the right one (except for
the couple of bugs that should be issues). We already have some links
in the wiki with neat functionality that point to dead pages, so
putting stuff on an external website is not my preferred choice.

>Is there a better way?  I love Roundup and I'd like to help.  I've 
>already written a number of articles on my blog 
>(http://[email protected])

I assume you meant: http://creditscorenz.blogspot.co.nz

>advocating Roundup, but I think 
>I'm using Roundup quite differently from most of you - I'm a sole trader 
>and I use Roundup as a sort of CRM tool (only the email part, the Web 
>interface is private) and as a way to keep information overload to a 
>minimum.  Perhaps in the final analysis, I should create a new page 
>dedicated to Roundup on my website (http://www.creditscore.co.nz)

I suggest adding a wiki page RoundupAsCRM and a link pointing to it on
the CustomisationExamples page. (Maybe you want to add a new section
on the CustomisationExamples page called: Use Cases.)

On the RoundupAsCRM add the zip file and overall commentary.

Then for particular functionality (spam dispatch, internal/external
users etc), create a few pages that have an explanation of that
feature and a reference to RoundupAsCRM and the files that need to be
changed.

How does that sound? It provides:

   * your ideas exposure from the CustomingExamples page
   * you a central place to put all of the files (except for Firebird
     which I discuss below).
   * it highlights some of a the particular modifications (spam
     dispatch ...) in the indexes and title searches (and they can be
     added as links to CustomisationExamples as well)

On RoundupAsCRM state what version of roundup your changes are based
on. This will give people a starting reference for templates/code
changes so they can merge your changes into their furture version of
roundup.

>On second thoughts, I really do want the FirebirdSQL backend to get onto 
>your Wiki, since that is independent of all the other mods I've made.  

A page on the FirbirdSQLBackend (or some such name) could be linked
from the RoundupAsCRM, but it would be good if the firebird page that
had it's own zip file or set of attachments separate from the rest
since the CRM functionality doesn't depend on using firebird (IIRC).

Thanks for your work with roundup. I look forward to looking at the wiki.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft