make task 1 simpler

[jcolomb]

I love the idea to get a document in markdown for the first task, I like the idea that this document could be expanded later, but I think it is too difficult (and fuzzy, where and how to write that ?) to start from scratch, it is probably a great task, but not as the first one.

We can discuss this, but I would like to move it to a later task, and start with something easier, lasting less than 10 minutes, what about:

• introduce yourself on slack
• introduce yourself in a github issue (to use markdown
• a bit of both: making a issue on github and see it appear on slack (we would need to add github application on slack)

[jcolomb]

another possibility would be a blog post, is there any way for people to add a blog post entry without logging in github ??

[Protohedgehog]

Thanks as always for the feedback after the launch, rather than the 6 months you had beforehand.. ;)

We can design this into a third task, if you like? I think the GitHub issue thing might be a bit difficult, but the intro on Slack would be perfect.

[Protohedgehog]

As for the blog post, @jcolomb, that was the original idea! If you check older versions of this task on GH. Problem atm is that @dannycolin is rebuilding the site atm and I don't know the exact protocol for new posts. It is something we can reintroduce in the future.

[jcolomb]

Sorry for the (very?) late feedback, I plead guilty (again).

tend to think writing an issue with slack integration might be the most fun and easy to access for newcomers. We can even make a issue template to make it super easy.

We could have a dedicated (= different) website for that. Put some thought, and we can probably make it via OSF. Task 3 would be:

• sign in osf with your orcid,
• get to our osf project,
• write a blogpost,

this will create a pull request on github. I Would need to make some test to see whether it works, though.

[Protohedgehog]

Do you want to have a play with the GH-Slack integration? I think you're an admin..

For the blog post, one of the ideas was to combine it with the skills from Module 5, in that you could write it in markdown, and use Git to push it to the site. We can totally re-implement this as a separate task when the new site is up. I think it could be good fun!

We actually don't exist on the OSF yet either, for some reason. Zenodo is the platform of choice atm.

[dannycolin]

@Protohedgehog the procedure to write a blog post on the new website will be similar.

We could have a dedicated (= different) website for that. Put some thought, and we can probably make it via OSF

Isn't OSF as complicated as GitHub?

tend to think writing an issue with slack integration

Keep in mind that we're still thinking about migrating to an other platform. Just saying that to make sure you don't put a lot of work (hours) on that in case we decide to switch to Mattermost or something else. :)

[Protohedgehog]

Figured, @dannycolin! But I just need some specifics like making sure articles are in the right directory.

I suspect the platform migration might be an ongoing issue. There's little consensus coming out of it from the steering committee atm.

[dannycolin]

I suspect the platform migration might be an ongoing issue. There's little consensus coming out of it from the steering committee atm.

A that's sad to hear :(. Sure, there's a learning curve in any migration but I think switching to GitLab is worth it in terms of functionnalities and principles.

[jcolomb]

combine it with the skills from Module 5

Only works for a task after module 5, we want people to take module 1 before any other.

Isn't OSF as complicated as GitHub?

no commit-pull request needed, you just add your file, so I would say it is simpler.

We actually don't exist on the OSF yet either, for some reason. Zenodo is the platform of choice atm.

OSF does not provide what zenodo does, and vice versa.

GH-Slack integration

only works to write in issues and pull requests, not for adding/modifying files.

thinking about migrating

osf-gitlabintegration does not exist, so we could either keep the website on github, or create a dedicated (simpler?) website for that purpose on GitHub. slack-gitlab is possible I would suspect mattermost-gitlab integration exists? On the other hand, we can keep the slack and github tools for this task, even if the mooc developement goes to mattermost

[jcolomb]

If we go the slack+github issue path, I think we should get a specific slack for that, or our #general channel will be spammed by people doing the task who are not interested in the mooc dvt ??

[dannycolin]

osf-gitlabintegration does not exist, so we could either keep the website on github, or create a dedicated (simpler?) website for that purpose on GitHub.

I think a dedicated website would be a better solution. It would avoid unnecessary PRs to the production repository.

I would suspect mattermost-gitlab integration exists?

Yes.

On the other hand, we can keep the slack and github tools for this task, even if the mooc developement goes to mattermost If we go the slack+github issue path, I think we should get a specific slack for that, or our #general channel will be spammed

Good idea! I'm also in favor to create a separate slack instance and/or channel juste for that.