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, notably: - open close status immediately visible, which I intend to maintain on a best effort basis. But it is better than the mailing list, where you have to browse N emails before finding out. - you can opt in for notifications only from certain threads - you can reply to messages even though you weren't subscribed when they were made: https://webapps.stackexchange.com/questions/23197/reply-to-mailman-archived-message Notably, if new maintainers come along, they can't mention that some old bug was closed. - tagging, specially for archs - neater markdown formatting We don't need to make it an official mechanism, but I'd rather let people use their preferred method. Also anyone easily subscribe and unsubscribed to receive an email whenever a new issue is created, much like the mailing list. On Mon, Apr 9, 2018 at 1:29 PM, Andreas Sandberg <andreas.sandb...@arm.com> wrote: > 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 right, we ended up shutting down > the tracker since it was mainly used for spam and none of the devs was > using it. > > Cheers, > Andreas > > > > On 07/04/2018 21:20, Ciro Santilli wrote: >> >> 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 formatting problems >> >> and I will not use it for anything else. >> >> I have been supporting users often on the mailing list / GitHub / Stack >> Overflow over the last month, and Andreas can also serve as my reference. >> _______________________________________________ >> gem5-dev mailing list >> gem5-dev@gem5.org >> http://m5sim.org/mailman/listinfo/gem5-dev > > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
