The typical way is to ask on the list.
It is possible an old module is an orphan. There are several ways a module is
orphaned:
The source for the module is no longer available.
The module maintainer is no longer willing/able/available to work on the module.
This is true regarding any module, esp
Original-Nachricht
> Datum: Sun, 6 Jan 2013 10:21:41 -0500
> Von: Andrew Thule
> An: Chris Burrell , "SWORD Developers\' Collaboration
> Forum"
> Betreff: Re: [sword-devel] Updating copyrighted modules
> Yes, exactly Chris.
>
> Both Chri
On 1/6/2013 7:52 AM, Chris Burrell wrote:
My point still stands, it would be nice to know who we talk to make
fixes to modules.
Some submitters elect to sign their modules in the .conf file. Check
there for a name and/or email address.
In lieu of that, email me at modu...@crosswire.org and I
Andrew, we've already established that you just plainly don't understand
copyright. You think it simply doesn't apply to you if you don't feel
like having it apply to you. That's why you are still hosting illegally
produced copies of translations of the Dead Sea Scrolls. We established
this a w
My point still stands, it would be nice to know who we talk to make fixes
to modules.
Chris
On 6 January 2013 15:45, David Haslam wrote:
> There's nothing "fishy" about our distribution notices for works that are
> copyright.
>
> Our wiki states that copyright and distribution licensing agree
There's nothing "fishy" about our distribution notices for works that are
copyright.
Our wiki states that copyright and distribution licensing agreements are [to
be] lodged by CrossWire.
The email address for all such & related communications is copyright AT
crosswire DOT org.
See http://crossw
Yes, exactly Chris.
Both Chris and Peter have publicly accused me of breaking the law (thus
tarnishing my reputation, and sullied my efforts to contribute). This
implies I've breeched the terms of Crosswire's licensing agreement with the
ISV foundation as the Copyright owner. What exactly is the
I think what Andrew meant by "secretive" is that there doesn't seem to be
an obvious documented place where there is a link between who owns the
relationship with the copyright holder, who generated the module in the
first place, and who if different is the person maintaining the module.
Chris
O
> Von: Manfred Bergmann
> Am 06.01.2013 um 09:50 schrieb Andrew Thule :
>
> > The site makes it seem like anyone can contribute to module creation,
> modification.
> >
>
> Anyone can contribute to module creation.
Thanks, Manfred. Indeed, anyone can. We have hundreds of modules produced by
Am 06.01.2013 um 09:50 schrieb Andrew Thule :
> The site makes it seem like anyone can contribute to module creation,
> modification.
>
Anyone can contribute to module creation. If the module is finally
published/released in our repos is another matter.
Modification is normally only done by
Sorry, I was frustrated when I fired off that last email in hast. I would
still like an apology, but I have a better idea. I think we're moving
towards transparency.
Since you and Chris have made my attempts to improve the ISV personal, and
you've threatened a number of times to boot me off the
So module development IS restricted to a select and apparently secret group
(who know who they are)? You have not quite been honest, transparent, or
forthright in this then Peter. How was I suppose to know that was the
case?; and yet you've stood my accuser knowing full well that your
accusatios
Much of what we publish is copyrighted. We obtain detailed clear permission
before anything goes on a public server. For the avoidance of doubt I describe
the usual process of updating such modules.
There is usually a core group member who has negotiated the exact, often highly
variable terms
13 matches
Mail list logo
