PBS Challenges - adopt a different organizational structure

[ilessing]

adopt a School=GH org, Classroom=Gitrepo, Desk=Folder organizational scheme

I suggest we have just one Git Repo and in that repo each person has their own folder where they do their coding.

That way we can all see each others code but know not to step on another person's work.

I think we can rely on etiquette rather than Github administration to keep folks working on their own code and not others'

If someone mis-behaves we just kick them out of the organization.

Having just one repository cuts down on what I call "repo sprawl" which can get confusing and leads to spending a lot of time managing Git repos rather than working on challenges.

I'd love to hear from others in this PBS learning about your ideas about how to organize ourselves.

• @podfeet
• @benjaminrose
• @macLurker

review proposed text at: https://github.com/pbs-challenges/.github/blob/organize-in-1folder/README.md

[benjaminrose]

I was thinking that one repo per project was likely going to be a lot. One benefit of the many repos that this loses is that you worked on project X next to other people's project X. We could do one repo, then a folder per project, then a sub-folder per participant.

Also, if we are having a code of conduct and policies on removing bad actors, it is best to have that written down rather than implicit.

[ilessing]

To Ben's suggestion...

a folder per project, then a sub-folder per participant

That could work too.

But I'd kind of like the idea of having a top level folder for each learner and then within that folder the learner can have complete freedom to do at they like. And no one else needs to setup/maintain a project folder each time an episode comes out with each learners' folder inside it. Learners can join whenever they like and no admin needs to keep track.

Here is a screenshot of the repo folder structure I'm suggesting....

[podfeet]

I'm a bit worried that people (probably mistakenly) will write over each other's stuff. Let's use today's HOT MESS I created as an example...

It's not hard for me to create a repo for each person I invite (and I have to invite them so that keeps out the bots and mean people hopefully).

What I've created already (one repo for each of us PLUS one top-level repo called .github) and then within that we can structure the folders as we please. Makes sense to have a suggested naming convention but I wouldn't be a drill sargent about it.

Other than me not having to create a repo per person (which doesn't sound like a heavy lift yet), what's the advantage of one giant repo with folders for everyone?

[ilessing]

advantages of one repo:

• If I want to look at the work of another learner I don't have to go to Github and clone their repo.
• If I want to look at the Latest work of another learner a simple git pull will get it from Github and I can just open their directory.
• It get's learners used to working cooperatively with others on one repo. You'll get practice with other people's code showing up on your machine when you git pull

I'm not worried that someone else will write over my stuff at all.

1. this whole thing is about learning so why would I be messing with your code? motive = NULL
2. if someone were to change my code it is all in git version control so I could revert their changes.