[sakai2-tcc] Infrastructure discussion for future meeting?

[Berg, Alan]

Hi all,

I was speculating that  if we had a list of concrete actions that we can scope into to units of effort, then we advertise and then crowd fund within the community.

Funding could be:

Money
Developer hours
Student hours with mentoring
Or any unit that we can convert into an impulse.

I was speculating that perhaps we don't need infrastructure todo this. We could use for example a Google form and push at the conference. For example, the Sakaigersden, but with the expectation of resource owners turning up with real resources.

Examples include:

http://crowdfunding.piwik.org/
http://selfstarter.us/





Regards,
           Alan


Alan Berg

Innovation working group
On the use of ICT in Education & Research
University of Amsterdam
________________________________
From: sakai2-tcc-bounces at collab.sakaiproject.org [sakai2-tcc-bounces at collab.sakaiproject.org] on behalf of Charles Severance [csev at umich.edu]
Sent: 12 March 2013 21:05
To: sakai2-tcc at collab.sakaiproject.org Committee
Subject: Re: [sakai2-tcc] Infrastructure discussion for future meeting?

Dave -

I agree with what you say below - if you read my message further - I suggested that we (the TCC) even keep track of *who* would be the right folks to work on these things - since a random developer is not (as you say) likely to go into these things - but we may know a person or organization that might go after something for $10K-$20K - we would raise funds and then we would help make sure the funds went to someone competent to make the progress.

I am not suggesting we hope to find random free developers who without any prior Sakai dev skill would be able to fix our sticky session problem :)  I am talking about the "old fashioned" resource - money.   And Alan's suggestion for some kind of crowd-fund raising has some real merits.

/Chuck

On Mar 12, 2013, at 2:44 PM, David Adams wrote:

That level of specificity and purpose will be required to shake the
"hypothetical" resources free. Otherwise, it will remain just be a big
list of things no one will ever tackle.

Another big reason institutions are shy about taking leadership on
these projects themselves is the risk that their contributions will be
ignored or turn out to have been misguided. If the TCC takes the lead,
they can be relatively sure the work will be going to good use, will
be technically sound within the Sakai architecture, and will end up in
the community code and will generate a clear benefit and not a
fruitless burden. Not to mention it's good experience and training for
their staff to be able to work directly with the icons of the Sakai
community.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130312/da4a433a/attachment.html