@Andreas, can you reply to Gabe's request?
On Mon, Apr 9, 2018 at 10:17 PM, Gabe Black wrote:
> As an aside, opengrok was set up by Ali who now works for ARM. He has
> showed up very briefly since I came back to the project, but I don't think
> he's actively following the project. I would take ca
Definitely dev. gem5-users is primarily for questions about how to use gem5.
Cheers,
Jason
On Tue, Apr 10, 2018 at 7:24 AM Ciro Santilli
wrote:
> Should bugs be reported on gem5-dev or gem5-users? -dev I expect, but
> let's confirm.
>
> On Mon, Apr 9, 2018 at 10:37 PM, Jason Lowe-Power
> wrote
Should bugs be reported on gem5-dev or gem5-users? -dev I expect, but
let's confirm.
On Mon, Apr 9, 2018 at 10:37 PM, Jason Lowe-Power wrote:
> Hi Ciro,
>
> I think deactivating the github issues makes sense. And, I'll happily sign
> off on a patch to the CONTRIBUTING document if you want to crea
Hi Ciro,
I think deactivating the github issues makes sense. And, I'll happily sign
off on a patch to the CONTRIBUTING document if you want to create a quick
review request :).
@Ali: Could you add me to the gem5 github group? I can take care of
removing the issue tracker and other github admin st
No problem Jason,
Do we think we should delete the GitHub issues completely or just
leave it there?
If not, people will still open issues there, and what should we do about those?
An intermediate approach is to add a CONTRIBUTING.md saying that "the
official issue tracker is the mailing list".
_
As an aside, opengrok was set up by Ali who now works for ARM. He has
showed up very briefly since I came back to the project, but I don't think
he's actively following the project. I would take care of some of these
things, but for some reason my root access on gem5.org seems to have been
removed
Hi Ciro,
First of all, we appreciate your efforts to further document gem5 and
answer questions on the gem5 users list!
Right now, we're really just using github as a backup mirror of gem5. I'm
not sure why this was started initially, TBH. It doesn't seem necessary now
that we are hosting the cod
If made collaborator, I commit to keep every spam out. But there is
little to no spam on GitHub by default anyways.
I feel that if users want to use GitHub issues, which seems to be the
case, we should cater for their preferred communication mechanism.
Issue trackers have several advantages, nota
Hi Everyone,
I think the first thing we need to establish is whether we want to use
GitHub for issue tracking in the first place. The issue tracker there
was left enabled by accident.
As some of you may recall, we used to run a Flyspray-based issue tracker
a long time ago. If memory serves me ri
Can I be made a collaborator on GitHub https://github.com/gem5/gem5 to help
manage the issues there?
This is my account: https://github.com/cirosantilli-work
I want this permission to be able to:
- close resolved issues
- tag issues appropriately, specially by architecture when appropriate
- fix
10 matches
Mail list logo