[sakai2-tcc] Proposal: eliminate all indies, re-version trunk to CLE 4.0

John Bush jbush at anisakai.com
Thu Jul 25 07:24:40 PDT 2013


For the record, I support the removal of the indies proposal.  I've never
liked the indies idea and its done nothing for me but give me more busy
work to attempt to unravel it.

Regarding the version, I don't mind 2.10 or 4.0.  I understand the
technical and other concerns to version 3.  I'm not sure a move to 4.0
helps adoption or changes anyone's idea about the state of the project,
unless they are really uninformed.  It's just a name to me, so I wouldn't
oppose the move.


On Thu, Jul 25, 2013 at 4:28 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> The original proposal is here:
>
> http://collab.sakaiproject.org/pipermail/sakai2-tcc/2013-June/003563.html
>
> I've held off starting any work until sufficient consensus exists
> warranting the investment of time and effort.  A number of TCC members have
> commented favorably on the proposal but others have not voiced their
> opinion.
>
> Anth
>
> On Jul 25, 2013, at 2:23 AM, Steve Swinsburg wrote:
>
> It looks like we've stalled on this. What can we do to get this underway?
> Do we have consensus on an approach? Can we get a new proposal discussed
> and voted on? We should get any change like this in and bedded down so we
> can resolve issues early.
>
> cheers,
> Steve
>
>
> On Fri, Jun 21, 2013 at 12:20 AM, David Adams <da1 at vt.edu> wrote:
>
>> I misunderstood the thing about Github in the original message.
>> Apparently it was discussed and put off at the conference, but I don't
>> see how waiting does anything but hurt the project's future. The
>> collaborative design of git fits much better into the style of
>> development we need to foster. As for Github, a project in Github is
>> light-years more friendly to new developers than the current
>> code-hidden approach with our source spread out in a morass of other
>> semi-related projects on the current SVN.
>>
>> Just on a lark, I decided to time cloning Noah's sakai-cle github
>> project and checking out the sakai full trunk from SVN. Results? From
>> SVN, 2 minutes, 31 seconds. Cloining from Github? 17 seconds. And the
>> github clone comes with significant chunks of the revision history.
>> Clone a few more branches, and it just takes a few more seconds,
>> whereas in SVN, a second branch would take another 2.5 minutes.
>> Developers who don't yet know git can learn pretty much all they need
>> to know to get started in the two minutes they won't be waiting for
>> the check-out to happen...
>>
>> David Adams
>> Director, Systems Integration and Support
>> Virginia Tech Learning Technologies
>>
>>
>> On Tue, Jun 18, 2013 at 3:15 PM, Steve Swinsburg
>> <steve.swinsburg at gmail.com> wrote:
>> >
>> >> Dashboard, ElasticSearch, Keitei, LTI 2.0, tincanapi, Samigo
>> improvements, key library upgrades, eliminating indies, simplifying the
>> build, etc.
>> >
>> > Yes, this is a great reason to upgrade! I think that with very little
>> effort we can even slot in a few more major and mature improvements like
>> Roster2, Syllabus, Signup and maybe a few more.
>> >
>> > Just a subtle note that with a major version switch this is an ideal
>> time to move to github. We could just do it for Sakai 5, though that may be
>> a few more years away, do we want to wait that long to get the efficiency
>> and code quality improvements that we so desperately need?
>> >
>> > I don't particularly like Sakai 10 as a version number for the reasons
>> outlined previously, too high a jump and aligning to calendar years locks
>> us in too much.
>> >
>> > cheers,
>> > Steve
>> >
>> >
>> >
>>
>
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>


-- 
John Bush
602-490-0470

** This message is neither private nor confidential in fact the US
government is storing it in a warehouse located in Utah for future data
mining use cases should they arise. **
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130725/3d04cfaa/attachment-0001.html 


More information about the sakai2-tcc mailing list