Neat! I still think that the only way you'll get good adoption is to have an online form, forced on you when you create a tool... that particular horse may have already bolted, of course.
Harry On Fri, Aug 15, 2014 at 10:58 AM, Magog The Ogre <[email protected]> wrote: > > Question: will the tool choke and/or emit unwanted error messages if it > finds JSON fields it doesn't recognize? Because these are a sneaky way to > include comments (http://stackoverflow.com/q/244858). > > Also, Hay, you are a coding, documentation, and implementation genius. :-) > > > On Friday, August 15, 2014, TParis <[email protected]> wrote: > >> Might also be useful to know if a tool has an API and if the source code >> is viewable. >> >> -----Original Message----- >> From: [email protected] [mailto: >> [email protected]] On Behalf Of svetlana >> Sent: Thursday, August 14, 2014 6:52 PM >> To: [email protected] >> Subject: Re: [Labs-l] A proposal for better tool discoverability >> >> On Thu, 14 Aug 2014, at 22:59, Hay (Husky) wrote: >> > Hey Hedonil, >> > thanks for the suggestion for a 'repository' property, i've added >> > that. Adding it now adds a 'source available' link in the tool card, >> > and also groups them in a special category. >> > >> > -- Hay >> >> Maybe also indicate a tool source code license? Would be adorable >> >> svetlana >> >> _______________________________________________ >> Labs-l mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/labs-l >> >> >> _______________________________________________ >> Labs-l mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/labs-l >> > > _______________________________________________ > Labs-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/labs-l > >
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
