-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decide which repos we're proud of and pin them #151
Comments
@dxw/technology-team we'd like to show off some of our code in pins on our GitHub profile; do you have any suggestions? |
@Floppy An issue I see is that most of the repos I've worked on belong to another organisation and have been worked on since by other suppliers. The older our involvement becomes the less accurate and honest it is as a reflection of our work.
When our involvement ends could we take dxw forks of any public projects at the point our involvment ceased and set them as archived repos, solely for this purpose? We did do this with Teaching Vacancies https://github.com/dxw/teacher-vacancy-service. For active projects like RODA, I don't think we can pin it since it belongs to an external organisation right? Is a dxw fork made today, respite it being active, better than no pin? |
Good question @tahb! Good point on the other-org thing; your plan seems like it could work, but I don't know if we want to do that. Hmm. |
I'd suggest we pin things that belong to us, not our clients. Our templates are a good example, as well as any tools we're particularly proud of. |
https://github.com/dxw/mail-notify is a good example. |
@Floppy Are we able to close this? I notice we have a few pinned repos, but we could add some more... |
We never really came to any good conclusions... not sure if it's worth keeping open or not. It would be nice to have some more, though. |
See RFC 29
The text was updated successfully, but these errors were encountered: