[cle-release-team] Crucible/Fisheye ready for action

[John Bush]

Thanks!  I wouldn't mind be more active in jira admin stuff as necessary.

On Tue, Sep 17, 2013 at 9:18 AM, Matthew Jones <matthew at longsight.com> wrote:
> I created this as an infrastructure jira, added these to two new
> repositories and resolved this request.
>
> If you think you'd want to be more active in jira and/or crucible
> administration including occasionally resolving other tickets in the future
> I'd be +1 for giving you jira admin access. Right now a few of us just
> resolve these as time permits, but it's generally not too much time
> commitment.
>
>
> On Fri, Sep 13, 2013 at 2:42 PM, John Bush <jbush at anisakai.com> wrote:
>>
>> Ok can we start with these:
>>
>> https://source.sakaiproject.org/contrib/evaluation/trunk
>> https://source.sakaiproject.org/contrib/turnitin/trunk
>> https://source.sakaiproject.org/contrib/gradebook2/trunk
>> https://source.sakaiproject.org/contrib/signup/trunk/
>> https://source.sakaiproject.org/contrib/dashboard/trunk/
>> https://source.sakaiproject.org/contrib/delegatedaccess/trunk/
>> https://source.sakaiproject.org/contrib/etudes/sakai-jforum/trunk/
>> https://source.sakaiproject.org/contrib/etudes/melete/trunk/
>>
>> I'd say clog but that its going to github I think
>>
>> If there are problems with msubs, could I just get:
>> https://source.sakaiproject.org/svn/msub/rsmart.com/sakai/trunk/rsmart/
>>
>> at that level I don't think it would be an issue.
>>
>> I'd be happy to do this myself, if you want to give me appropriate
>> access as well.
>>
>> On Fri, Sep 13, 2013 at 11:19 AM, Matthew Jones <matthew at longsight.com>
>> wrote:
>> > Any contrib projects are fine (if just trunk), just let me know which
>> > ones
>> > to bring. Can just put them in the Sakai Contrib Repository.
>> >
>> > We could bring in msubs but we'd have to be careful to set enough
>> > exclusions
>> > so it doesn't end up bringing down the server because of all the copies.
>> > ;)
>> >
>> > For whatever reason you can't set wildcards on crucible's include but
>> > you
>> > can on exclude. So it seems like you have to exclude everything you
>> > don't
>> > want in order to make a repository work. As a test, I brought in the
>> > branches with wildcard exclusions so we could be able to review in
>> > branches
>> > (like assignments/branches/SAK-12345)
>> >
>> > tags/**
>> > msub/**
>> > trunk/**
>> > sakai-2.5*
>> > sakai-2.6*
>> > sakai-2.7*
>> > sakai-2.8*
>> > sakai_2* (Basically really old sakais)
>> > sakai-3.0* (Yes it existed)
>> > *2.9.0* (The original 2.9.0 branch)
>> >
>> > This still resulted in around 500 branches because we don't clean up
>> > branches very well and some false matches. Maybe there's a better way to
>> > do
>> > this, but this would be the consideration for msub.
>> >
>> >
>> >
>> > On Fri, Sep 13, 2013 at 2:05 PM, Aaron Zeckoski <azeckoski at unicon.net>
>> > wrote:
>> >>
>> >> Some of the msubs are basically like forks of the full sakai trunk so
>> >> probably those would not work. Individual contrib projects seem safe
>> >> enough though so I am in favor of that. All that said, if it works
>> >> then why not?
>> >> -AZ
>> >>
>> >> On Fri, Sep 13, 2013 at 1:57 PM, John Bush <jbush at anisakai.com> wrote:
>> >> > So what are people's thought on bringing selected msub's repo's into
>> >> > this thing.  I know the whole tree was causing an issue but what
>> >> > about
>> >> > upon request?  My reasoning being I think it would help move things
>> >> > from msub into core, because reviews could happen there, and things
>> >> > could be found by others more easily.
>> >> >
>> >> > Also, same for contrib tools.  Could we bring in some selected
>> >> > contrib
>> >> > tools?   Like the big ones a lot of people are using: turnitin, eval
>> >> > sys, etc...
>> >> >
>> >> > On Thu, Sep 5, 2013 at 10:45 AM, Neal Caidin <neal.caidin at apereo.org>
>> >> > wrote:
>> >> >> Hi All,
>> >> >>
>> >> >> It appears that the data is indexed and Crucible/Fisheye are ready
>> >> >> for
>> >> >> use.
>> >> >> If anybody can confirm the functionality works that would be
>> >> >> terrific.
>> >> >>
>> >> >> Is there a way we can take this for a community test-run (in a
>> >> >> couple
>> >> >> of
>> >> >> weeks when fall rush is mostly done)?
>> >> >>
>> >> >> Thanks,
>> >> >> Neal
>> >> >>
>> >> >>
>> >> >>
>> >> >> Neal Caidin
>> >> >> Sakai CLE Community Coordinator
>> >> >> neal.caidin at apereo.org
>> >> >> Skype: nealkdin
>> >> >> Twitter: ncaidin
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> cle-release-team mailing list
>> >> >> cle-release-team at collab.sakaiproject.org
>> >> >> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > 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. **
>> >> > _______________________________________________
>> >> > cle-release-team mailing list
>> >> > cle-release-team at collab.sakaiproject.org
>> >> > http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>> >>
>> >>
>> >>
>> >> --
>> >> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>> >> _______________________________________________
>> >> cle-release-team mailing list
>> >> cle-release-team at collab.sakaiproject.org
>> >> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>> >
>> >
>>
>>
>>
>> --
>> 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. **
>
>



-- 
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. **