As I don't have permission to edit the page, here is my suggestion to improve the page:
Things You Do Not Have to Worry About
If you are thinking about taking over a project, you might have some doubts in due course. Here are some common concerns and how you can better deal with them:
I don’t like the current code and don’t want to learn it.
- That’s okay. You don’t necessarily have to keep the current code. You can start a new branch and only work on your own version. But the users should be advised since the beginning on the ways of working and would also important to have more context on the why you are starting a new code and the improvements and gains to be obtained with the changes you are doing.
I don’t want to help the old users.
- It is not mandatory that you assist old users. Although it will be a good practice and users will be very appreciated for the help provided. One suggestion is that you can leave a note on the top of the page explaining which is the latest version you support on the project page, so users will have awareness on what kind of assistance they will have.
I don’t want people to think I’m part of a failed project.
- You can change the project page to show what is new and better in your version. This can help people see your work as something useful and clear for everyone.
A Note About Ethics and Trust
Taking over a project should be done in an open and honest way. The community expects people to act with good intentions and having empathy for users. Respect and good intentions are expected so the community can be guided in the best way as possible.
It is also important to note that is you want to adopt a project, make sure your actions are transparent and visible to others. In case you are a co-maintainer you should be aligned with the major maintainer to guarantee you are on the same page. And in the roles of Project Owner and Maintainer would be interesting to follow the good practices the community give.
Things You Do Not Have to Worry About
If you are thinking about taking over a project, you might have some doubts in due course. Here are some common concerns and how you can better deal with them:
I don’t like the current code and don’t want to learn it.
- That’s okay. You don’t necessarily have to keep the current code. You can start a new branch and only work on your own version. But the users should be advised since the beginning on the ways of working and would also important to have more context on the why you are starting a new code and the improvements and gains to be obtained with the changes you are doing.
I don’t want to help the old users.
- It is not mandatory that you assist old users. Although it will be a good practice and users will be very appreciated for the help provided. One suggestion is that you can leave a note on the top of the page explaining which is the latest version you support on the project page, so users will have awareness on what kind of assistance they will have.
I don’t want people to think I’m part of a failed project.
- You can change the project page to show what is new and better in your version. This can help people see your work as something useful and clear for everyone.
A Note About Ethics and Trust
Taking over a project should be done in an open and honest way. The community expects people to act with good intentions and having empathy for users. Respect and good intentions are expected so the community can be guided in the best way as possible.
It is also important to note that is you want to adopt a project, make sure your actions are transparent and visible to others. In case you are a co-maintainer you should be aligned with the major maintainer to guarantee you are on the same page. And in the roles of Project Owner and Maintainer would be interesting to follow the good practices the community give.