Re: [ospo.zone] Minimal Viable OSPO

[Boris Baldassari <boris.baldassari@xxxxxxxxxxxxxxxxxxxxxx>]

Dirk, Mike,

Thanks for the inputs. I agree it would probably be a good start, but I don't think it'd be enough to define a minimal OSPO -- at least not in the OSPO Zone and Good Governance Initiative contexts.

In my humble opinion and understanding, what makes the OSPO Zone different is precisely that: a body of knowledge that goes beyond compliance and spans to organizational, cultural, and strategical areas. 

Not all of them must be addressed in the beginning, of course, but I'd personally recommend starting quite early with e.g. educational and cultural topics. One example would be to provide people and teams with a point of contact for questions related to open-source within the organization. It may look futile, but I think it's a great way to actually start the community building and get traction.

--

boris

On Wed, Sep 22, 2021 at 5:42 PM Dirk RIEHLE <dirk@xxxxxxxxxx> wrote:

It would indeed be sad if you stopped with OpenChain 2.1, but today it
probably gives you a minimum viable OSPO. The spec will keep evolving and
probably build out the contribution part and add a strategy and leadership
part. That's in line with how most companies / OSPOs follow the basic maturity
path of use, contribute, lead. Cheers, --Dirk

On 22.09.21 17:30, Mike Milinkovich wrote:
> On 2021-09-22 11:27 a.m., Dirk Riehle wrote:
>> Fulfill the OpenChain spec?
>
> Perhaps a good start, but (personal opinion only) I have always felt that
> focusing OSPOs purely on compliance is a fundamental error.
>
>>
>> On Wed, Sep 22, 2021, 17:20 Boris Baldassari
>> <boris.baldassari@xxxxxxxxxxxxxxxxxxxxxx
>> <mailto:boris.baldassari@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>>
>>     Hiho good people,
>>
>>     There has been a question frequently coming up in discussions on OSPO
>>     Zone and in the Good Governance Initiative, and I would like to ask for
>>     the audience's wisdom on this:
>>
>>     What would a Minimal Viable OSPO look like?
>>
>>     I.e. is there a set of basic activities, or duties, that would be enough
>>     to start an OSPO, and if so, what would they be?
>>
>>     An elaborate answer would probably depend on the domain and context of
>>     the organization, but maybe we can find a minimal working set to, say,
>>     bootstrap the process.
>>
>>     Any ideas, inputs, or experience on this topic?
>>
>>     Thank you, have a wonderful day!
>>
>
> --
>
> *Mike Milinkovich*
>
> *Executive Director | **Eclipse Foundation AISBL*
>
> mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
>
> @mmilinkov
>
> +1.613.220.3223 (m)
>
>
> _______________________________________________
> ospo.zone mailing list
> ospo.zone@xxxxxxxxxxx
> To unsubscribe from this list, visit https://accounts.eclipse.org
>

--
Confused about open source?
Get clarity through https://bayave.com/training
--
Website: https://dirkriehle.com - Twitter: @dirkriehle
Ph (DE): +49-157-8153-4150 - Ph (US): +1-650-450-8550

_______________________________________________
ospo.zone mailing list
ospo.zone@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org