bug-librejs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Contribution to LibreJS - Backup and Restore Feature


From: Ian Kelling
Subject: Re: Contribution to LibreJS - Backup and Restore Feature
Date: Tue, 23 Jan 2024 11:56:12 -0500
User-agent: mu4e 1.10.3; emacs 30.0.50

Mónica Gómez <eunbyeol64@naver.com> writes:

> [[PGP Signed Part:Undecided]]
> Dear Bug-librejs email list,
>
> I hope this email finds you well. My name is Mónica Gómez, and I have
> recently added a new feature to LibreJS that I believe could be a
> valuable addition to the project. The feature allows users to create and
> restore backups of their whitelisted and blacklisted sites, enabling
> them to maintain their settings when using a different computer or
> switching web browsers (e.g., from Firefox to IceCat).
>
> I made 10 tests and none of them had any errors, and also tested the
> extension using it with the new changes in my web browser and everything
> worked correctly and no other functionality was affected. The mechanism
> is the following: it creates a JSON file with the values of
> `pref_whitelist` and `pref_blacklist` and lets the user download the
> file in their computer. Upon restoring the same JSON file, the extension
> reads the saved values and updates LibreJS' localstorage accordingly,
> overwriting any previous data. Additionally, the page is updated to
> ensure users can immediately see the changes.
>
> To align with the LibreJS development process, I referred to the
> official manual available on gnu.org for the "Building" and "Releasing a
> new version" sections. I have already made and signed the
> commit. However, I am currently facing challenges in pushing the changes
> to Savannah or making a pull request, as I have never used such website
> and I understand it works differently from other git hosting platforms
> like GitHub or Codeberg.
>
> I am enthusiastic about contributing to the project, and I would greatly
> appreciate your guidance on the Savannah process and the rest of the
> packaging and release steps. If you find my contribution valuable,
> please let me know, and I would be happy to proceed as needed.
>

This sounds great. Thank you. You don't need to package or release
anything. As far as I know, the #1 preferred way to send your code is
via email to this list, a guide on that is here:
https://git-send-email.io/.

If you run into problems, then try hosting a git repo somewhere and
letting us know the url & branch. In the past people have used
https://pagure.io/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]