I"m not really happy with the code but its the best I can do for now.  But
it does work so I don't see a reason not to put in in sourceforge.

Any tips on how to do this? I've never released a project as opensource.

Jorge

On Mon, May 5, 2008 at 10:36 AM, Vinko Vrsalovic <[EMAIL PROTECTED]> wrote:

>
>
> On Thu, May 1, 2008 at 4:46 PM, Jorge Schrauwen <[EMAIL PROTECTED]>
> wrote:
>
>
> > Though so :)
> >
> > I'm not that eager to get the java project out to the masses. Maybe its
> > better that I'll keep that as a personal tool.
> > The confused users on the db backend side will probably run into other
> > problems running that said configuration.
> >
> >
> I suggest creating a separate "project" with a name and a site on
> sourceforge or wherever else where you can dump the source and binaries and
> link to the project page, mentioning in the wiki that you used the tool
> "foo", at http://foo.sourceforge.net to manage it.
>
> That'd provide imo:
> - some level of credibility
> - the notion that it is not needed to make this work, but it's just a tool
> to help
>
> Plus you might even get help improving the tool.
>
> But then again, I understand you might not want to do so. It'd be cool if
> you gathered the courage though.
>
> V.
>



-- 
~Jorge

Reply via email to