Hi all, I've set up a Phabricator instance at http://phab.lowrisc.org/. The intent is to better keep track of issues and to better share ideas and progress with the wider community. Consider it 'beta' for now, and any suggestions on making best use of it and organisation are most welcome. You should be able to log in with a Github account. Please do start kicking the tires and help filling out relevant issues. For those not familiar with Phabricator, it is a collaboration tool that originally came out of Facebook <http://en.wikipedia.org/wiki/Phabricator>;. I'll happily declare that it "sucks less" than the other available bug tracking or collaboration solutions out there. * Why not Github issues? We have no control over the proprietary Github platform, and hope to keep track of issues across a wide range of projects while being searchable from one place. * Why not report issues directly upstream? For straight-forward bugs with a non-lowRISC upstream they should be reported to the appropriate bug-tracker (and ideally tracked on the lowRISC phabricator as well). However, there's also the need to keep track of feature requests or lowRISC-specific issues, and the policy of the upstream bugtracker may not welcome such issues. * A hope is that the phabricator will keep track of feature requests, providing a useful starting point for people wanting to contribute. See also http://phab.lowrisc.org/T3 * In time, I expect we will extend our use of Phabricator to use the code review components, as used successfully by LLVM, FreeBSD, and others All feedback very welcome, Alex