[sakai-core-team] source email list needed?

[Neal Caidin]

I've created a google group and opened a ticket with Wush. If we can get
this one out of the way, one less thing to worry about.

-- Neal


On Mon, Feb 2, 2015 at 10:24 AM, Matthew Jones <matthew at longsight.com>
wrote:

> Right, the post commit hook would be on wush now. It probably just
> migrated over "as-is" when the entire repository was copied. If you need
> the address changed you should contact them.
>
> The only thing that the windstream Jenkins is really still used for is
> supporting the 2.9.x (non-all) releases. We could get rid of it without a
> problem but we'd have to say always use the 2.9.x-all (
> https://source.sakaiproject.org/svn/sakai/branches/sakai-2.9.x-all/)
> branch to build. Since there would be no more artifacts in the
> repositories. We'd also need to move over the RSF projects to the other
> Jenkins. I believe that the RSF projects could be fixed up to build on
> Travis CI like the Sakai project is and probably even publish without
> Jenkins but this would take some time to setup for sure.
>
> I'd say once you move the mail archives, I'd have the time available to
> take care of Jenkins and you could shut that server down tho.
>
> On Mon, Feb 2, 2015 at 9:54 AM, Neal Caidin <neal.caidin at apereo.org>
> wrote:
>
>> Hi Sakai Core team,
>>
>> Stephen Marquard let me know he would appreciate if we could keep a hook
>> into SVN for the Sakai 10.x branch.  We could move the email list to a
>> Google group (since one of our goals is to retire Mailman, and move Jenkins
>> and get rid of the need for the Windstream server).
>>
>> Would that be okay? Maybe we could make this a private Google group,
>> since the need is probably quite limited, and after Sakai 12 will go away
>> (since 10.x won't be supported anymore).
>>
>> Is Greg Thomas , Indiana the only one who has access to do that (per an
>> earlier email)? I thought we moved our svn to Wush, so wouldn't some of us
>> have access?
>>
>> Thanks,
>> Neal
>>
>>
>> On Wed, Jan 14, 2015 at 3:01 PM, Brian Jones <bjones86 at uwo.ca> wrote:
>>
>>> I don't think it's a huge deal to remove the src list; however I will
>>> say that the only benefit I find it has at this point, is to brief me on
>>> commits my colleagues have made in our msub.
>>>
>>> Brian Jones
>>> Programmer/Analyst
>>> Information Technology Services
>>> Support Services Building, Suite 4300
>>> Western University
>>> (519) 661-2111 x86969
>>> bjones86 at uwo.ca
>>>
>>> On 2015-01-14 02:58 PM, Earle Nietzel wrote:
>>> > On github I am already receiving mails about merges and such not sure
>>> we
>>> > really need something additional.
>>> >
>>> > On Wed, Jan 14, 2015 at 1:19 AM, Steve Swinsburg
>>> > <steve.swinsburg at gmail.com <mailto:steve.swinsburg at gmail.com>> wrote:
>>> >
>>> >     Yeah my filter is to move them to the trash. Occasionally I have a
>>> >     look through but nothing a source history browse can't accomplish.
>>> I
>>> >     know that Seth enjoys the read.
>>> >
>>> >     On 13 Jan 2015 09:42, "Matthew Jones" <matthew at longsight.com
>>> >     <mailto:matthew at longsight.com>> wrote:
>>> >
>>> >         I've had this as a filter for quite awhile
>>> >
>>> >         Matches: subject:([sakai] svn commit)
>>> >         Do this: Skip Inbox, Mark as read
>>> >
>>> >         So I don't know how good a read they are anymore, but I didn't
>>> >         want to speak for anyone else. ;)
>>> >
>>> >         On Mon, Jan 12, 2015 at 5:30 PM, Seth Theriault
>>> >         <slt at columbia.edu <mailto:slt at columbia.edu>> wrote:
>>> >
>>> >             On Mon, Jan 12, 2015 at 5:26 PM, Matthew Jones
>>> >             <matthew at longsight.com <mailto:matthew at longsight.com>>
>>> wrote:
>>> >             > Do we know what is sending email to that? Is that an svn
>>> post commit hook on
>>> >             > the server? I'd say we probably don't need it but we
>>> should try to turn off
>>> >             > whatever is trying to send to it.
>>> >
>>> >             Yes, it's the post-commit hook. Of course, mail to the list
>>> >             would only
>>> >             go through if you were on the list (and sometimes we would
>>> >             forget).
>>> >
>>> >             > Though we could set up a github hook to keep this
>>> process going in-case
>>> >             > there was value to it for anyone.
>>> >
>>> >             Do you mean that the Sakai source list is no longer the
>>> best
>>> >             read on
>>> >             the Internet? ;-)
>>> >
>>> >             Seth
>>> >
>>> >
>>> >
>>> >         _______________________________________________
>>> >         sakai-core-team mailing list
>>> >         sakai-core-team at collab.sakaiproject.org
>>> >         <mailto:sakai-core-team at collab.sakaiproject.org>
>>> >
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>> >
>>> >
>>> >     _______________________________________________
>>> >     sakai-core-team mailing list
>>> >     sakai-core-team at collab.sakaiproject.org
>>> >     <mailto:sakai-core-team at collab.sakaiproject.org>
>>> >     http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > earle,
>>> > asahi net int.
>>> >
>>> >
>>> > _______________________________________________
>>> > sakai-core-team mailing list
>>> > sakai-core-team at collab.sakaiproject.org
>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>> >
>>> _______________________________________________
>>> sakai-core-team mailing list
>>> sakai-core-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>>
>>
>>
>> _______________________________________________
>> sakai-core-team mailing list
>> sakai-core-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150206/880222ee/attachment.html