text stringlengths 0 1.17k |
|---|
[3715.90 --> 3719.20] we're going to ask one simple question because that's that's the way we're going to roll around |
[3719.20 --> 3725.90] here but um inspectors new it's you know let's say it's you know barely a day old in terms of release |
[3725.90 --> 3734.48] um can you kind of give the listeners a way that you're looking for engagement you know is there |
[3734.48 --> 3738.92] a feature set like you'd mentioned earlier you know supporting different systems debian and and |
[3738.92 --> 3743.18] were some of the ones that you'd mentioned that you use so you're supporting those are are there a |
[3743.18 --> 3749.82] hit list that you have a road map how can people jump in and and help you launch the open source side |
[3749.82 --> 3756.86] and right and uh maybe even how to buy the pro side well i what i would love what i need right now |
[3756.86 --> 3761.66] is just users you know it's a brand you know it is a brand new project so i would love people to |
[3761.66 --> 3768.92] download it try it out um i'm definitely not strong in terms of the operating system packaging |
[3768.92 --> 3775.12] so deb support rpm support i i spent probably a month trying to polish it and get it working |
[3775.12 --> 3780.12] but i'm sure that there's uh plenty of room for improvement there so maybe some code review on |
[3780.12 --> 3785.40] certain areas yeah exactly i mean if there's a if you know you got more of a debian guy or more of a |
[3785.40 --> 3796.26] um a fedora guy uh wants to or or girl for for that matter uh agenda is is not an issue um if if |
[3796.26 --> 3803.12] anyone wants to come in and uh and help me out there i'm happy to have that uh i've cobbled together |
[3803.12 --> 3807.54] what i have right now but i'm sure there's room for improvement and the other thing is is just use it |
[3807.54 --> 3815.04] and and give me give me ideas for features um send prs and uh and remember the there's that demon |
[3815.04 --> 3820.16] specific feature where you know i want i want inspector to know about as many of these popular |
[3820.16 --> 3828.74] different application components as possible and so getting uh prs to add more and more of them |
[3828.74 --> 3834.98] would be awesome so yeah that's that's definitely ripe for uh for some for uh prs |
[3834.98 --> 3840.92] well awesome well is there anything else that you want to cover mike and in closing before we uh |
[3840.92 --> 3846.58] take the show out not really i just want to thank you guys for giving me the opportunity to come on |
[3846.58 --> 3852.72] and and uh ramble on a bit cool well uh we'll have all the links in the show notes so if uh |
[3852.72 --> 3857.90] uh we'll mention here on the air but uh mparum on twitter if you want to follow mike but we'll have |
[3857.90 --> 3863.66] some links in the show notes to back to the code back to um your your uh your company site we'll even |
[3863.66 --> 3870.38] link that blog post that jared mentioned about this uh this fantastic way to have this path of |
[3870.38 --> 3875.32] success like mike has found for sure so mike thanks for coming on the show um we had some awesome |
[3875.32 --> 3879.36] sponsors for this show so as you might know not only are we member supported but we're also |
[3879.36 --> 3883.82] sponsor supported because we work with some really really cool companies one of those cool companies |
[3883.82 --> 3889.90] is code ship love code ship those guys are awesome hired.com uh and also digital ocean we're |
[3889.90 --> 3893.90] hosting on digital ocean we love digital ocean and we think you should too if you're not using them |
[3893.90 --> 3898.86] then i just make a sad face and that's just that's just how it goes but that's it for this uh this |
[3898.86 --> 3904.92] week's of changelog and we'll be back as soon as you want to hear us let's say goodbye bye |
[3904.92 --> 3905.88] bye |
[3905.88 --> 3909.88] you |
[3909.88 --> 3913.88] you |
[3913.88 --> 3915.88] you |
[3915.88 --> 3917.88] you |
[3917.88 --> 3919.88] you |
[3919.88 --> 3921.88] you |
[3921.88 --> 3923.88] you |
• Definition of changelog and its importance |
• Differences between changelog and release notes |
• Challenges of maintaining a changelog in open source projects |
• Proposed changelog format (Added, Deprecated, Removed, Fixed) |
• Goals of the Keep a Changelog project |
• Semantic difference between changelog and history file |
• Context and value of changelog versus Git diff dump |
• Standard changelog format and its absence |
• Importance of clear changelogs for open source users |
• Difficulty of maintaining up-to-date changelogs |
• Value of empathizing with users and providing clear information |
• Benefits of a well-maintained changelog, such as reduced misunderstandings and confusion |
• The Keep a Changelog format, which includes a markdown format and specific sections for changes |
• Importance of clear and consistent date formatting in changelogs |
• The need for a clear and concise way to document changes in open source projects |
• Discussion of international date formats and their advantages |
• Use of yyyy-mm-dd format on various documents, including checks |
• Debate on using consistent date formats across contexts |
• Proposal to start a revolution for using consistent date formats |
• Explanation of markdown formatting, including use of pound signs and dashes |
• Discussion of auto-linking anchors and GitHub Flavored Markdown |
• Criticism of unconventional file formats and debate on optimal formatting |
• Portable and accessible format for changelogs |
• Use of markdown and its benefits |
• Goal of achieving consensus on a basic format |
• Importance of changelogs in open source projects |
• Frustration caused by incomplete or misleading changelogs |
• Breaking API changes and the need for clear documentation |
• Importance of semantic versioning and API stability |
• Personal experience with frustration while upgrading an app |
• The goal of Keep a Changelog as a solution to these problems |
• Shields is a standardized system for badges that provides a simple and consistent format for displaying information about a project |
• The idea for Shields originated as a response to the proliferation of inconsistent and poorly designed badges |
• Olivier Lacan created a template for Shields and worked with other developers to create a consistent format for badges |
• Shields now has a centralized platform (Shields.io) that allows for easy generation of badges using APIs |
• The goal of Shields is to create a convergence around a standardized format for badges, similar to how changelogs have become a standard practice |
• Discussion of how to effectively use Shields, including when to add changelog entries and what information to include. |
• Implementing a changelog entry for every minor release to inform users of bug fixes and potential regressions |
• Importance of clear release notes to reduce user frustration and facilitate self-diagnosis |
• GitHub's Releases feature and its potential to muddy the waters of changelogs |
• Potential for GitHub to parse and display changelog files in the project dashboard |
• GitHub's goal of making Git more accessible and the meaning behind the Releases feature |
• Discussion of an open source project's approach to versioning and changelogs |
• Using Git tags to automatically generate changelogs |
• Importance of conventions in reducing overhead for developers |
• Aaron Swartz as a programming hero for his fight for internet freedom and open access to information |
• Civic hacking and using technical skills for social good |
• Documentary about Aaron Swartz's life and legacy |
• Discussion of Aaron Swartz and his legacy, including his mentor Lawrence Lessig's campaign to create a super PAC to stop super PACs |
• Importance of keeping a changelog in open source development, and the need to focus on incremental improvements rather than trying to change the world |
• Olivier Lacan's personal story of working on a project, documenting it, and receiving help from others, illustrating the power of community in open source development |
• Discussion of Olivier Lacan's other interests, including photography and his desire to take pictures that capture the essence of people |
• Use of Instagram as a platform for finding and engaging with communities around shared interests, and the desire to make Instagram's tag data public |
• Adam Stacoviak's enthusiasm for using Instagram's tag data to research and make product decisions. |
• Discussion of foodies and restaurant selection based on Instagram presentation |
• The inadequacy of Yelp for restaurant reviews |
• The "if not doing what you do" question and Olivier's answer (photography) |
• A brief technical aside about GitHub and release notes |
• Discussion of upcoming guests and potential future topics |
**Adam Stacoviak:** Today we're joined by Olivier Lacan... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.