Re: [Jgeneral] *which* repo for enhancement proposals?
An alternative which may not require as much organisation and complexity (may be preferable depending on the agreed process) is to just triage and tag tickets in the issues for the jsource repo as they come in? The Julia community is another good one to look at. https://github.com/JuliaLang/julia/issues On Wed, Sep 15, 2021 at 4:54 AM Michal Wallace wrote: > Before I go too much further, do you guys want these feature requests in > the *jsource* repo, or should we make a new repo? > > An alternative is to have a separate github project specifically for > proposals that may or may not be implemented, while they are under > discussion. > > Here's how python does it: > > https://github.com/python/peps > > At the company I work, we also do something like this... We have a separate > "requests" JIRA board where anybody can submit anything for discussion, and > then a weekly triage meeting where we decide what to do with the > requests... If we decide to implement it, we move it to the "actual work to > do" project... Sometimes this involves quite a bit of rewriting / > clarifying / breaking or joining of tickets / etc. > > If we think we might want a separate repo down the line, we should probably > act now. > > With a separate repo you could also give a person (like me) doing this > request management stuff access to that repo, for tagging and organizing > tickets, without necessarily giving them write access to the code. (maybe > you can do this anyway with github's admin tools?). > > A separate repo would also allow us to give users a single point of > contact, without worrying about which repo (qtide, base9, etc) they should > post it to. > -- > For information about J forums see http://www.jsoftware.com/forums.htm > -- For information about J forums see http://www.jsoftware.com/forums.htm
Re: [Jgeneral] bug/feature request tracking
This looks good. Something to bear in mind for the future - Github repos have both issues and projects. At some point we might have issues = bug reports, and projects = proposed new features. On Tue, Sep 14, 2021 at 6:43 AM Michal Wallace wrote: > Okay, I've made a start. Will resume tomorrow. > I'm doing a lot of manual wiki->github cleanup in passes, so apologies if > you guys are getting a bunch of unformatted emails. > (I decided to record the process and talk through the bugs, so I'll > probably post a video of this after some editing...) > > On Mon, Sep 13, 2021 at 12:36 PM Eric Iverson > wrote: > > > I am better informed now and see that your suggestion has great merit. In > > particular your offer to 'do all the ... work' :) > > > > You have the blessing of Jsoftware, I can't imagine anyone being opposed, > > so full speed ahead! > > > > On Mon, Sep 13, 2021 at 11:42 AM Michal Wallace < > michal.wall...@gmail.com> > > wrote: > > > > > I suggest we take this: > > > > > > https://code.jsoftware.com/wiki/System/Interpreter/Requests > > > > > > ... and migrate everything here: > > > > > > https://github.com/jsoftware/jsource/issues > > > > > > Pros: > > > - permalink to issues (currently the link breaks when moved to > "done") > > > - issues can be assigned, searched, etc > > > - can be associated with pull requests / code reviews on github > > > - can be marked as "easy" or "help wanted" to encourage outsiders > > > - commit messages can auto-link to the issue > > > - free and fairly standard for github accounts > > > - github accounts don't require manual setup (vs j wiki accounts) > > > > > > Cons: > > > - requests would no longer show up in j wiki search > > > - requestors would need a github account > > > - might be other options that are even better > > > - inertia? > > > > > > Thoughts? > > > > > > (I am happy to help with / do all of the migration work, if people > aren't > > > opposed to the idea...) > > > -- > > > 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 > -- For information about J forums see http://www.jsoftware.com/forums.htm
[Jgeneral] *which* repo for enhancement proposals?
Before I go too much further, do you guys want these feature requests in the *jsource* repo, or should we make a new repo? An alternative is to have a separate github project specifically for proposals that may or may not be implemented, while they are under discussion. Here's how python does it: https://github.com/python/peps At the company I work, we also do something like this... We have a separate "requests" JIRA board where anybody can submit anything for discussion, and then a weekly triage meeting where we decide what to do with the requests... If we decide to implement it, we move it to the "actual work to do" project... Sometimes this involves quite a bit of rewriting / clarifying / breaking or joining of tickets / etc. If we think we might want a separate repo down the line, we should probably act now. With a separate repo you could also give a person (like me) doing this request management stuff access to that repo, for tagging and organizing tickets, without necessarily giving them write access to the code. (maybe you can do this anyway with github's admin tools?). A separate repo would also allow us to give users a single point of contact, without worrying about which repo (qtide, base9, etc) they should post it to. -- For information about J forums see http://www.jsoftware.com/forums.htm
Re: [Jgeneral] bug/feature request tracking
What you are doing here is great. A video would be a bonus. On Tue, Sep 14, 2021 at 9:43 AM Michal Wallace wrote: > Okay, I've made a start. Will resume tomorrow. > I'm doing a lot of manual wiki->github cleanup in passes, so apologies if > you guys are getting a bunch of unformatted emails. > (I decided to record the process and talk through the bugs, so I'll > probably post a video of this after some editing...) > > On Mon, Sep 13, 2021 at 12:36 PM Eric Iverson > wrote: > > > I am better informed now and see that your suggestion has great merit. In > > particular your offer to 'do all the ... work' :) > > > > You have the blessing of Jsoftware, I can't imagine anyone being opposed, > > so full speed ahead! > > > > On Mon, Sep 13, 2021 at 11:42 AM Michal Wallace < > michal.wall...@gmail.com> > > wrote: > > > > > I suggest we take this: > > > > > > https://code.jsoftware.com/wiki/System/Interpreter/Requests > > > > > > ... and migrate everything here: > > > > > > https://github.com/jsoftware/jsource/issues > > > > > > Pros: > > > - permalink to issues (currently the link breaks when moved to > "done") > > > - issues can be assigned, searched, etc > > > - can be associated with pull requests / code reviews on github > > > - can be marked as "easy" or "help wanted" to encourage outsiders > > > - commit messages can auto-link to the issue > > > - free and fairly standard for github accounts > > > - github accounts don't require manual setup (vs j wiki accounts) > > > > > > Cons: > > > - requests would no longer show up in j wiki search > > > - requestors would need a github account > > > - might be other options that are even better > > > - inertia? > > > > > > Thoughts? > > > > > > (I am happy to help with / do all of the migration work, if people > aren't > > > opposed to the idea...) > > > -- > > > 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 > -- For information about J forums see http://www.jsoftware.com/forums.htm
Re: [Jgeneral] bug/feature request tracking
Okay, I've made a start. Will resume tomorrow. I'm doing a lot of manual wiki->github cleanup in passes, so apologies if you guys are getting a bunch of unformatted emails. (I decided to record the process and talk through the bugs, so I'll probably post a video of this after some editing...) On Mon, Sep 13, 2021 at 12:36 PM Eric Iverson wrote: > I am better informed now and see that your suggestion has great merit. In > particular your offer to 'do all the ... work' :) > > You have the blessing of Jsoftware, I can't imagine anyone being opposed, > so full speed ahead! > > On Mon, Sep 13, 2021 at 11:42 AM Michal Wallace > wrote: > > > I suggest we take this: > > > > https://code.jsoftware.com/wiki/System/Interpreter/Requests > > > > ... and migrate everything here: > > > > https://github.com/jsoftware/jsource/issues > > > > Pros: > > - permalink to issues (currently the link breaks when moved to "done") > > - issues can be assigned, searched, etc > > - can be associated with pull requests / code reviews on github > > - can be marked as "easy" or "help wanted" to encourage outsiders > > - commit messages can auto-link to the issue > > - free and fairly standard for github accounts > > - github accounts don't require manual setup (vs j wiki accounts) > > > > Cons: > > - requests would no longer show up in j wiki search > > - requestors would need a github account > > - might be other options that are even better > > - inertia? > > > > Thoughts? > > > > (I am happy to help with / do all of the migration work, if people aren't > > opposed to the idea...) > > -- > > 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
[Jgeneral] replace in QTide
If I do a Find|Replace in a script under QTide, the line where the replace have to be executed jumps out of sight, below my QT-window, which is a nuisance. How do I repair that? JVERSION Engine: j903/j64avx2/windows Beta-p: commercial/2021-09-13T09:34:33 Library: 9.03.03 Qt IDE: 1.9.2/5.12.10(5.12.10) Platform: Win 64 Installer: J903 install InstallPath: c:/program files/j903 Contact: www.jsoftware.com R.E. Boss -- For information about J forums see http://www.jsoftware.com/forums.htm
