Our goals out of paper, into Gitlab issues


#1

Hi Goshers!

We are starting to make a move on the Gitlab issues that greg so nicely created to keep track of developments on the actions we came up with on the last day of GOSH 2018.

At the moment I’m trying to make sure that every issue has a person assigned to them and to do that, people need to create a gitlab account.

I’ll ping some people here, who I couldn’t find a Gitlab account, but are marked as point of contact for actions (although I see some of you were already sent invitations! please make sure they didn’t fall into your spam folders):

@shannond, @Moritz or @moritz_lablab, @pixel,


#2

Also, it seems I can only add 10 @ handles per post, so here is some more people:

@mariafrangos, @sam , @andy, @saibhaskar, @liuliying, @Pollock


#3

And here some more (last ones) @Shan, @francois , @marymaggic, @agnieszka, @pia , @mennu20,
Does anyone know the handles for these peeps: Andy D, Kevin, Yao, Anne-Pia.


#4

Last but not least, we can’t find who was assigned to these actions:

If you are it, send a reply here, or if you know who it is, let them know that we are looking for them!


#5

Nice, let’s get moving! My GitLab user is @jarancio.


#6

Mine is @alexander.kutschera


#7

Ok, so now the only issues missing “owners” are the ones where people are still not in GitLab.
If you are tagged in the messages about, please drop me a line here or via DM, so we can get you up and running!
:slight_smile:


#8

I have joined the gitlab group now. Thanks for the notice!


#9

seems i got automatically added… thanks.

but i have to say, i have no experience sofar with gitlab. a little instructions for newbies would help me a lot.
i was kinda overwhelmed with all the stuff there and never openend it again.

thanks for all your effort!
marc


#10

Hi Marc,
that is a good point. Here is a brief explanation on the whole thing for people watching this space (maybe we can also make a more extensive explanation as a separate thread).

If you don’t know what GIT or a Version control system is, read this, otherwise skip two paragraphs down:
We are using a version control system (here is a explanation on version control systems) to keep track of the tasks raised on the last day of GOSH 2018. More specifically, we are using Git, a system developed for the Linux Kernel project to enable parallel software development. Anyway, the system was widely adopted by software developers and recently by other people keeping track of hardware, design and other projects.

Gitlab, a company offering an open source system for development around git is where we are hosting these projects. Another company you might have heard of (it was recently bought by Microsoft) is GitHub.

In Gitlab, we have created a “Gosh-roadmap” project. Each of the tasks people suggested in Shenzhen were uploaded as “Issues” inside this project, basically because in this system we can assign people to issues and have a nice messaging system where we can link other people/issues and what not (if I’m not mistaken the idea is to also hook the issues with threads in the forum, so everything that is written on Gitlab gets posted directly on a thread in the forum).

To see all the Issues we created, go here. If you would like to see them as parallel boards (with a different organization, but similar content), go here.

In this two views you can search and filter things, so you can find right away things. For instance these are all issues assigned to me.

once you find the issues assigned to you, you can click on it and open the messaging system. In this example, I left a note saying where the project is being developed. I’ll return to it once I have more developments to share. Ideally people would write a little note with developments on regular basis, just to keep others informed and so that we can also make suggestions/offer help, etc.

If people are thinking about sharing more things then messages, let’s say software code, or large documents/texts/images, then I would suggest opening a repository (either Gitlab, or GitHub, whatever people feel more comfortable with, as it is super simple to migrate things from one to the other), and share the link to the repo on the messaging system of their issue. If you never opened a repository and would like to learn how use it, I recommend taking a look here or having a search online for “learning git” or “learning github”. If there are still questions, send us a message here, and we can help out!

sorry, this was a bit longer then I expected. But I hope it is clear enough!


#11

One more interesting issue/idea:

As people start to create their repositories to document things, I think it would be pretty useful if each repository had a file stating what is the code of conduct and another file stating what is the license the project is distributed in. Would it make sense to have a “GOSH template” which people could alter as they needed?


#12

I’m pretty sure I us added. but anyway, my git is @flor_esta


#13

Hi Marina,

thanks! @gbathree and I were debating who flor_Esta was on gitlab… :stuck_out_tongue: