Difference between revisions of "User talk:David Haslam"

From CrossWire Bible Society
Jump to: navigation, search
m (Hosting of GoBible source: BPBible made into link to help the casual reader)
(Hosting of GoBible source: Response to refdoc)
Line 18: Line 18:
 
-- [[User:Jmmorgan|Jmmorgan]] 00:18, 15 November 2008 (UTC)
 
-- [[User:Jmmorgan|Jmmorgan]] 00:18, 15 November 2008 (UTC)
  
We have Jira on Crosswire which is fine for issue tracking. SVN for version control, access to the server for putting up corresponding web pages, the ability to run mailing lists and CrossWire is a well known (in open source circles at least) outfit for bible software. So, in summary I am not convinced of Jonathan's argument. [[User:Refdoc|Refdoc]] 11:58, 15 November 2008 (UTC)
+
:We have Jira on Crosswire which is fine for issue tracking. SVN for version control, access to the server for putting up corresponding web pages, the ability to run mailing lists and CrossWire is a well known (in open source circles at least) outfit for bible software. So, in summary I am not convinced of Jonathan's argument. [[User:Refdoc|Refdoc]] 11:58, 15 November 2008 (UTC)
 +
 
 +
::Even so, there is a lot of information on the [http://code.google.com/p/gobible/w/list Google code wiki] that would also need to be transferred, plus all the open [http://code.google.com/p/gobible/issues/list issues] to copy. [[User:David Haslam|David Haslam]] 21:17, 15 November 2008 (UTC)

Revision as of 21:17, 15 November 2008

This is the talk page for David Haslam. You can leave messages for me here. To begin a new topic use the [+] tab at the top of the page. Keep posts to topics in chronological order. Indent reponses using colons. Never post your real email address. Always sign your edits using four tilde. David Haslam 13:00, 12 September 2008 (MDT)

Hosting of GoBible source

I think you would be better to host GoBible on Google Code (as it is currently) rather than at Crosswire, for the following reasons:

  1. Better support for collaboration: Google Code has been designed for collaboration in open source projects, and I suspect it will serve you better. It will probably be easier to add additional developers, have additional people uploading releases, ...
  2. Better support for issue tracking: The Google Code issue tracker is by far the best issue tracker I have ever used.
  3. Better visibility to developers: Having it on Google Code makes it more likely that software developers looking for Bible software will find it, I think.

BPBible has certainly had good support from Google Code.

-- Jmmorgan 00:18, 15 November 2008 (UTC)

We have Jira on Crosswire which is fine for issue tracking. SVN for version control, access to the server for putting up corresponding web pages, the ability to run mailing lists and CrossWire is a well known (in open source circles at least) outfit for bible software. So, in summary I am not convinced of Jonathan's argument. Refdoc 11:58, 15 November 2008 (UTC)
Even so, there is a lot of information on the Google code wiki that would also need to be transferred, plus all the open issues to copy. David Haslam 21:17, 15 November 2008 (UTC)