Reorganize the README
Merge request reports
Activity
Added 1 commit:
- 59c9be63 - Fix links
Added 1 commit:
- f991adeb - Start howto/README.md
@axil I am running into an overlap between information in GDK and in http://docs.gitlab.com/ce/development/rake_tasks.html . My first instinct is to move information from GDK to gitlab-ce/doc/development. But then we will end up with a strange mix of documentation in GDK (for GDK-specific things) and gitlab-ce, and that will make it hard for people to find what they are looking for.
Do you have any thoughts on how to deal with this?
@jacobvosmaer-gitlab hmm, true we don't want to duplicate things either. Since GDK is what we support, what we can do is link to GDK from
gitlab-ce/doc/development.The raketasks are part of GitLab, nothing you can do about it. The documentation should just tell what each task is for (like reference docs) and then GDK is like a tutorial that binds all the info together. At least that's how I see it.
Of course anyone with the expertise is welcome to use their own way of setting up development.
Added 17 commits:
-
f991adeb...3583a2af - 16 commits from branch
master - 80998b60 - Merge branch 'master' of https://gitlab.com/gitlab-org/gitlab-development-kit into reorganize-readme
-
f991adeb...3583a2af - 16 commits from branch
Added 1 commit:
- f90aa789 - Remove obsolete marker line
Thanks @axil !
I decided I am just going to move ahead and not worry too much. Also, I am not going to preserve anchors and create cross links for everything I move. The GDK documentation is constantly evolving anyway.
Added 1 commit:
- 7ccd20b1 - Mention HELP
mentioned in commit f4b0b7d3
