Date: Fri, 29 Mar 2024 02:29:21 +0000 (UTC) Message-ID: <1724489218.15.1711679361940@46612395e753> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_14_1365419392.1711679361940" ------=_Part_14_1365419392.1711679361940 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you would like more information about the Vireo Users Group, includin= g how to join the Steering Committee, please contact the TDL Program Coordi= nator at info@tdl.org.
Membership is open to any Vireo user, regardless of membership in the Te= xas Digital Library; this includes non-Texas institutions. Although the VUG= is sponsored by the TDL, it welcomes participation by Vireo users and pote= ntial users worldwide.
If you would like to join the Vireo Users Group listserv, and to be adde= d to the growing list of Vireo Users Group members, please use the SUBSCRIB= E feature at this link&= nbsp;or contact the Texas Digital Library at info@tdl.org.=
Anyone engaging with Vireo may join the vireo-oss-community slack channe= l, administered by the Texas Digital LIbrary. To be added, send a request t= o the Vireo User Group email discussion list.
TDL, Vireo=E2=80=99s OSS development home, wants to know who you are. Th= e Steering Committee has developed a survey that takes about 5-10 minutes t= o complete which will help the lead developers and SC better understand the= make-up of our community of users, which will in turn help us develop bett= er methods for understanding your needs over time. These =E2=80=98instituti= onal profiles=E2=80=99 will be added to our Vireo user documentation and al= low us to work more closely with users and developers at institutions outsi= de of TDL.
>>> Please complete this Google Form: https://forms.gle/fiECiUxksvLcWMxn9 <<= <
Report issues and interact with the core software developers via the Github.
The core development team will at times arrange to involve the community= in sprints. Community sprints will be announced via the Vireo User Group l= istserv.
During sprint weeks, the team expects that you attempt to clear you= r schedule enough to work on few tickets/tasks during the sprint. At the be= ginning of the sprint, you might be asked for your estimated availability (= e.g. 20% time or 1 day each week, 40% time or 2 days each week, etc), which= allows the team leads to steer you toward tickets achievable within your a= vailable time. You may also specify your exact availability in the signup f= orm provided before the sprint.
You will be expected to manage your own work schedule, attend minimal me= etings & report your ongoing progress.
You will be expected to have some existing knowledge of and proactive in= learning any new Vireo concepts. While you are more than welcome to use th= is Sprint as a learning experience, we will not have any formalized trainin= g/workshops during the Sprint itself.
You will be expected to be proactive in asking for help or asking questi= ons if you get stuck. Ongoing support will be available on Slack (#vireo-os= s-community) from Sprint Coaches and other participants.
Technology/skills prerequisites:
UI: angular.js Version 1
Backend: Java, spring-boot & JPA/Hibernate on the backend
Note that Vireo is built using Texas A&M's web application framework= , Weaver: https://= github.com/TAMULib/Weaver-UI-Core and https://github.com/TAMULib/Weaver-Web= service-Core
If you are working on development tasks you may follow the direct deploy= ment proscribed in the README or you use https://github.com/TexasDigi= talLibrary/Vireo4VagrantAnsibleDeploy to build vireo4 within a vi= rtual machine. The latter option will require the installation of Vag= rant, VirtualBox, and Ansible.
Sprint coaches should be available during both sprint weeks for help get= ting up to speed / answering questions / debugging issues / pair programmin= g requests, etc.
Feature requests should be shared with the Vireo Users Group by con= tacting tdl-vireo@utlists.utexas.edu. Items will be = added to the list upon receipt, and at a certain point during the year, use= rs with active installations of Vireo will have opportunity to vote on the = list of items. Highly requested features will be prioritized, translated in= to user stories, and shared with the TDL product owner and development grou= p to guide future development.
This list should not be used for bug-reporting&nbs= p;or to request Vireo support. To report errors or bu= gs to TDL, please contact the TDL Helpdesk in one of two ways:
Via web form: http://www.tdl.org/support/
Via e-mail: support@tdl.org