Thank you so much, Yares.
Thank you.
Hi everyone.
It's a pleasure being here with you all.
Hello.
Hello everybody.
So good to have all of you here.
Uh, and welcome once again to our session.
What was contributionsbuilding a transparent system
for a stronger community.
Before we start, I wanna ask, uh,everybody here a very small question.
How many people here.
Have contributed to WordPress.
Can you, uh, have a show of hands please?
Wow, that is like 80% of you.
Amazing.
How many of you who've not contributedwant to contribute to WordPress?
This is for just the peoplewho've not contributed.
Okay.
Good, good, good.
So that is excellent.
Um, with that note, let'skick off the session.
Uh, what are we doing here today?
We, um, we are gonna explaina project that we worked on.
Uh, we worked on a contributed dashboardproject last year and the year before.
Uh, and here are some of the thingsthat we're gonna talk about today.
We are gonna cover, um, the topic ofthe dashboard that we built, the vision.
We are going to explore the toolthat we used to build the dashboard.
We are gonna give you awalkthrough of what we did.
Uh, we are gonna share someof the insights that we
learned from the dashboard.
So of course we have the dashboard.
What did we learn from it?
What are the contents thatare there in the dashboard?
We are going to walk you throughthat and finally, we will
wrap up with the road head.
Where does this project lead to?
Where are we going?
Um, so let's kick off by taking alook at, into the World, into the
wonderful, wonderful world of dashboards.
So how did all of this kick off?
Um, to give you some context, I, I usedto be full-time WordPress contributor.
I technically still am, but I'm,I've sort of bossed my contributions.
Um, I worked on a programcalled Five for the Future.
Five For The Future is the officialWordPress contribution program
where organizations, uh, pledgeup to 5% of their contributions.
Uh, and I also used to work on,um, the word official WordPress
contributor mentorship program.
So while working on these programs,we all realize that there is a need.
For, uh, more transparency.
So when organizations pledge to WordPress,they need more transparency, and when
contributors contribute, they are notgetting the information that they need.
So that was very clear to me,and I heard this feedback from
talking to so many contributors.
So with that in mind, what if everysingle wordless contributor could see the.
Impact of their contributions at a glance.
I mean, contribu contributorsboth sponsored and non-sponsored,
they do a lot for the project.
So WordPress, as you all know,is an open source project.
It relies on scores, not scores,actually hundreds of thousands of
contributors all over the world.
I would say that there's around a hundredthousand plus contributors till now.
So what if every single one of thea hundred thousand historic purpose
contributors could see the impactof their contributions at a glance?
What if every single contributor here,they knew exactly where helpers needed.
So what, this is the big project.
We power 43% of the internet.
There are so many areas in this projectthat need help, but the challenge is
even for experience con even I, I, I'vebeen contributing for since 2016 even,
I don't fully know where help is needed.
I, I, trust me, I've beenworking on this project still.
I still not know.
I don't, if you ask me now, I donot know where help is needed.
What if there is a page where, whichshows which are the areas, which
are the projects, which are thespecific things where we need help?
That would be so cool.
Right.
And finally, I mentionedFI for the future.
Fi for the Future.
Currently has over 200 companiesthat have pledged their time
to contribute to WordPress.
So these companies, they arededicating their, their, their time.
I mean, they, they create products, theycreate revenues, but they're dedicating
a portion of that time to open source.
So that time is extremely valuable.
It is sometimes worth millions, or in somecases even billions of dollars, right?
So these companies, they needto know how much impact that
they're making on workers.
It's not like they, they cannot see now,but what if they could clearly see it?
And this is where the world ofdashboards come in and I'm gonna invite
my friend Ida to talk more about it.
Thank you, Harry.
Thanks a lot.
So, as Harry was mentioning, we'revery, very much involved in this
project last year because, uh.
Of the dream of getting a clear way foreveryone involved in the project to see
at first, where to start from, um, see,uh, check the status, the tracking, the
progress that we were making, and also,uh, at the end also have a way to see
the, um, uh, the weather impact thatwe were, um, we were, um, achieving as
individuals and a contribution team.
So the idea from there were was,okay, let's find a way to centralize
in one place and let have peoplevisualize what they need without
having to go around and around.
Has we always have been doing?
I believe so.
Here comes the idea of dashboards.
Um, find a one place to centralize theinformation and help, um, contributions
and companies navigating more easilythe, uh, the world of contributions.
So we start, um, giving more for toit and we kind of identified, uh,
main challenges and benefits for, uh,individual contributors and contribution
teams and fight for the future companies.
So I believe that, uh, most of ushave been in a situation where we
wanted to start to contribute toa specific team, maybe a new team
for us, and we felt overwhelmed or.
Lost, completely lost at the beginningbecause maybe the new team was using
completely different tools than theteam that we were used to, or it wasn't
clear the status of a project, andin some cases, at least I've done it.
In some cases, I, I just drop itbecause it was like too much and
I didn't feel comfortable askingfor help or digging more into it.
So the first, um, the first problemthat we wanted to address was,
uh, accessibility to contribution.
Make it easier for everyone.
For contribution, contribution teams andcon contributors, um, we really wanted
to find a way to provide a, an easy wayto streamline the work organization.
So usually teams have multipleprojects going on at the same time,
and so how we can divide the taskamongst the con, uh, the contributors.
How can we see as new contributors?
What we can better help withand how in the case it's needed.
How can we also transfer taskfrom one working group to another?
I. For, uh, fight for the future companiesinstead, in addition to, for this to
be a easier way to onboard, because Idon't know if anybody in the audience
have experimented it, but, uh, workingwith Fight for the Future Organizations,
r and I realized that at the beginning.
Um, companies want to support the project.
They want to sponsor, contributorto help with, um, with the overall
projects, but if they don't have anybodyto guide them, uh, they can be stuck.
So what are the projects thatmore, uh, that align the most
we, the company's values?
What are the projects or the task that,uh, um, contributors can relate more on?
So, okay.
Here it is.
We can start with this.
And ultimately having an easier way to,uh, get companies interest and keep them.
It also ensure, um, a stronger way fortheir commitment to the WordPress project.
Now, I, I pass it on to GaN andto talk a little bit more in, in
the case of what we've been doing.
Thank you.
Soda.
So, Asda mentioned thereare so many challenges and.
The best way to solve this, we thinkis dashboards, and what does dashboards
mean and where can dashboards help?
So first of all, let'sexplore what our dashboard is.
So dashboard, uh, I mean, it's a verygeneral term, but as we envision it,
it is a, it, it could be a page, itcould be a centralized page, could be
something that every make word PRIs team.
So you, you may know what, whatmake, make teams are, right?
So, um, every make teamare for the entire project.
There is a page or there's a sectionwhich shows very clear visual elements,
uh, that showcase the progress ofvarious parts in the WordPress project.
So how many, how many, um, how manyprs are there in, um, WordPress score
or, uh, how many translations happen?
Uh, what is the number of translationsthat happen in Spanish language?
So imagine having all ofthis information in one page.
So that is, that is the goal,that is the end goal that we have.
How can these dashboards help?
In so many ways.
So the first thing, as I mentioned,is having a place, having a central,
having ev all this data in acentral place that goes a long way.
Uh, it helps to see everything in oneplace, and it makes life easier for
every single contributor and not justcontributor anybody who's interested
in WordPress, who wants to see what,where the progress of the project lies.
Having a dashboard immensely helps.
And the other thing is real time tracking.
So I'm a con, I've doneall sorts of contributions.
I've done events, I've done translations,uh, I've helped out with big projects.
But sometimes when I translate, I, I'm,I'm, I'm a gt of a language called Malal.
Sometimes when I translate, I amnot able to see like, what is the
number of strings that I've done.
I mean, it helps to seethat right in one place.
So.
A dashboard could have real time tracking.
And in my dashboard in, if there'sa dashboard, I could take a personal
profile, which shows what is thenumber of translations that I've made,
what, what happened, what is happeningwith each project at the same time,
maybe, maybe a bulk of contributorsare working on a particular project.
What does, how much progresshas that project made?
So real time tracking goes a long way.
Personalized stats, again, theexample that I mentioned before.
If we could provide every singlecontributor detailed personalized
stats embedded to their WordPressprofiles, how cool would that be?
I mean, imagine if you're a contributor.
You take your profile, you see detailedcharts and graphs about your conversion.
You started in 2016 or 2017, or even 2023.
And uh, this is the number ofpatches that you've made, the
number of comments that you've made.
How cool would it be to see allof these things in one space
and, uh, organization reports?
This is important.
So if you're familiarwith five for the future.
Currently, if you look at a company'sprofile and fight for the future, it just
shows, uh, the company's contributors,the teams they're contributing to.
That's it.
But what if when you open acompany's fight for the future
profile, it shows the contributionsthe company's employees have made?
You know, that help that, that'sgonna help that company immensely
because they can see the impact of thecontributions that they're making and.
It is going to inspirecompanies to contribute.
Currently it only lists the hours, butare the companies actually contributing
to the hours that they've pledged to?
For example, like I could right nowgo ahead and pledge 20 hours, uh, for
a X, Y, Z company that I'm making andmake no contributions and it'll, it
would still show up in the profile.
But when those hours are backed byactual data with visualizations, how
cool and how powerful would that be?
Uh, now the benefits actually extend.
Uh, there's so many, so many benefitsthat, uh, you know, these contributions
have, uh, for the community.
You get, you get so much morevisibility into contributions.
So like as a community, as a WordPresscommunity, when we, when, when there are
contributions, when there's a dashboard,you get to see into more detail what
the number of contributions are, whatis the impact that's having, and.
I personally believe that havingmore data provides clarity
and it improves motivation.
So in my case, like I'veactually tried doing this a bit.
Um, so when, when I, when my, when,when my contributions are visualized,
like it really shows the impact ofthe contributions that I'm making.
I mean, I may have made, I have, I mayhave done so much work, but when it's not
visible, it doesn't really motivate me.
But when it is visible, it motivates mepersonally to contribute more And, uh.
When, when all this contribution isavailable in data in a, in a very clear
visual form, it helps collaborationsignificantly, uh, in so many ways.
For example, uh, inverters, we areseeing so much crossing collaboration,
especially around releases.
So if you look at the, the latestrelease that just came out LA last
year, 6.7 versus 6.7, we had Mark, wehad, uh, we had polyglots, we had uh,
documentation, we had tests, we had code.
We have multiple teams collaborating.
So these teams can only collaborate.
When there is a clear view ofthe need of each team, right?
So when that need is made visible in adatadriven way, it really helps folks
and for make teams, it helps immensely
when all the data is out there,you can make data-driven decisions.
So sometimes teams make decision arbitraryabout, for instance, like when, when
they're shipping a new feature, um,they, they don't really, they cannot
really track the number of bugs.
Uh, I mean, of course they can, butit could be a very manual process.
But when there is a dashboard, whichreally shows here are the number of issues
in this and, and what is the resolutionrate in, uh, in this component or in this,
uh, GitHub, in, in this GitHub repository.
So like, things like that go a long way.
And as I'm, I've been mentioning aboutthe benefits of the five organization,
so I'm not gonna repeat it, but.
Um, like, but just to share a verysmall point, when I fi fight for the
future companies, they, they, they,they're actually spending the revenue
they're making back into contribution.
So it is an investment.
I personally believe that everysingle contribution is not charity.
It's an investment even forindividual contributors.
I honestly, very strictly believe inthat because like we are giving back
to WordPress, but it is an investment.
You're investing in your own future.
So when a company makes an investmentinto WordPress, they wanna see
return and what is the return?
It is the impact of thecontribution that they're having.
So when we have a dashboard,it clearly shows the impact.
And, um, even though the pointis for organizations, uh, on
identifying high impact areas, Ithink it applies to individuals also.
So there are many contribution areaswhich have relative, which could have
relatively low effort and high impact.
So having dashboards, it's really,really brings out those areas forward.
So, uh, there is a principlecalled the Pato principle.
It's called a 2080 rule.
Which means 20% of effortleads to 80% of impact.
So in WordPress and as, as withalmost any other project, such, uh,
such things are extremely valuable.
So having dashboards help us identifythe 20% that will move the 80%,
and it'll be immensely helpful.
We, we will see growth manifold inWordPress having a dashboard like this.
Uh, I also want to share somehistory, uh, about our project.
So, and, uh.
Uh, this is what we've builtactually, uh, this, uh, this post
is from September 12th, 2024.
This is essentially the project.
It's a, it's a, we will be sharinga link to it in the final slide.
Uh, so we, you know what?
We eventually built the dashboard.
Uh, it's a very manual dashboardand I wanna very quickly share
some history as to how we did it.
So this all started inwebcam Europe 2023 at Athens.
Uh, so in the q and a,our, uh, CEO, our um.
Not the C of automatic, but theco-founder of WordPress, uh, Matt,
he emphasized the need for projecthealth dashboards that really came up.
So folks are very much inspired by it.
There was a post in the meta blog, uh,about it and, um, multiple individuals,
Cody Robertson, uh, now Kota, myself.
So we all sort of formed like an, uh,informal working group and a bunch
of other contributors also joined in.
We published a post exploringwhat could dashboards look like?
How, like, like a first exploration.
In the first year, in 2023, wedid not have a lot of movement.
But, uh, around January, 2024, uh,nco, the very enterprise pricing
NCO Ano, who you might know asthe, uh, in fact the first global
leader of, uh, webcam Asia 2023.
She explored and found a toolcalled bia bia, uh, will, will
explored more to it, is what I isgoing to talk about that in a bit.
Uh, we use the tool to setup some visualizations.
We got some data.
Um, and we, uh, but the, the challengeis that it's a very expensive tool.
Uh, it, the cost is around athousand euros per, per month.
Uh, but we still a automatically,generally, generally funded that
tool and we use that tool tostart looking at some information.
So, together then, uh, more, a moreformal working group was set up by
Courtney Robertson later, and, uh,there was, there were in, in May,
2024, uh, there were a lot of projecthealth discussions that were held.
And so much ideas were collected.
So the main aspects that we focusedon was what should we meta measure,
what are the metrics or what arethe key process indicators that
we should measure in dashboards?
And finally what we, but the, thechallenge we realized was that,
was that the BIT dashboard that wascreated, it is private it at this,
in the shape that we have today.
It needs a lot more customization,a lot more work to be made public.
But what we decided to do in the Interbus.
We, we decided to collect allthe data from this dashboard and
publish this in a set of blog posts.
So we have, as you can see inthis post four uh sections.
We have a core team dashboard.
We have a community team dashboard.
We have a training teamdashboard, and 6.6 status six.
So this was published in September 20, 24.
And back then, purpose 6.6was the latest release.
So we published, we collectedall this information.
We have separate pagesfor all these dashboards.
We published this, so this wasthe first version of the project.
We shared this as an experimentand we put it out for feedback.
So this is what we have today,and I'm gonna hand it over to
Otta to walk you through bge.
So I, as I mentioned, BGEis a tool that we have.
Otta is gonna walk you through it.
So it's an excellent tool.
And, uh, take a look atwhat she has to show.
Um, Azar was, um, was anticipatingwe started use experimenting
with this tool, which we loved.
And by the way, we're notaffiliated to this tool.
But, uh, we explored it and wethought it was a great first step
because as you will see later inthe, uh, in the blog post, what we
got from now are static dashboards.
Our goal is.
To make sure that we can have, um, uh,an interactive tools that we can use.
And so the first step was to explore, um,the option that this Vitoria could offer.
Vitoria is a dashboard tool createdto support open source communities and
projects, and it has the ability topull data from a variety of, of sources.
For these tests, we only activatedto pull information from GI GitHub.
So this is why, uh, our explorationwas limited to specific teams.
And, um, we identified benefits,advantages, and also challenges.
One of the challenges Imentioned is the price.
It's not a free tool and, uh, asmany for each new source that we want
to add, the price gonna increase.
This is also one of the reasonwhy we kept the experimentation,
uh, limited to one source.
Um, one of the best feature that thistool provides is the ability to connect
the contributors with the company theywork for or that sponsor them or, uh,
if they are self sponsored contribution.
So this is also can give an ideaof the percentage from like where a
specific project is getting the support.
Um, it also give the possibility to updatethe organization you are affiliated with.
So there is almost endless, endlessopportunities to have information
about, uh, your own contributions, yourcompany contribution, and the project.
Overall.
Um, one of the limitation is that,for example, in the case that, uh, in
the case of company affiliation, uh,there is a lot of minor work to do.
So we have a right side and, uh, a hardside and challenge to, to overcome.
Um, eh, we thought thatthe best way to, um.
Explain you what we've tried to do,what are the potentials, the limits,
and also hopefully, uh, help youkick off these thoughts in your hand
and then come back to us and keepdiscussing on what we want to achieve.
Was to, uh, show you, uh, I prepareda very quick tour of the tool and
it's gonna be just two minutes.
And so I hope that you canhave a, a better idea of this.
What, which one should be, sorry.
Oh,
sorry.
We need a little bit about to play.
We have a video.
Uh, I'm gonna try, uh, help hopeto get the systems team to play it.
Yeah.
Yep.
Mm-hmm.
Sorry.
In the thank you in the rehearsal.
Uh.
It work, but as always happen.
Okay, so this is the main, uh, maindashboard that where you open the tool.
And so you can see thereare different views.
You can create custom views.
You can use uh, thousand of filters.
You can maximize panels, you candownload information from them, and.
You can customize the view as you need.
So this is what we were working on.
You can decide what information you wantto, you want to highlight in the overview.
And as you, as you probably noticedearlier, there was a specific
curtain overview that she, she used.
To, to experiment.
You can filter by, um, day trend.
You can go, uh, up to 10 years ago,and you can create custom, uh, custom
ranges for any type of data you wantto see, and you can eventually also
save it and keep a link for the future.
There are different panelsthat you can explore.
In this case, it's all aboutGit and Git contributions,
as we mentioned, but you can.
You can create whatever youneed, including, uh, custom
filters and save labels.
So at any time you need to visualizejust a specific filter information.
You have it handed.
And you can, uh, you have differentoption to modify your, your query
and to share it with others.
Of course, you can, uh, easily, uh,change anything related to filters and
including creating these custom filtersthat you can share with the other
people in the project or your employee.
Uh, anybody who need tocheck it with the link.
Whenever you don't need themanymore, you can just delete them.
Um, so this is, uh, this isat glance how it could be.
It doesn't have to bethis way, this is in here.
There's a lot of information,but imagine, um, having the
possibility to use a similar tool.
You can, you can createwhatever you need to.
So I'll hand it back to Ari then.
Okay, thank you, SOTA.
Uh, so what you literally sawwas the tip of the iceberg.
This tool is amazing.
There's so many insights.
The only, only limitation hours,it only looks at the entire
WordPress, GitHub organization.
So WordPress as a GitHub organization,github.com for slash WordPress,
which has, uh, I think around 82,no more than a hundred rep actually.
So it covers all of it.
But, uh, that's it.
It does not look at track.
So, as you all know, WordPressdevelopment takes space to SVN and we
have a back tracking tool called Track.
It does not, we dug acan connect to Slack.
We not used uh, slack yet, butit, it still has so much features,
uh, which we can explore.
Now, I'm gonna quickly go throughthe insights that we learned, uh,
through the, uh, through the process.
So the first thing is, yeah, um.
So we, as you, as I shared earlier,we had the WordPress 6.6 dashboard.
This is one of the biggest insights thatwe learned from looking at WordPress 6.6.
Now, to note, we did not use BIA for this.
We have the props list.
We use the props list todo some data analysis.
That's where we used toget this information.
So as you can see, 23 point.
26 point.
So of all the contributors, Inus6.6, only 26.5% are sponsored.
That is their, their, uh, part ofthe time somebody's paying for them.
They're doing contributionsin their work time.
73.5% of all workers contributionsare done By volunteers, I mean
a hundred percent volunteers.
Now, if you look at countries,84 contributors come from the
United States and 69 from India,23 from Bangladesh, 13 from Japan.
And as you can see, Asia, I mean,we are at World Camp Asia here, so.
A majority of WordPress contributionsare actually coming from Asia.
So big kudos to all Asians.
Yeah, big kudos to World Camp Asia.
Asian contributors have done fantasticjob with all WordPress releases in, uh,
last year, which is 6.5, 6.5, 6.6, 6.7.
But yeah, this clearly shows howAsia has made a big presence in
Word in WordPress conventions.
Um, and um, this is alist of the companies.
I mean, some of these bubbles are smallbecause, uh, but there are so many
companies out there which concrete.
Uh, there are some small companies,so this com small company called
Loose Inc. It is one contributor.
He's from Japan.
His name is Aki Ano.
So that is just one personwith 2 74 contributions.
Uh, but yeah, there are so manycompanies who sponsor their contributors
to make contributions and big, bigkudos to all of them, uh, for doing
all they can to support WordPress.
Uh, now this is a very interestingchart which we picked up from.
In fact, I, uh, collected moredata for this presentation.
So.
All the charts that you see,were from the, our original post.
This post, this is different because this,uh, we pulled this data for until 2025.
So like all this, the data thatyou're seeing is as of January, 2025.
So this is the number of attractivedevelopers and tors getting inactive.
So as you can see, thischart is fairly good.
So it shows that WordPress,the WordPress was, is healthy.
We have, we've always beengetting new contributors.
So the blue line is new contributorscoming in, whereas the red
line is contributors leaving.
But as you can see, this chart towardsthe end has, there's a spike, there's
more contributors leaving and, uh,less contributors coming, which
is probably because of automaticpossible contributions, because
automatic was a big contributor.
So that is connected to thespike in, uh, in, uh, January.
But other than that, verushas been very healthy.
We've always had more people comingin and, uh, almost the same amount of
people coming in and leaving, whichis very, which, which is a sign of
a very healthy open source project.
And this is a community structurediagram that we've pulled from bega.
So there are three types of contributorsthat's, uh, casual, that's, uh, regular.
The score casual contributorsare contributors.
Who make very small contributions andjust leave Core are the very active folks.
So these people, they are,they are there, they're making
the most active contributions.
And regular folks are people whomake some contributions, who,
who, who are there, but, uh, whomake occasional contributions.
Uh, but they're not, they're,they're, they're there,
they're making contributions.
They, they, they contribute about about40% of the contribution contributions, but
whereas the core people, they contributearound 80% of the contributions.
So.
Again, this shows a very healthy set ofcontribution, contribution contributions.
We have an even distribution between thenew people coming in and, uh, regular
contributors and cashew contributors.
So there's a lot of open sourceliterature on how a healthy
open source project should be.
So if any open source story looks atthis site, it shows that WordPress is a
very, very healthy, open source problem.
Uh, and we have, uh, this final slide thatI wanna quickly talk, walk you through.
So it shows the, uh, the growthof contributors over time.
So again, this start is, uh, this startis actually until September, 2024.
Uh, when we did the project.
I'm, I'm taking thisdirectly from the project.
Um, yeah.
So it shows that.
Our contributor growth has been very nice.
Like you can see, you can see spikeslike, uh, so around 2 20 18, that
is when Gutenberg started coming in.
So you can see the spikearound alongside Gutenberg.
We've had a very active list of,uh, contributors being active
and, uh, uh, like the spike,the numbers are always good.
So you, you see spikes around covid.
So this, uh, spike around 2021and that's very much connected to
Covid and the spike around 2019.
That's also very much connected to Covid.
So in short, all these numbers, theanalysis that we have, the insight that
we have this, if I were to summarize inone sentence, it is that WordPress is a
very, very healthy, open source project.
We have a very, uh, good distributionof active and, uh, active quantum.
With us.
As I was mentioned at the beginning,we were not alone in this dream, so we
really wanted to use also this opportunityto, uh, shout out the other people
who mainly helped with make this ideabecoming a, a beginning of a project.
And so, uh, we want to thank CourtneyRobinson and now Kurt Ano for being.
Such a massive help.
NACO was the first one findinga tool who could be a good
fit for the first exploration.
She explored her first and thentaught us all how to, how to use it
and how to make the best out of it.
And then K was pivotal intobringing this beginning of idea.
To the broader community.
She organized, uh, brainstorming sessions.
She was pivotal in helping usreaching everyone in the project.
So, uh, thanks to them, uh, wewere able to work on this and come
here and share it with you all andhopefully, uh, moving forward with
more of you in the upcoming months.
Yes.
So, uh, the road ahead.
Um, I wanna share a,well, how do I share it?
Well, this project that we'vedone, it was done as an experiment.
So what we essentially didwas we used pge, we manually
collected data, we published it.
Uh, we've honestly not done anywork on it ever since because
a lot of things have changed.
Uh, and I, uh, and Courtney and now go, weare not working on this project right now.
So in short, we published this.
We got some feedback.
And the, the hope was to use that feedbackto continue building forward, but we've
not done, uh, work on it after this,which we, which, which still brings the
question what, what lies ahead, ideally,yes, we have a lot of hopes and plans.
The, the ideal goal towards this, as Ishared earlier, would be to automate,
to build an automated dashboard.
So the, the idea that wehave, we already have.
It's slightly expensive to maintain.
Uh, automatic is paying for it, butprobably we could use help there.
Uh, and it only measures, uh, GitHub.
We, what if we could bring it to trackand what, what if we could open it up?
So in short, the ideal goal wouldbe to build a fully automated
dashboard completely automated.
No manual intervention needed, nomanual publishing of data, like what we
did in the make project block needed.
That is, that is the goal.
And.
How could, how cool would it be to haveit integrated into workers' profiles?
So that is where it isheaded, but currently we are
not working on it right now.
Um, but yes, the eventual hope is that
once we have a dashboard likethis, it could go a long way
in, as we shared earlier.
In improving WordPress assets.
So having a data driven approach, havingmore data out there, having it out in
public, having very clear insights onthe various aspects of pro of WordPress,
WordPress contribution, WordPressdevelopment, because this is the, this is
the world's biggest open, I wouldn't, Iwouldn't call it WordPress world's biggest
open source project, but at least the, theworld's biggest content management system.
So this is the world's biggestcontent management system.
It's a huge open source project.
We could all use the insights so.
Let's to wrap things up, I wannaask you all a question and, uh, how
should the word contributed dashboard?
What do you think?
I mean, we shared a demo.
What we have is a demo, uh, which we did.
As I said, we are not working on it rightnow, but this is an important project.
We still believe it's an importantproject and it needs a lot of work.
It needs, and it needs contributors.
It needs ideas, so.
And that's, that's why wedecided to do this stuff.
We wanted to share about ourpro our work with you, and we
wanted to get your feedback.
What should the WordPress, uh,contributed dashboard be, and how
should the WordPress contributeddashboard of the future look like?
So let us know in the comments.
This QR code links directly to the makecorpus, uh, blog post that we published.
Isda, do you wanna share something?
Yeah, I, I would love to add,if any of you is interested in
the project, want to jump on it.
Uh, there's no need to waitfor Harry, myself, Courtney, or
anybody else to pick it up again.
Just please feel free to ping us andtell us, Hey, I want to work on this.
I want to bring it forward.
Uh, I have ideas.
I have, uh, maybe other.
People, the, uh, who want to help.
So, uping us, we give you all theadditional context information that
you may need, and we say, yeah, westill completely believe in this,
and we can't wait for also us tocome back and help make this happen.
So now you've, you've seen whatwe've done, uh, inside limitations.
Please, any idea is more than welcome.
Drop a comment in that post.
Um.
Let's try to make it happen together.
Thank you all so much.
Thank you.
Thank you so much.
Uh, if you have any questions, pleasefeel free to ask us and we would love,
love, love contributions from you.
Uh, again, I mean, building adashboard seems very technical.
Trust me.
It doesn't need to be that way becauseItta and I, we are not developers.
If we could do this, anyone could do this.
And even if you do not have thebandwidth to do it, you could
probably even share ideas.
We need ideas.
Like, I'll give you some questionsto think about if you want.
Uh.