GitHub's Issues interface is good for both alerting a project's maintainers, and also for users to get a sense how actively it's being maintained.
GitHub has decent mechanisms for transferring ownership of repositories, so questionable/abandoned addons could go somewhere out of the way (but still publicly available, to encourage fixing) until someone wants to take ownership. On Wed, Apr 25, 2018 at 6: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)? > > > On Wed, Apr 11, 2018 at 7:56 PM, Raul Miller <[email protected]> > wrote: > > > This looks like a good idea. > > > > The one suggestion I would have is that this makes it easy to install > > broken stuff. Of course, we have already had breakages with system > > upgrades - interface changes or removed dependencies can show up as > > addons not working right. 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? > > > > Thanks, > > > > -- > > Raul > > > > > > On Wed, Apr 11, 2018 at 2:49 PM, chris burke <[email protected]> > wrote: > > > (This is cross posted to general and programming - please send any > > comments > > > to general.) > > > > > > We plan to move the addons source from SVN to github, and at the same > > time > > > support installs from personal github repos outside the main addons > > source. > > > See code.jsoftware.com/wiki/Addons/GitHub . > > > > > > We have this working now, but would appreciate comments before going > > ahead, > > > thanks. > > > ---------------------------------------------------------------------- > > > 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
