Great to see this contribution :) Having only glanced at the code, not tested it, a few thoughts: Would it be better to put everything in the macro, e.g. `[[gittip_button username=brondsem]]` and not store it on the project? Although there might be some advantage of tracking it at the project level. If we do keep it on the metadata page, we should make sure that field is accessible for user-projects (many other metadata fields are not available for user-projects).
--- ** [tickets:#6569] Added a Gittip maco to the Wiki tool** **Status:** code-review **Labels:** community **Created:** Thu Aug 15, 2013 07:40 PM UTC by Wayne Witzel ❸ **Last Updated:** Thu Aug 15, 2013 09:24 PM UTC **Owner:** nobody Add a Gittip macro to the Wiki tool. Allowing projects to promote their project. More information at https://www.gittip.com/about/. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
