--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uportal-dev...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-dev/568596366.3660704.1561138310788.JavaMail.zimbra%40unicon.net.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-dev/13A705C0-4489-497C-8834-E81A36876B76%40wisc.edu.
Hi,
Aaron's feedback give a way, having doc near to the sources is
required whereas developpers won't upgrade it.
To get an example CAS may have a good approach, the doc is
global to all projects and at one place (a warning sometime we
don't know on which project properties have a concern). I didn't
watch exactly how the git doc repository was made but it's a
linked (recursive) one inside cas project. Maybe we can have a
such link inside several project ?
What to you think about this other approache ?
Julien
You received this message because you are subscribed to the Google Groups "uPortal Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uportal-user...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-user/CAOsfLuT%3DNSgD%2BxiA3mcBrNyeSDRFENk%2Bv46ngZtU%3DB3-Ma4TgA%40mail.gmail.com.