Version 1.0.0 proposal #2
Conversation
- We want a single issue tracker for all the projects. - Added a section for preferred data and documentation formats. - Made documentation clearer in multiple places.
* Merge all the docs into a single file. * Move some parts to other documents. * Large number of changes to existing parts.
We might still use JSON in some API, so it wouldn't be appropriate to release a document stating that we will use XML Schema only. The list partner developers is not complete it would be better to remove it for now. Maybe it will be brought back later.
| GitHub. **We will require developers to review and accept documentation | ||
| often** throughout the project. We believe that these tools will help them | ||
| with this task. | ||
|
|
There was a problem hiding this comment.
I'd say "All developers are familiar with Git" is a bit too far fetched, there are other version control systems, and some people have been using them before Git existed and may even find the transition uncomfortable or not have the time to learn new "tricks"
There was a problem hiding this comment.
I agree, I'll try to rephrase that in the new version.
Side note: Do you think that it would be difficult for non-Git developers to import our history to their own favorite version control system? Or, if not entire history, then at least the versions they are about to review?
There was a problem hiding this comment.
Actually, what I meant is that it was a bit to much to expect that. But,
I agree that some decisions have to be taken when you launch a project,
so it should be up to the developer to decide if they prefer to learn
Git or to find a way to interface her favourite tool with Git.
No description provided.