ius-community team mailing list archive

[BJ Dierkes <derks@xxxxxxxxxxxxxxxx>]

Ness and I had this same dilemma back in the day.  Super annoying in this use case that GitHub doesn’t have issue tracking at the organization level.  What we don’t want is managing bugs/feature requests across 300 repos for every package.  Need everything in one place, however I don’t think that “wishlist” is the best terminology.  I think we should have a single project for managing all interaction with community including bugs, feature requests, wishlist items, etc.  Those should all be tags/labels under the same project.

I would suggest “iuscommunity/support” which covers all that pretty generically…. or something similar.

--- 
BJ Dierkes
Data Folk Labs, LLC

[w] http://datafolklabs.com
[e] team@xxxxxxxxxxxxxxxx


On February 3, 2015 at 10:29:57 AM, Ben Harper (ben.harper@xxxxxxxxxxxxx) wrote:

Greetings,  

The ius-coredevs have been debating if IUS should switch from using  
LaunchPad bugs to GitHib issues. We have really been enjoying GitHib  
for source control and GitHib does a good job integrating issues with  
source control and pull requests. Unfortunately, Github does not have a  
native way to submit an issue for an entire organization for things like  
new package requests. We are currently testing a dedicated repo for new  
package requests[0] and are looking for feedback. Please let us know if  
you have any thoughts about moving away from LaunchPad bugs and to  
GitHib issues.  

-Ben and the rest of the IUS covedev team  


[0] https://github.com/iuscommunity/wishlist  

_______________________________________________  
Mailing list: https://launchpad.net/~ius-community  
Post to : ius-community@xxxxxxxxxxxxxxxxxxx  
Unsubscribe : https://launchpad.net/~ius-community  
More help : https://help.launchpad.net/ListHelp