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

PSA: Ferrit v0.1.0, a fork of Libreddit, released #599

Closed
Daniel-Valentine opened this issue Oct 16, 2022 · 4 comments
Closed

PSA: Ferrit v0.1.0, a fork of Libreddit, released #599

Daniel-Valentine opened this issue Oct 16, 2022 · 4 comments

Comments

@Daniel-Valentine
Copy link
Member

Daniel-Valentine commented Oct 16, 2022

I've released Ferrit v0.1.0 today. Ferrit, previously libbacon (see #594), is a fork of Libreddit to build on @spikecodes et al.'s excellent work, address outstanding Libreddit issues, and keep the project alive. Ferrit v0.1.0 already includes code to address open issues/PRs in this project:

If you are hosting a Libreddit instance, I highly encourage you to switch over to Ferrit, which is actively maintained, whereas Libreddit is not. The Ferrit GitHub org also maintains a separate repo, ferritreader/ferrit-instances, that hosts a hopefully up-to-date list of active Ferrit instances. Should you switch to Ferrit, you are more than welcome to open a PR in that to add your instance.

We have a separate Matrix room for Ferrit, although I am also active in the Libreddit room as well; see the Discuss Ferrit wiki page.

@spikecodes: Once again, thank you for building Libreddit. Please let us know when you are back, and if we should synchronize Ferrit with Libreddit.

@spikecodes
Copy link
Collaborator

Hi all! I apologize for my absence but I am back.

There is clearly a lot of people who still use Libreddit so I will do my best to keep the project alive and am grateful for your efforts to do so. @Daniel-Valentine

  1. Are those four pull requests/issues the only things currently separating Ferrit from Libreddit? I would happily support synchronizing the new projects (into this repo as it has most of the contributions currently).
  2. To prevent my absences from stalling the project's growth in the future, I'm launching the @libreddit organization and will transition Libreddit there to become a community-maintained project. @Daniel-Valentine If you're interested, I'd love for you to become a project manager. Feel free to message me on Matrix about this further.

@eUgEntOptIc44
Copy link

Hi @spikecodes great to have you back! 👍

@Daniel-Valentine
Copy link
Member Author

Daniel-Valentine commented Nov 2, 2022

@spikecodes: Great to have you back, and as I've said before, thank you so much for your hard work on Libreddit. Answering your questions in reverse order:

To prevent my absences from stalling the project's growth in the future, I'm launching the https://github.com/libreddit organization and will transition Libreddit there to become a community-maintained project. @Daniel-Valentine If you're interested, I'd love for you to become a project manager. Feel free to message me on Matrix about this further.

I would be more than happy to take on this role, and I'd like to put in a good word for @sigaloid, who had also made numerous contributions to the Ferrit codebase since its start. I agree that we should merge the two projects together. Here is what I think we should do:

  1. Begin the process of porting Ferrit changes into Libreddit. This will require some ugly diffing, but I'll be more than happy to assist with this.
  2. Come up with a new name for Libreddit. We have to do this, unfortunately, because of the probable Reddit API TOS violation. This is where I'd like community input. Admittedly, I'm biased toward "Ferrit" simply because I think the name is cute, which is partly why I think we should have the public decide on this, precisely because of my bias.
  3. Port issues in ferritreader/ferrit to this project.
  4. Terminate the Ferrit fork as it no longer serves its purpose.

Re (2), I think we should do this in a poll either here in GitHub or on Matrix. GitHub would provide more visibility, but Matrix has a lower barrier to entry (there are people who will not sign up for GitHub).

Are those four pull requests/issues the only things currently separating Ferrit from Libreddit? I would happily support synchronizing the new projects (into this repo as it has most of the contributions currently).

These were just the fixes that have made it into 0.1.0. Those issues have corresponding PRs:

Some of the other substantial fixes that made it into 0.1.0 I neglected to include are:

Since that release, there have been new additions to the code base:

There are a few other fixes that I committed directly into master. Bad form on my part, I know, and I would have to look through the commit history to account for those changes. Most major revisions to code, however, went through the PR process, and were co-reviewed by me and @sigaloid.

@spikecodes
Copy link
Collaborator

spikecodes commented Nov 2, 2022

Thank you for the detailed write-up of Ferrit's distinctive features to be moved into Libreddit. This will serve as a useful checklist in re-streamlining the development of the project. I'll open a discussion for this list where it can be easily referred back to as we synchronize the two projects.

I am totally fine with @sigaloid being added to the Libreddit organization, he seems like a valuable contributor.

New discussion launched here: #608

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

3 participants