Plan for new development

[AdamPS]

Branches

I propose to introduce some minor interface changes as part of developing some new features and bug fixes. Therefore I suggest to move to a new major version v3. I intend v3 to become available within a few months. So my preference is like this, which should minimise the amount of merging needed.

1. Rename branch feature-safeeyes-3 (stale) to old-safeeyes
2. Use master branch for v3 development
3. Create a new branch for v2 if we need to backport high-priority bug fixes.

Roadmap

• My top priority is to fix some 'bugs' where the breaks don't come when I expect/want them do.
• Based on my earlier experiences I believe this will be easier if making some minor interface changes.
• Features are good, however it can still be improved, I have ideas for more.
• Visually the program is already good.

We can link issues here if they should be fixed before releasing v3 (i.e. they cause interface changes). We could also create a v3 tag for that purpose.

@slgobinath How closely do you want to be involved? You are very welcome to review in more detail, or if you prefer, leave me to work myself.

[slgobinath]

Thanks @AdamPS 🙏

I won't be able to involve much and I am happy to leave it to your leadership. Totally agree with your proposal.

[nifadyev]

Hey @AdamPS , sorry for disturbance, just wanted to know if you need any help with maintaining the project. I can deal with current issues and take part in developing V3

My background is 4 years of Web development using Django. During that period I dealt with many non-web related tasks like Docker setup, writing documentation, changing CI/CD and so on. I'd love to help and to be involved in making a tool which I use daily.

P.S.: @slgobinath , thank you for creating SafeEyes

[AdamPS]

That's great, I would welcome help, as I've been pretty busy. The next step is #552 and I'm sure the community would appreciate your help with that.

I suggest that you start by actively making useful comments, reviews, pull requests, etc. You can let me know which PR are ready and I can commit. Once you have become a successful active contributor then we can ask @slgobinath if he would make you a maintainer.

[nifadyev]

Thanks, sounds like a plan. I will start from reviewing existing PRs and then dealing with issues. It would be useful to write a contribution guide for other enthusiasts like me.

[AdamPS]

Great, the contribution guide is a good idea. However I'm still trying to figure things out for myself, so I guess we'll have to learn together😃.

[nifadyev]

Hey @AdamPS , I've looked into project codebase, relevant issues and V3 drafts and I think it would be wise to start planning V3 as soon as possible. There is no point fixing old deprecated logic which will be replaced soon (hopefully). What are your thoughts about it?

[deltragon]

Hello @AdamPS, I am open to becoming a co-maintainer for this project. I have already implemented a port to gtk4, along with other improvements and wayland fixes. In the case this project doesn't see any movement in the next few months, I am planning to fork this project under a new name and maintain it there until this project is revived.

[slgobinath]

Hi @deltragon and @nifadyev , I just saw your comments. I already saw your PRs and reviews and you guys are already contributing a lot to improve this project. Happy to see the Safe Eyes community growing with more maintainers. Sent the invitation to both of you.

@archisman-panigrahi shall I add you as well to the maintainer list?

[archisman-panigrahi]

Yes, I will be happy to be a maintainer

[nifadyev]

Hey @slgobinath , thank you for your trust, it's a challenging opportunity, but I'm afraid I won't be able to collaborate any time soon. I can review PRs and check issues and if that small amount of activity is OK for now, I will happily become a maintainer.

[nifadyev]

Hi @slgobinath , were you able to read my previous comment? The invitation will be expired in 2 days, and I'd like to receive your feedback before accepting/rejecting the invite.

[slgobinath]

Hi @nifadyev , Reviewing the PR is a lot of work. Please accept the invitation.

We all have other priorities. Having more people will help us keep the project alive even if some people are busy.

[AdamPS]

Sorry everyone I was busy and I only just found time to come back to safeeyes. I'm glad that there are now more maintainers and we can share the work.

[nifadyev]

Hey everyone, I would suggest converting this issue into discussion and slowly start working on future plans there