Looking for members interested in helping with the Annual Ecosystem Report

[edsadr]

For context, please take a look at: https://github.com/openjs-foundation/cross-project-council/tree/main/proposals/incubating/ANNUAL_ECOSYSTEM_REPORT

To make this proposal a reality, we would need a new collaboration space focused on creating the annual ecosystem report, which ideally should be done at the end of Q3 2024, and in the process, define all the guidelines and methodology for years to come.

We will follow the process described here: https://github.com/openjs-foundation/cross-project-council/blob/main/collaboration-spaces/COLLABORATION_SPACE_PROGRESSION.md#ii-collaboration-space-proposal-process, so far working with @anfibiacreativa to make this happen.

We are currently seeking CPC members who are interested in contributing to this initiative. Some of the responsibilities will be:

• Participate in defining the scope, objectives, and methodology for the Annual Ecosystem Report.
• Contribute to data collection, analysis, and interpretation.
• assist in drafting, reviewing, and finalizing the report.
• Engage with the community to gather feedback and disseminate the findings.

[tobie]

Just skimmed through this. It looks intriguing; I'd love to understand the ecosystem better! My key questions are:

1. What are the goals and desired outcome of this project?
2. How does the proposed solution help meet those goals?
3. What other options are there to meet those goals and why was the proposed solution picked over them?

[mhdawson]

Sounds interesting to me.

[edsadr]

Hey @tobie

Here are the answers:

1. What are the goals and desired outcome of this project?

The first goal is to create a standard process to get the feedback and thoughts of the end-users of the JS ecosystem. The second goal is to create a standard report of that feedback and thoughts from the end-users, including also the latest news, roadmaps, and activities for the OSS projects associated with the foundation.

We are currently lacking both mechanisms, and I think it is important for the foundation to work in that direction to foster a more connected relationship with our users.

2. How does the proposed solution help meet those goals?

The proposal will work to create the process from scratch to produce the instruments to provide the two-way communication channel with end-users and will establish a repeatable project for years to come.

3. What other options are there to meet those goals and why was the proposed solution picked over them?

This is the first proposal I am aware in that direction, ideas are welcome.

[tobie]

Thanks for answering my questions, @edsadr. I really like the idea of getting more info about our projects and how they're used. Some follow-up questions (to answer here or takeaway as input to this work, as you see fit):

4. In what way will this effort differ from State of JavaScript, Stackoverflow's survey, or State of Open Source survey?
5. What additional insights do we hope to gather?
6. How actionable will those insights be? Do we have buy-in from projects to actually consider end-user inputs? Are we planning on building end-user groups for certain projects? Or the foundation as a whole? Do you know of end-user groups in foundation projects or elsewhere (e.g. CNCF) and have you talked with those projects? Etc.
7. The initial project talks about gathering data from projects (notably roadmaps). Is this still something you're considering?
8. Beyond roadmaps, I'm fairly concerned about project sustainability and maintenance. Are these topics you're considering gather information about?
9. There are ongoing security efforts/inventory. Are you thinking about leveraging and surfacing this information too?
10. Have you considered data analysis tools like Bitergia to help with this?

[italojs]

amazing project do you already have a to-do list or some specific topic to discuss?

[edsadr]

Hey @tobie

Thanks for your interest and insights here, as we explore the potential of this initiative. You've raised several important points that are part of the work of the Collaboration Space needed for the initiative, However, here are my takes on each of your questions:

4. In what way will this effort differ from State of JavaScript, Stackoverflow's survey, or State of Open Source survey?

Our effort aims to complement existing surveys like the one you mention by focusing on the unique aspects of the OpenJS Foundation projects and their usage. We hope to delve deeper into specific areas that are relevant to our community.

5. What additional insights do we hope to gather?

We aim to gather insights that are directly applicable to our projects, such as user needs, usage patterns, and areas for improvement. This will help us tailor our efforts more effectively to serve our community.

6. How actionable will those insights be? Do we have buy-in from projects to actually consider end-user inputs? Are we planning on building end-user groups for certain projects? Or the foundation as a whole? Do you know of end-user groups in foundation projects or elsewhere (e.g. CNCF) and have you talked with those projects? Etc.

Ensuring the insights are actionable is a priority. We plan to engage with project teams to discuss how they can incorporate end-user feedback into their roadmaps. The idea of being a more user-friendly bridge between end-users and projects is something we should explore further.

7.The initial project talks about gathering data from projects (notably roadmaps). Is this still something you're considering?

Gathering data from project roadmaps is definitely on the table. This information will be invaluable in understanding the end-users points of view on the direction of our projects and identifying areas their input can be most impactful.

8. Beyond roadmaps, I'm fairly concerned about project sustainability and maintenance. Are these topics you're considering gather information about?

Understanding the challenges projects face in these aspects will help us support their long-term sustainability, something that we really need to include in the initiative for sure, imagine if we could gather data on the challenges projects like Express faced during previous years, we could act early to prevent cases like it.

9. There are ongoing security efforts/inventory. Are you thinking about leveraging and surfacing this information too?

Leveraging and surfacing information from ongoing security efforts is a great idea, not included in the original proposal but something we could definitely consider.

10. Have you considered data analysis tools like Bitergia to help with this?

We have not yet considered specific tools, but we will definitely need to explore the best tools for the job, is a key task for the collaboration space.

Your questions underscore the importance of a collaborative approach in addressing these topics. This is precisely why we are looking to create a collaboration space where diverse perspectives can come together to develop a comprehensive proposal.

Would you be joining this space? I think your insights would be invaluable in shaping the initiative.

[edsadr]

Welcome @italojs

Thanks for your interest, this issue is for getting people to signup for the new collaboration space. If you want to join this effort, I would recommend you start attending the CPC meetings and once the collaboration space is created, we will invite you to attend the space meetings, there we will plan every task to execute.

[tobie]

@edsadr wrote:

Would you be joining this space? I think your insights would be invaluable in shaping the initiative.

I like where you're taking this. I'll do my best to show-up but won't be taking a leadership/driving position (I just don't have the time).

[edsadr]

Ok, I will be requesting the creation of the Collaboration Space today. I will add everyone involved in this issue as part of the initial group and will use this issue to update on the progress.

Thank you, everybody, for your interest.

[PaulaPaul]

Hello! @edsadr I'm interested in joining the collab space - Thanks-

[mhdawson]

I'm interested in joining at least the first few calls to better understand the work the space will do.

[tobie]

@bensternthal / @edsadr to workout next steps together. Formal CPC approval through PR adding the collab space to the repo.

[edsadr]

The PR is this one: https://github.com/openjs-foundation/cross-project-council/pull/1282

once we get the repor, I will add few issues there, and we will move the discussions, the first step will be to find a space to meet and start the initial planning

[joesepi]

This is moving forward