starred/shiori

Fork 0

mirror of https://github.com/go-shiori/shiori.git synced 2026-04-25 14:35:52 +03:00

[GH-ISSUE #256] Archived and looking for a new maintainer #187

New issue

Closed

opened 2026-02-25 23:33:39 +03:00 by kerem · 7 comments

kerem commented

2026-02-25 23:33:39 +03:00

Owner

Originally created by @RadhiFadlillah on GitHub (Jun 20, 2020).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/256

Originally assigned to: @deanishe on GitHub.

Hi everyone,

I'm really, really sorry for not updating this application for so long. Unfortunately, as much as I'd love to, I can't work on this project anymore.

There are several reasons on why I can't work on this anymore :

Time.

I've made this app several months ago when I'm unemployed with lots of free time. Fortunately, now I have job and married (with child expected soon), which make my time is spent between job and family. For little "alone time" that I still have, I use it for my entertainment and side projects that I used daily, which leads to 2nd reason.
I'm not using Shiori anymore in my daily life.

When I built Shiori for the first time, I made it with two main purposes: to bookmark and archive. However, nowadays I've stopped using bookmark. There are several reasons for this :

a. I've stopped reading news.

Unfortunately, news nowadays only make me stressed and depressed, worrying about the future where my child will live, surrounded with pandemic, racism, climate change and impending doom of war.

b. I've limited the tech site that I read.

Back when I still unemployed, I will try to read and follow any new programming framework or architecture. Now I'm unemployed, I try to stick on what is essential for me, and not running to every shiny project that I see.

c. Bookmark doesn't really work for me.

Since long ago, I've got a habit to bookmark everything that looks interesting, even those that I haven't read. Thanks to this, I have a huge amount of backlog of article that I haven't read. To fix this, now I use a private blog where I wrote interesting things that I've found from other articles. This way, I'm forced to read the article, because if I didn't read it properly, then I can't convey it in written form properly.

With that said, I will archive this project for now. If anyone would like to maintain this project, feel free to send me email. Please understand that it might take me several hours or day to answer it.

Once again, I'm sorry for everyone that use, contribute and donate for this project, and thanks.

By the way, while I stopped working on Shiori, I still maintain the packages that Shiori uses, e.g. dom, go-readability and obelisk.

Originally created by @RadhiFadlillah on GitHub (Jun 20, 2020). Original GitHub issue: https://github.com/go-shiori/shiori/issues/256 Originally assigned to: @deanishe on GitHub. Hi everyone, I'm really, really sorry for not updating this application for so long. Unfortunately, as much as I'd love to, I can't work on this project anymore. There are several reasons on why I can't work on this anymore : 1. **Time**. I've made this app several months ago when I'm unemployed with lots of free time. Fortunately, now I have job and married (with child expected soon), which make my time is spent between job and family. For little "alone time" that I still have, I use it for my entertainment and side projects that I used daily, which leads to 2nd reason. 2. **I'm not using Shiori anymore in my daily life**. When I built Shiori for the first time, I made it with two main purposes: to bookmark and archive. However, nowadays I've stopped using bookmark. There are several reasons for this : a. *I've stopped reading news.* Unfortunately, news nowadays only make me stressed and depressed, worrying about the future where my child will live, surrounded with pandemic, racism, climate change and impending doom of war. b. *I've limited the tech site that I read.* Back when I still unemployed, I will try to read and follow any new programming framework or architecture. Now I'm unemployed, I try to stick on what is essential for me, and not running to every shiny project that I see. c. *Bookmark doesn't really work for me.* Since long ago, I've got a habit to bookmark everything that looks interesting, even those that I haven't read. Thanks to this, I have a huge amount of backlog of article that I haven't read. To fix this, now I use a private blog where I _wrote_ interesting things that I've found from other articles. This way, I'm forced to read the article, because if I didn't read it properly, then I can't convey it in written form properly. With that said, I will archive this project for now. If anyone would like to maintain this project, feel free to send me email. Please understand that it might take me several hours or day to answer it. Once again, I'm sorry for everyone that use, contribute and donate for this project, and thanks. --- By the way, while I stopped working on Shiori, I still maintain the packages that Shiori uses, e.g. [`dom`](https://github.com/go-shiori/dom), [`go-readability`](https://github.com/go-shiori/go-readability/) and [`obelisk`](https://github.com/go-shiori/obelisk).

kerem closed this issue

2026-02-25 23:33:39 +03:00

kerem commented

2026-02-25 23:33:39 +03:00

Author

Owner

@deanishe commented on GitHub (Aug 6, 2020):

I'm your huckleberry :)

@deanishe commented on GitHub (Aug 6, 2020): I'm your huckleberry :)

kerem commented

2026-02-25 23:33:39 +03:00

Author

Owner

@fmartingr commented on GitHub (Feb 1, 2022):

Hey @RadhiFadlillah, @deanishe. Does the project require a new maintainer? I emailed @RadhiFadlillah about the subject a few days ago but I'd like to make it public here as well.

@fmartingr commented on GitHub (Feb 1, 2022): Hey @RadhiFadlillah, @deanishe. Does the project require a new maintainer? I emailed @RadhiFadlillah about the subject a few days ago but I'd like to make it public here as well.

kerem commented

2026-02-25 23:33:39 +03:00

Author

Owner

@symgryph commented on GitHub (Feb 1, 2022):

I would suggest that either a new co-admin or a fork would be necessary. This was a cool project but seems to have stagnated. I could help with docker/security stuff, but an not a go programmer.

Thomas J Munn

On Feb 1, 2022, at 10:35, Felipe Martin Garcia @.***> wrote:

Hey @RadhiFadlillah, @deanishe. Does the project require a new maintainer? I emailed @RadhiFadlillah about the subject a few days ago but I'd like to make it public here as well.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.

@symgryph commented on GitHub (Feb 1, 2022): I would suggest that either a new co-admin or a fork would be necessary. This was a cool project but seems to have stagnated. I could help with docker/security stuff, but an not a go programmer. Thomas J Munn > On Feb 1, 2022, at 10:35, Felipe Martin Garcia ***@***.***> wrote: > > > Hey @RadhiFadlillah, @deanishe. Does the project require a new maintainer? I emailed @RadhiFadlillah about the subject a few days ago but I'd like to make it public here as well. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > Triage notifications on the go with GitHub Mobile for iOS or Android. > You are receiving this because you are subscribed to this thread.

kerem commented

2026-02-25 23:33:39 +03:00

Author

Owner

@fmartingr commented on GitHub (Feb 2, 2022):

I would suggest that either a new co-admin or a fork would be necessary. This was a cool project but seems to have stagnated. I could help with docker/security stuff, but an not a go programmer.

A fork was my first thought as well, but a lot of work is already in this repository (issues/prs) to just either discard it or do the insane amount of work of migrating it manually or ask everyone to contribute to another repo. Let's try to communicate with current maintainers first.

@fmartingr commented on GitHub (Feb 2, 2022): > I would suggest that either a new co-admin or a fork would be necessary. This was a cool project but seems to have stagnated. I could help with docker/security stuff, but an not a go programmer. A fork was my first thought as well, but a lot of work is already in this repository (issues/prs) to just either discard it or do the insane amount of work of migrating it manually or ask everyone to contribute to another repo. Let's try to communicate with current maintainers first.

kerem commented

2026-02-25 23:33:39 +03:00

Author

Owner

@symgryph commented on GitHub (Feb 2, 2022):

you will find that fruitless but good luck nonetheless

Thomas J Munn

On Feb 1, 2022, at 13:39, Thomas Munn @.***> wrote:

I would suggest that either a new co-admin or a fork would be necessary. This was a cool project but seems to have stagnated. I could help with docker/security stuff, but an not a go programmer.

Thomas J Munn

On Feb 1, 2022, at 10:35, Felipe Martin Garcia @.***> wrote:

Hey @RadhiFadlillah, @deanishe. Does the project require a new maintainer? I emailed @RadhiFadlillah about the subject a few days ago but I'd like to make it public here as well.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.

@symgryph commented on GitHub (Feb 2, 2022): you will find that fruitless but good luck nonetheless Thomas J Munn > On Feb 1, 2022, at 13:39, Thomas Munn ***@***.***> wrote: > > I would suggest that either a new co-admin or a fork would be necessary. This was a cool project but seems to have stagnated. I could help with docker/security stuff, but an not a go programmer. > > Thomas J Munn > > >>> On Feb 1, 2022, at 10:35, Felipe Martin Garcia ***@***.***> wrote: >>> >> >> Hey @RadhiFadlillah, @deanishe. Does the project require a new maintainer? I emailed @RadhiFadlillah about the subject a few days ago but I'd like to make it public here as well. >> >> — >> Reply to this email directly, view it on GitHub, or unsubscribe. >> Triage notifications on the go with GitHub Mobile for iOS or Android. >> You are receiving this because you are subscribed to this thread.

kerem commented

2026-02-25 23:33:39 +03:00

Author

Owner

@RadhiFadlillah commented on GitHub (Feb 2, 2022):

Hi @fmartingr

Thanks for reaching out to me and sorry for the late response. I almost reaching my job's deadline so I've been offline for the last few days to focus on that.

Does the project require a new maintainer?

Yes, it does. Unfortunately I'm busy between my main job and freelancing so I haven't been able to contribute to any open source project, and it seems @deanishe is busy and can't work on this project as well. With that said, I'll send you invite to this project as soon as possible.

@RadhiFadlillah commented on GitHub (Feb 2, 2022): Hi @fmartingr Thanks for reaching out to me and sorry for the late response. I almost reaching my job's deadline so I've been offline for the last few days to focus on that. > Does the project require a new maintainer? Yes, it does. Unfortunately I'm busy between my main job and freelancing so I haven't been able to contribute to any open source project, and it seems @deanishe is busy and can't work on this project as well. With that said, I'll send you invite to this project as soon as possible.

kerem commented

2026-02-25 23:33:39 +03:00

Author

Owner

@fmartingr commented on GitHub (Feb 3, 2022):

Thanks and don't worry! Let's go try and get things moving again :)

@fmartingr commented on GitHub (Feb 3, 2022): Thanks and don't worry! Let's go try and get things moving again :)

kerem referenced this issue

2026-02-25 23:34:38 +03:00

[PR #187] [CLOSED] Fix custom title and excerpt not being saved when adding a new bookmark #532