search

agrisemantics / gacs-qip

GACS Quality Improvement Project (2017) data and utilities
1 stars 3 forks source link

suggest migrating this to the GACS organizational repo #1

Open brandonnodnarb opened 5 years ago

brandonnodnarb commented 5 years ago

I think simply changing ownership will do this rather seamlessly

tombaker commented 5 years ago

Do you mean the organization account? The purpose of the gacs-qip repo is as a backend for the GACS guidelines.

On Fri, Aug 23, 2019 at 1:12 PM brandon notifications@github.com wrote:

I think simply changing ownership will do this rather seamlessly

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/agrisemantics/gacs-qip/issues/1?email_source=notifications&email_token=AAIOBJXCRVQYRO3CLQ6Y4IDQF7A3TA5CNFSM4IO6QRWKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHAP2HQ, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIOBJV5CIE3RNI5M4OJ7WTQF7A3TANCNFSM4IO6QRWA .

brandonnodnarb commented 5 years ago

yes, sorry. I meant move this repo to the GACS Organizational account.

However, i would split the content. Move the website related stuff (mostly .md files) to the agrisemantics.org/website repo and put the actual qip content in a repo with the same name under the GASC org.

Does that make sense?

tombaker commented 5 years ago

I think it makes sense to archive the QIP project materials on a (private) archival repo somewhere, along with notes and presentations related to the old GACS WG.

Then there could be a dedicated repo just for the guidelines:

- 2017-11-27  11:06        833  README.md
- 2017-11-27  11:03        459  deploy.sh
- 2019-08-06  11:22        529  mkdocs.yml
d 2019-08-06  11:20        416  docs

If you did that, you could take the opportunity change the name of the repo to, say, gacs-guidelines.