投稿時間:2022-06-05 01:10:19 RSSフィード2022-06-05 01:00 分まとめ(14件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
Git	Gitタグが付けられた新着投稿 - Qiita	Gitコマンドあれこれ	https://qiita.com/shiho97797/items/6bd26431c3a1026145c6	gitconfigglobaluser	2022-06-05 00:06:17
海外TECH	Ars Technica	An actively exploited Microsoft 0-day flaw still doesn’t have a patch	https://arstechnica.com/?p=1858179	windows	2022-06-04 15:14:24
海外TECH	MakeUseOf	How to Convert a PowerPoint Presentation to Google Slides	https://www.makeuseof.com/convert-powerpoint-presentation-to-google-slides/	slides	2022-06-04 15:45:13
海外TECH	MakeUseOf	How to Delay or Disable the Taskbar Thumbnail Preview in Windows	https://www.makeuseof.com/windows-delay-disable-taskbar-thumbnail/	steps	2022-06-04 15:15:13
海外TECH	DEV Community	What are the first steps you take when starting a new thing from scratch?	https://dev.to/brunoj/what-are-the-first-steps-you-take-when-starting-a-new-thing-from-scratch-2mlo	What are the first steps you take when starting a new thing from scratch Whether totally greenfield or a substantial new part of an existing system ーwhat do you do to ground yourself on a brand new project	2022-06-04 15:37:12
海外TECH	DEV Community	How to empower your open source users and contributors	https://dev.to/juliaferraioli/how-to-empower-your-open-source-users-and-contributors-17c4	How to empower your open source users and contributorsThis article is cross posted from The Lead Dev and juliaferraioli com When the concept of open source first emerged people collaborated on projects very intentionally Without today s vast internet and information retrieval systems the network of people largely researchers working on these shared systems largely grew via word of mouth If you were working on a piece of software with folks outside of your institution you likely would have communicated with them directly prior to them ever viewing a single line of code Even as more of the world gained access to the internet finding information was a challenge Usenet a distributed discussion platform that came out of University of North Carolina at Chapel Hill and Duke University in arrived on the scene as a popular way to discover and communicate about software with freely available source code Still the effort needed to start using or contributing to a new project was high In order to find resources that you needed such as source code or documentation if any existed you d generally have to contact the author of the project But eventually web search improved and with the rise of hosting and distribution platforms such as SourceForge it became much easier to find information about how to use and contribute to open source Improvements in infrastructure hardware and computer science reduced the cost of experimentation and simultaneously increased the reach of freely modifiable and distributable software Barriers to people embracing open source started falling away Breaking down the barriers to open sourceOpen source is more accessible to new contributors than ever before in part due to the user experience improvements pushed forward by platforms such as BitBucket GitHub and GitLab They provide a way to discover new repositories and view their source This means that you can browse and understand a project before becoming deeply invested It has the added benefit for people with resource constraints such as disk space or network bandwidth because you no longer have to clone an entire repository copy the files to your computer in order to view its contents That said there s still a fair amount of improvement that can be made to the open source experience Four ways to empower open source users and contributorsLast time we extended the initial social model of open source by outlining why open source projects should provide information about how they operate This time we ll explore how projects can take a similar approach to helping users and contributors engage with them DocumentationTechnical documentation existed long before the first line of code Good documentation rests at that intersection between art and science with technical writing expertise being highly sought after in open source projects Creating documentation for open source poses several challenges including the sheer variety of audiences that need the docs One of the most effective ways that a project can lower barriers to becoming involved is by specifying not only where documentation lives but also what type of documentation is available Consider the example set by the Python programming language which points to several sets of documentation targeting different skill levels and roles IssuesWhile many projects these days choose to take reports of issues alongside where their code is hosted some prefer to use an open source or third party solution such as Bugzilla or Trac Wherever a project takes reports of issues and discusses them making it very clear where community members should report current issues makes it an easier experience for them As a side benefit it lowers costs for maintainers by reducing the amount of redirection they need to do Jaeger sets a good example of this by specifying where its issue trackers live as well as where to file various types of issues Bonus points if a project publishes guides or templates for how to file issues DiscussionThe frequency of communication between maintainers and users is of increasing importance to adopters and can be a factor when making technology decisions However facilitating conversation between contributors and users alike signals a thoughtfulness and intentionality that benefits all participants in the project s community Projects that make a point of documenting official channels for discussion encourage the growth of a healthy community allowing community members to support each other An example is how Apache Beam lists its various discussion fora and when to use each ContributingAs the complexity of software increases so does the complexity of contributing to open source Projects may have language specific style guidelines that they ask modifications to follow or processes that must be adhered to when a new contributor wants to pick up a bug to fix While these working agreements might on occasion seem overly prescriptive to prospective contributors they are there to maximize the success of everyone involved Contributors minimize the amount of wasted effort and maintainers minimize the amount of back and forth answering questions and requesting changes in reviews Generally setting these expectations improves morale Inkscape s CONTRIBUTING md file outlines some general guidance as well as instructions about decision making building testing and documentation Along the same lines of providing contributor guidelines is documenting processes that architectural development should follow such as how Bazel calls out how to make larger scale changes to the core project ReflectionsAnother way to think about open source is through the lens of empowerment You are empowered to see the source code of the software you use You are empowered to modify it distribute it and learn from it So why not take that to its logical conclusion and empower your community members with the information they need to be productive with and within your open source project These are just a few community focused elements that you might consider through our social model of open source though they are common to many if not most projects There are a few missing elements from our social model that we will address in the subsequent post The next time you are updating the README for your project review it to see if you are empowering your community with resources that will make them successful whether as users contributors or future co maintainers	2022-06-04 15:20:11
海外TECH	DEV Community	Why open source projects should embrace operational transparency	https://dev.to/juliaferraioli/why-open-source-projects-should-embrace-operational-transparency-49dk	Why open source projects should embrace operational transparencyThis article is cross posted from The Lead Dev and juliaferraioli com From operating systems to CSS frameworks open source gives creators the ability to accelerate development learn from communities of experts and incorporate thoroughly reviewed code At its heart open source concerns freedoms relating to code but an open source project is a complex system that happens to focus on code In my last article we started to explore how we might move past the typical focus on the open source license and instead develop a social model that captures additional complexity As a recap we established that the technical model of open source describes what you can and cannot do with it typically by way of the project s license whereas the social model describes how open source interacts or doesn t with the larger ecosystem and the people within it That initial article addressed capturing the purpose of a project based on its specific goals within the open source ecosystem In this second piece we will continue to develop the social model of open source by exploring the benefits of operational transparency and outlining some key characteristics that maintainers should aim to make publicly available The benefits of operational transparencyA key benefit to open source is that anyone can examine the code they incorporate but how the project operates is just as important to a project s success as the functionality itself With open source making up an estimated of today s modern technology it s increasingly critical to make operational information readily available to the public so that you can empower contributors and users to evaluate projects based on the criteria important to them The operational characteristics of an open source project are often thought of as fundamentals to the teams behind them and yet they re rarely communicated well beyond the maintainers This is a lost opportunity as open source projects that clearly concisely and consistently articulate how they operate give contributors and users the social frameworks that they need to work well within the project Here are some high priority details that projects should aim to make publicly available The decision making modelA vital part of running an open source project is deciding how to run the project While governance is an ever expanding term its primary concern is around how decisions get made and who gets to make them The Open Source Way has a fantastic comprehensive guidebook around open source governance Whether a project is managed by a benevolent dictator for life BDFL or is foundation backed clearly communicating the model in use benefits potential contributors and project alike An example is Node js which openly shares that it follows a consensus seeking decision making model The project s affiliationsAs more companies start to create open source as part of their strategic initiatives it can instill a healthy amount of skepticism in potential adopters When a project is run by a corporation decisions about the future of the project can but not necessarily become opaque to the end user That said a corporate sponsored project may also have the ability to focus on security developer experience and usability in a way that independent projects cannot as they can leverage the time talent and treasure of the company By identifying the affiliation of a project whether it be a company government non profit or individual it allows consumers to make informed decisions based on their own strategy and values An example is TypeScript s open affiliation with Microsoft The funding sourcesWhile open source is free as in puppy to consume it is most definitely not free to create From bandwidth and infrastructure to time costs can add up For people looking to build products by integrating with open source software the price of switching components can be high as interoperability between projects is rare Exposing how the project supports itself provides a two fold benefit people deciding on a technology can evaluate if the project fits their risk profile and current integrators can clearly see when a project becomes at risk of running out of capital Plus financial transparency is right in line with open source values An example is Homebrew which has been openly funded by GitHub sponsors OpenCollective and Patreon The maintainers and the core teamAs incidents such as logj and Heartbleed have shown us open source software that provides key functionality for many services and applications is often maintained by only a handful of people Additionally information about the people maintaining projects may be difficult to find forcing users to trawl the project s metadata through mailing lists commit history etc…in order to determine the size of the core team Effectiveness of a team may be dependent on the number of members but there are many other variables that influence how well a team manages their processes Publishing an up to date list of core team members even without any information beyond usernames can signal when a piece of software is in danger of becoming under maintained or effectively unmaintained In turn this opens up an opportunity for users to step up and offer to take a more active role within a crucial dependency An example is Font Awesome which publicly shares its team list Transparency helps everyoneOpenness is about more than just code it is also about how we make decisions how we support ourselves how we prioritize issues and how we delegate responsibilities Of course the operational details that a project considers important may vary and maintainers will choose to highlight those that are most relevant to them A project in its beginning phase might not yet have a formalized governance model or funding while a more established project may have a variety of defined roles and responsibilities But wherever possible increasing transparency around how work gets done sets clear expectations for contributors raises the visibility of when a project is in need of support and reduces the amount of effort that falls on the maintainers collective shoulders Keep an eye out for my next article where we ll explore how to incorporate dynamics and conventions around communication into our social model of open source	2022-06-04 15:18:30
海外TECH	DEV Community	Microservices anti-patterns	https://dev.to/evanhameed99/microservices-anti-patterns-5gdg	Microservices anti patternsThis blog mainly talks about the anti patterns of building microservice architecture systems A microservice architecture helps a lot in many aspects Readability Maintainability scalability separation of concerns and many more On the other hand these pros might turn into cons if some anti patterns are applied in a microservice architecture and it would be very difficult to maintain What does anti pattern mean In software engineering and computer science an anti pattern is a term that describes how not to solve repetitive recurring issues in your codebase Therefore they are always considered to be bad practices in the design of systems Different Microservices architecture anti patterns Distributed Monolithic systems This is an anti pattern that I have experience working with A monolithic app means a system that encapsulates the whole logic of the app in one unit or codebase One of the mistakes some people do is distributing the logic of that big monolithic app into several small monolithic apps and calling it a microservice architecture The fact is these small monolithic apps will eventually chat with others to achieve how the big monolithic app was working Any small change in one of these monolithic apps will cause the saga to break And a change in other systems will be required and that defeats the purpose of microservice architecture Cohesion chaos and coupling Cohesion in microservice architecture means the amount of how components of a single entity are tied together With that being said a microservice should not care about the components of other entities This anti pattern arises when unrelated components or functionalities are constantly being added to a specific microservice Dependency distortion This anti pattern also arises when all of the microservices should be deployed in a specific order otherwise the saga and the chattiness between the microservices will break This is caused by the separation of concerns as well Shared schemas and datastores This is an anti pattern that occurs when multiple microservices are connected to the same db For example if one microservice needs to change a specific schema due to its internal logic the microservice that is also connected to that database should adapt to the corresponding change Actions redundancy Action redundancy occurs when there are some functionalities that are occurring in each microservice Suppose that in order for an action to start a saga in the microservices the user who is doing the action should be authenticated For that matter the user should be authenticated once Having an API gateway becomes very handy in such situations to centralize shared logic between microservices and also to orchestrate the events between them ConclusionUnderstanding microservice architecture and its anti patterns are very important A lot of complexity might be added trying to apply them without thinking of the overall design of how they should be built	2022-06-04 15:16:20
海外TECH	Engadget	Apple is reportedly enlisting Hollywood talent to create content for its upcoming AR headset	https://www.engadget.com/apple-hollywood-directors-mixed-reality-headset-154640921.html?src=rss	Apple is reportedly enlisting Hollywood talent to create content for its upcoming AR headsetApple has reportedly enlisted Hollywood directors like Jon Favreau to create video content for its long rumored mixed reality headset According to The New York Times the filmmaker is developing an experience that brings the dinosaurs from Prehistoric Planet the Apple TV original series he helped produced to life on the device Corroborating recent reporting from Bloomberg s Mark Gurman The Times states the headset is “expected to ship next year It will reportedly feature a design that s reminiscent of a pair of ski goggles With the start of WWDC mere days away it s unclear if Apple will have anything to say about the device on Monday However The Times reports the company plans to announce new software tools that would allow developers to add additional camera and voice features to their apps thereby creating the framework for experiences that you could navigate without a visual interface Citing “two people familiar with the project The Times reports that “continuing challenges with battery life made Apple decide to delay the headset to That broadly aligns with reporting Bloomberg published at the start of the year that said the company was likely to delay the device due to development issues like overheating	2022-06-04 15:46:40
ニュース	BBC News - Home	Platinum Jubilee: Festivities to continue with Party at the Palace	https://www.bbc.co.uk/news/uk-61690149?at_medium=RSS&at_campaign=KARANGA	william	2022-06-04 15:36:17
ニュース	BBC News - Home	French Open: Iga Swiatek beats Coco Gauff in Paris final	https://www.bbc.co.uk/sport/tennis/61689560?at_medium=RSS&at_campaign=KARANGA	favourite	2022-06-04 15:23:02
ニュース	BBC News - Home	Epsom Derby: Desert Crown romps to victory to give Sir Michael Stoute sixth success in race	https://www.bbc.co.uk/sport/horse-racing/61691659?at_medium=RSS&at_campaign=KARANGA	epsom	2022-06-04 15:47:59
ニュース	BBC News - Home	Armenia 1-0 Republic of Ireland: Visitors fall to shock Nations League defeat	https://www.bbc.co.uk/sport/football/61675560?at_medium=RSS&at_campaign=KARANGA	Armenia Republic of Ireland Visitors fall to shock Nations League defeatThe Republic of Ireland s Nations League campaign begins in deeply disappointing fashion as they fall to a surprise defeat by Armenia in Yerevan	2022-06-04 15:26:25
北海道	北海道新聞	全仏テニス、シフィオンテクがＶ　２年ぶり２度目、ガウフに完勝	https://www.hokkaido-np.co.jp/article/689647/	全仏オープン	2022-06-05 00:02:00