On Mon, Sep 14, 2015 at 01:31:45PM -0600, Bruce Cran wrote: > On 9/14/15 1:19 PM, Jordan Justen wrote: > >I think the bug tracker on sf got shut down when sf stopped supporting > >their 'hosted services'. (Ie, for example, when they shut down the > >hosted mediawiki service.) > > It got broken when SF changed their URLs. I asked about it back then but > nobody seemed to care.
Considering recent developments on sourceforge, it seems as good a reason as any to leave. > >Well, there has been discussion on this topic at Intel. It is a > >mentioned goal: > > > >http://www.tianocore.org/news/2015/05/01/UnderConst.html > > Then let's do it! I guess there must be internal discussions going on, but > it's a little frustration to see no update for months at a time. > > >Some want to try to somehow run a bugzilla server. Personally, I think > >the path of least resistence is to just use github's issues system. It > >seems to go along with moving the source tree to git on github, and I > >think their system works reasonably. > > I think I'd prefer a dedicated system, personally. I'm already running > Phabricator for the EDK2 repository browser at https://edk2.bluestop.org and > enabling the bug/task tracker Maniphest module > (http://phacility.com/phabricator/maniphest/) is just a few clicks. > But I'd have to have buy-in from the Intel folks etc. for it to be used. Whether running a standalone system or a hosted service, I don't think it makes sense to use one completely separate from code hosting. If you're using github for code, it makes sense to use github for issues; if you were using Phabricator for code review and maintenance, then using it for issues makes sense. - Josh Triplett _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
