This repository has been archived by the owner on Mar 22, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
[doc] describe development environment #36
Comments
erikbgithub
added a commit
that referenced
this issue
May 14, 2013
See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
erikbgithub
added a commit
that referenced
this issue
May 14, 2013
See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
erikbgithub
added a commit
that referenced
this issue
May 15, 2013
See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
Changed the topic to reflect the real problem. It's mostly not about adding more lists with even more information. It's about giving the new user a guided tour through the dev process, that he can start to work more efficiently. |
erikbgithub
added a commit
that referenced
this issue
May 21, 2013
See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
erikbgithub
added a commit
that referenced
this issue
May 22, 2013
See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
erikbgithub
added a commit
that referenced
this issue
May 23, 2013
Following the recent changes in the development environment, adding support for virtualenv, depencies and so on, it was a good time to also rewrite the contributing page. A tutorial was added, which walks through the creation of a development environment and the creation of this task. Reviewers should add themselves to the tutorial section which talks about Acked-bys, to complete the tutorial (there's a TODO for it at the right place) and they might also explain something about their review process. See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
can be reviewed. |
This was referenced May 27, 2013
erikbgithub
added a commit
that referenced
this issue
May 27, 2013
Following the recent changes in the development environment, adding support for virtualenv, depencies and so on, it was a good time to also rewrite the contributing page. A tutorial was added, which walks through the creation of a development environment and the creation of this task. Reviewers should add themselves to the tutorial section which talks about Acked-bys, to complete the tutorial (there's a TODO for it at the right place) and they might also explain something about their review process. See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
"make html" does not work. 👎
|
erikbgithub
added a commit
that referenced
this issue
May 28, 2013
Following the recent changes in the development environment, adding support for virtualenv, depencies and so on, it was a good time to also rewrite the contributing page. A tutorial was added, which walks through the creation of a development environment and the creation of this task. Reviewers should add themselves to the tutorial section which talks about Acked-bys, to complete the tutorial (there's a TODO for it at the right place) and they might also explain something about their review process. See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com>
ACK |
1 similar comment
ACK |
erikbgithub
added a commit
that referenced
this issue
May 28, 2013
Following the recent changes in the development environment, adding support for virtualenv, depencies and so on, it was a good time to also rewrite the contributing page. A tutorial was added, which walks through the creation of a development environment and the creation of this task. Reviewers should add themselves to the tutorial section which talks about Acked-bys, to complete the tutorial (there's a TODO for it at the right place) and they might also explain something about their review process. See Github Issue #36. Signed-off-by: Erik Bernoth <erik.bernoth@gmail.com> Acked-by: Eik Binschek <binschek@dresearch-fe.de> Acked-by: Peter Winkler <winkler@dresearch-fe.de>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
The current contributing.rst is merely a list of dos and don'ts. Neither does anybody want to read that nor does it really tell people how to develop for MONK. I feel that this page should mostly be a guide going step by step through installing the system requirements, creating the development environment, running the test suite and making a little change to MONK. Only in the end should be the rules and details for people who want to dive in more deeply or iif the team needs some arguments for decision making. But those cases are rare.
Solution
Create tutorial with git, virtualenv, test suite and use this issue as example for making a change to MONK.
Notes
the spell checking will be done after @toang is back from her holidays
to close this task you need to build the docs without warnings and errors with
f-docs-devenv
The text was updated successfully, but these errors were encountered: