-
Notifications
You must be signed in to change notification settings - Fork 37
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
Website - Collaborators and Funding Sources #42
Conversation
The collaborators and funding sources look good to me. I was under the NCSU's GFINE fellowship during my first year while work with Zapdos, if you think we should include that as a funding source. |
Looks awesome!
…On Tue, Oct 22, 2019 at 11:02 AM csdechant ***@***.***> wrote:
The collaborators and funding sources look good to me. I was under the
NCSU's GFINE fellowship during my first year while work with Zapdos, if you
think we should include that as a funding source.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42?email_source=notifications&email_token=ACOGA4CGLNIV256FUN56LDLQP452LA5CNFSM4JDTANJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6U47Q#issuecomment-545083006>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOGA4EY57FVLXRKXD2HO2TQP452LANCNFSM4JDTANJA>
.
|
@csdechant Isn't the GFINE internal department funding? Since NCSU is the principal developer, I figured that internal support would be assumed, so I didn't really go into it. But I can add it if you'd like me to. |
I am not sure if it counts as purely internal department funding, since it is a grant from the NRC to the department and the department picks the students (I know I had to include it under the "Acknowledgement" section for last year GEC poster, which is why I brought it up). I would include it with the mention of the NRC to be on the safe side, but I will double check will Mario or Dr Murty to see if it counts as internal funding. |
Ah, ok. How did you include it in your GEC 2018 Poster? |
I just wrote it as "We would like to acknowledge the NSF Grant 1740300 and the GFINE fellowship program." I just emailed Mario to see if it needed to be included with mention of the NRC or if it counts as internal department funding. |
Hi, Mario replied saying that the GFINE can be considered internal department funding. So it is alright with just stating the NCSU as the principal developer and assuming that there was internal support. |
Awesome, I'll merge this, and update the webpage branch. Eventually I'll get CIVET to do this automatically... |
Should we include ORNL as collaborators as well?
…On Tue, Oct 22, 2019 at 6:25 PM Casey Icenhour ***@***.***> wrote:
Awesome, I'll merge this, and update the webpage branch. Eventually I'll
get CIVET to do this automatically...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42?email_source=notifications&email_token=AE57AGEYGLPVMS3TJTOFCWLQP54WTA5CNFSM4JDTANJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7NFTY#issuecomment-545182415>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE57AGDJF6WIMCIKVUFQRQ3QP54WTANCNFSM4JDTANJA>
.
|
Yeah, we probably should, considering I've worked/discussed with them on Zapdos-related topics. Thanks for the catch! |
Updated website is now live. If you find a bug or mistake, please let me know and I can correct it during the next update later this week. https://shannon-lab.github.io/zapdos |
Refs #41
Adds collaborators and funding sources for Zapdos (with links) based on discussions with @skatersaurus.
@lindsayad @csdechant Is there anyone/anything I'm forgetting? Here's how the webpage currently looks on my desktop: