| Info | ||
|---|---|---|
| ||
A Plenary session implies that all attendees are expected to attend due to either their relevance or importance to LFN as a whole. This usually means that no other sessions will be running in parallel. Topics may be reclassified as "General Interest" by the Program Committee to run as a parallel session if deemed appropriate. |
Topic Leader(s)
...
| Excerpt |
|---|
Bazaar vs. Cathedral Should LFN communities be building functioning platforms or build components that work in multiple environments? How can we build the RI2 Lab for community adoptability? An RI2 implementation id being constructed in UNH. How can the Community take advantage of it? Ensuring Stronger Collaborative efforts:
How do we validate the value created by our projects and how do we get more adoption and contributors? LFN documentation self help group/ Cross Community Documentation best practices Community release management. How to learn it from projects already doing it? |
Topic Overview
Slides & Recording
| Info | ||
|---|---|---|
| ||
Please indicate your session type in the blank space below and then remove this Info field.
LFN Staff may elect to publish some videos to YouTube. Please indicate here if you do not want your session to be published to YouTube. |
Agenda
Awesome presentation
- Point 2
No recording captured.
Minutes
Beth Cohen asked who is using the Anuket Assured program and if you are not, why?
- Alla Goldner For those outside of the community there may be some level of uncertainty.
- Ranny Haiby Sylva is developing their own RA but features Anuket.
- There may be a disconnect between the test bed and user CNF/VNFs
- Alla suggested that additional developer diversity is needed.
- Robert echoed this statement. When new projects come in, they siphon development resources away from the projects that are more mature and stable.
- More attention needs to be paid to what that new project is going to do and how it will affect the existing projects
- Ranny Haiby I don't see developers jumping from project to projects, but there is certainly some shifts in investments based on the needs of their
- Robert Varga Resources focus follows interest. When new projects are launched, developers often shift to the "shiny object" so organizations have an opportunity to be engaged.
- Alla Goldner When projects have a limited development pool, we should look at re-launching them like what we did with OPNFV rather than starting a parallel project that may siphon resources or kill off more mature projects that could be in production.
- A general discussion ensued regarding user tracking. In open source it has been a challenge for projects to identify who is deploying the code. This doesn't seem to be as bad of an issue tracking deployment in the OpenStack community.
- Robert Varga I don't think it's about getting rid of the freeloaders, but rather building engagement. There are a number of projects that are using ODL, but they don't participate in development, marketing or otherwise.
- Ranny Haiby Based on my experience in the past, If someone wants to have a successful deployment of an open source project, they will eventually need to start contributing to the community or their deployment will collapse under the weight of trying to maintain their fork.
- Ildiko Vancsa We should avoid using the term freeloader as it is not really applicable in open source. It will probably hurt us in the long run. At the same time, we need to do a better job of education to ensure that companies and organizations understand what open source and open collaboration means and how to leverage that. There is also a point that we need to recognize that in the telecom vendor segment often the teams who start getting involved in the projects are the research teams. When a new project comes out, they will leave to work on the new shiny so they can understand what the new innovations are all about. At the same time, the companies' products often still integrate and depend on the more mature projects, but the product development teams most often don't participate in the open source communities to develop and maintain those components (IPR issues, lack of understanding about open source, business model issues, etc).