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 <[email protected]> wrote: > > It might be nice to have a way of marking addons as broken, either with a > todo/fixme note or maybe just a documented way of deleting them? > > I think that's a splendid idea. > > Whenever I engage with an addon I've never used before, it takes me far too > long to conclude that it's derelict. To stop our treasury of addons > degenerating into a midden, I'd welcome an accepted *easy* way of alerting > the owner – or fellow-users – to broken code (i.e. not a full-blown bug > tracker). > > Am I the only one? Are we going to do something about it? Are we going to > finish what we start? > > What's the best/most obvious alert mechanism? …the Talk page of the landing > page for the Addon in question at code.jsoftware.com/wiki/Addons > <http://code.jsoftware.com/wiki/Addons/GitHub> ? This forum? Or something > Github-based? (and hence over the vendor's horizon)? > > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
