Chris Little wrote:
> peter wrote:
...SNIP...
>> There is also no fast way of doing corrections on released module - at
>> least for those without adequate rights on the server. Another
>> difficulty for those of us behind slow upload connections are that even
>> minor changes in the module become
On Jan 16, 2008 10:30 AM, Eeli Kaikkonen wrote:
>I meant that the illegal copyrighted text sharing has not stopped
other projects offering that possibility.
a) A distinction needs to be made between the gratis, and non-gratis
Bible Study Programs here.
b) One also has to look at how the differe
Eeli Kaikkonen wrote:
> On Wed, 16 Jan 2008, jonathon wrote:
>
>> Eeli wrote:
>>
create resources --- piracy. I'm not sure how to prevent it. [One
>>> That is a real issue but even some commercial Bible applications have
>>> resource sharing if I have understood correctly.
>> I've seen mo
On Wed, 16 Jan 2008, jonathon wrote:
> Eeli wrote:
>
> > > create resources --- piracy. I'm not sure how to prevent it. [One
>
> > That is a real issue but even some commercial Bible applications have
> > resource sharing if I have understood correctly.
>
> I've seen most, if not all of the cu
Eeli wrote:
> > create resources --- piracy. I'm not sure how to prevent it. [One
> That is a real issue but even some commercial Bible applications have
> resource sharing if I have understood correctly.
I've seen most, if not all of the currently available commercial bible
Study Programs a
On Wed, 16 Jan 2008, jonathon wrote:
> There is one major issue with tools that make it easy for users to
> create resources --- piracy. I'm not sure how to prevent it. [One
> thing that would help, would be if copyright owners were more serious
> about cracking down on pirated material of thei
On Tue, 15 Jan 2008, Karl Kleinpaste wrote:
> I am thinking through these sorts of problems because I am again
> considering how to integrate the idea of users authoring their own
> modules, and how they could get them published in some sense, where
> friends/students/the world could get at them.
Karl wrote:
> I believe that as long as it's difficult for Joe Random to produce and
> distribute a Sword module (cf. Peter, who succeeds because he is bull-headed
> enough to keep pushing), that kind of community critical mass will not come
> into being.
+1
I look at the number and type of
I think Peter's suggestions are very good, for the most part.
The lack of an "alpha" area where authors can make more or less
immediate updates when problems are addressed is a serious sore point.
It's why I put up a public repository of my own in the first place,
where a half dozen of the 30 modu
Karl,
If you'd like to contribute code to make mvnforums, linux, and our new
community site all use a common passwd repository, I'd welcome it. I
actually tried to port htpasswd code to java so the community site would
share our svn passwd repo. My code produces what looks like an htpasswd
h
"Troy A. Griffitts" <[EMAIL PROTECTED]> writes:
> You can already sign up for your login id, but not much else is
> testable yet.
So I've got a login on Crosswire itself. And a forums login. And a
JIRA login. And now this one.
Perhaps some things should be managed in common.
_
A quick note in regard to this thread. As Chris has mentioned, we have
wanted to do this for quite some time. Work has been done toward
developing a facility for people to maintain module sets. Wycliffe and
others have expressed a desire to maintain their own repositories of
texts and we hav
DM Smith wrote:
> On Jan 15, 2008, at 5:33 AM, Chris Little wrote:
>
>> peter wrote:
>>> One of the things which are recurrent on the mailing list is the
>>> difficulty + slowness of getting a module through the door - i.e.
>>> both
>>> to put it into beta and to get it from beta eventually tran
On Jan 15, 2008, at 5:33 AM, Chris Little wrote:
> peter wrote:
>> One of the things which are recurrent on the mailing list is the
>> difficulty + slowness of getting a module through the door - i.e.
>> both
>> to put it into beta and to get it from beta eventually transferred
>> into
>> rel
peter wrote:
> One of the things which are recurrent on the mailing list is the
> difficulty + slowness of getting a module through the door - i.e. both
> to put it into beta and to get it from beta eventually transferred into
> release.
I don't know what you mean by 'alpha' since we have no such
One of the things which are recurrent on the mailing list is the
difficulty + slowness of getting a module through the door - i.e. both
to put it into beta and to get it from beta eventually transferred into
release.
There is also no fast way of doing corrections on released module - at
least for
16 matches
Mail list logo
