I'm jumping the gun here a bit. Jsoftware is planning to move a bit in the directions under discussion.
The basic idea is that we will host a git J GPL source that is kept current and that is open to all. Those who want to 'do their own thing' under GPL can clone from that and head off on their own. Jsoftware will encourage the use of branches on that repo for community developed bug fixes and enhancements. Pushes back to that repo will have copyright that allows Jsoftware to incorporate changes into the evolving official source. Branch projects could be minor things such as bug fixes as well as more significant changes and could be individual or group efforts. Given other priorities it will probably be a few months before we have this in place. On Tue, Jun 23, 2015 at 9:49 AM, Joe Bogner <[email protected]> wrote: > Thank you for the comments. I agree with all of your statements. I am > not a strong advocate of the reduce change. Rather, I am interested in > participating in a community effort to contribute a change back to the > core. If this isn't the right change, then perhaps this thread could > be useful as a guide in the future and let others know of my interest. > > > > On Tue, Jun 23, 2015 at 9:38 AM, Raul Miller <[email protected]> wrote: >> On Tue, Jun 23, 2015 at 9:12 AM, Joe Bogner <[email protected]> wrote: >>> 1. Demonstrated a real need. More generally, what constitutes a need to >>> change? >>> >>> - Performance? >>> - Ease of use? >>> >>> In terms of the reduce idea, it sounds like this may fit both criteria >>> as there are performance issues and the proposed solution[3] is not >>> easy for a beginner. I think further testing is needed on both though >>> to demonstrate the need. >> >> I can't help but think we should do a bit more here. >> >> I tried to find a statement by Ken Iverson about his criteria for >> including a feature in the language, but I wasn't able to find >> anything specific. >> >> I did find >> http://www.jsoftware.com/pipermail/general/2001-November/008227.html >> which has to do with the "easy for a beginner" issue. >> >> And, I guess, personally, I would be looking for evocative uses. Even >> if it's just one really nice example - the documentation will need >> good examples. >> >> If the only reason for including this is "other languages do it", I >> suspect that the right approach would be to create a package which >> contains those kinds of words. Perhaps: 'general/misc/colloquial'? >> >> That said... I can see using this project to get into jgplsrc - but >> I'd want to view this particular thing as practice rather than as >> "intended for release". Getting things right takes a lot of work, but >> introducing a feature implies being willing to support that feature, >> which requires a lot more dedication than the initial implementation. >> >> Thanks, >> >> -- >> Raul >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
