Hey, I've built a project over the course of a year. I've put in a lot of hours into it, and it has come out great. A bunch of people use it, and a bunch of people write plugins for it. However, I have since moved on to different languages, different styles, the codebase is dirty and hackish, and I'm not sure I want to continue working in the framework I built it in.
嘿,我在一年的时间里建了一个项目。我花了很多时间,它已经很棒了。一群人使用它,一群人为它编写插件。但是,我已经转移到不同的语言,不同的样式,代码库是脏的和hackish,我不确定我想继续在我构建它的框架中工作。
When do you know that you should shut down a project and move on?
你什么时候知道你应该关闭一个项目并继续前进?
5 个解决方案
#1
Once you have lost inspiration and a project starts to get boring and you are to the point you can't get much or anymore experience from the project it's time to move on. If a project's codebase is too screwed up to fix then it's time to move on. If people use it and people write plugins for it, I'd personally make the project open source and turn it over to the community to continue otherwise just end it.
一旦你失去了灵感,一个项目开始变得枯燥无味,你就无法从项目中获得太多或更多的经验,现在是时候继续前进了。如果项目的代码库过于搞砸而无法修复,那么就该继续前进了。如果人们使用它并且人们为它编写插件,我个人会将项目开源并将其转交给社区继续,否则就会结束它。
Find a new maintainer since it's already open source. Ask for a volunteer. If they like it they will surely jump at the opportunity to maintain it.
找一个新的维护者,因为它已经是开源的。请一位志愿者。如果他们喜欢它,他们肯定会抓住机会来维持它。
#2
When you don't want to work on it anymore. Have you thought about open sourcing it so the community of users could continue to support it if they wanted?
当你不想再继续工作了。您是否考虑过开源,以便用户社区可以继续支持它?
#3
If you are sure you are ready to leave the project, then you can do so, but you should consider your users first. They still find it useful; they have contributed hours of work to write the plugins.
如果您确定准备离开项目,那么您可以这样做,但您应该首先考虑您的用户。他们仍觉得有用;他们贡献了数小时的工作来编写插件。
So, your first imperative is to make sure that those who want to use what they find useful can still do so, and can still enhance it. So, ask for a volunteer to take over the project, or a group. Provide them with the source, and your candid assessment of where the flaws are and what needs to be done to rectify them (rewrite).
因此,您的第一要务是确保那些想要使用他们认为有用的东西的人仍然可以这样做,并且仍然可以增强它。因此,要求志愿者接管项目或团队。向他们提供来源,并坦诚评估缺陷的位置以及需要采取哪些措施来纠正这些缺陷(重写)。
If you simply close down the project, you will make a lot of people unhappy with you who are currently happy with you - that would be silly. It's easy enough to make enemies without going out of your way to alienate people who will otherwise respect your decision.
如果你只是关闭项目,你会让很多人对你当前对你感到满意的人感到不满 - 这很愚蠢。这样做很容易让敌人不顾一切地疏远那些否则会尊重你的决定的人。
#4
Are you certain you won't gain more valuable experience/knowledge from working on this project? Why not reimplement it in the language/platform of your choice thereby making it a learning experience?
你确定你不会从这个项目的工作中获得更多宝贵的经验/知识吗?为什么不在您选择的语言/平台上重新实现它,从而使其成为一种学习体验?
#5
I would say that if you are going to spend more time rewriting and trying to work around your current framework then starting from scratch with a better design and plan, then it's a good time to move on.
我会说,如果你要花更多的时间重写并尝试解决当前的框架,然后从头开始设计和计划更好,那么现在是继续前进的好时机。
I think it really depends on your motivation for the project though. If it's purely financial then you can do a straight cost analysis. If it was for a hobby or learning experience, you may want to move on even if it would be easier to stay with the current project.
我认为这实际上取决于你对该项目的动机。如果它纯粹是财务方面,那么您可以进行直接成本分析。如果它是为了一个爱好或学习经验,你可能想要继续前进,即使它更容易与当前项目保持一致。
#1
Once you have lost inspiration and a project starts to get boring and you are to the point you can't get much or anymore experience from the project it's time to move on. If a project's codebase is too screwed up to fix then it's time to move on. If people use it and people write plugins for it, I'd personally make the project open source and turn it over to the community to continue otherwise just end it.
一旦你失去了灵感,一个项目开始变得枯燥无味,你就无法从项目中获得太多或更多的经验,现在是时候继续前进了。如果项目的代码库过于搞砸而无法修复,那么就该继续前进了。如果人们使用它并且人们为它编写插件,我个人会将项目开源并将其转交给社区继续,否则就会结束它。
Find a new maintainer since it's already open source. Ask for a volunteer. If they like it they will surely jump at the opportunity to maintain it.
找一个新的维护者,因为它已经是开源的。请一位志愿者。如果他们喜欢它,他们肯定会抓住机会来维持它。
#2
When you don't want to work on it anymore. Have you thought about open sourcing it so the community of users could continue to support it if they wanted?
当你不想再继续工作了。您是否考虑过开源,以便用户社区可以继续支持它?
#3
If you are sure you are ready to leave the project, then you can do so, but you should consider your users first. They still find it useful; they have contributed hours of work to write the plugins.
如果您确定准备离开项目,那么您可以这样做,但您应该首先考虑您的用户。他们仍觉得有用;他们贡献了数小时的工作来编写插件。
So, your first imperative is to make sure that those who want to use what they find useful can still do so, and can still enhance it. So, ask for a volunteer to take over the project, or a group. Provide them with the source, and your candid assessment of where the flaws are and what needs to be done to rectify them (rewrite).
因此,您的第一要务是确保那些想要使用他们认为有用的东西的人仍然可以这样做,并且仍然可以增强它。因此,要求志愿者接管项目或团队。向他们提供来源,并坦诚评估缺陷的位置以及需要采取哪些措施来纠正这些缺陷(重写)。
If you simply close down the project, you will make a lot of people unhappy with you who are currently happy with you - that would be silly. It's easy enough to make enemies without going out of your way to alienate people who will otherwise respect your decision.
如果你只是关闭项目,你会让很多人对你当前对你感到满意的人感到不满 - 这很愚蠢。这样做很容易让敌人不顾一切地疏远那些否则会尊重你的决定的人。
#4
Are you certain you won't gain more valuable experience/knowledge from working on this project? Why not reimplement it in the language/platform of your choice thereby making it a learning experience?
你确定你不会从这个项目的工作中获得更多宝贵的经验/知识吗?为什么不在您选择的语言/平台上重新实现它,从而使其成为一种学习体验?
#5
I would say that if you are going to spend more time rewriting and trying to work around your current framework then starting from scratch with a better design and plan, then it's a good time to move on.
我会说,如果你要花更多的时间重写并尝试解决当前的框架,然后从头开始设计和计划更好,那么现在是继续前进的好时机。
I think it really depends on your motivation for the project though. If it's purely financial then you can do a straight cost analysis. If it was for a hobby or learning experience, you may want to move on even if it would be easier to stay with the current project.
我认为这实际上取决于你对该项目的动机。如果它纯粹是财务方面,那么您可以进行直接成本分析。如果它是为了一个爱好或学习经验,你可能想要继续前进,即使它更容易与当前项目保持一致。