Skip to content

Conversation

@jonathondilworth
Copy link
Contributor

Two suggestions in terms of materials that the educational working group can provide. These suggestions serve two purposes:

  1. To help organise project collaboration (and tracking) via Git & GitHub (aimed at non-technical or not as technical individuals).
  2. To begin indexing our library of resources and make it easy to navigate and search through for different members.

@jonathondilworth
Copy link
Contributor Author

(Wasn't too sure where to drop this comment)

Thanks for the feedback from dev-general regarding Git & GitHub procedures — anyone can go and view our discussion in that channel, it’s very helpful and doesn’t go unnoticed — I appreciate it.

I was asking in dev-general to try and get a feeling for how you guys are collaborating on features that require input from more than just one person — I think keeping it as basic as possible is the best idea.

With that said, I found a blog post that pretty much summarises how I think/thought a procedure should be established (if one was to be established): https://www.tomasbeuzen.com/post/git-fork-branch-pull/

I am still trying to figure out how difficult this would be for people who haven’t really used SCM systems before though; if I remember correctly, this was all fairly confusing for me when I (originally had to use SVN, but) started using Git (a while ago).

But of course, I am open to all kinds of suggestions :) I think Devs are 100% capable to manage themselves, I was inquiring as it would be helpful for everyone to understand how Git & GitHub should be used moving forwards (not just developers) — it’s something being discussed within the administration WG.

Again, thank you for your helpful input :)

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.

1 participant