Setup a Skype call with @substack and @dominictarr

[rosekaron]

ping @substack @dominictarr

[mikaelkaron]

Adding some context.

• First read the ol manifesto to get a general idea about the overall goal of the initiative.
• Then read the git4ol docs but mostly the git4ol guide.

What we'd like some help with (feel free to add your own):

• Input on the git4ol specs focusing on compatibility with nodeschool format (is there one?)
• Develop tool to export nodeschool content to git4ol
• Development on git4ol-* projects
• PR for [open-learning}(../..) in whatever form - blog, speaking, interpretive dance.

I'll try to get a hold of you (again) on twitter.

[dominictarr]

hey, so I read most of this material.

I see you have had the content-addressability revelation!

Though if you want to have true public verifications then you'll need to sign the commits
(the name on a git commit is just a text field so you can make a commit with anyone's name on it)

Did you just write it up as git to explain how it works? This would be much easier to use if you made another tool that just wrapped git. With commands like list lessons create lesson which would manage git refs under the hood.

Im a little worried about this: https://github.com/open-learning/git4ol/blob/master/activities.md#assets
how you are defining the steps within the refs - as a tree of refs. I worry you are overusing refs here.
And it seems very strange to use git and then create another version manager (with those version numbers) on top of it. The problem here is that refs are just mutable pointers, and so while you can verify the git trees, you can't verify the refs... Would it be possible to put the steps into a file, and then check that in? then you can version the lessons with git.

[mikaelkaron]

Broke out new issue regarding git refs in open-learning/gi4ol#2

[mikaelkaron]

hey, so I read most of this material.

I see you have had the content-addressability revelation!

Though if you want to have true public verifications then you'll need to sign the commits
(the name on a git commit is just a text field so you can make a commit with anyone's name on it)

Sure thing. I wanted to leave signed commits optional but yeah, I should write it up somewhere.

Did you just write it up as git to explain how it works? This would be much easier to use if you made another tool that just wrapped git. With commands like list lessons create lesson which would manage git refs under the hood.

I was thinking to add that both as git extensions so you can do git ol lesson list and similar, and also as a CLI that just wrapped the git extension.

Im a little worried about this: https://github.com/open-learning/git4ol/blob/master/activities.md#assets
how you are defining the steps within the refs - as a tree of refs. I worry you are overusing refs here.
And it seems very strange to use git and then create another version manager (with those version numbers) on top of it. The problem here is that refs are just mutable pointers, and so while you can verify the git trees, you can't verify the refs... Would it be possible to put the steps into a file, and then check that in? then you can version the lessons with git.

Started new issue open-learning/git4ol#2 for that.