Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

整理你问我答区中的崩溃求助 #8

Open
1 of 3 tasks
Glease opened this issue Feb 7, 2016 · 2 comments
Open
1 of 3 tasks

整理你问我答区中的崩溃求助 #8

Glease opened this issue Feb 7, 2016 · 2 comments
Labels

Comments

@Glease
Copy link
Contributor

Glease commented Feb 7, 2016

你问我答区经常看到许多重复的崩溃求助,解释的时候经常看到“见XXXX楼”等字样,这样既不方便求助者查找,也不方便以后解答者记忆,需要整理。

问题:

  • 整理多少?

个人建议整理2015/9/1日以后的求助

  • 文件系统结构?

每份整理出的报告的根目录: /Crashes/YY/MM/XX/
./crashreport.log
崩溃报告(如有)
./result.md
求助处理结果,包括处理人,处理日,求助日等信息
./logs.zip
日志(如有)
./hs_err.log
JVM错误报告(如有)
./mods.json
mod list(如无崩溃报告,则有)

@Glease Glease added the 仓库 label Feb 7, 2016
@LasmGratel
Copy link

建议:用机器人(具体怎么实现我就不知道了,百度的API简直GG)将每个帖子中的crash-report,logs,hs_err,mods等整理。
或者可以换一条路,用Bugzilla/JIRA实现Bug反馈系统自动增加某些活跃的评论员为审核员
并且,积极帮助的人可以在吧内进入**“表彰榜”(置顶帖)
这样
有时间和精力的人就会经常活跃于这个系统。管理员也不需要花费大量时间和精力进行清理工作。(因为反馈系统已经帮你实现**了233)

@Glease
Copy link
Contributor Author

Glease commented Jun 10, 2016

不管哪条路,首先你都必须要有Baidu Tieba API, 然后按你的说法,GG

--- Original Message ---

From: "Lasm Gratel" notifications@github.com
Sent: June 10, 2016 9:55 PM
To: "MCIndustrial2Bar/MCIC2BAR" MCIC2BAR@noreply.github.com
Cc: "Glease" glease.wang@outlook.com, "Author" author@noreply.github.com
Subject: Re: [MCIndustrial2Bar/MCIC2BAR] 整理你问我答区中的崩溃求助 (#8)

建议:用机器人(具体怎么实现我就不知道了,百度的API简直GG)将每个帖子中的crash-report,logs,hs_err,mods等整理。
或者可以换一条路,用Bugzilla/JIRA实现Bug反馈系统,自动增加某些活跃的评论员为审核员。
并且,积极帮助的人可以在吧内进入“表彰榜”(置顶帖)
这样有时间和精力的人就会经常活跃于这个系统。管理员也不需要花费大量时间和精力进行清理工作。(因为反馈系统已经帮你实现了233)


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/8#issuecomment-225188328, or mute the threadhttps://github.com/notifications/unsubscribe/AEX9lZLesOcUkSzvSOrG2CeR543cymhtks5qKWzNgaJpZM4HVIYP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants