[Building Sakai] Sakai BigBlueButton Issue tracking

[Fred Dixon]

Hi Adrian,

Agreed -- let's use JIRA for issue tracking.

At the moment, Jesus Federico and I are working closely with Bryan 
Holladay, Sam Ottenhoff, and Scot Siddall at LongSight, and yourself, to 
do a first pass of testing and fixing of all the obvious bugs.  The tool 
is still in development.  Once everything is looking solid (we're 
getting closer), we will post a follow-up to sakai-dev inviting everyone 
to test (consider it BETA at that point), open issues in JIRA, and 
report anything we would have missed.

In this way, we will make best use of the communities time and have lots 
of opportunities for testing and bug fixing to make it really solid.  In 
parallel, we're testing against the latest beta for BigBlueButton 0.8 to 
ensure everything is working, and will be releasing BigBlueButton 
0.8-beta-4 soon.

The latest development code for the Sakai Meeting Tool is available on 
GitHub

https://github.com/blindsidenetworks/bigbluebutton-sakai

The latest code for BigBlueButton is also available on GitHub

https://github.com/bigbluebutton/bigbluebutton


Again, Jesus and I post an update when the Sakai Meeting Tool is ready 
for wider testing.  We're looking forward to it..

Regards,... Fred
BigBlueButton Developer



On 1/27/2012 5:08 AM, Adrian Fish wrote:
> Github's issue tracker doesn't seem very feature rich. You can't even 
> attach a file to an issue, unless I'm gravely mistaken. If that is the 
> case I suggest we keep the issues in JIRA but just host the code in 
> github.
>
> Agreed?
>
> Adrian.
>
> On 25/01/2012 09:58, Adrian Fish wrote:
>> You should read this if you use Sakai BBB.
>>
>> Has anybody got any problem with us (Blindside Networks and I) moving
>> the Sakai BigBlueButton issues from JIRA into github? The latest code is
>> now hosted there and I've started migrating the confluence pages over to
>> github's wiki. We're keeping the same license and copyright statement as
>> I think they comply fully with github's definition of open source.
>>
>> Maybe the issues should remain in JIRA although I can't think of any
>> particular reason why they should.
>>
>> Cheers,
>> Adrian.
>>
>