you have a point here, there's also been a bit if frustration expressed by infra about the volume of stuff stored in people's home directories. perhaps access to extra storage (other than version control) for on-topic assets is also something that a lab could have. d. On 5 Apr 2016 9:58 p.m., "Zachary Jaffee" <z...@case.edu> wrote:
> The real value that labs could provide over something like github would be > access to apache infrastructure. If I had the ability to spin up VMs on > demand without having to pay (insert cloud provider), the place where I > could do that would be the perfect place to experiment with new projects. > This would be even more valuable if there was a system in place that would > just auto build and deploy a project with a dockerfile, or something > similar, in it. > > On Tue, Apr 5, 2016 at 1:42 PM, Rich Bowen <rbo...@rcbowen.com> wrote: > > > > > > > On 04/04/2016 11:51 AM, Danny Angus wrote: > > > So after I recklessly offered to step up and let Jan move on I started > > > wondering where labs was at, and had a look round at some stuff. > > > > > > I have a small amount of time to offer to the role, the PMC role, not > > > coding any particular lab, and I was wondering if anyone has a todo > list > > of > > > admin and/or organisational tasks that they'd like me to pick up. > > > > > > From my own observations I have one suggestion > > > > > > My bugbear is the list of projects on the website, which I don't think > is > > > very informative and doesn't even contain as much info as is in the > > > doap.rdf files. I'd propose to write a script or xslt or something to > > > generate the list from the doap files. > > > > > > I'd also like to chase down the PI on each lab and make sure that the > > > stauses are up-to-date. > > > > > > > > I would personally like to see Labs return to its roots - or, perhaps to > > what I originally understood it was to be. That is an easy place for > > Apache folks to spin up a test project. I feel that the barrier to entry > > is too high. We need to encourage people to start projects, without > > having to justify them. Right now, the default path is "make a project > > on github." > > > > Perhaps we need to step back a bit further and figure out what we're > > trying to do here, and why. > > > > Meanwhile, I want to start a project - an ASF version of what I'm doing > > at https://github.com/rbowen/openstack-echo - and labs is the obvious > > place to do it. But my initial gut feeling is, way too much overhead, > > why bother? > > > > I'd like to figure out how we can make Labs a place where if an Apache > > member wants to start a project, they think of Labs first, rather than > > Github. > > > > Thoughts? > > > > > > -- > > Rich Bowen - rbo...@rcbowen.com - @rbowen > > http://apachecon.com/ - @apachecon > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org > > For additional commands, e-mail: labs-h...@labs.apache.org > > > > > > > -- > Zach Jaffee > B.S. Computer Science > Case Western Reserve University Class of 2017 > Operations Director | WRUW FM 91.1 Cleveland > (917) 881-0646 > zjaffee.com > linkedin.com/in/zjaffee > github.com/ZJaffee >
