https://forge-allura.apache.org/p/allura/tickets/You searched for labels:"for-community"enMon, 21 Jan 2019 07:20:33 -0000https://forge-allura.apache.org/p/allura/tickets/7168/It would be really nice to have a wiki macro that could pull content from a repository. If we had this, we could include general end-user usage docs of the Allura platform (as opposed to the more operator geared docs at allura.sf.net), which would be distributed along with the Allura platform. This would also make it easier for general Allura docs to live side-by-side in a wiki that also contains more site specific information (like SourceForge). I believe this would also be a viable alternative to feature requests such as https://sourceforge.net/p/forge/feature-requests/58/ and https://sourceforge.net/p/forge/feature-requests/31/Chris TsaiThu, 20 Aug 2015 22:07:00 -0000https://forge-allura.apache.org/p/allura/tickets/7168/https://forge-allura.apache.org/p/allura/tickets/6047/Provide tighter integration with other forges. For example, if a project has a forum at Google Code and their Git repo at Github, we should provide a way, via the various available APIs, to integrate with that content. This may be as simple as a link (which we can of course do already, but it would be nice to offer this as an actual "Tool" in the admin) or Git repo mirroring of some kind. On project creation, a project could indicate that their Git repo was elsewhere, or that their mailing list is hosted elsewhere, and we would do the right thing on our side. In this way, we would become a hub for that project, and allow a given project to pick and choose the resources they want from a variety of providers, as best fits their particular project needs. It would also enable a project to have SCM repos at various different places, and have a central location to provide links to all of them. Rich BowenWed, 01 Apr 2015 00:57:15 -0000https://forge-allura.apache.org/p/allura/tickets/6047/https://forge-allura.apache.org/p/allura/tickets/5715/Provide in-site messaging that says "This is the email address we have on file for you. Is it correct?" and provide a link to the profile edit page. Initially for sfpy (and maybe sfx) since we want to hit classic projects. Showing it on Allura can be later.Rich BowenFri, 04 Jan 2019 22:03:12 -0000https://forge-allura.apache.org/p/allura/tickets/5715/https://forge-allura.apache.org/p/allura/tickets/5284/*Originally created by:* scoop Split out of [#3728]. Requires input of project's Twitter handle from [#5282].AnonymousWed, 18 Mar 2015 06:48:28 -0000https://forge-allura.apache.org/p/allura/tickets/5284/https://forge-allura.apache.org/p/allura/tickets/5233/It would be nice to be able to add Trove categories for our users without having to log tickets for you guys to do it.Chris TsaiTue, 06 Jan 2015 04:28:12 -0000https://forge-allura.apache.org/p/allura/tickets/5233/https://forge-allura.apache.org/p/allura/tickets/5159/I just discovered the 'awards' functionality, and I'd like to have a few features added to it, so that it can be exploited for my nefarious needs. * Add a URL when an award is granted, so that the icon can link to something that elaborates on why the award was granted. * Associate awards with particular behaviors. For example, auto-grant an award based on a certain number of commits in a week, a certain number of closed tickets in a week, a certain number of downloads in a week. That's right, I want to gamify the awards. This association might be permanent (this project was once in the top 20) or temporary (this project is *currently* in the top 50). * Add a page that links to all projects that have the "Foo" award. * Add the ability to grant an award to a user as well as to a project. * Add a "grant/revoke award" button to the project summary page itself. Rich BowenFri, 06 Mar 2015 12:04:48 -0000https://forge-allura.apache.org/p/allura/tickets/5159/https://forge-allura.apache.org/p/allura/tickets/4725/Need a way to send a user a message in-site - that is, that they'll somehow get the message when they log into the site, perhaps with some kind of a notification that they have messages waiting. Rationale: We have many users who are active, but who have an email address on file that bounces. This leaves us with no way to contact them, even though they are active.Rich BowenMon, 21 Jan 2019 07:20:33 -0000https://forge-allura.apache.org/p/allura/tickets/4725/https://forge-allura.apache.org/p/allura/tickets/4218/We need a tool that helps connect projects with developers. This would include the following features: * The ability of a developer to indicate their strengths and skills, e.g., Perl, Database, Documentation * A project may post a "help wanted" listing for a particular bug, feature, or task, and tag it with certain accompanying skills that would be required. This should probably always be associated with a ticket. May possibly associate a bounty with this listing. (?) * A developer may be notified of listings that match their profile (email, twitter, listed on user's page when they log in, or otherwise actively notify them as they use the site) * Anyone may search for listings by language, skill, or other keywords. * Keep track of when the loop is closed (ie, a developer is successfully connected with a project) so that we can follow up on success stories. * Track developer statistics. i.e., user_x has responded to this many Help Wanted postings, and has closed this many tickets as a result of their involvement.Rich BowenWed, 22 Mar 2017 13:31:07 -0000https://forge-allura.apache.org/p/allura/tickets/4218/