How about leaving some TODO markers in the page via commit? Maybe somebody will follow up on that commit, and actually make the changes.
Why should the marker be within a ticket, instead of the codebase itself? Again, if somebody goes to fix this, then they have double-work: make some commits, and make some ticket changes. The ticket system is entirely divorced from the codebase. Consider: community members can spend the next month handling tickets. Does that accomplish anything? Nope. Alternative: work within the actual product, making changes/notes as they are discovered. Cheers, -g On Fri, Mar 15, 2013 at 12:11 PM, Apache Bloodhound <[email protected]> wrote: > #467: About page should include a link to Apache Bloodhound > --------------------------+--------------- > Reporter: jdreimann | Owner: > Type: enhancement | Status: new > Priority: major | Version: > Resolution: | > --------------------------+--------------- > https://bh-demo1.apache.org/about > Currently contains plenty of links to trac, but no links to any Bloodhound > pages. > > Also, the Footer shows: > "Visit Apache Bloodhound at https://issues.apache.org/bloodhound/"; - I > think it should be "Get involved in [Apache Bloodhound]" and the [name] > should be a link to our site. > > -- > Ticket URL: <https://issues.apache.org/bloodhound/ticket/467> > Apache Bloodhound <https://issues.apache.org/bloodhound/> > The Apache Bloodhound (incubating) issue tracker
