<transcript><audio_140>projects have gone down having you know people get alienated you know started Twitter war and so forth about how they're treated when they try to contribute to a project if you want your</transcript><transcript><audio_141>project to be taken seriously by business then you have to pay attention to the culture of business and these days the culture of business requires this kind of sort of professional interaction the the days of I wouldn't</transcript><transcript><audio_142>say that the days of the kind of the incredibly blunt benevolent dictator for life are over but if you want your open-source project to be business then you have to treat it like business and code of conduct is one of the ways to do</transcript><transcript><audio_143>that by the way if you want to just grab a code of conduct take a look at the one that Mozilla promulgates it's a pretty good one and that's just an example there are plenty of different examples out there are plenty of different styles</transcript><transcript><audio_144>but consider coding a code of conduct in github repository from day one the next thing you have to figure out is your contribution licenses and again this is a completely separate topic</transcript><transcript><audio_145>when you release an open-source project and you apply a license to it like Apache or like a GPL what you're doing is you're saying what license terms are what license rights are flowing from the</transcript><transcript><audio_146>project out to the world so we call that an outbound license but when people give you code as a contribution you have to figure out what the inbound license is and there are essentially a couple of</transcript> projects have gone down having you know people get alienated you know started Twitter war and so forth about how they're treated when they try to contribute to a project if you want your project to be taken seriously by business then you have to pay attention to the culture of business and these days the culture of business requires this kind of sort of professional interaction the the days of I wouldn't say that the days of the kind of the incredibly blunt benevolent dictator for life are over but if you want your open-source project to be business then you have to treat it like business and code of conduct is one of the ways to do that by the way if you want to just grab a code of conduct take a look at the one that Mozilla promulgates it's a pretty good one and that's just an example there are plenty of different examples out there are plenty of different styles but consider coding a code of conduct in github repository from day one the next thing you have to figure out is your contribution licenses and again this is a completely separate topic when you release an open-source project and you apply a license to it like Apache or like a GPL what you're doing is you're saying what license terms are what license rights are flowing from the project out to the world so we call that an outbound license but when people give you code as a contribution you have to figure out what the inbound license is and there are essentially a couple of
{"source": "grass-yt-cc-by.0lgq4ubIYF4|shard_10051_61|create_multimodal_data.extract_yt_and_generate_transcripts.57|shard_10051|create_multimodal_data.generate_captions.58|shard_10051|create_multimodal_data.generate_captions.59", "params": {"id": "0lgq4ubIYF4", "channel_id": "UCBhXFK70DbOU15N2BhDQVTg", "duration": 2799, "view_count": 454, "age_limit": 0, "chapters": [{"start_time": 0.0, "title": "Introduction", "end_time": 90.0}, {"start_time": 90.0, "title": "Open Source can be a labor of love", "end_time": 148.0}, {"start_time": 148.0, "title": "Open Source is big business", "end_time": 222.0}, {"start_time": 222.0, "title": "How can you make money", "end_time": 237.0}, {"start_time": 237.0, "title": "Turn your project into a business", "end_time": 307.0}, {"start_time": 307.0, "title": "Business Models", "end_time": 344.0}, {"start_time": 344.0, "title": "Question Mark", "end_time": 383.0}, {"start_time": 383.0, "title": "Maintenance and Support", "end_time": 556.0}, {"start_time": 556.0, "title": "Quality Assurance", "end_time": 712.0}, {"start_time": 712.0, "title": "Online Services", "end_time": 827.0}, {"start_time": 827.0, "title": "Professional Services", "end_time": 880.0}, {"start_time": 880.0, "title": "Business Model", "end_time": 946.0}, {"start_time": 946.0, "title": "Staging Release Model", "end_time": 1005.0}, {"start_time": 1005.0, "title": "Dual Licensing", "end_time": 1115.0}, {"start_time": 1115.0, "title": "Open Core", "end_time": 1382.0}, {"start_time": 1382.0, "title": "Comments", "end_time": 1660.0}, {"start_time": 1660.0, "title": "NonCommercial", "end_time": 1712.0}, {"start_time": 1712.0, "title": "Brand", "end_time": 1892.0}, {"start_time": 1892.0, "title": "Getting Ready", "end_time": 2382.0}, {"start_time": 2382.0, "title": "Answering Questions", "end_time": 2412.0}, {"start_time": 2412.0, "title": "The History of GPL", "end_time": 2799}], "channel_follower_count": 5120, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@AllThingsOpen", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10051/0lgq4ubIYF4.tar.gz"}}