Skip to content

Tasks for 01 Creating a repository#12

Merged
feiphoon merged 9 commits intomasterfrom
fei-first-task
Feb 22, 2019
Merged

Tasks for 01 Creating a repository#12
feiphoon merged 9 commits intomasterfrom
fei-first-task

Conversation

@feiphoon
Copy link
Copy Markdown
Owner

Tasks with images! Don't know how tightly I can keep to this format yet, but here's a shot at it :D

Comment thread workshop/01-creating-a-repository/README.md Outdated
Comment thread workshop/01-creating-a-repository/README.md Outdated
Co-Authored-By: feiphoon <1391178+feiphoon@users.noreply.github.com>
@alesssia
Copy link
Copy Markdown
Collaborator

Sorry, don't understand what is this. Is it a duplicated of the website? Are we abandoing the idea of a website? I believe the screenshot were to be integrated in the gh-pages markdown to be shown as webpage rather than README. I am a bit lost 😅

@feiphoon
Copy link
Copy Markdown
Owner Author

@alesssia a quick recap of this morning's pull requests:

  • Yesterday I thought we needed to take advantage of our initial drafts for each part, to regroup and make sure our materials were all going in the same direction. I was nervous of time.

  • I really needed the task list we had to be structured into high-level sections we could easily make references to it during the workshop. So I did this last night, here: Improve the task list in README & propose sections #9.

  • I merged the above in (and yours as well - now I know that was not good for you :() with the intention of reconciling the sections task list with your material. I would have moved instructions around into different files. Instead of editing on top of your work, I actually wanted to open a separate pull request into it, alongside the cleaned-up task list, as a suggestion. I tried to do this this morning, but you had removed the material, so I submitted this anyway so that we could finally have some visuals, and so that Ester could start refining her collection of screenshots.

We are short of time, and the most important thing is to get the content right - we need to prioritise ease of review. Our content is already in Markdown, so if we have time after finalising the content, conversion to Jekyll should be no issue, am I right?


![Choose a license](images/license.png)

4. Now your teammate and new repository owner should add the rest of your groups as collaborators on the repository. Go to the repository settings and add them by Github username.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remember that they have to accept the email ✉️

@feiphoon feiphoon changed the title Tasks for Creating a repository Tasks for 01 Creating a repository Feb 21, 2019
@feiphoon
Copy link
Copy Markdown
Owner Author

@alesssia by the way!! Remember we'll have a post-session recap/reference (DOCS.md for now). I'll base it on what I showed some time ago, but that text needs updating/trimming/improvement. @estramcar and I will help out with filling out the rest of these tasks, with the aim of reviewing all as a whole very soon for consistency/style/brevity. Any extra points of interest won't be wasted, we will move them to the reference.

@Ester-Ramos Ester-Ramos self-requested a review February 21, 2019 23:13
@feiphoon feiphoon self-assigned this Feb 22, 2019
@alesssia
Copy link
Copy Markdown
Collaborator

Ok, so it still make sense for me to complete task 5 :)
Will do tomorrow, today is impossible, sorry.

@feiphoon feiphoon merged commit c6871bd into master Feb 22, 2019
@feiphoon feiphoon deleted the fei-first-task branch February 22, 2019 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants