Jessie & Matt
Thank-you for raising and elaborating on the topic of how CNCF helps projects.
Personally I do not want "CNCF could do more to help projects" to be chiselled on my gravestone. I think the TOC, Contributors and project leads can ALL show some direction here, and I think we have to do so.
And so - Jessie & Matt & anyone else!
Please could you help me & Chris do something more about this.
Let's (again) make a list of what we think Incubated & Graduated projects really need, by talking with the project leads & others. This list needs to be in a shared public doc. Not everyone wants the same things, but there are themes.
Such as: * docs & project management * community management * project services (hosting, CI, etc) * github wrangling * community / contributor summits * AR/PR help (esp: for projects that don't have 1-2 companies driving them) * maintainer psychotherapy & creche ;-)
WDYT?
a
toggle quoted message
Show quoted text
Then when those projects need help with things the foundation can offer, money for infrastructure, a place for shared IP it seems like it would be obvious that they should be projects in the foundation, of course they need to qualify etc.
Beyond neutral IP, I agree this is the most important thing the foundation provides, and IMHO CNCF does not do enough of it (there are so many things that high velocity projects need I could go on and on and on). Unfortunately, this is the area in which decisions will need to be made. There are limited funds and they will need to be allocated across the increasing portfolio of projects in the foundation, so clearly some decision criteria will need to be developed (whether based on graduation level or something else) to decide how funds are allocated and for what purpose (and unfortunately this in and of itself will involve politics).
I'm happy to see this conversation happening, as I ultimately I do believe that some level of choosing "favorites" is going to be required for the foundation to realize its full benefit to its most popular member projects.
--
|
|

Chris Aniszczyk
If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
toggle quoted message
Show quoted text
On Thu, Sep 20, 2018 at 2:08 AM, alexis richardson <alexis@...> wrote: Jessie & Matt
Thank-you for raising and elaborating on the topic of how CNCF helps projects.
Personally I do not want "CNCF could do more to help projects" to be chiselled on my gravestone. I think the TOC, Contributors and project leads can ALL show some direction here, and I think we have to do so.
And so - Jessie & Matt & anyone else!
Please could you help me & Chris do something more about this.
Let's (again) make a list of what we think Incubated & Graduated projects really need, by talking with the project leads & others. This list needs to be in a shared public doc. Not everyone wants the same things, but there are themes.
Such as: * docs & project management * community management * project services (hosting, CI, etc) * github wrangling * community / contributor summits * AR/PR help (esp: for projects that don't have 1-2 companies driving them) * maintainer psychotherapy & creche ;-)
WDYT?
a
Then when those projects need help with things the foundation can offer, money for infrastructure, a place for shared IP it seems like it would be obvious that they should be projects in the foundation, of course they need to qualify etc.
Beyond neutral IP, I agree this is the most important thing the foundation provides, and IMHO CNCF does not do enough of it (there are so many things that high velocity projects need I could go on and on and on). Unfortunately, this is the area in which decisions will need to be made. There are limited funds and they will need to be allocated across the increasing portfolio of projects in the foundation, so clearly some decision criteria will need to be developed (whether based on graduation level or something else) to decide how funds are allocated and for what purpose (and unfortunately this in and of itself will involve politics).
I'm happy to see this conversation happening, as I ultimately I do believe that some level of choosing "favorites" is going to be required for the foundation to realize its full benefit to its most popular member projects.
--
-- Chris Aniszczyk (@cra) | +1-512-961-6719
|
|
Jessica Frazelle <me@...>
Pay the maintainers and high contributors who don't have other means to make money.
toggle quoted message
Show quoted text
If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
|
|
Jessica Frazelle <me@...>
Bounties on bug fixes comes to mind.
toggle quoted message
Show quoted text
Pay the maintainers and high contributors who don't have other means to make money. If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
|
|
A FAQ of practical knowledge to share between projects.
A mentor program to help people who have to lead projects that are part of the CNCF.
It’s different to lead an open source project on your own or as part of a company than it is under the CNCF. When I do something on my own or as part of a company I’m not vendor neutral. As part of a company I have can get to their policies. In the CNCF keeping vendor neutrality isn’t always obvious and we don’t have easy self service access to all the CNCF/TLF policies.
This is all with my non-technical hat on and wanting to scale the org. As the number of projects go up I don’t see how Dan, Chris, and co scale without more self service and automation.
toggle quoted message
Show quoted text
If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
|
|
Cannot +1 this enough. There are folks out there donating their time/sweat to projects who have to rely on pittance/donations/freelance work. This foundation has more than enough means to provide a decent sustainability bonuses/stipends to these folks.
Best, Ruben
toggle quoted message
Show quoted text
Pay the maintainers and high contributors who don't have other means to make money. If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
|
|
Bounties on bug fixes comes to mind.
+1. Bug bounties, pay for regular third party security audits, pay to have a white hat on staff doing security work on behalf of projects full time, etc.
Pay the maintainers and high contributors who don't have other means to make money.
Yes. For certain types of projects such as critical libraries where it's very difficult/impossible to make money maintaining, CNCF should consider adopting those projects and helping pay maintainers to work on them, even if part time.
Even for projects in which there are other means to make money, some of us don't necessarily *want* to make money that way. We do it because, well, that is how we make money. There are real benefits for an organization like the CNCF providing fellowships to allow maintainers to remain neutral. I've written more about this here for those of you that haven't seen it: https://medium.com/@mattklein123/the-broken-economics-of-oss-5a1b31fc0182. The recent Linus salary discussion complicates discussion of this topic which is unfortunate because I think it's one that we increasingly need to have, but hopefully as some time passes we can come back to it.
Such as
All of the things Alexis points out. I would like to see more work on improving the GH experience around things like DCO, bots, issue management, CI, etc. I suspect there is easily a full time tooling job across all of CNCF. CI and negotiating with the vendors for the right amount of concurrency and machine types takes a lot of time. More dedicated help with docs perhaps by sourcing, hiring, and nurturing multiple full time tech writers. Basically, all of this. Bounties on bug fixes comes to mind. Pay the maintainers and high contributors who don't have other means to make money. If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
--
|
|
Shannon Williams <shannon@...>
Excellent point Jesse and Ruben – this is something I know I’d love to see the TOC bring to the Governing Board before our next meeting in Shanghai, Chris.
Best Regards,
Shannon Williams
Rancher Labs
shannon@...
+1 650-521-6902
toggle quoted message
Show quoted text
From: cncf-toc@... <cncf-toc@...>
On Behalf Of Ruben Orduz
Sent: Thursday, September 20, 2018 8:44 AM
To: me@...
Cc: Chris Aniszczyk <caniszczyk@...>; CNCF TOC <cncf-toc@...>
Subject: Re: Helping Projects (was Re: [cncf-toc] What's the point? (or,"What's the Emperor wearing?"))
Cannot +1 this enough. There are folks out there donating their time/sweat to projects who have to rely on pittance/donations/freelance work. This foundation has more than enough means to provide a decent sustainability bonuses/stipends
to these folks.
Pay the maintainers and high contributors who don't have other means to make money.
If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
On Thu, Sep 20, 2018 at 2:08 AM, alexis richardson <alexis@...> wrote:
Jessie & Matt
Thank-you for raising and elaborating on the topic of how CNCF helps projects.
Personally I do not want "CNCF could do more to help projects" to be chiselled on my gravestone. I think the TOC, Contributors and project leads can ALL show some direction here, and I think we have to do so.
And so - Jessie & Matt & anyone else!
Please could you help me & Chris do something more about this.
Let's (again) make a list of what we think Incubated & Graduated projects really need, by talking with the project leads & others. This list needs to be in a shared public doc. Not everyone wants the same things, but there are themes.
* docs & project management
* project services (hosting, CI, etc)
* community / contributor summits
* AR/PR help (esp: for projects that don't have 1-2 companies driving them)
* maintainer psychotherapy & creche ;-)
Then when
those projects need help with things the foundation can offer, money
for infrastructure, a place for shared IP it seems like it would be
obvious that they should be projects in the foundation, of course they
need to qualify etc.
Beyond neutral IP, I agree this is the most important thing the foundation provides, and IMHO CNCF does not do enough of it (there are so many things that high velocity projects need I could go on and on and on). Unfortunately, this is
the area in which decisions will need to be made. There are limited funds and they will need to be allocated across the increasing portfolio of projects in the foundation, so clearly some decision criteria will need to be developed (whether based on graduation
level or something else) to decide how funds are allocated and for what purpose (and unfortunately this in and of itself will involve politics).
I'm happy to see this conversation happening, as I ultimately I do believe that some level of choosing "favorites" is going to be required for the foundation to realize its full benefit to its most popular member projects.
On Wed, Sep 19, 2018 at 10:23 AM, Jessica Frazelle via
Lists.Cncf.Io <me=jessfraz.com@...> wrote:
Yeah that was what I meant with shared IP.
I think there are ways to limit the effect of gamification of the
system and I think you all have done a great job of this so far
especially with the format for sandbox projects....
I think this is more a culture problem in that, if people see the
leaders of projects and in the community pushing for more projects to
be added to the foundation at a very past pace then we have lost a
culture of "making the best tool of high quality for the job" and we
lost a culture of innovation.... we merely have the culture of
"winning". Which I am still unsure as to what people seek to win but I
digress.
Regardless, I think the right measures are in place with the sandbox
to limit kingmaking. I think the focus should now be put on promoting
(and I don't mean marketing) but leading the ecosystem to focus on
building tools that innovate technology in the cloud native space with
a high importance on quality and fostering collaboration. Then when
those projects need help with things the foundation can offer, money
for infrastructure, a place for shared IP it seems like it would be
obvious that they should be projects in the foundation, of course they
need to qualify etc.
Just my 2 cents.
On Wed, Sep 19, 2018 at 1:12 PM Matt Farina <matt@...> wrote:
>
> In addition to what Jess said, a foundation provides a vendor neutral (or as close as we can get) location for a project. Competitors on products and services have a place to work together on projects that are not controlled by a single vendor in its governance.
>
> I think this is one of the biggest reasons for a foundation. Not everything needs this. But, some foundational things benefit from it.
>
> Then there is being frank on the politics. People are trying to game the system for career advancement, getting money for startups, more tag lines in marketing campaigns, for bragging rights, and more. In this highly competitive marketplace with money being
thrown to the degree it is, I don’t know if we can avoid this all together.
>
> But, we can put a target on being useful and building useful things. For this I mean Jakob Nielsen’s definition whose gist is useful = usability + utility. Projects and people can be promoted for the useful.
>
> --
> Matt Farina
> mattfarina.com
>
>
>
>
--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3
pgp.mit.edu
--
--
Chris Aniszczyk (@cra) | +1-512-961-6719
--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3
pgp.mit.edu
|
|
I've read this thread (and its predecessor) with interest and there have been so many great suggestions.
One quick thing that would add some value and might (?) not be that hard... I actively do-not-want CNCF to "sell" its member projects to the companies in the end-user community. That said, it would be immensely valuable for CNCF to provide opportunities to engage in well-controlled user research *benefitting the OSS software* within those end-user organizations. The requests on this thread for developer compensation are heard and I think that would be :100:; in addition to paying developers, though, I think another challenge for a lot of OSS projects – especially those that have a point-and-click UI or similar HCI concerns – is actually getting user research beyond the actively committing developers. The downstream effect is that many OSS projects have challenging UIs. (Speaking as a commercial vendor, I may even personally benefit from this challenge, but I would *vastly* prefer to live in a world where OSS is a dream to use, and there's no way we're going to get there without better user research directed specifically towards the needs of the OSS projects)
So, more briefly, it would be interesting if CNCF could at minimum provide an exchange / "marketplace" (sans money, I'd hope) where incubated or graduated projects could engage with end-user ICs to do user research; or, even better, if CNCF could actually administer that user research in a way that's aligned with best practices in that discipline.
Just a thought. (And I'm interested to hear responses to ^^^; I don't see it suggested much, which usually means I'm wrong ;)
Ben
toggle quoted message
Show quoted text
On Thu, Sep 20, 2018 at 2:08 AM alexis richardson <alexis@...> wrote:
Jessie & Matt
Thank-you for raising and elaborating on the topic of how CNCF helps projects.
Personally I do not want "CNCF could do more to help projects" to be chiselled on my gravestone. I think the TOC, Contributors and project leads can ALL show some direction here, and I think we have to do so.
And so - Jessie & Matt & anyone else!
Please could you help me & Chris do something more about this.
Let's (again) make a list of what we think Incubated & Graduated projects really need, by talking with the project leads & others. This list needs to be in a shared public doc. Not everyone wants the same things, but there are themes.
Such as: * docs & project management * community management * project services (hosting, CI, etc) * github wrangling * community / contributor summits * AR/PR help (esp: for projects that don't have 1-2 companies driving them) * maintainer psychotherapy & creche ;-)
WDYT?
a
Then when those projects need help with things the foundation can offer, money for infrastructure, a place for shared IP it seems like it would be obvious that they should be projects in the foundation, of course they need to qualify etc.
Beyond neutral IP, I agree this is the most important thing the foundation provides, and IMHO CNCF does not do enough of it (there are so many things that high velocity projects need I could go on and on and on). Unfortunately, this is the area in which decisions will need to be made. There are limited funds and they will need to be allocated across the increasing portfolio of projects in the foundation, so clearly some decision criteria will need to be developed (whether based on graduation level or something else) to decide how funds are allocated and for what purpose (and unfortunately this in and of itself will involve politics).
I'm happy to see this conversation happening, as I ultimately I do believe that some level of choosing "favorites" is going to be required for the foundation to realize its full benefit to its most popular member projects.
--
|
|
This is a great idea Ben
Overall a strong theme going into the GB off-site was "the TOC community wants more feedback from end users please". The GB and exec staff said that was heard and understood..
toggle quoted message
Show quoted text
On Thu, 20 Sep 2018, 19:27 Ben Sigelman, < bhs@...> wrote: I've read this thread (and its predecessor) with interest and there have been so many great suggestions.
One quick thing that would add some value and might (?) not be that hard... I actively do-not-want CNCF to "sell" its member projects to the companies in the end-user community. That said, it would be immensely valuable for CNCF to provide opportunities to engage in well-controlled user research *benefitting the OSS software* within those end-user organizations. The requests on this thread for developer compensation are heard and I think that would be :100:; in addition to paying developers, though, I think another challenge for a lot of OSS projects – especially those that have a point-and-click UI or similar HCI concerns – is actually getting user research beyond the actively committing developers. The downstream effect is that many OSS projects have challenging UIs. (Speaking as a commercial vendor, I may even personally benefit from this challenge, but I would *vastly* prefer to live in a world where OSS is a dream to use, and there's no way we're going to get there without better user research directed specifically towards the needs of the OSS projects)
So, more briefly, it would be interesting if CNCF could at minimum provide an exchange / "marketplace" (sans money, I'd hope) where incubated or graduated projects could engage with end-user ICs to do user research; or, even better, if CNCF could actually administer that user research in a way that's aligned with best practices in that discipline.
Just a thought. (And I'm interested to hear responses to ^^^; I don't see it suggested much, which usually means I'm wrong ;)
Ben
On Thu, Sep 20, 2018 at 2:08 AM alexis richardson <alexis@...> wrote:
Jessie & Matt
Thank-you for raising and elaborating on the topic of how CNCF helps projects.
Personally I do not want "CNCF could do more to help projects" to be chiselled on my gravestone. I think the TOC, Contributors and project leads can ALL show some direction here, and I think we have to do so.
And so - Jessie & Matt & anyone else!
Please could you help me & Chris do something more about this.
Let's (again) make a list of what we think Incubated & Graduated projects really need, by talking with the project leads & others. This list needs to be in a shared public doc. Not everyone wants the same things, but there are themes.
Such as: * docs & project management * community management * project services (hosting, CI, etc) * github wrangling * community / contributor summits * AR/PR help (esp: for projects that don't have 1-2 companies driving them) * maintainer psychotherapy & creche ;-)
WDYT?
a
Then when those projects need help with things the foundation can offer, money for infrastructure, a place for shared IP it seems like it would be obvious that they should be projects in the foundation, of course they need to qualify etc.
Beyond neutral IP, I agree this is the most important thing the foundation provides, and IMHO CNCF does not do enough of it (there are so many things that high velocity projects need I could go on and on and on). Unfortunately, this is the area in which decisions will need to be made. There are limited funds and they will need to be allocated across the increasing portfolio of projects in the foundation, so clearly some decision criteria will need to be developed (whether based on graduation level or something else) to decide how funds are allocated and for what purpose (and unfortunately this in and of itself will involve politics).
I'm happy to see this conversation happening, as I ultimately I do believe that some level of choosing "favorites" is going to be required for the foundation to realize its full benefit to its most popular member projects.
--
|
|
FYI: at Fluent Bit project (part of Fluentd) we started using IssueHunt I/O mostly to get more help on issues.
toggle quoted message
Show quoted text
Bounties on bug fixes comes to mind.
+1. Bug bounties, pay for regular third party security audits, pay to have a white hat on staff doing security work on behalf of projects full time, etc.
Pay the maintainers and high contributors who don't have other means to make money.
Yes. For certain types of projects such as critical libraries where it's very difficult/impossible to make money maintaining, CNCF should consider adopting those projects and helping pay maintainers to work on them, even if part time.
Even for projects in which there are other means to make money, some of us don't necessarily *want* to make money that way. We do it because, well, that is how we make money. There are real benefits for an organization like the CNCF providing fellowships to allow maintainers to remain neutral. I've written more about this here for those of you that haven't seen it: https://medium.com/@mattklein123/the-broken-economics-of-oss-5a1b31fc0182. The recent Linus salary discussion complicates discussion of this topic which is unfortunate because I think it's one that we increasingly need to have, but hopefully as some time passes we can come back to it.
Such as
All of the things Alexis points out. I would like to see more work on improving the GH experience around things like DCO, bots, issue management, CI, etc. I suspect there is easily a full time tooling job across all of CNCF. CI and negotiating with the vendors for the right amount of concurrency and machine types takes a lot of time. More dedicated help with docs perhaps by sourcing, hiring, and nurturing multiple full time tech writers. Basically, all of this.
Bounties on bug fixes comes to mind. Pay the maintainers and high contributors who don't have other means to make money. If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
--
|
|
Hi all
Please keep these suggestions coming. Chris is gathering them up. I want to get us to a structured proposal here.
a
toggle quoted message
Show quoted text
On Thu, Sep 20, 2018 at 8:24 PM Eduardo Silva < eduardo@...> wrote: FYI: at Fluent Bit project (part of Fluentd) we started using IssueHunt I/O mostly to get more help on issues.
Bounties on bug fixes comes to mind.
+1. Bug bounties, pay for regular third party security audits, pay to have a white hat on staff doing security work on behalf of projects full time, etc.
Pay the maintainers and high contributors who don't have other means to make money.
Yes. For certain types of projects such as critical libraries where it's very difficult/impossible to make money maintaining, CNCF should consider adopting those projects and helping pay maintainers to work on them, even if part time.
Even for projects in which there are other means to make money, some of us don't necessarily *want* to make money that way. We do it because, well, that is how we make money. There are real benefits for an organization like the CNCF providing fellowships to allow maintainers to remain neutral. I've written more about this here for those of you that haven't seen it: https://medium.com/@mattklein123/the-broken-economics-of-oss-5a1b31fc0182. The recent Linus salary discussion complicates discussion of this topic which is unfortunate because I think it's one that we increasingly need to have, but hopefully as some time passes we can come back to it.
Such as
All of the things Alexis points out. I would like to see more work on improving the GH experience around things like DCO, bots, issue management, CI, etc. I suspect there is easily a full time tooling job across all of CNCF. CI and negotiating with the vendors for the right amount of concurrency and machine types takes a lot of time. More dedicated help with docs perhaps by sourcing, hiring, and nurturing multiple full time tech writers. Basically, all of this.
Bounties on bug fixes comes to mind. Pay the maintainers and high contributors who don't have other means to make money. If you have ideas on how we can help projects more, please give us ideas here or take a look at the servicedesk where we document the services CNCF offers for projects: https://github.com/cncf/servicedesk
This was recently updated and we appreciate any feedback.
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
--
Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu
--
--
|
|