马上登录/注册，结交更多好友，享用更多功能，让你轻松玩转社区。
您需要 登录 才可以下载或查看，没有账号？立即注册
x
NEWS NeoForged Steering Council Meeting #1
NeoForged 指导委员会第一次会议纪要
时间：2023年7月17日 15:00（UTC-4）
地点：Discord
Agenda
议程
Three core groups: Steering Council, Maintainers team, Moderation team.
设三个核心小组：指导委员会、维护组和管理组。
Maintainers in charge of technical matters; Moderators in charge of community matters; Council in charge of the rest (and generally supervises the other two).
维护组成员负责技术事务，管理组成员负责社区事务；指导委员会负责其他所有事务（通常监督另两个小组的工作）。
Other teams created by Council (with approval of other two teams in certain cases), with charter delineating responsibilities and authority.
其他小组由指导委员会创建（在某些情况下须获得其他两个小组的支持），其义务和权利由小组章程规定。
Modification of certain docs (core governance, Code of Conduct, technical structuring) require approval of two/three core groups, depending on areas the docs fall into.
某些重要文件的修改（如核心治理条例、行为准则、技术架构等）需要得到两个/三个核心团队的批准，具体取决于文件所属的领域。
Steering Council has permanent members (currently cpw, Curle) and elected members (none yet). Elected term is 1 year. Council has spokesperson as first among equals.
指导委员会置常务委员（目前是cpw和Curle）与非常务委员（由选举产生，目前没有）若干。选举周期为1年。指导委员会置一位发言人作为众委员的代表。
Council may have interim members standing in for a regular member due to inactivity. Temporary members until original returns to activty. Original member can nominate their interim, and approved by rest of the council.
当一位委员不活跃时，指导委员会可指定一位临时委员来替补该席位。其替补资格在原委员重新活跃后终止。原委员可提名人选作为其替补，并交由指导委员会批准。
- Choose a third Council member
Responsible for breaking deadlocks between the two remaining (cpw and Curle).
Temporary appointment until governance is finalized and elections can begin.
See below answer.
负责打破只有2位常委（cpw 和 Curle）所造成的僵局。
此为临时任命，当治理工作结束且选举开始后此任命终止。
具体请见下文。
- Announce an interim Council member
Will take Curle’s place on the council while she goes on a break.
在Curle休假期间，将替补她的位席。
The current Steering Council team will become cpw, SizableShrimp, and Orion, with Curle still being a permanent member but on leave. We will determine the specifics of which member is which between SizableShrimp and Orion at a later date, just know all council members have equal say.
当前的指导委员会将由cpw、SizableShrimp和Orion组成。Curle 仍然是常委，但休假。我们将在稍后确定SizableShrimp和Orion的具体工作事项，不过目前只需知道所有委员会委员都有平等的发言权。
We need to plan for NAP 2023 / NAP23 - our annual discussion, in the same vein as FAP from previous years.
我们需要为我们的年度讨论 —— NAP（NeoForge Annual Parley, NeoForge年度茶话会） 2023 / NAP23做准备。与以往年份的FAP（Forge Annual Parley, Forge年度茶话会）类似。
We will plan and announce the official date later, but we think it will be sometime in September. We will also have a longer meeting during NAP23 where we will be able to answer more questions.
我们将在稍后计划并宣布正式日期，但我们认为它将在九月的某个时候举行。在NAP23期间，我们会举行一次更长的会议，以便回答更多问题。
- Decide where we will officially break
Upstream has demonstrated that there is little consideration for breaking changes in the mainline, so we should think about what we’re going to do. Keep trying to maintain compatibility with them, or go our own way now?
上游项目（指原始的Forge项目）已证明他们对于主线中的重大更改几乎没有任何考量，所以我们得思考我们要做什么。是继续努力与他们保持兼容性？还是从现在开始就走我们自己的路？
Our official stance is that we will try to maintain as much compatibility as we deem reasonable. We will review upstream changes on a case-by-case basis and either fix it to fix our standards or outright throw out bad changes that we deem not beneficial to maintain and support as a feature.
我们的官方立场是，我们将尽力保持我们认为合理的、尽可能多的兼容性。我们将根据具体情况审查上游的更改：要么将其修复以符合我们的标准，要么就彻底放弃那些我们认为对维护和支持不利的不良更改。
- Look at all the cool demo branding art made by the community
- 第六项议程：查看由社区所供的所有炫酷的候选项目标识
Particularly good art will hopefully be able to be commissioned formally for adoption by the project. We’re also looking for colour themes and a cohesive art style across the various pieces.
To look at all the art, see this thread.
特别好的作品有望被我们项目所正式采纳。我们目前也在寻找我们项目的颜色主题和贯穿各作品的艺术风格。
若想查看所有作品，请点击此链接。
One thing we want to make clear is that we are trying to get away from the anvil motif and develop our own style. We plan to choose 1-2 artists who submitted amazing art in the thread that we personally like and want to continue developing by commissioning them to make our entire branding.
有一点我们需要明确，我们正努力摆脱“铁砧”图案并发展我们自己的风格。我们计划选择1-2位在讨论中提交了出色作品的艺术家，委托他们来制作我们的完整项目标识。
After consideration during the meeting, we have decided to contact Mr. Crayfish and Ultramega for further discussion on the style that Mr. Crayfish brought to the table and Ultramega improved upon. Congratulations!
Here are the links to Mr. Crayfish’s demo and Ultramega’s demo.
经过会议期间的考量，我们决定就Mr. Crayfish提出并由Ultramega改进的风格，联系二位艺术家做深入讨论。恭喜他们！
这里是Mr. Crayfish’s demo和 Ultramega’s demo 的链接.
We want to reiterate we are so thankful to everyone who submitted demo art. It was all so lovely, thank you so much! Again, you can see all the art in this thread on the Discord.
我们要再次强调我们对所有提交作品demo的人表示衷心的感谢。非常感谢你们！你可以在Discord上的此讨论中看到所有作品。
Questions
问题
We won’t be answering detailed technical questions at this meeting - we will be raising those with the team and reviewing for discussion at NAP 2023.
我们在本次会议中不会回答详细的技术问题——我们会将这些问题提交给团队，并在NAP 2023的讨论中进行审议。
To submit questions to (possibly) be answered during the meeting, see this Google Form link.
New questions won’t be accepted/added here after the meeting starts.
要提交问题以便在会议中（可能）被回答，请参见此Google表单链接。
会议开始后将不再接受/添加新问题。
品牌
Q:Is NeoForge the final name for the project? Why does this name still have Forge in it?
A:Yes, NeoForge is the final name for the project. This was chosen as a nice mix between the new and the old. We still want people to immediately recognize the connection to “Forge”, while also emphasizing the new and freshness with “Neo”, quite literally meaning new!
问：NeoForge是项目的最终名称吗？为什么这个名称中仍然包含Forge？
答：是的，NeoForge是项目的最终名称。这是一个很好的折中选择，既保留了人们对“Forge”的直接联想，又强调了“Neo”所代表的新颖和新鲜的含义——从字面意义上是新的！
Q:What are appropriate abbreviations or nicknames for NeoForge? Neo? NF? NeoF?
A:We prefer Neo or NeoForge, thanks!
问：NeoForge的合适缩写或昵称是什么？Neo？NF？NeoF？
答：我们更喜欢Neo或NeoForge，谢谢！
Q:What is NeoForge’s mascot?
A:Foxes, squirrels, frogs?? I don’t think we fully know yet! Any Minecraft animal (or squirrels!) will work 
问：NeoForge的吉祥物是什么？
答：狐狸、松鼠、青蛙？我认为我们还不太确定！任何Minecraft动物（或松鼠！）都可以！
治理
Q:How are plans to procure funding for the project going? Will NeoForged become a legal registered non-profit organization?
A art of our plan is to be a zero-sum hosting project, where we don’t incur any cost in hosting by using things such as CloudFlare or partnering with other community members and projects. This would mean we don’t need any funding, period! NeoForged will definitely become a legal registered non-profit organization; we will have more information later. We will definitely still take up funding from people who want to provide it to us and perhaps try to setup a distribution model among contributors to give them some pocket change for their hard work.
问：获取项目资金的计划进展如何？NeoForged会成为一个合法注册的非营利组织吗？
答：成为一个零和托管项目——这是计划的一部分。通过使用CloudFlare或与其他社区成员和项目合作，我们不需要承担任何托管成本。这意味着我们不需要任何资金支持！NeoForged肯定会成为一个合法注册的非营利组织，我们将在以后提供更多信息。我们肯定会接受愿意向我们提供资金的人的支持，并可能尝试建立一个分配模型，以给予贡献者一些零花钱以表彰他们的辛苦工作。
Q:Will there be more public Steering Council meetings?
A:We will tentatively say that we want to try and do these meetings monthly or something akin to that. We want to emphasize that we don’t want this to become a chore, so we will try to keep it fresh and interesting each time we do it without becoming boring and monotonous. We also have NAP23 to think about.
问：是否会有更多公开的指导委员会会议？
答：我们暂定每月举行该会议或类似会议。得强调的是，我们不希望这成为一项任务。因此我们将努力使每次会议都新鲜有趣，而不会变得乏味和单调。我们还有NAP23要考虑。
Q:Is there a publicly viewable roadmap?
A:Nope, we don’t have a roadmap yet. We are going to work on this, though! We’ll let the community into this plan as we know more. As King Lemming best said, we can’t have a roadmap without a road!
问：是否有公开可查看的路线图？
答：没有，我们还没有路线图。不过我们将努力制定一份！随着我们了解得更多，我们将让社区参与进这份计划。正如King Lemming所说，如果没有方向，我们就没办法有路线图！
对外关系
Q:Have you been in communication with CurseForge / other partners yet?
A:Yep! We don’t have more information than that right now. CreeperHost is currently providing the server that neoforged.net is hosted on, thanks CreeperHost!
问：你们与CurseForge/其他合作伙伴有过交流吗？
答：是的！我们目前没有更多可以提供的信息。CreeperHost目前提供了neoforged.net的服务器，感谢CreeperHost！
Q:There was talk of buying the original Forge, are discussions for that happening?
A:We don’t think there was talk of buying the original Forge.
问：关于购买原Forge的讨论是否正在进行？
答：我们并没有讨论购买原Forge的相关事宜。
Q:Any possible collaboration with Sponge, if Sponge decides to move to NeoForge?
A:We are happy and open to working with any team, not just Sponge. If they want to work with us, we are happy to start communication channels.
问：如果Sponge决定转向NeoForge，是否有可能与Sponge进行合作？
答：我们愿意与包括Sponge在内的任何团队合作。如果他们想与我们合作，我们很乐意开启沟通渠道。
Q:What will happen to the Forge Community Wiki (FCW) going forward? Will it document both projects or will it focus entirely on NF?
A:There are no concrete plans yet, but given it is run by Curle, who is on the Steering Council team, she knows exactly what will happen to it. It might turn into a general modding wiki, we don’t know yet.
问：Forge社区维基（FCW）将如何发展？它是会同时记录两个项目，还是将完全关注NF？
答：目前还没有具体计划，但这件事由指导委员会的Curle负责，她知道将发生什么。它有可能会变成一个普通的模组编写维基，我们还不确定。
Q:Some people believe NeoForge will further split the already-shattered modded Minecraft community. What’s the NeoForged team’s stance on this?
A:Curle and cpw decided that the best way to continue Forge and keep it running long into the future was to fork it and create NeoForge. This was not an easy decision, but it is the one we made.
问：有些人认为NeoForge将进一步分裂已经四分五裂的Minecraft Mod社区。NeoForged团队对此持何种立场？
答：Curle和cpw认为延续Forge项目并使其在将来继续运行的最好办法是fork它并创建NeoForge。做出决定的确很艰难，但这还是我们最终做出的决定。
Q:Has there been any talk about how multiple Forge forks will be handled at the user level?
A:This question isn’t very clear to us, but we don’t think there will many Forge forks going forward. The core of it is that you can obviously only run one Forge at a time. We will cross these bridges as we come to them.
问：在用户层面，是否有讨论如何处理多个Forge分支？
答：我们不太清楚这个问题的具体意思，但我们认为未来不会有太多的Forge分支。显然你一次只能运行一个Forge。我们将根据实际情况解决这些问题。
项目设计与贡献
Q:What’s the path to starting to accept outside contributors?
A:We will work on getting a public document up and running that people can use as a jumping-off point to get started with us. We will let you know!
问：接受外部贡献的途径是什么？
答：我们将努力建立一个公开的文档，供人们作为与我们合作的起点。我们会告诉你的！
Q:Is the mere mention of coremodding still considered a threat in PRs and issues?
A:There will be zero punishment for the mention of coremodding/Mixins/whatever in PRs going forward. If you have a proof of concept using Mixins/coremodding, please let us know and share it with us in the PR! This can make it easier for us to test your idea.
问：在PR和issue里提及Coremodding仍然被视作威胁吗？
答：今后提及Coremod/Mixin或任何内容的PR将不会受到任何惩罚。如果您在概念验证时有使用Mixin/Coremod，请在PR中告诉我们并与我们分享！这将使我们更容易测试您的想法。
Q:What are some issues that went unresolved that will be picked up now that Forge has been forked?
A:We will be comprehensively taking a close eye to everything in the NeoForge ecosystem and improving what we see fit. Some things on our mind include overhauling registries, the Gradle toolchain, and the installation process.
问：有哪些未解决的问题将在Fork Forge后得到解决？
答：我们将全面审视NeoForge生态系统中的所有内容，并改进我们认为合适的内容。我们关注的一些事情包括改进注册表、Gradle工具链和安装过程。
Q:Is the whole Java Platform Module System (JPMS) thing imposed by modlauncher going to stay or change?
A:Yes, we will be keeping this going forward. We think that jumping ship to JPMS now is the best step forward to the future, as Java itself continues locking us into this system with newer JDKs. However, this isn’t all bad! There are many, many things in the JPMS that we simply cannot do with the pre-module systems. There are both drawbacks and benefits, as with any solution.
问：modlauncher引入的Java平台模块系统（JPMS）是否会保持不变？
答：是的，我们将在未来继续使用它。我们认为，现在跳到JPMS是最佳的举措，只要我们使用新JDK，Java本身就会将我们和这个系统锁死。然而，这并不全是坏事！JPMS中有很多我们以前的模块系统无法实现的功能。就像任何解决方案一样，它既有优点也有缺点。
Q:Many of the project leads are well known to have difficult time commitments. The triage team also was mostly inactive for the last few months. What can be done for Neo to improve the pace of development?
A:The triage team inactivity was largely due to internal disagreements, which have since been resolved with the fork of NeoForge! The triage team will cease to exist and will be merged into the new general Maintainers team. cpw himself recognizes his inactivity in past years, but he also has new passion for the fresh NeoForge project. He will stay active and around as he is a Council member. Do note that we are humans and have busy real lives! We will continue to improve upon this to work in the frame of our team having their own commitments so that nothing gets stalled.
问：众所周知，许多项目负责人在时间安排上有困难。过去几个月里，有三分之二的团队也基本处于不活跃状态。为了提高Neo的开发速度，有什么可以做的？
答：三分之二团队的不活跃主要是因内部分歧引起的，但随着NeoForge的fork，这个问题已经得到解决！这三分之二的团队将并入新的维护团队。cpw本人承认他在过去几年里的不活跃，但他对新的NeoForge项目充满了热情。作为委员会委员，他将保持活跃。请注意，我们是人类，我们有忙碌的现实生活！我们将继续努力改进，使团队能够在自己的承诺范围内工作，以避免任何事情的停滞。
Q:Is NeoForge’s code style going to remain the same as Forge’s? Are patches/the decompiled code still going to have three-space indention?
A:We will definitely be getting autoformatters for our codebase set up and changing the decopile/patch output to look nicer for everyone.
问：NeoForge的代码风格会保持与Forge相同吗？补丁/反编译的代码是否仍将保持三空格缩进？
答：我们肯定会设置自动格式化工具来处理我们的代码库，并且会改变反编译/补丁输出的样式，使其对所有人更加友好。
Neoforge的发布
Q:What will be the new running stance on 3rd-party launchers auto-installing NeoForge?
A:Our stance is do whatever you want! If we can get our zero-sum hosting plan in action, then 3rd-party launchers installing NeoForge through our servers should be no problem at all.
问：你们对于第三方启动器自动安装NeoForge的立场是什么？
答：我们的立场是你可以随意选择！如果我们能够实现零和托管计划，那么通过我们的服务器让第三方启动器安装NeoForge将不成问题。
Q:Are there plans for having NeoForge builds on snapshot or pre-release Minecraft versions in the future?
A:We want to have snapshot builds, but there is also a lot of work that goes into these updates that we have to change to be able to more publicly share it with everyone.
问：将来是否计划在快照或预发布的Minecraft版本上发布NeoForge构建？
答：我们希望能够发布快照版本，但是这也需要进行许多工作，以便能够更公开地与所有人分享。
Q:Are there plans to curate a list of mirrors for the NeoForged installer to use? Forge itself uses CreeperHost’s mirror, see https://files.minecraftforge.net/mirrors-2.0.json. Are y’all open to someone offering mirror services to shared the load?
A:We currently have no plans for an official mirrors list because we have (almost) nothing to mirror! If we can properly setup CloudFlare hosting/caching, then it will probably not even make sense to use any mirrors at all as CloudFlare will be the fastest we can possibly achieve around the globe.
问：是否计划为NeoForged安装程序提供一系列镜像列表？Forge本身使用CreeperHost的镜像，请参见https://files.minecraftforge.net/mirrors-2.0.json。你们是否愿意接受某人提供镜像服务以分担负载？
答：我们目前没有提供官方镜像列表的计划，因为我们（几乎）没有什么需要镜像！如果我们能够正确设置CloudFlare托管/缓存，那么使用任何镜像可能根本没有意义，因为CloudFlare下载可能是我们在全球范围内可能提供的最快速度。
Q:Can we expect an official Kotlin language provider? Over the years, the community has maintained one; however, official support would be nice.
A:We want to provide closer support to language providers, but we have gotten burned (Scala) in the past which delayed this going forward. Let’s say, we have plans!
问：我们可以期望官方的Kotlin语言支持吗？多年来，社区一直在维护一个，但倘若有官方支持肯定会更好。
答：我们希望为多编程语言支持提供帮助，但我们过去遇到了一些问题（例如Scala），这延迟了我们在未来的计划。也就是说，我们有计划！
社区参与
Q:Will there be a NeoForgedJam?
A:If there is a NeoForgedJam, it will be announced at NAP23.
问：是否会举办NeoForgedJam？
答：如果有NeoForgedJam，将在NAP23上宣布。
Q:If there’s a NeoForgeJam, will it be possible to use Mixins in the mod submissions without getting judged harshly for it?
A:Yes, you can use Mixins. We might even have a criteria for most creative Mixin!
问：如果有NeoForgeJam，是否可以在模组中使用Mixins而不会受到严苛的评判？
答：是的，你可以使用Mixins。我们甚至可能会制定一个最有创意的Mixin的标准！
Answered Questions
已回答的问题
These questions have been answered ahead of time by discussion of the council and the team.
这些问题已由委员会和项目团队提前回答。
Q:Is NeoForge going to be free?
A:Yes.
问：NeoForge将是免费的吗？
答：是的。
Q:Will Eclipse still be a supported IDE?
A:Yes! Definitely.
问：Eclipse仍是受支持的IDE吗？
答：当然。
Q:What’s the difference between NeoForged and NeoForge?
A:NeoForged is the name of the GitHub organization and the website domain (neoforged.net). This is because “NeoForge” was simply not available. Therefore, NeoForged is the organization name, while NeoForge is the modding project itself. This also means we can better distinguish the two.
问：NeoForged和NeoForge有什么区别？
答：NeoForged是GitHub组织和网站域名（neoforged.net）的名称。这是因为“NeoForge”这个名字不可用。因此，NeoForged是组织名称，而NeoForge是该项目本身的名称。这样我们可以更好地区分两者。
Q:Will you continue to have a private repository for updating NeoForge to newer versions of Minecraft, or will the porting procedure made public?
A:Having an internal, private repository for update NeoForge is a necessity so that the team can collaboratively fix compile errors without having to rely on generating patches.
This means the entire decompiled game is stored in private Git history, which we obviously cannot share for legal reasons. However, we still have much to discuss on how this process might change in the future to be more visible to the community.
问：你们是否会保留高版本Minecraft的私有源码仓库以供NeoForge的更新，或是公开整个版本迁移过程？
答：为了不依赖生成补丁的方式来解决编译错误，我们必须拥有一个内部的私有仓库。
这意味着整个反编译的游戏代码都存储在私有的Git历史记录中，出于法律原因，我们显然不能分享它。然而，关于如何将这个过程更可见地展示给社区，我们还有很多东西要讨论。
Q:Will existing Forge modpacks (like Better Minecraft, Create: Above and Beyond, and Vault Hunters) be supported on NeoForge?
A:We plan to keep compatibility with original Forge, for the time being. This means that existing modpacks on 1.20.1 should work the exact same on Neo. Going forward, we will see what compatibility looks like with new Minecraft versions. It’s up to modders and modpack makers which platform they want to support.
问：现有的Forge整合包（如Better Minecraft、Create: Above and Beyond和Vault Hunters）是否会在NeoForge上受支持？
答：我们计划保持与原始Forge的兼容性，至少目前是这样。这意味着在1.20.1上的现有整合包应该与Neo上的情况完全相同。对于新的Minecraft版本，我们将看看兼容性如何。模组开发者和整合包制作者可以自行决定他们要支持哪个平台。
Q:Will older minecraft versions (mainly 1.7/1.12/1.16) receive some degree of support, or at the very least not result in a ban when asking about them?
A:You can already receive user support for these versions in the NeoForged Discord. You will not get banned for talking about legacy versions. There are still plans of continuing RetroGradle, which is an effort to get our modern toolchains working on legacy versions. Currently, 1.12.2+ can already be used on our modern toolchains.
问：旧版的Minecraft（主要是1.7/1.12/1.16）是否会获得一定程度的支持，或者至少不会因为谈论这些版本而受到封禁？
答：您已经可以在NeoForged Discord中获得这些版本的用户支持。如果您讨论旧版本，不会因此被封禁。我们仍然计划保持与这些旧版本的兼容性。但是，请记住，我们工作的主要焦点是当前和未来版本。
Q:Are there plans to try and create a cross-version API?
A:No. Efforts like Bukkit already exist for this purpose. Part of the problem with cross-version APIs is that you lock yourself into design choices for years to come without even knowing what is coming in future Minecraft versions. The effort needed to design these APIs is also huge and taxing. For these reasons, we will not be making a cross-version API.
问：有计划尝试创建跨版本API吗？
答：不会。已经有像Bukkit这样的努力来实现这个目的。跨版本API有一个问题是，你会依赖当前的Minecraft版本来做出设计上的决策，但你却不知道未来的Minecraft版本会有什么变动，这会让人在设计时非常纠结。设计这些API所需的工作量也非常大。出于这些原因，我们不会创建跨版本API。
Q:A common refrain from the old Forge team is that they don’t have time to do X, but also that they don’t want help with X. Will this attitude be similar?
A:Asking for help for things we can’t spend time on is tricky. We take pride in our work, and we need to be able to ensure that other side projects (like maintaining 1.7.10 or 1.12.2) have the same quality standards. Taking on random community members with no verification is not something we are willing to do, people have to be vetted and onboarded. Making this process easier and more open is something we are wanting to move towards.
问：旧Forge团队经常说他们没有时间做某事，但也不希望别人帮助他们。NeoForged团队的态度会类似吗？
答：在我们没有时间处理的事情上寻求帮助是棘手的。我们对自己的工作感到自豪，我们需要确保其他项目（如1.7.10或1.12.2的维护）具有相同的质量标准。我们不愿意接纳未经审查的社区成员加入工作，人们需要经过审查和融入的过程。我们希望让这个过程更加简单和开放。
Q:Factorio has a really nice system for syncing client and server mods before joining. What are the thoughts on adding that kind of functionality to Forge? They do control the mod portal as part of that, but could you partner with CF/Modrinth and do this?
A:While this may work for Factorio, it is not something we are planning on adding into NeoForge itself. We have no control over external mod distribution platforms, and downloading arbitrary code gets risky.
问：Factorio有一个非常好的系统，在加入服务器之前同步客户端和服务器的模组。关于将这种功能添加到Forge，你们有什么想法？他们通过控制模组下载网站来实现这一点，你们是否可以就此与CurseForge/Modrinth合作？
答：虽然这对于Factorio可能有效，但我们没有计划将其直接添加到NeoForge中。我们无法控制外部模组分发平台，并且下载任意代码存在风险。
Q:Adding mods right now requires a complete reboot of the client. Is there any future where Forge mods could act more like datapacks, being able to be added/removed on the fly?
A:This is a potential future goal, but it also requires engineering to support. We may look into this.
问：目前添加模组需要完全重新启动客户端。未来是否有计划使Forge模组更像数据包一样，可以在运行时添加/删除？
答：这是一个可能的未来目标，但它也需要工程上的支持。我们可能会考虑这一点。
Q:What’s the attitude towards Bukkit+Forge hybrid? Any chances of collaboration?
A:There is little chance of collaboration from our side. Bukkit and its ecosystem is too invasive to put on top of (Neo)Forge, and vice versa. Attempts have been made in the past, and they always lead to issues. It’s not something we are interested in putting manpower to at this time.
问：对于Bukkit+Forge混合有什么态度？是否有合作的机会？
答：从我们这边来看，合作的机会很小。Bukkit及其生态系统对于（Neo）Forge来说过于侵入，反之亦然。过去曾尝试过合作，但总是会出现问题。我们目前对此不感兴趣。
Q:Are you planning on making Forge somewhat compatible with Fabric?
A:Multiplatform mods are fine and we will be making sure that next-gen NeoGradle tooling will be able to support these scenarios. Using Fabric directly in NeoForge will probably not be something we consider in any reasonable timeframe. Future collaborations with Fabric developers are definitely on the cards however, we have been speaking with Fabric developers and they have offered help and insights already.
问：你们是否计划使Forge在某种程度上与Fabric兼容？
答：多平台模组是可以的，我们将确保下一代NeoGradle工具能够支持这些情况。直接在NeoForge中使用Fabric不会成为我们考虑的事情。然而，与Fabric开发人员的未来合作肯定是可以的，我们已经与Fabric开发人员进行了交流，并得到了他们的帮助和见解。
Q:"One issue that I think Forge faced, as an open source project, is that decisions kept being made behind closed doors and in private. Whilst there is definitely an appropriate time for some decisions to be made behind closed doors when it comes to discussions relating to PRs many people found it not to be in the spirit of the open source nature of Forge to have these discussions in private. It meant decisions, and discussions, weren’t held to the same level of scrutiny as perhaps should’ve been and left people confused and uninformed.
In the future, do you see these kind of discussions continuing behind closed doors?
Whilst I understand that as a team you may wish not to contradict eachother I don’t think that really matters as no one expects an entire team to be on the same page about everything."
A:We will be talking about this and how the steering council will try and avoid this kind of stalling out.
问：“我认为Forge作为一个开源项目面临的一个问题是，决策一直在闭门状态下私下进行的。尽管在涉及PR讨论的情况下，有适当的时机参与一些闭门决策，但许多人发现这不符合Forge作为开源项目的精神，这意味着决策和讨论没有接受应有的审查，让人感到困惑和不知情。
将来，你们是否会继续在闭门的情况下进行这些讨论？
虽然我理解作为一个团队，你们可能希望彼此保持一致，但我认为这并不重要，因为没有人指望整个团队在每个问题上都达成一致。”
答：我们将讨论这个问题，以及指导委员会将如何避免这种情况。
Q:Are you going to support Bungeecord/Velocity?
A:If they wish to talk to us about what they need from us, we are willing to talk to them.
问：你们是否支持Bungeecord/Velocity？
答：如果他们希望与我们讨论他们对我们的需求，我们愿意与他们交流。
Q:Eliminate the frogs in our #squirrels chat, please?
A:No
问：请在我们的#squirrels聊天中移除青蛙，好吗？
答：不行。
Q:Will the McModLauncher org and ModLauncher itself remain independent of NeoForge?
A:Yes. It was never intended to be part of Forge or NeoForge.
问：McModLauncher组织和ModLauncher本身是否将继续独立于NeoForge？
答：是的。它从未打算成为Forge或NeoForge的一部分。
Questions we won’t be answering today
我们目前不会回答的问题
Q:What happened with LexManos and why did you decide to kick him?
A:The post from cpw on neoforged.net goes into detail. We won’t be expanding further on this decision in future, other than maybe a post from Curle if/when she wishes to speak about it.
问：在LexManos身上发生了什么？以及你们为什么决定要将其踢出去？
答：cpw在neoforged.net上的帖子详细说明了情况。我们不会进一步阐述这个决定，除非Curle希望写一篇帖子来讲述此事。
【ABlueCat 译自 neoforged 在 2023 年 07 月 17 日发布的 NeoForged Steering Council Meeting #1；原作者 NeoForged】
【本文排版借助了：SPXX v2.4.14】
|
服务器提升卡
