[SOLVED] migrating wiki to evilsocket repo

[themighty1]

@gustavo-iniguez-goya , what kind of access do you have to evilsocket's repo?
Can you enable Wiki there so we could move wiki files to that repo?

[gustavo-iniguez-goya]

only commit access, I can't configure the repo to enable these things.

[themighty1]

Would it be possible for you to ask evilsocket to make you a collaborator so that you could create and edit wiki?
Or maybe better still, we could have a /doc directory with the layout similar to what wiki has now. This will allow people to make PRs to make changes to the docs.

[gustavo-iniguez-goya]

I emailed him a few weeks ago regarding this and another things, but I have no answer for now. I'll email him again.

[themighty1]

Thanks.

[jonau01]

I'm not so sure that migrating to evilsocket repo is such a good idea when you don't have 100% control of the repo.

I thinks it's much safer to keep the whole thing as it is : a fork.

Have a good holiday.

[themighty1]

@jonau01, safer? do you mean as in "safe from the possibility of evilsocket suddenly deciding to shut down his repo"?

[jonau01]

Yes it is.

[gustavo-iniguez-goya]

All options are fine to me. But certainly, opening the possiblity to collaborate would improve the documentation a lot.

By the way, I also asked him to use the opensnitch repo: https://github.com/opensnitch

Mainly because I wanted to move the GUI to its own repository. Now if you want to tag a new release, and release only a new version of the GUI is a mess. And also I'd like to open a new repository with the cli tool, and maybe other tools that may appear (a web UI, etc..).

[themighty1]

There is a solution how to have the wiki in a doc/ folder (to be able to accept PRs for it) and sync any changes to doc/ to the WIki section.
https://stackoverflow.com/questions/10642928/how-to-pull-request-a-wiki-page-on-github
2nd answer from devonfw
I plan to test it out and see how well it works.

[themighty1]

I tested it and found it to work satisfactorily.
We still need the wiki section to be enabled on the repo.

[gustavo-iniguez-goya]

@themighty1 can you post the git commands you used? for future reference (I guess that these are the commands https://github.com/devonfw/devon4j/blob/develop/.travis.yml#L32)

In the meantime we can keep improving the wiki in this repo, and later move it to the original one.

[themighty1]

The main idea was that we git commit the current wiki into the repo under e.g. wiki/
And from then on whenever we want to make changes to the wiki, we make a PR for those changes.
This means, we should avoid editing the wiki directly on github. (or else there may be merge conflicts).
Does this sound ok for you?
If it is ok, I can make a github Action workflow for this repo.

[gustavo-iniguez-goya]

yep, sounds ok.

[themighty1]

@gustavo-iniguez-goya ,against which branch should I make a PR for the wiki?
Also I'd like to know what is the purpose of main/master branches of your repo. And why are they behind/ahead of evilsockets repo?

[gustavo-iniguez-goya]

I cherry-picked a couple of commits some time ago, so now the history diverges... -_- that's why github thinks that they're behing evilsocket's branch.

I've maintained them updated because some AUR packages still points here, but after the 1.3.5 release I'll probably delete them.

Should I create a new branch only for the wiki, in order to update only the wiki ?

[themighty1]

yes, a new branch would be nice.

[gustavo-iniguez-goya]

@themighty1 https://github.com/gustavo-iniguez-goya/opensnitch/tree/wiki

[themighty1]

PR made #127

[gustavo-iniguez-goya]

merged

[themighty1]

@gustavo-iniguez-goya , is it ok if I make a new PR to move the wiki into evilsocket's repo tree and a github action to update wiki via PRs ?

[gustavo-iniguez-goya]

yes please!

[themighty1]

@gustavo-iniguez-goya I was gonna make a PR, but I don't see the Wiki section in evilsocket's repo. Please enable it and create at least one blank Home page (needed to activate the wiki)

[gustavo-iniguez-goya]

oops, sorry! done.