Replies: 15 comments 5 replies
-
|
另外我有个想法，我们按 star 数量给最佳实践排序一下怎么样（是不是有点太势利了x |
Beta Was this translation helpful? Give feedback.
-
|
可能需要一个综合评价，star占一定的权重（如果能计算的话。 |
Beta Was this translation helpful? Give feedback.
-
不是很支持，写的游戏比较冷门的话用户本来就少 |
Beta Was this translation helpful? Give feedback.
-
|
应该分两个榜单 一个针对玩家
另一个针对开发者
二者好像都没有必要根据star来排行 开发者榜单就没什么变动的必要 |
Beta Was this translation helpful? Give feedback.
-
|
再单独弄一个文档好了，包括一个大而全的目录，来者不拒，任何项目都可以放进去，也不会清 主页的既然叫“最佳实践”，我觉得还是要有一定限制的 |
Beta Was this translation helpful? Give feedback.
-
|
感觉又不太好，如果有一些游戏，主要日常部分常年不更新，所以脚本也不需要更新，同时功能比较简单也很稳定，没有什么 bug（所以没有 issue），这种还是应该留着的吧 怎么区分作者跑路了和软件太稳定不需要更新（ |
Beta Was this translation helpful? Give feedback.
-
原来我想法是直接discussion区开个投票，后来感觉大部分用户应该是上github下一个脚本就跑了，根本不会一直关注这个repo的，估计开了投票也没人参加 |
Beta Was this translation helpful? Give feedback.
-
如果稳定的话star应该也会涨点吧，不能毫无变化 |
Beta Was this translation helpful? Give feedback.
-
查issue啊,假如有个一周前的issue被标记已经解决,但是commit记录最晚都是半年前 |
Beta Was this translation helpful? Give feedback.
-
|
感觉都太主观了而且不好查，还得跟侦探似的（ 得找一个比较好量化的指标 |
Beta Was this translation helpful? Give feedback.
-
|
要不让最佳实践里面的作者都加下开发群，如果满足条件了就@一下作者，如果没反应就删了吧 |
Beta Was this translation helpful? Give feedback.
-
|
好像可以直接去发个 issue 问一下 |
Beta Was this translation helpful? Give feedback.
-
|
最终结论： 同时满足以下几个条件
我会去对应项目提一个 issue 询问作者是否弃坑，并告知将从最佳实践移除。 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
还可以再开一个used by列表 |
Beta Was this translation helpful? Give feedback.
-
|
还是建议搞个不移除的列表，里面放所有用FW开发的实践，这样有人问还有没有别的游戏的maa的时候我就可以把列表甩给他了 |
Beta Was this translation helpful? Give feedback.
-
|
这就事used by吧 |
Beta Was this translation helpful? Give feedback.
-
我看删完了没加used by列表就再提醒一下 |
Beta Was this translation helpful? Give feedback.
-
同时满足以下几个条件的最佳实践将被移除
这种一般都是作者跑路了（
当然如果有某些特别优秀的项目，会酌情保留
Beta Was this translation helpful? Give feedback.
All reactions