Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abandoned repo? #30

Open
hoijui opened this issue Jun 16, 2021 · 9 comments
Open

Abandoned repo? #30

hoijui opened this issue Jun 16, 2021 · 9 comments

Comments

@hoijui
Copy link
Collaborator

hoijui commented Jun 16, 2021

The last activity from @stevenhoneyman on this repo, regarding PRs, Issues and commits, is from December 2017 (EDIT: The whole account of @stevenhoneyman has not seen any activity since Dec. 2017).
... are you still here?
Would you be fine with someone else taking over?
I don't really want to, but maybe someone else wants?
It seems to be used by some, and some of us are also active here...
if some of those could get push access to this repo, or one of us declares his repo as the new main repo, and gives access to some of the others, the project could be a bit more lively again.

@stevenhoneyman
Copy link
Owner

I’m still alive but moved away from Linux as main OS a few years ago. I would be happy with someone else adopting this project that has the time to keep it going

@eyalroz
Copy link

eyalroz commented Jul 17, 2021

@stevenhoneyman : Would you mind altering the README to explain:

  1. how this project differs from the original leafpad.
  2. the fact that it is in search of a maintainer?

@hoijui
Copy link
Collaborator Author

hoijui commented Jul 20, 2021

I would say, we could do this ourselfs in a PR.
The difference to the original leafpad is, as much as I know, only that it uses GTK3 instead of GTK2; right?

@eyalroz woudl you be willing to co-take-over ownership/maintainership of this?

I don't have the time to .. further development, but to do basic maintenance against bit-rod, and check the eventual PR, I could do, would prefer not to be alone though.
If you would do it alone, I would also be happy. ;-)

@eyalroz
Copy link

eyalroz commented Jul 20, 2021

@hoijui : Unfortunately, I am already maintaining a bunch of repos which weren't originally my projects, due to a lack of maintenance/caretaking by others' and I'm not experienced with GTK. So, I have to decline... I might still write that PR though.

@hoijui
Copy link
Collaborator Author

hoijui commented Feb 14, 2022

@stevenhoneyman Could you please give me access?
I can not guarantee always fast reactions or anything, but I would do some stuff right now, and I think... even in the worst case: better two mostly inactive devs then only one.

@stevenhoneyman
Copy link
Owner

@stevenhoneyman Could you please give me access? I can not guarantee always fast reactions or anything, but I would do some stuff right now, and I think... even in the worst case: better two mostly inactive devs then only one.

Sure - invite sent for collaborator access. Thanks for offering to at least attempt some maintenance on it :)

@eyalroz
Copy link

eyalroz commented Feb 14, 2022

@hoijui : Please consider creating a Wiki page with your "action plan", now that you have write access :-)

@hoijui
Copy link
Collaborator Author

hoijui commented Feb 14, 2022

@eyalroz an action-plan ... :D

  • I will add 2 feautre-branches (never to be merged), and link to them from the README.
  • I might merge in the cmake branch. Please note objections in the associated issue
  • I will try to keep up with issues and pull requests, from time to time

I have a gazillion other projects, and I personally need no changes to l3afpad, except the above mentioned.

@usergreen
Copy link

Hello,
I am interested in l3afpad. it is a nice light and simple editor with auto-detection of encordig.

l3afpad has been adopted in Debian 12 (bookworm) instead, though leafpad was abondoned in Debian 10 and Debian 12. leafpad was once very popular among Japanese uses. I think it worth maintaining as it supports gtk3, and at lease keep translation updates.

I am not an experienced user, but hoping to continue to be maintained by someone like you. There seems to
be no need to develop a new function.

Best regards,
Green

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants