Split general information into general info, group expectations, and …

…prof development pages.

_quarto.yml

@@ -12,6 +12,7 @@ book:
     - part: general-info.qmd
       chapters:
         - code-of-conduct.qmd
+        - group-expectations.qmd
         - onboarding.qmd
     - part: "Group Processes"
       chapters:
@@ -21,6 +22,7 @@ book:
         - sprint-planning.qmd
         - standups.qmd
         - hiring.qmd
+        - professional-development.qmd
     - part: "Group Programming"
       chapters:
         - drop-in-hours.qmd

general-info.qmd

@@ -22,61 +22,3 @@ We work in the Bioscience Research Laboratory (BSRL)
 -   Parking Easiest parking is the garage two blocks east of BSRL: \$2 hourly or \$8 daily.
 -   Public Transportation
 
-# Expectations
-
--   Working hours, breaks, sick and annual leave
-    -   Expected to be in during normal working hours
-    -   Please let me know at least 2 weeks in advance of any vacation time
-    -   You can ask HR about how many sick and vacation days you have. This is an important and valuable part of your compensation!
--   Communication
--   We use multiple methods of communication: In Person, Email, Slack, GitHub, Zoom, Google Drive; see [Software and Computing](https://osf.io/tzmhp/wiki/Software%20and%20Computing%20Resources/) for details.
--   We should all aim to reply to inquiries within a day. If someone doesn't reply in a timely fashion, please remind them **early**, **often**, and through **multiple channels**.
-
-## Supporting Scientists and Building Collaborations
-
-While we need to balance our unpaid 'support' with work on funded projects, enabling researchers is a first step in building the collaborations from which successful and interesting projects emerge.
-
-## Feedback and Iteration
-
-Feedback is essential to our group.
-Expect me to ask for it, and expect to provide feedback at any time, through any channel.
-Please let me know if you have any questions.
-
-## Time reporting
-
--   Inform Kristina by email of upcoming vacation or leave as soon as is practical; *at least two weeks in advance*.
--   Employees must report their time by 10:00 a.m. on the Friday of a non-pay week. Supervisors (time approvers) must approve time by 5:00 p.m. on that day. See <https://hr.arizona.edu/supervisors/compensation>
--   For Appointed personnel, you only need to report leave time (sick, vacation, jury duty, etc). Holidays and campus closures are automatically added to your time sheet. For more information on winter holiday closure: <https://hr.arizona.edu/employees-affiliates/leaves/university-winter-closure>
-
-## Professional Development
-
-I encourage all group member to attend (at least)
-
--   One conference or workshop per year. Our group's mission is inherently collaborative, and this outreach is important.
--   Seminars, webinars, and classes that will help you gain skills and knowledge related to your current work or work that you would like to do. For example:
--   On Campus: TRIPODS ecosystem genomics, data7 seminars, phenomics)
--   [Posit Webinars](https://posit.co/resources/videos/)
--   Help writing grants and papers.
-    -   (Learn) and use the [Pivot](https://pivot-proquest-com.ezproxy3.library.arizona.edu/funding_main) database to identify opportunities.
-
-The University of Arizona provides a number of professional development opportunities.
-
--   <https://ce.arizona.edu/professional-development>
-
--   Funding: you have the opportunity to **seek external funding** - this will help with your professional development and our bottom line.
-
--   All University of Arizona employees age 21-45 should consider joining "Tucson Young Professionals".
-    The U of A covers membership fees (normally \$200/y) - see [this website for more information](https://olod.arizona.edu/typ)).
-
-## Publishing \[Under construction\]
-
-Documentation, GitHub threads, Slack Discussions are all great places to find inspiration for publishable units; peer reviewed publications help provide an academic foundation for our group's contributions, with outreach as well as future funding.
-
-### Papers and Conference Proceedings
-
-### Data
-
-### Software
-
--   Zenodo: Major releases should get a doi here; can set up a github hook to archive each release.
--   Journal of Open Source Software: JOSS <https://joss.theoj.org/>

group-expectations.qmd

@@ -0,0 +1,31 @@
+---
+title: Group Expectations 
+---
+
+Everyone should follow the [Code of Conduct](code-of-conduct.qmd). 
+
+# Working hours and time off
+
+* Everyone is expected to be in during normal working hours. Since we are distributed across time zones, work with Kristina to establish your working hours.
+* Please let Kristina know at least 2 weeks in advance of any vacation time. 
+* You can ask HR (or look in UAccess) to track your available sick and vacation time. This is an important and valuable part of your compensation!
+
+# Communication
+
+-   We use multiple methods of communication: In Person, Email, Slack, GitHub, Zoom, Google Drive; see [Software and Computing](https://osf.io/tzmhp/wiki/Software%20and%20Computing%20Resources/) for details.
+-   We should all aim to reply to inquiries within a day. If someone doesn't reply in a timely fashion, please remind them **early**, **often**, and through **multiple channels**.
+
+# Feedback and Iteration
+
+Feedback is essential to our group.
+Expect me to ask for it, and expect to provide feedback at any time, through any channel.
+Please let me know if you have any questions.
+
+
+# Time reporting
+
+-   Inform Kristina by email of upcoming vacation or leave as soon as is practical; *at least two weeks in advance*.
+-   Employees must report their time by 10:00 a.m. on the Friday of a non-pay week. Supervisors (time approvers) must approve time by 5:00 p.m. on that day. See <https://hr.arizona.edu/supervisors/compensation>
+-   For Appointed personnel, you only need to report leave time (sick, vacation, jury duty, etc). Holidays and campus closures are automatically added to your time sheet. For more information on winter holiday closure: <https://hr.arizona.edu/employees-affiliates/leaves/university-winter-closure>
+
+

professional-development.qmd

@@ -0,0 +1,37 @@
+---
+title: Professional Development
+---
+
+# Professional Development
+
+I encourage all group member to attend (at least)
+
+-   One conference or workshop per year. Our group's mission is inherently collaborative, and this outreach is important.
+-   Seminars, webinars, and classes that will help you gain skills and knowledge related to your current work or work that you would like to do. For example:
+-   On Campus: TRIPODS ecosystem genomics, data7 seminars, phenomics)
+-   [Posit Webinars](https://posit.co/resources/videos/)
+-   Help writing grants and papers.
+    -   (Learn) and use the [Pivot](https://pivot-proquest-com.ezproxy3.library.arizona.edu/funding_main) database to identify opportunities.
+
+The University of Arizona provides a number of professional development opportunities.
+
+-   <https://ce.arizona.edu/professional-development>
+
+-   Funding: you have the opportunity to **seek external funding** - this will help with your professional development and our bottom line.
+
+-   All University of Arizona employees age 21-45 should consider joining "Tucson Young Professionals".
+    The U of A covers membership fees (normally \$200/y) - see [this website for more information](https://olod.arizona.edu/typ)).
+
+
+# Publishing \[Under construction\]
+
+Documentation, GitHub threads, Slack Discussions are all great places to find inspiration for publishable units; peer reviewed publications help provide an academic foundation for our group's contributions, with outreach as well as future funding.
+
+### Papers and Conference Proceedings
+
+### Data
+
+### Software
+
+-   Zenodo: Major releases should get a doi here; can set up a github hook to archive each release.
+-   Journal of Open Source Software: JOSS <https://joss.theoj.org/>