On Sat, Apr 28, 2018 at 8:55 PM, Ian Clark wrote:
> Now I'm not a novice user, and I have powerful tools, so nothing much stops
> me for long. So please don't offer to hold my hand in individual cases.
> That misses the point.
The issue we need to solve is not so much
> AFAIK, the current set of addons is in reasonably good shape, if not
always properly documented. Are you aware of specific issues with them?
It's how they're documented that concerns me. But without even a "how to
proceed" message on loading – just nothing – the addon in question is by
One thing still to do is a page that lists all J-related github repos. This
would include not just the current set of addons, but any repos of interest
to the community.
The usual starting page name for this is jsoftware.github.com, which can be
in any format. Right now it just redirects to a J
AFAIK, the current set of addons is in reasonably good shape, if not always
properly documented. Are you aware of specific issues with them?
On Wed, Apr 25, 2018 at 3:27 PM, Ian Clark wrote:
> > It might be nice to have a way of marking addons as broken, either with a
>
Thanks, this is done now, see
code.jsoftware.com/wiki/Addons/Installation#install_Verb
On Wed, Apr 25, 2018 at 12:58 PM, Alex Shroyer wrote:
> Pulling the latest master branch from GitHub is a nice default, but PLEASE
> make it possible to specify a particular version.
> A
This is now complete, and all SVN repos are now on github.
Developers should let me know if they want access/ownership of any repo.
On Tue, Apr 24, 2018 at 5:09 PM, chris burke wrote:
> An update on this -
>
> Tomorrow we will change all Jsoftware SVN repos to read-only,