Pin on github #378

Closed
raq929 opened this Issue Nov 9, 2016 · 9 comments

Comments

Projects
None yet
5 participants
@raq929
Contributor

raq929 commented Nov 9, 2016

In requirements:

Pin your repository on GitHub
Make sure it has a description so that employers can see it

per planning meeting for cohort 015

@raq929 raq929 added the enhancement label Nov 9, 2016

@gaand gaand added the question label Nov 12, 2016

@gaand

This comment has been minimized.

gaand commented Nov 12, 2016

@ga-wdi-boston-migrated/core Should this be a requirement for the game-project? I think it makes sense for the rest of the projects, but unless you've done something really interesting with tic-tac-toe, maybe this isn't something to show off? Also, it's the developer's first project.

Thoughts?

@raq929

This comment has been minimized.

Contributor

raq929 commented Nov 14, 2016

So, it might be nice to not add one more requirement to the first project, and as you say, it's often not their most exciting work.
On the other hand, it's nice to have all the requirements be similar; it gets them in the habit of doing it, and they can always unpin it later.
In conclusion,

@gaand

This comment has been minimized.

gaand commented Nov 14, 2016

We talk more until it feels right 🤖

@bengitscode

This comment has been minimized.

Contributor

bengitscode commented Jan 24, 2017

I read the updates to this issue because I was wondering why it hadn't been implemented yet—but Antony's comment makes sense to me. I think it should for every project but this one.

@raq929

This comment has been minimized.

Contributor

raq929 commented Mar 29, 2017

I'm OK with that. We can close this issue if y'all agree.

@gaand

This comment has been minimized.

gaand commented Apr 2, 2017

@payne-chris-r

This comment has been minimized.

Contributor

payne-chris-r commented Apr 2, 2017

I think consistency is good. They can always unpin it. It's probably a good thing for them to get in the habit of pinning whatever they're most proud of at the moment. So I think I vote for having them do it if we ask them to do it later on.

That said, I'm of the opinion that pinning projects should be up to them and not necessarily a requirement, but a suggestion.

@gaand

This comment has been minimized.

gaand commented Apr 3, 2017

@payne-chris-r Is that part of an issue on a different repository?

Also, requiring that developers pin a repository doesn't keep them from unpinning it after the cohort.

@MicFin

This comment has been minimized.

Contributor

MicFin commented Aug 30, 2017

This is a good pattern to have consistent between projects. They can always unpin it after graduation if they do not believe it represents them well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment