Develop DCIG process

[micheldumontier]

We must describe the process by which the DCIG will identify and track tasks, milestones and deliverables, and the people to do it.

[micheldumontier]

I suggest we use GitHub to track tasks, milestones and deliverables. We can create issues to assign tasks to specific participants. Discussions should be captured in the context of these issues. Issues can refer to other issues using '#' (auto-suggestions arise). Updates on the status of tasks/milestones/deliverables can be managed at GitHub.

We should use Google Docs to develop documentation. It enables us to collaboratively edit documents, without worrying about conflicts (version histories are maintained automatically). Relevant documents should be linked from the GitHub issue. Final documents can be archived in the repository, and linked to from the GitHub README.md file.

We should use a mailing list to communicate more widely to other participants. A mailing list has already been setup - [email protected]

[iherman]

On 17 Apr 2014, at 23:35 , Michel Dumontier [email protected] wrote:

I suggest we use GitHub to track tasks, milestones and deliverables. We can create issues to assign tasks to specific participants. Discussions should be captured in the context of these issues. Issues can refer to other issues using '#' (auto-suggestions arise). Updates on the status of tasks/milestones/deliverables can be managed at GitHub.

We should use Google Docs to develop documentation. It enables us to collaboratively edit documents, without worrying about conflicts (version histories are maintained automatically). Relevant documents should be linked from the GitHub issue. Final documents can be archived in the repository, and linked to from the GitHub README.md file.

Because we already have github, I wonder whether using github and maybe even using some simple text format would not be simpler. I frequently have problems using google doc, let alone the fact that one might want to do some work while off line... Github takes care of versioning after all.

Just a thought...

Ivan

We should use a mailing list to communicate more widely to other participants. A mailing list has already been setup - [email protected]

—
Reply to this email directly or view it on GitHub.

---

Ivan Herman
Bankrashof 108
1183NW Amstelveen
The Netherlands
GPG: 0x343F1A3D
http://www.ivan-herman.net

[stefanproell]

Dear all,

I also agree with Ivan to use the github powered wiki pages for internal
documentation purposes and maybe even for external documents. It should
be possible to export the documents into different formats if needed.
Obviously we can attach any other document files if needed as well. The
wiki itself comes with versioning and it can be cloned to your local
machine and thus be edited offline:
https://github.com/numenta/nupic/wiki/Editing-Wiki-Offline

In my experience Google doc causes an increasing amount of problems with
an increasing number of authors :-) I know its at first convenient, but
permissions and people moving around documents can be tricky.
Just my two cents...

Cheers,
Happy Easter everyone

Stefan

On 2014-04-18 05:15, Ivan Herman wrote:

On 17 Apr 2014, at 23:35 , Michel Dumontier [email protected]
wrote:

I suggest we use GitHub to track tasks, milestones and deliverables.
We can create issues to assign tasks to specific participants.
Discussions should be captured in the context of these issues. Issues
can refer to other issues using '#' (auto-suggestions arise). Updates
on the status of tasks/milestones/deliverables can be managed at GitHub.

We should use Google Docs to develop documentation. It enables us to
collaboratively edit documents, without worrying about conflicts
(version histories are maintained automatically). Relevant documents
should be linked from the GitHub issue. Final documents can be
archived in the repository, and linked to from the GitHub README.md file.

Because we already have github, I wonder whether using github and
maybe even using some simple text format would not be simpler. I
frequently have problems using google doc, let alone the fact that one
might want to do some work while off line... Github takes care of
versioning after all.

Just a thought...

Ivan

We should use a mailing list to communicate more widely to other
participants. A mailing list has already been setup -
[email protected]

—
Reply to this email directly or view it on GitHub.

---

Ivan Herman
Bankrashof 108
1183NW Amstelveen
The Netherlands
GPG: 0x343F1A3D
http://www.ivan-herman.net

—
Reply to this email directly or view it on GitHub
#2 (comment).

[micheldumontier]

I've never had any problem with google docs and have been using it consistently for the past 3 years. My concern with wiki editing is that it is laborious to format and poses problems for concurrent editing (you will have to resolve conflicts if people edit the same sentences). With Google Drive, you can edit the documents offline.
I think it makes sense to edit in google docs until there is a sufficiently stable version, at which point it may make sense to put these documents in GitHub. But there is no compelling reason that I can see to use wiki editing.