Its too hard to contribute to the Iceberg wiki

Ok - my love affair with Github ends at the wiki - what a load of $%$%^$%… there is no sane and easy way to fork a wiki, make some changes and then submit a PR. (how the hell did they get into that state?).

Can we agree to scrap the wiki Iceberg wiki and just have a longer readme.md (with sections of the current wiki?). Or if someone can explain easy instructions for both me (as a contributor) and the admins of iceberg then I’m all ears….

If not - I’ll submit a PR with my subtle changes to the readme.

Tim

hi,

> On 29 Jun 2018, at 16:25, Tim Mackinnon <[hidden email]> wrote:
>
> Ok - my love affair with Github ends at the wiki - what a load of $%$%^$%… there is no sane and easy way to fork a wiki, make some changes and then submit a PR. (how the hell did they get into that state?).

yes, github wiki is crap.
specially the absent possibility of make fork and PRs as other parst of the github project.

>
> Can we agree to scrap the wiki Iceberg wiki and just have a longer readme.md (with sections of the current wiki?). Or if someone can explain easy instructions for both me (as a contributor) and the admins of iceberg then I’m all ears….

I will have a longer README.md with pointer to others .md files.

cheers!
Esteban

>
> If not - I’ll submit a PR with my subtle changes to the readme.
>
> Tim

--

yes, but is annoying. 

Another solution is to clone the wiki, it offers its github link and then
make a new repo for the wiki alone and upload the files which are regular md
files (github markdown). The good news is that you wont be losing any of the
conveniences because github offers a markdown editor with live previews ,
the only you will be losing will be the automatic table of contents but that
can be hosted as a seperate md file.

I have done this for creating a Wiki for Pharo you can find the example here

https://github.com/kilon/PharoWiki/blob/master/README.md

This can also be implemented as a branch to a project, usually the branch is
named "gh-pages" but I dont think there is a restriction you can host the
wiki then as a website which will be available using a link very similar to

<username>.github.io

or orgname if its a organisation.

If it's done this way you and everyone else will enjoy all the privileges of
a regular github repo.

Because is markdown it's also compatible with gitlab and gitbooks , gitbook
can take a wiki and easily turn it to a book with export to pdf etc.

Is just a matter of setup, the default way of github wikis is not to give
you access to such advanced features and instead prioritize ease of use. If
you want full nuclear power then a regular github repo is the way to go.

Of course "advanced mode" will give you also easy access to using Pillar or
whatever you want to use.

Frankly PR seems a bit overkill for a wiki, becoming a contributor to the
wiki repo would make your life a lot easier with direct access to editing
the md files online without the whole trouble of git pull, push, pull
requests etc.

But of course all that is up to Iceberg devs

I started Pharo wiki as an experiment and it worked much better than I
expected and of course far better than a regular Github wiki. Ease,
straightforward and super flexible.

I am more a Gitlab user nowdays but its the same workflow there too.

Tim Mackinnon wrote
Quoted from:
http://forum.world.st/Its-too-hard-to-contribute-to-the-Iceberg-wiki-tp5080884.html




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html