[04/2023] Reference ongoing work of the FINOS InnerSource Licensing Working group

[spier]

@chamindra gave a presentation at the ISC Summit 2022 about the work of the FINOS InnerSource SIG, specifically the FINOS InnerSource Licensing Working group.

They want to create a license generator, that orgs can use to generate their own InnerSource licenses.
Please review key points of the talk related to InnerSource at:
https://www.youtube.com/watch?v=pDG_CqvTWrE&t=453s

This work is ongoing. From what I can tell it has not produced results yet that others can immediately use. However it might still be interesting for readers of our InnerSource License pattern to know that this work is ongoing. I am a bit torn whether to add this information to the pattern already or not.

By filing this issue I figured we keep at least some trace of this ongoing work that could enrich the InnerSource License pattern in the future.

[spier]

@chaimandra I saw the timeline that you presented in your talk. Would it make sense to check back with the FINOS InnerSource Licensing Working group in April/May 2023 to see how far you have come with this work?

[chamindra]

Hi Sebastian, Thank you for your interest and sorry for the late reply. As mentioned in the talk, though we are running this through FinOS we welcome participation in the working group from other industries even now. The working group meetings are open to non-FinOS members as well. The next meeting will be on Monday 5th Dec 4pm UK and 11am EST (meeting details: finos/InnerSource#80) At this stage we are gathering prior work on organization specific Inner Source licenses, CLAs, contracts or guidelines. This will feed into our analysis to define a common set of license clauses that we can build the license generator from. If anyone here knows of any prior work beyond what was captured here, would like to encourage you to share it here -> finos/InnerSource#75 or at the working group next meeting If not you are still most welcome to join our working group meetings and give your input representing your org or otherwise. You can reach out to me on linkedin if needed Best Regards, Chamindra de Silva *Linkedin:* https://www.linkedin.com/in/chamindra/

…

On Wed, Nov 23, 2022 at 7:50 PM Sebastian Spier ***@***.***> wrote: @chaimandra I saw the timeline that you presented in your talk. Would it make sense to check back with the FINOS InnerSource Licensing Working group in April/May 2023 to see how far you have come with this work? — Reply to this email directly, view it on GitHub <#488 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTG6G7GZNUQXEPB4QZG72LWJZYPHANCNFSM6AAAAAASJKJ5FM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[spier]

Thanks for the reply @chamindra, and for the invite to the working group meetings.
It's great to have this here in the open for anybody who is interested.

I will leave this GitHub issue open, as a little earmark to check back with you in April/May 2023.
Then we can what material your group has produced, and what of that we can work into our existing pattern.

Good luck 🍀

[spier]

Hi @chamindra, I had this issue here open as a reminder to contact you again.
Well, it did remind me just now, even though some months later than I thought :)

Where did the work in FINOS related to InnerSource Licenses lead?
Anything related to this that could be shared in the open?

[chamindra]

Hi Sebastian, Thanks for reaching out. We have an initial simple codebase for the license generator though it still needs a bit of work. Most of the work however is in refining the license clauses and putting it through legal review. It is presently hosted at FinOS labs https://github.com/finos-labs/innersource-license-generator There is an updated presentation that was done on it at the last FINOS member meeting which was documented here https://osr.finos.org/docs/osr-resources/innersource/ At this stage I am looking for a few more contributors to get involved both in refining the license clauses and a bit of python work (the latter is the easier part and a backlog has been defined). It would be great if we can a join working group around this between ISC and FINOS InnerSource SIG (+ Russell who participated in our last meet) Best Regards, Chamindra de Silva https://www.linkedin.com/in/chamindra/

…

On Sun, Oct 1, 2023 at 5:30 PM Sebastian Spier ***@***.***> wrote: Hi @chamindra <https://github.com/chamindra>, I had this issue here open as a reminder to contact you again. Well, it did remind me just now, even though some months later than I thought :) Where did the work in FINOS related to InnerSource Licenses lead? Anything related to this that could be shared in the open? — Reply to this email directly, view it on GitHub <#488 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTG6GYMODPT5NMFN5LQIPTX5GLDPANCNFSM6AAAAAASJKJ5FM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[spier]

Thank you for the quick response @chamindra.

The way that your slides are shown side by side with the speaker notes is really neat. Allowed me to go through the content almost as if I had been at the meeting. Great job!

If you like, you can share your project in the InnerSource Commons Slack again, and ask for like-minded folks and possible contributors there. Feel free to reference this issue here, if that is helpful.

[chamindra]

Thanks Sebistian, I am just organizing the next working group meeting on this which is planned for Tuesday next week. Will post an invite here and on slack for those who are interested in joining this initiative. We are looking for the following types of involvement in particular: 1) Contribution to the development of the python web app 2) Reviewing the terms/clauses representing your org or industry needs 3) As a early adopter to give feedback WIP meeting issue finos/InnerSource#101 (will be confirmed) Best Regards, Chamindra de Silva *Linkedin:* https://www.linkedin.com/in/chamindra/

…

On Mon, Oct 2, 2023 at 12:00 PM Sebastian Spier ***@***.***> wrote: Thank you for the quick response @chamindra <https://github.com/chamindra> . The way that your slides are shown side by side with the speaker notes is really neat. Allowed me to go through the content almost as if I had been at the meeting. Great job! If you like, you can share your project in the InnerSource Commons Slack again, and ask for like-minded folks and possible contributors there. Feel free to reference this issue here, if that is helpful. — Reply to this email directly, view it on GitHub <#488 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTG6G5GUANO7LWLXQICWC3X5KNDHANCNFSM6AAAAAASJKJ5FM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[chamindra]

Hi Sebastian, All, Just to confirm the FinOS InnerSource SIG meeting will happen every two weeks on Tuesday 10am EST 3pm BST (attached is the invite) starting from this coming Tuesday 10th of October For the next week we will have a focus on the InnerSource license generator and discuss more on how we can improve collaboration between the FinOS SIG and InnerSource Commons. Anyone interested is welcome to join. Meeting details are provided below finos/InnerSource#101 Hope to see some of you there Best Regards, Chamindra de Silva https://www.linkedin.com/in/chamindra/ On Tue, Oct 3, 2023 at 8:42 AM Chamindra de Silva ***@***.***> wrote:

…

Thanks Sebistian, I am just organizing the next working group meeting on this which is planned for Tuesday next week. Will post an invite here and on slack for those who are interested in joining this initiative. We are looking for the following types of involvement in particular: 1) Contribution to the development of the python web app 2) Reviewing the terms/clauses representing your org or industry needs 3) As a early adopter to give feedback WIP meeting issue finos/InnerSource#101 (will be confirmed) Best Regards, Chamindra de Silva *Linkedin:* https://www.linkedin.com/in/chamindra/ On Mon, Oct 2, 2023 at 12:00 PM Sebastian Spier ***@***.***> wrote: > Thank you for the quick response @chamindra > <https://github.com/chamindra>. > > The way that your slides are shown side by side with the speaker notes is > really neat. Allowed me to go through the content almost as if I had been > at the meeting. Great job! > > If you like, you can share your project in the InnerSource Commons Slack > again, and ask for like-minded folks and possible contributors there. Feel > free to reference this issue here, if that is helpful. > > — > Reply to this email directly, view it on GitHub > <#488 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABTG6G5GUANO7LWLXQICWC3X5KNDHANCNFSM6AAAAAASJKJ5FM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >