devstaff-crete/DevStaff-Heraklion

Move from multi-repo to mono-repo for presentations

Closed this issue · 12 comments

gsaslis commented

At the moment, we are creating a new GitHub repo for every new meetup, to hold the content (slides, code, etc.) that the speakers are willing to share.

This is something we decided on very (very) early on. After so many meetups, I think it's time we reconsider.

Here are some pros and cons for the multi-repo approach:

Pros:

  • i can only star (receive notifications) for the meetups i'm really interested in
  • we don't need to maintain any particular format - each repo can be entirely different
  • we have a separate set of issues per repo, e.g. in the case

Cons:

  • we need to open a new repo every time
  • it's a hassle to have to star every new repo (to receive updates)
  • not so easy to have "everything in one place"

Please share your thoughts on the topic below, so we can agree on a course of action before opening a PR, etc.

sonaht commented

e.g in the case ???

Not sure our meetup repos have so many stars or even people got so bothered to star them ;-)

I am not really particular, I have been creating the repos since day one, so this is not a major issue for me.

As far as having everything into place, it is only a small script that loops through the repos and pulls the latest.

I would say, do not change if it ain't broken...

mzampetakis commented

For me the main issue is that we have to create a new repo for each meetup which also leads to many repos in Devstaff. Also all these repos are not active (except when meetup occurs where presentations are added).
So for me I would recommend using a single repo for all the meetups!

  • 👍2
gsaslis commented

@sonaht looking at the pros vs. cons above and thinking about discoverability again and the UX for how someone could find all material from all the meetups, I think it is a little broken. ;)

would you be ok with merging a PR on the main repo, if I went to the trouble of gathering all info from previous meetups?

I'd hate to do that and then have someone object after all the work is done... ;) which is why i raised the issue first as well... :)

sonaht commented

Please go ahead by all means. If it helps I support this 100%. Let me know if I can help with something more !!!

HoodElliot commented

As @gsaslis and @mzampetakis said I think the main issue with having many repos instead of gathering all in one is that it gets harder to find a new presentation, having all in one repo we solve that by getting a notification when something new has merged and another pro is that new members can find easier the presentations (as the may only check the main DevStaff-Heraklion, as I did 😄 ).

sonaht commented

Ok as per last night's org team meetup and final decision, I will be moving the multi repo structure of all meetups done up to now into a single repository, probably named meetups, and having separate directories for every meetup done, adding in there all the files that previously existed in isolated repos

  • 👍1
mzampetakis commented

After this, we also have to update the main readme file of the DevStaff-Heraklion repo and the static website as well with the new links.

mzampetakis commented

What about the old repos? Should we delete them? Is there any other possible solution like archiving?

sonaht commented
daknob commented
sonaht commented
sonaht commented

closing this as done I think