Thanks for joining in and voicing your thoughts :) I didn't reply yet
because there's a lot to think about and I'm trying to figure out how to
put some ideas together into coherent proposals. A lot of unknowns to
think about.
Yes, of course.
> I figured that I have not the rights required to edit the wiki of the
> wiki repository.
I gave you more permissions, does it work now?
Thanks, it works.
> To be honest, I think github wiki is inconvenient. Why not
> rely on markdown files inside git instead, so that we can rely on
> pull-requests and better review changes?
We didn't think about the technology at all, we just started jotting
down ideas as fast as we could... The markdown approach is a good idea
to try.
But would it be slow to edit things?
I think that it is the same. Editing a markdown file inside the github repo is
similar to editing the wiki with the exception that there is no buttons to
"help" with markdown. There is a way to edit files in the git repository
directly from the browser.
The wiki is meant more for early stage planning so the ideas are not super coherent.
The thing is that having several tools will hinder the traceability of our work. The current
situation is that there is one git repository that is empty and another git repository for the
wiki which means when we will move to the git repository, the history will be lost. That is
why I am asking to only use the main git repository in order to not loose track of all the
guess work.
Would pull requests be better for something that is a bit more polished or has been
thought more about?
What I was suggesting is that at least with the main repository, one can do a pull-request.
Whereas with the wiki it is not possible at all. I believe pull-requests will be required at some
point.
If we agree, I will push the wiki inside the main repository and add my frontend.md thing.