> offload the support of this to someone else who cares Yes. This is the "freedom to fork" succeeding.
Going forward, let's continue to look for ways to be more aware about what expectations we're setting and about who should be paying attention to and having responsibility for what. I think the giant bucket of 63 repositories at https://github.com/Jasig is proving problematic. It would be cleaner to have a https://github.com/uPortal -ish namespace for those repos that a uPortal project PMC is responsible for, and then be deliberate about what repos come into that namespace. Kind regards, Andrew On Mon, Dec 8, 2014 at 10:59 AM James Wennmacher <[email protected]> wrote: > I'm not sure whom in Apereo besides uPortal is using the SASS maven > plug-in (https://github.com/Jasig/sass-maven-plugin) but it is pretty > clear we haven't been very responsive to other user's needs based on the > number of pull requests that we haven't actioned. On the uPortal side I > believe the desire is to drop using SASS and instead focus on LESS. > > 1. Is there a way to find out whom else in Apereo is using the plug-in? > 2. Even in advance of above information, I vote that we/Apereo > officially announce deprecating support for the plug-in and to use one > of the forked versions that has adopter interest and maintenance. In > other words, offload the support of this to someone else who cares more > than we appear to at this time. > > Thoughts? > > -- > James Wennmacher - Unicon > 480.558.2420 > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/uportal-dev > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
