It has been involved in the Big Lebuton project for over 10 years.
So we are really passionate about this.
We have Stephen Muggy, who is the executive director of the Big Lebuton Foundation.
We're all wearing the same shirts.
Okay, so Big Lebuton, it is a virtual classroom.
You can think of it as a web conferencing, a video chat, and others found in 2008, a 7.7K
get the stars on GitHub.
So we've been around for a while.
Funny thing, there's these other products in the market.
Sometimes people say that Big Lebuton is the free open source of equivalent of Zoom.
Every here's Zoom, not here, probably, but we think of it a different way.
We think Zoom is the paid, a close source equivalent of Big Lebuton, because we came first.
So let's just say the world needs more Big Lebuton, more collaboration.
So we actually went for a very specific market segment when we did Big Lebuton.
That was online learning, synchronous learning, distance education.
So we say that Big Lebuton is a virtual classroom that provides built-in tools for active
learning and live analytics to ensure every student learns.
There's no back of the classroom with Big Lebuton.
It's not dependent on webcams.
The students are sharing webcams.
You can still see how they're doing.
It's obviously free opens for software and it's been built into Moodle, Canvas,
Camille, Open Social, and many other platforms.
So two examples, for example, so if anyone knows that graph, that was a graph on a graph
from Beta Woodenberg.
So during COVID, they had 3,000 schools, they ran 4,000 Big Lebuton servers, and they
peaked at 185,000 concurrent teachers and students.
All with open source.
We didn't even know about it until they contacted us.
As of that, and a lot of other adoption worldwide, look lies in 65 languages.
Big Lebuton was built into the core of Moodle.
The world's most popular learning management system.
But we have a problem.
We have a product and how do we move it to a platform.
I'll turn over to you, Chego.
Thank you.
So before the version that we are launching by the end of February,
that is 3,0.
So before 3,0, in order to customize Big Lebuton,
you had to modify the service code.
You had to build the package that you modified,
and you had to deploy these package in servers.
And this was a bit complicated because sometimes one little customer
wants a little change, and you had to run a server for this customer,
because you was running customized service codes.
And of course, even if you was doing that,
you had to reapply the changes every time a new version
of Big Lebuton service code was available.
It was a bit traumatic for the developers.
So with Big Lebuton 3,0,
we are introducing Applegene architecture.
And with the plugin architecture, now you can create a plugin,
host it locally or externally.
In able the plugin via the session creation API call,
and the end, of course, the developers are not
having to write the same code again and again.
And the important thing about this architecture
is that one server can run different plugins in different meetings.
So you don't need to have customized a server,
or you don't need to have the same plugins running
for all the classrooms.
So it's really important.
So what a client plugin can do in Big Lebuton.
It can access real-time session data.
It means that a plugin can observe the current is light text,
or the number of participants, or if there is someone
with the hand raised and the plugin can react to this.
There are some predefined methods.
Like you can say, yeah, use the current is light,
and then you have it ready to go,
or you can write custom GraphQL queries.
The GraphQL queries are going to run obviously
in a secure way, limited to the context of the session
that a plugin is running.
So it's pretty secure as well.
It's the same way that the Big Lebuton UI in 3.0
is consuming data from GraphQL.
So we expose this data layer to the plugins as well.
So it's really powerful.
We enable real-time user interactions, which
means that a plugin running in a browser can
publish to a data channel, and this data
is flowing to the other participants in the same session,
running the same plugin.
So the plugin can create, it can exchange any data, it once.
It also allows you to query and control the UI.
Let's say the plugin wants to reduce the volume
of the external video player, or it wants to reduce it automatically.
A plugin can do it, so it can perform operations
on behalf of the user.
We can Big Lebuton, of course.
And you can customize chat rendering.
We have an example of a plugin that
do code highlight.
So you can customize how the chat message
are rendered.
You can add more features on the chat.
And much more.
We have more than 80 APIs ready for use, it's really powerful.
So we are launching Big Lebuton 3.0.
We've some plugins that we created.
But obviously, the idea is that the community
will create plugins, and the universities
will be creating plugins as well.
So the plugins we are going to chip in Big Lebuton 3.0
is the peak random user.
Sometimes you are in a meeting, and you
want to decide who starts talking.
So you can use it in our daily meetings.
So we click OK, pick a random user.
So it says OK, Tiago says now, the other user.
So it ensures that all the users will
have the change to speak.
Share website link as a content.
So let's say you want to share a Google Docs document,
or something.
You can share, and everyone will get the same page rendered
within a Big Lebuton, and more.
So here, I'm showing you how the peak random user
displays in Big Lebuton.
As you can see, the peak random user
button is here.
And it's integrated in the UI.
Someone that doesn't know it's a plugin.
It thinks it's in Big Lebuton itself.
So it has a seamless UI integration.
And this is the closet captions plugin,
where someone can be writing the text.
And so others can read instead of listening.
This is the shared website link as content as well.
So here, I'm listing some ideas.
Potential examples of what you can do if a plugin.
So you can have AI power transcription.
So instead of someone typing, you can integrate with an LLM,
or something, and the API can do it for you.
CRM and LMS integration.
Imagine you join from a CRM into a call with a customer.
And you can show within Big Lebuton the last interactions
you had with this customer.
Because you can add anything in the Big Lebuton AI
with this powerful plugin architecture.
Also, telemedicine and have the same thing.
If you are joining from a software where
you do online consultancy, the doctor can see the previous prescriptions
and things like that, all in the same screen, which
is really powerful.
And obviously, educational.
We are integrating Big Lebuton with H5B, which
will open to several package that allow gaming
and engaging tools for the classrooms.
So how you can build a plugin?
You clone the SDK repository.
You select a simple plugin as a starting point.
We have several simple plugins there.
And you customize it in the way you want.
You build the plugin using the provided command.
It's a simple command.
And then it generates two files.
A JavaScript bundle and a manifest file.
You just need to host these two files in any HTTP as server.
And when you are creating the Big Lebuton session
from an API call, you pass the manifest URL
and then everything happens.
So this is the Big Lebuton plugin SDK repository.
Here is a list.
It's just the first page.
I think we have four pages of these examples.
So of course, I'm not going to explain any of them.
But basically, you have examples showing each hook of the API.
So it's anything you want to do.
As a plugin, you will find an example showing you how to do.
And here, I don't know if there are some react developers
here, but basically I'm showing you how
is the code.
We created it in a way you have a setter.
So whenever your plugin is loaded, you receive this setters.
And you can say, yeah, set presentation to bar items.
So you pass an array of items for this setter.
And you get a button.
So here in this example, I'm creating a two bar button
on the presentation area.
It's a really simple example.
But a more powerful example could be, OK, look,
the current is light text.
If you find something in this slide,
like a special director or a YouTube link, for example,
add a button on the toolbar that when you click,
it plays the YouTube video.
So it would be just more 10 lines of code in this plugin
architecture.
So it's really simple to develop.
We want to really make the learning curve as a smaller
as possible in order to create a plugin.
So here, you can set the presentation to bar items.
Here, we are passing one item.
And after 10 seconds, we are passing an empty array.
So I'm showing you how to remove things.
So the plugins have its own scope.
So let's say you have two plugins running.
And one plugin set, add the button,
and another plugin, add the button.
And if this first plugin defines an empty array,
when defining, it's going to remove the button only
of the plugin itself.
So it have different partitions in the plugin core.
Yeah, so it's pretty much it.
Here, we are inviting you to join our community.
We have a mailing list.
We have the GitHub.
And that's it.
Yeah.
All right, we have three minutes left.
So feel free.
If anyone has any questions?
Any questions about the plugins?
So it will release, big loop on 3.0 or release end of February.
As Diego said, it will come with lots of examples.
You can download it, try it out.
The whole part was to turn our product into a platform
that other people have built upon it.
You can leverage our 16 years now of building
the collaborative application.
There's a lot of stuff that is in big loop
button that's open source as well.
Most recently, we're moving to the user's live kit
for the audio and video.
I said the scalability.
We talked about the plugin.
And there'll also be a new user interface
as coming out this summer.
So if we present again next to us, it will be almost
like it will look like a whole new product.
So we are very passionate about what we're doing
because it's improving education for the world.
And as a speaker who's before us, talking about climate change,
education is one of the sustainability development goals
for United Nations.
And it is underpinning almost all of the activities
you want to do.
Yes, we are all intelligent people,
but we need to be intelligent people
that can work, collaboratively with other people.
Because the world's problems, they can't be solved by an individual.
They can only solve by communities, by groups,
by governments working together.
All right, thank you.
APPLAUSE
There was a question.
Oh, my God, yes.
Are you planning on making a platform for sharing
plugins on climate change with the language?
Jacob, do you want to say?
Yeah, this I forgot to mention.
The next step is creating the, we don't know
where we're going to call it as a plugin platform,
plugin, star or plugin directory.
But yeah, we're going to create it.
And we will enable you to submit open source plugins
and also paid plugins because we want developers to succeed.
So why not we allow you to create a paid plugin
and benefit the whole ecosystem with good quality software, as well.
So yeah.
All right.
Thanks again.
APPLAUSE