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

soft fork arc-theme for future maintenance #840

Open
fossfreedom opened this issue Oct 12, 2017 · 10 comments
Open

soft fork arc-theme for future maintenance #840

fossfreedom opened this issue Oct 12, 2017 · 10 comments

Comments

@fossfreedom
Copy link

fossfreedom commented Oct 12, 2017

**EDIT:

Soft fork of arc-theme is now available here:**


Hi @horst3180 ,

this is a reach-out as to the status of this project. I understand that you have been busy on other projects and maybe don't have the time to push through with current and future maintenance. Is this a correct statement? Apologies if otherwise.

Thus, would you support a fellow enthusiast to collaborate and drive forward with this project?

To everyone who has starred or is watching the project, are there anyone among you who is willing to be that collaborator?

Possibly under the guise of a soft-fork - i.e. make changes and feedback through PR's to here with changes.

@ItamarShDev
Copy link

though i am not yet fully understand the mechanism of theming. i am willing to learn more and contribute when i have time

@NicoHood
Copy link

NicoHood commented Nov 5, 2017

@fossfreedom Is it correct, that you are the debian/ubuntu maintainer of the Arc-Theme?

I've tried to email horst about a week ago. He was really collaborative when he added the GPG Signatures. If he does not answer, we possibly need to go the way of a soft-fork.

My suggestion is, that we as OS Maintainers (I am packaging arc-theme for Arch Linux) continue the project as a fork, test new PRs and merge them if it makes sense to us. Once someone of the community contributes frequently to the project we could consider to make him a maintainer too. This way we can at least package those small fixes that appear in the recent PRs without writing tons of manual patches.

What do you think?

@fossfreedom
Copy link
Author

@NicoHood correct ... Yes Debian maintainer.

Happy to support your suggestion.

@NicoHood
Copy link

NicoHood commented Nov 5, 2017

@fossfreedom Nice! I've created a fork here: https://github.com/NicoHood/arc-theme
You should get an invitation link as collaborator via email.

To track changes from the current master, I've also tagged a new release:
https://github.com/NicoHood/arc-theme/releases/tag/20171105

I will look through the issues and PRs in the next days and comment there. We should give horst one more week to respond via mail. If he does we can merge back the changes without problems.

Edit: Here is some more information from Horst about how to do edits on this theme:
https://github.com/horst3180/arc-theme/blob/master/HACKING.md

@fossfreedom
Copy link
Author

+1

@ghost
Copy link

ghost commented Nov 18, 2017

I also would like to learn about theming and contribute in this project. Feel free to contact me.

@NicoHood
Copy link

@s-kaczmarek Sure. Feel free to review existing PRs and (re)open them on the new fork project.

@NicoHood
Copy link

NicoHood commented Jan 8, 2018

@fossfreedom Can you please post the following link t the very top of the first post in bold? This thread can be found by google, so it is easier to navigate. The fork is still not listed on google.
https://github.com/NicoHood/arc-theme

2Shirt added a commit to 2Shirt/WizardKit that referenced this issue Mar 6, 2018
* Avoids (undocumented) gtk3 build-time dependency
* The community package is based on the new soft-fork of the main repo
  * Link for details: horst3180/arc-theme#840
@NicoHood
Copy link

@fossfreedom I am in contact with Github about the outdated upstream repository. They were also unable to contact horst. The only option currently is to detach the fork, so it will look like a normal repository. Do we want to do this or should we keep it as a fork? What do you think?

@fossfreedom
Copy link
Author

@NicoHood hmm - agree with you - if we can we should detach.

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