[Management] Proposed change to msub requirements

[Michael Osterman]

I think Peter's spot on here--the commiter + institution (or employer if
commercial partners get brought into the mix) should submit the appropriate
paperwork so that the contributions really belong to Sakai. That in itself
slows the process down and would be enough of a deterrent to prevent casual
(ab)use.

Plus, there are those watching the svn commits like a hawk who can make sure
it's used for the right purposes. :)

As for the Foundation hosting SVN, I recall Seth looked in to using EC2, for
example, and the bandwidth costs would be prohibitive based on traffic. It
would likely require some institution hosting it, even if just as a
colocation to help avoid bandwidth charges, or perhaps some kind of VPS
solution from a commercial hosting provider to keep costs contained.

-Mike

On Thu, Jul 30, 2009 at 8:05 AM, Knoop, Peter <knoop at umich.edu> wrote:

> That is my recollection as well; start small by limiting it to Sakai
> Partners to gain some experience, and then consider expanding the program,
> if the situation warranted it and the cost of supporting it wasn't out of
> line with expectations.  (Right now there are only 13 of the 92 Sakai
> Partners/Commercial Affiliates making use of msub, and some of those are
> still just placeholders.)  What does Indiana think about scaling things up?
>
> Also, what about the Foundation taking on hosting responsibilities?  There
> were volunteers from the community to help admin the msub space (field
> directory creation and commit access requests), however, Indiana wasn't able
> to provide them with the necessary access, so the foundation staff had to
> handle things.  Perhaps Indiana has a solution in place for this now?
>
> The key requirement that likely should be retained is that anyone granted
> commit, regardless of their organizations' Partner status, should be covered
> by CCLA/CLA licensing.  That way contributions can be utilized by anyone or
> in a subsequent Sakai release without having to track things down.
>
> -peter
>
> > -----Original Message-----
> > From: management-bounces at collab.sakaiproject.org [mailto:management-
> > bounces at collab.sakaiproject.org] On Behalf Of Ray Davis
> > Sent: Thursday, July 30, 2009 8:44 AM
> > To: Michael Osterman
> > Cc: management at collab.sakaiproject.org
> > Subject: Re: [Management] Proposed change to msub requirements
> >
> > Those were the two reasons I remember. My original proposal suggested
> > that "the Foundation should get paid back by more contributions and by
> > easier tracking of pain points," but I didn't take into account that
> > (at
> > that time) the Subversion administrative costs were being carried
> > completely by Lance's team.
> >
> > Best,
> > Ray
> >
> > On 7/29/09 7:25 PM, Michael Osterman wrote:
> > > The recent proposed by-laws amendments rattled loose another
> > community
> > > requirement that came up at the Boston conference during the
> > > Programmer's Cafe afternoon session.
> > >
> > > Under "Requirements and Rules for Use" at Deployment Source Code
> > > Repository (mSub)
> > >
> > <http://confluence.sakaiproject.org/display/PROD/Deployment+Source+Code
> > +Repository+%28mSub%29>,
> > > it states that one of the requirements of using mSub is Sakai
> > Partners
> > > Program membership.
> > >
> > > When trying to come up with the "why" behind this requirement, the
> > best
> > > those present could recall was that it was a mechanism to control the
> > > volume of repository requests. I additionally recall another thought
> > was
> > > that this would provide a tangible benefit of Partner membership.
> > >
> > > The general feeling in the room is that this requirement no longer
> > makes
> > > sense, so I wanted to bring that idea up in a broader forum. Not sure
> > if
> > > this is the right list for this discussion, but I had to start
> > somewhere.
> > >
> > > Thanks,
> > > Mike
> >
> > _______________________________________________
> > management mailing list
> > management at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/management
> >
> > TO UNSUBSCRIBE: send email to management-
> > unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/management/attachments/20090730/ba87ba59/attachment-0001.html