Hi all,

I was on holiday, but I am now taking a look.
I want to share a bit of experience from the CloudStack project.
This year, we are doing the CloudStack Collaboration Conference in the John 
McIntyre Conference Centre, The University of Edinburgh. We deliberately have 
chosen to do this in the University Campus so that we can also provide access 
to the event to students. We also have a program for free tickets for students, 
who would like to attend. And sessions - CloudStack for beginners for them.

Closer to the event we will send some communication to the students through the 
University channels. We already have had some calls with the university 
responsible people on the topic.

I will keep you posted on this.

————
Also on the same topic - each project can create a demo environment for 
students to test. And a few blog posts for beginners are also nice.

My experience from the past with Universities is that you need to have mainly 
personal connections and to propose them ideas and topics.
Also some internships are interesting - if we can provide summer internships 
(although not paid) but for students which can be considered as experience for 
them.
Google has Google Summer of Code, so we can wrap something like ASF Summer of 
Tech.

Random thoughts here.

Best regards,

On 29 Jul 2026, at 17:54, Rich Bowen <[email protected]> wrote:

We held (very last-minute) inaugural office hours today.

Main topic of discussion was university outreach, and what that looks like. 
We’re really not sure what University outreach would look like, but it sounds 
to me like we should participate in existing programs, rather than trying to 
create our own, since they’re the experts and we’re not. What we could/should 
do (based on this discussion) is:

1) Document where we are already participating in existing programs, so as to 
increase awareness, share best practice, and identify opportunities for 
projects to hook into existing efforts.
2) Have discussions on the mailing list (perhaps using a [University] Subject 
tag) where people can collaborate/commiserate about their existing efforts, so 
that people don’t feel alone in their efforts, and where they can share tips 
and experiences. We could, of course, split this to a separate list if it gets 
too loud for this one, but my inclination is not to proactively create Yet 
Another Mailing List to go be invisible and go stale, but rather to increase 
visibility here first and split if/when it becomes necessary.

So … if you’re already doing some kind of University outreach, please do start 
a thread, using [University] the subject, to tell us about it.

I also learned a new phrase — “Desperate Learner” — which I really like. This 
describes people who are learning something because they see it as their ticket 
to self improvement, and more specifically to income generation. Open source 
has always been about “scratching your own itch” and open source participation 
as a ticket out of poverty is a huge motivator, particularly in University 
settings where people are looking to create their career and life.

I mentioned https://boxofclue.com/comdev-metrics/ which I’ve been running for 
about a month now, and suggested moving it to one of the ComDev VMs. I’ve 
mentioned this before, and didn’t hear much feedback other than that it seems 
like a useful resource. I’m going to try to go ahead and stick it on 
projects.apache.org <http://projects.apache.org/> at some point, maybe? I don’t 
expect to have time to get that done this week, but would be delighted to work 
with anyone else who does have time for that. But I’ll get to it eventually if 
nobody else does.

I’d like to make this a regular thing and have put this on my calendar, weekly, 
at 10am Eastern US time. If you can drop in a few times a month, that would be 
fantastic. And I’ll try to post a proposed topics list here a day or two before 
the meeting.

—Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Reply via email to