[sakai2-tcc] Infrastructure discussion for future meeting?

[John Bush]

I like this idea, and the messaging around it.  Along with priorities
we could even get to a level of complexity, plausability, level of
effort type of thing, which would really help people match skill sets
and resources to issues, which is helpful for planning.  I've looked
at some of these issues in great detail, for example, the session
replication issue.  There are some of these issues where you can work
around if you are clever, and do it in ways that actually doesn't
impact the code base, for the really hard and risky problems sometimes
that is actually a better way to go.

On Tue, Mar 12, 2013 at 9:06 AM, Charles Severance <csev at umich.edu> wrote:
> I like the list and agree that the list is not hard to construct.  We all know our weaknesses.  And of course the product while imperfect does function so there is no need ot panic - but it would be good to flesh out these issues, write them down in a common place and then  add detail.
>
> The problem with lists like this is that we make the list, call it a "roadmap" and then "stakeholders" (i.e. people with desires but no resources) get unhappy because there is never any progress on these things due to lack of resources and then decide an oversight committee of "fans of Sakai" would fix every thing - and that just makes it worse.
>
> But we do need to break tat cycle - and not talking about this stuff does not break the cycle.
>
> So here is my proposal.  Lets make a confluence page called "Important Unfunded Mandate List" and put this stuff there and then add detail and even prioritize them and even meet about this from time to time (including San Diego).
>
> By calling it the "Important Unfunded Mandate List" we *emphasize* that resources are needed and until resources arrive no progress will be made.  And then if those "hypothetical" folks who want give resources (I always doubt these really exist) at least have a list of unfunded mandates that could use some funding.   We also could even have a (perhaps less public) list of folks who would be willing to take those projects on for money and who are plenty skilled to take the effort on.
>
> This could be solved by proper labeling.
>
> I attach "Chuck's Scary List" from December 2004 that was mistakenly sent to the dev list instead of the board list and resulted in Lleida doing the translations for Sakai 2.0.  Sadly some of the things are still open issues.
>
> /Chuck
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>



--
John Bush
602-490-0470