Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-15, 16:48 GMT, Peter Von Kaehne wrote: > What I said was not meant as a dismissal, but to clear up what > seemed to be misconceptions regarding the role of the repo. if > I was too blunt in that, then I am more than sorry. I don’t think you were too blunt. It was more Greg’s refusal

Re: [sword-devel] Contributing to sword-tools repo?

I would not call it a" dumping ground for us two to play", but more generically a dumping ground for things worth keeping and sharing in a loose way, but not worth releasing officially. If this makes sense. The only exception to that was usfm2osis.py/pl, a widely used and semiofficial tool,

Re: [sword-devel] Contributing to sword-tools repo?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! I apologize for having to write this e-mail in a haste. I've tried to be concise, but might have missed a few points and apologies to Troy. On 14.01.2016 22:12, Troy A. Griffitts wrote: > This is the part I'm sure will be much less appealing

Re: [sword-devel] Contributing to sword-tools repo?

> Von: "Matěj Cepl" > On 2016-01-15, 06:51 GMT, Peter von Kaehne wrote: > > My Module makefiles in turn live on the fact that certain scripts are > > in certain places so that they can pull them in.  > > Define “certain places”, please? Meaning that the directory > structure of

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-15, 06:51 GMT, Peter von Kaehne wrote: > My Module makefiles in turn live on the fact that certain scripts are > in certain places so that they can pull them in.  Define “certain places”, please? Meaning that the directory structure of sword-tools should be preserved, or that the code

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-15, 10:32 GMT, Peter Von Kaehne wrote: > av11n.py by Greg is another typical low tech utility script > which, when its time comes might need + enhancements, but > should not get altered for no good reason as it does what it > says on the tin - and that is all it should do right now.

Re: [sword-devel] Contributing to sword-tools repo?

; > An: sword-devel@crosswire.org > Betreff: Re: [sword-devel] Contributing to sword-tools repo? > > On 2016-01-15, 10:32 GMT, Peter Von Kaehne wrote: > > av11n.py by Greg is another typical low tech utility script > > which, when its time comes might need + enhancements,

Re: [sword-devel] Contributing to sword-tools repo?

Dear Jaak, Code security and software vulnerability is a subject that should be discussed privately. Ths list sword-devel is open to the general public. Dear Troy, If Jaak's observations about these two critical issues have merit, this is something we should take up outside this mailing list,

Re: [sword-devel] Contributing to sword-tools repo?

Peter, Gentle reminder... Please remove CzeNKB and CzeKMS modules from CrossWire Main and drop them into CrossWire Attic. Thanks. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Contributing-to-sword-tools-repo-tp4655762p4655783.html Sent from the SWORD Dev

[sword-devel] Contributing to sword-tools repo?

How am I supposed to contribute to the sword-tools repo? I use (as any sensible person would do these days ;)) git, so my repo is on https://gitlab.com/mcepl/sword-tools/ and all changes are in fix-av11n_py branch_. How can I propose those so far seven commits to be merged? Series of emails

Re: [sword-devel] Contributing to sword-tools repo?

I’ll be moving JSword’s master to the CrossWire server, but github will continue to be the public face. We put JSword under github.com/crosswire so that any other CrossWire projects could be placed there as well. In Him, DM > On Jan 14, 2016, at 7:08 AM, Baiju M

Re: [sword-devel] Contributing to sword-tools repo?

On Thu, Jan 14, 2016 at 3:57 PM, Matěj Cepl wrote: > Isn’t it the time to finally switch to git and create repo on > GitLab/GitHub/somewhereelse? +1 for the idea to use Git. It looks like "jsword" project is already maintained in Github: https://github.com/crosswire Regards,

Re: [sword-devel] Contributing to sword-tools repo?

g > Betreff: [sword-devel] Contributing to sword-tools repo? > > How am I supposed to contribute to the sword-tools repo? I use > (as any sensible person would do these days ;)) git, so my repo > is on https://gitlab.com/mcepl/sword-tools/ and all changes are > in fix-av11n_py br

Re: [sword-devel] Contributing to sword-tools repo?

or similarly named repo on > Github which deals specifically with usfm2osis.py which you are welcome to > contribute to, too, obviously. > > Peter > >> Gesendet: Donnerstag, 14. Januar 2016 um 11:27 Uhr >> Von: "Matěj Cepl" <mc...@cepl.eu> >> An

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-14, 12:22 GMT, Peter Von Kaehne wrote: > You can contribute to the subversion repo by asking Troy to > add you. So, there is no code review ... just everybody blindly dumps their changes to the repo? (more interesting for sword proper repo). > I am not sure if there is much

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-14, 15:06 GMT, Greg Hellings wrote: > Based on the way this conversation has gone in the past, nearly > everyone involved except the project administrator would welcome a > migration to git. Even if it was a self-hosted git. But the project > admin remained unconvinced the last time the

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-14, 22:11 GMT, Greg Hellings wrote: > I'd be happy to work through gitlab with you (though I would > strongly prefer github, where I've made my home) I don't care about GitHub or GitLab ... I prefer the latter (as it is FLOSS and it kind of grew on me), but no problem with moving it

Re: [sword-devel] Contributing to sword-tools repo?

On Fri, 2016-01-15 at 02:35 +0100, Matěj Cepl wrote: > On 2016-01-14, 22:11 GMT, Greg Hellings wrote: > > I'd be happy to work through gitlab with you (though I would > > strongly prefer github, where I've made my home) > > I don't care about GitHub or GitLab ... I prefer the latter (as > it is

Re: [sword-devel] Contributing to sword-tools repo?

On Thu, Jan 14, 2016 at 8:09 PM, Matěj Cepl wrote: > On 2016-01-14, 12:50 GMT, Baiju M wrote: >> I know that this project is encouraging new contributors. I can read >> like this here: http://crosswire.org/volunteers/ >> "Currently, the CrossWire Bible Society has a number of

Re: [sword-devel] Contributing to sword-tools repo?

Troy, I do want to say that I appreciate your leadership and dedication to quality, stability, and robustness of the code. I think your judgment and leadership in that regard has been excellent. When I was younger and newer I didn't necessarily understand it all the time, but the longer I've been

Re: [sword-devel] Contributing to sword-tools repo?

For those who don't want to go back and read the threads Greg has posted, and since I am the 'admin' mentioned for trunk of libsword, I'll make a few brief comments which I hope summarized those emails. I understand a move to git is likely inevitable. I like SVN better and I know many

Re: [sword-devel] Contributing to sword-tools repo?

Just one point that should be remembered. Free GitHub hostings are all public. So if you're doing collaborative text development on a copyrighted work, assuming you have permissions, you shouldn't be doing on a public GitHub project. If you want any private hostings on GitHub, there's an

Re: [sword-devel] Contributing to sword-tools repo?

Based on the way this conversation has gone in the past, nearly everyone involved except the project administrator would welcome a migration to git. Even if it was a self-hosted git. But the project admin remained unconvinced the last time the topic came up. So please, don't re-open this old sore

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-14, 12:50 GMT, Baiju M wrote: > I know that this project is encouraging new contributors. I can read > like this here: http://crosswire.org/volunteers/ > "Currently, the CrossWire Bible Society has a number of projects in > progress, all open to new volunteers" > I think moving to Git

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-14, 14:20 GMT, David Haslam wrote: > Free GitHub hostings are all public. > > So if you're doing collaborative text development on a copyrighted work, > assuming you have permissions, you shouldn't be doing on a public GitHub > project. > > If you want any private hostings on GitHub,

Re: [sword-devel] Contributing to sword-tools repo?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I totally agree with Matěj and I'm all for the git move, even to the point of suggesting to create competing Sword++ fork in case of further objections by Crosswire. I'd be happy to contribute to the C++ code. God bless! Jaak Ristioja On

Re: [sword-devel] Contributing to sword-tools repo?

Matej, Yes, I wasn't meaning to target you directly with my response. My comments were meant for newcomers to the thread. --Greg On Thu, Jan 14, 2016 at 9:24 AM, Matěj Cepl wrote: > On 2016-01-14, 15:06 GMT, Greg Hellings wrote: >> Based on the way this conversation has gone in

Re: [sword-devel] Contributing to sword-tools repo?

On 2016-01-14, 20:12 GMT, Troy A. Griffitts wrote: > Many projects at CrossWire do have loose to medium submission > policies: sword-tools, flashcards, swordweb, parts of I really have no ax to grind with libsword itself, because I am really not a C++ programmer, so I will let somebody else to

Re: [sword-devel] Contributing to sword-tools repo?

Matej, On Thu, Jan 14, 2016 at 3:56 PM, Matěj Cepl wrote: > On 2016-01-14, 20:12 GMT, Troy A. Griffitts wrote: >> Many projects at CrossWire do have loose to medium submission >> policies: sword-tools, flashcards, swordweb, parts of > > I really have no ax to grind with libsword