[sakai-pmc] [Building Sakai] RSS portlet now part of Sakai trunk

[Steve Swinsburg]

Since the branch for Sakai 10 has been created before this was committed, I am happy for this to stay in trunk (or experimental, but it doesn’t make much difference, just less exposure), with the proviso that the code stays in github. 

I oppose moving the code to SVN, especially given the current climate around moving the entire source to github in the very near future anyway (mid this year has been mentioned). I do not wish to, nor have the time to, maintain two copies of the code just to satisfy a codebase purity argument. 

regards,
Steve


On 27 Feb 2014, at 2:28 am, Seth Theriault <slt at columbia.edu> wrote:

> On Wed, Feb 26, 2014 at 9:36 AM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
> 
>> We've spent significant time this release cycle attempting to reduce our
>> project oddities.  This has involved hundreds of hours spent on removing our
>> indies, standardizing some of our Maven practices, and removing independent
>> JIRA projects.  My preference would be to keep our oddities to a minimum and
>> continue keeping all of our source in one place.
> 
> Would people be amenable to a temporary compromise: Move the RSS
> portlet to the experimental build? Perhaps we want to put the Sakai
> Project account to use here.
> 
> I don't really have a problem with the RSS portlet coming in from
> GitHub at the moment but it must be because I see it as the future. I
> will note the irony in re-creating the past for the "purity" of the
> code base (and that of my own position!).
> 
> Seth
>