You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a presentation of @Ainali. @Ainali and @clausmullie have created an interesting storyboard about what a public code is, what codebase is, how codebases are shared, changed, replicated and what the role of a codebase steward in this lifecycle is.
I 've added a selection of these slides including the speaker notes from @Ainali explaining each step. Would be great to maybe re-create these steps as individual elements as well as designing a poster which includes all the steps. These illustrations can be used as talking points or may even end op on a roll-up banner which could use on an event to explain our work.
The text was updated successfully, but these errors were encountered:
Story board that informed the activities page: https://drive.google.com/drive/folders/1ON6k65cAAgN_mjsXaL6S07bqvU7r_6S6?usp=sharing. This basically isolates the steps of a) what is a codebase, b) what does it mean for a codebase to be open source, c) what 'manipulations' are possible in open source, d) what are the opportunities, e) what are the risks, f) how does codebase stewardship/the foundation enhance/mitigate these
Lifecycle of a codebase adn codebase stewardship.pdf
In a presentation of @Ainali. @Ainali and @clausmullie have created an interesting storyboard about what a public code is, what codebase is, how codebases are shared, changed, replicated and what the role of a codebase steward in this lifecycle is.
I 've added a selection of these slides including the speaker notes from @Ainali explaining each step. Would be great to maybe re-create these steps as individual elements as well as designing a poster which includes all the steps. These illustrations can be used as talking points or may even end op on a roll-up banner which could use on an event to explain our work.
The text was updated successfully, but these errors were encountered: