Cool, yeah, I've started doing the same, going through and cleaning things up. The GUI code has tons of errors for two main reasons:<br> * Still not 100% sure how you solve localization, so there are a lot of labels and error messages still in the code
<br> * Most of that code was forked from the Blogapps code, where it was a standalone Swing app. Furthermore, a lot of it was autogenerated by Netbeans.<br><br>The license issue is kinda a tricky one. I've gone ahead and added the GPL to my code, but I haven't to the code I took from Blogapps. I don't think we can just remove Dave's copyright, especially when most of the code is unchanged. If you really want everything to be the same license, I can talk to Dave. There is also the GriddedPanel class I've been using that comes from a Java Swing book. That one I haven't modified at all, so we probably couldn't change its license.
<br><br>BTW, some background, I'm a Apache Software Foundation member and a committer on several ASF projects including some used by Bible Desktop, and we are very sensitive to licensing issues due to the size of our projects. We even have a legal team that keeps us in check as we move along.
<br><br>As for changes and author issues, I doesn't matter to me, and I fully expect you to mutilate my beautiful code :( (jk, ;)) There is still more work that needs to be done to better integrate the code, so I'll be posting attachments until it gets committed. Let me know when you start working on it, so I'll know to stop. In another project, we've found the JIRA ability to declare "Work Started" as a helpful way to avoid steping on each other. I don't remember if this project uses that or not.
<br><br>Anyways, I look forward to working with everyone. As I've said, I'm very impressed as to the quality and organization of this project. Keep up the good work!<br><br>Don<br><br><div><span class="gmail_quote">On 1/18/06,
<b class="gmail_sendername">DM Smith</b> <<a href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Don,<br> I have seen your Jira entry with attachment and hopefully I'll get<br>to it by the end of the weekend. I'll be running it through our<br>CheckStyle, FindBugs, PMD and other QA tools and making adjustments to<br>
minimize their whining. So don't be surprised at some changes. Also, I<br>will be setting you as author on new stuff and slapping on our license,<br>LGPL for library code and GPL for GUI code. For existing code that you<br>
changed, if the changes were more than a few lines or were significant,<br>we will add you as an author. If this is not OK, please speak up.<br> If the code tests well, we can do another release fairly soon. (You<br>caught us at a good time!)
<br>Thanks,<br> DM<br><br>Don Brown wrote:<br>> I'm in the process of building BibleBlogs.Net [1], a site that<br>> provides tools and a forum to help you in your personal search for God<br>> and to share your experiences with others. This is accomplished
<br>> through the marriage of web journals or "blogs" with Bible study<br>> tools, specifically, Bible Desktop [2].<br>><br>> To this end, I've built a blog client into Bible Desktop to allow<br>> someone to share their Bible study thoughts and experiences from
<br>> within the Bible Desktop itself. The blog engine, Roller [3], even<br>> supports group blogs to allow several people to collaborate on a<br>> single study easily and the client in Bible Desktop supports multiple
<br>> blogs per account. Initially, I was going to build everything around<br>> the blog engine, but once I saw Bible Desktop and how well-designed<br>> and commented it was, I decided to built it into the site.
<br>><br>> Anyways, my question is where should I go from here?<br>> #1 - I could donate the code to Bible Desktop, once it has been<br>> cleaned up to its standards.<br>> #2 - Continue as a separate project, forking code as needed.
<br>><br>> Since Bible Desktop is GPL, the code is available on the<br>> BibleBlogs.Net site [2], so option 1 is more about collaboration.<br>> Option 2 obviously necessitates me finding a new name, but it also
<br>> might help encourage Bible Desktop's design to better accept plugins<br>> and extensions.<br>><br>> Look forward to your feedback and ideas.<br>><br>> Don<br>><br>> [1] <a href="http://www.bibleblogs.net">
http://www.bibleblogs.net</a><br>> [2] <a href="http://www.bibleblogs.net/study">http://www.bibleblogs.net/study</a><br>> [3] <a href="http://www.rollerweblogger.org/page/project">http://www.rollerweblogger.org/page/project
</a><br><br>_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br></blockquote></div><br>