198 Matching Annotations
  1. Last 7 days
  2. May 2020
    1. The folks at Netlify created Netlify CMS to fill a gap in the static site generation pipeline. There were some great proprietary headless CMS options, but no real contenders that were open source and extensible—that could turn into a community-built ecosystem like WordPress or Drupal. For that reason, Netlify CMS is made to be community-driven, and has never been locked to the Netlify platform (despite the name).

      Kind of an unfortunate name...

    1. open source

      So open-source that there is no link to the source code and a web search for this product did not reveal where the source code is hosted.

      They're obviously using this term merely as a marketing term without respect for the actual meaning/principles of open source.

    1. "You wanted open source privacy-preserving Bluetooth contact tracing code? #DP3T software development kits/calibration apps for iOS and Android, and backend server, now on GitHub. iOS/Android apps with nice interface to follow." Michael Veale on Twitter (see context)

    1. the commented Python scripts optFromSmiles.py, optLigandInProtein.py and torsionalScan.py which serve as examplesof simple and constrained MMFF minimizations

      I will learn these scripts

    Tags

    Annotators

  3. Apr 2020
    1. Becouse of CanCan, StateMachine and others I deside to create OpenSource organization to maintain gems. People disappear, lose their passion about coding, get new interests, families, children. But if us many we can support gems much longer. I dont pretend to be an expierenced ruby developer, but I can do administarative work: managing teams, members, approve simple pool-requests. If you think it good idea and want to support some inactive gems, not life time, maybe just a little - welcome to organization.
    2. There's actually discussion among the rubygems team about a process for putting gems "up for adoption" that you might be interested in: http://www.benjaminfleischer.com/2014/08/17/rubygems-adoption-center/
    1. Our hope is that once a formal specification for these extensions is settled, this patchset can be used as a base to upstream the changes in the original project.

      What does "can be used as a base to upstream the changes in the original project" mean here?

    1. This repository contains the parts of the RubyMotion product that are opensource. It does not contain the full product, which can be purchased at www.rubymotion.com.
    1. http://undraw.co/illustrations

      Undraw 是 一个完全免费的开源插画库,您可以完全免费使用这些插画,并且无需归属,你可以在商业或个人项目中免费使用。

      它提供的每一张插画都是非常精美,质量非常高,网站也提供每张插画对应的内容,让你轻松找到自己需要的插画。

      它不仅支持以 SVG 格式下载,也支持 PNG 格式下载;如果你下载的是 SVG 格式,你可以通过修改代码的方式进一步修改制作属于自己的精美插画,如果你下载的是 PNG 格式,你可以直接用于博客文章和社交媒体。

    1. And most important: No proprietary encryption software can be fully trusted
    2. If you are concerned about privacy and looking for a bullet-proof solution then the only way to go is open-source software. For example, there was another incident with a proprietary file "encrypter" for Android/iOS which used the simplest possible "encryption" on earth: XORing of data that is as easy to crack a monkey could do that. Would not happen to an open-source software. If you're worried about the mobile app not being as reliable (backdoors etc.) as the desktop app: compile it yourself from sources. https/github.com/MiniKeePass/MiniKeePass You can also compile the desktop version yourself. Honestly, I doubt most people, including you and me, will bother.
    1. 1Password wasn’t built in a vacuum. It was developed on top of open standards that anyone with the right skills can investigate, implement, and improve. Open tools are trusted, proven, and constantly getting better. Here’s how 1Password respects the principles behind the open tools on which it relies:

      I found it ironic that this proprietary software that I have avoided using because it is proprietary software is touting the importance of open tools.

    1. Changing things doesn't necessarily imply improving them and it's improvement we should strive for, otherwise change is pointless.

      I'd even go further and argue why change things at all in first place ? And that's why Open Source Software is better in this debate too. Don't change your software just for the sake of change.

    1. So what will happen with these projects from now on? All of the projects above have one thing in common: they were created and maintained by passionate individuals who wanted to make positive contributions to their communities. Without these individuals and their efforts, these projects would not have become what they are today. Therefore, it is only fair that Plataformatec gives these individuals control of these projects moving forward.
    1. Automattic uses WordPress to power WordPress.com, and it contributes back code and time to the WordPress project. It is a symbiotic relationship. It isn’t accurate to say that WordPress is Automattic’s product, or that WordPress came from Automattic. Indeed, the opposite is true — Automattic came from WordPress, and Automattic (through WordPress.com) exists as part of the vast WordPress community and ecosystem.

      That's probably a common misconception. I'm glad they clarified that because I might have assumed that as well:

      It isn’t accurate to say that WordPress is Automattic’s product, or that WordPress came from Automattic. Indeed, the opposite is true — Automattic came from WordPress, and Automattic (through WordPress.com) exists as part of the vast WordPress community and ecosystem.

  4. Mar 2020
    1. Piwik PRO uses a fork of Piwik open-source software (similarly to RedHat using the Linux kernel and multiple open source tools), however we currently seamlessly integrate a part of open source Piwik in our proprietary platform via APIs. Moreover, Piwik PRO controls all the changes to the code used in its Analytics Suite and since 2016 has been maintaining and developing its own fork of “Piwik” alongside the proprietary modules of Analytics Suite.
    1. We are independently developing each of our products and don’t require permission from any other organization to improve them or create new functionalities.
  5. Feb 2020
    1. We commit to build the load testing tool with the best developer experience, k6, and developing it in the open with the community, read our document on stewardship of the OSS k6 project. We believe this is key and the necessary foundation to build great developer tooling.
    2. we believe that developer tools should be open source to allow for a community to form and drive the project forward through discussions and contributions. Hence why we built k6, the load testing tool we’ve always wanted ourselves!
    1. To never block or remove features from k6 in order to make them exclusive to Load Impact’s SaaS productStrive not to delay introduction of new features in the k6 OSS tool, if the feature was planned to appear both there and in Load Impact’s SaaS productTo never introduce into the k6 OSS tool any artificial limits designed to promote conversion to Load Impact’s SaaS productTo work with the community, participating in and prioritize building the functionality the k6 community wants, making it the prefered tool for load testing
    2. With k6, our goal has always been to create the best load testing tool for the modern working developer and that we do this in collaboration with the k6 community. Our revenue will not come from k6 directly, but from premium value creating offers based on k6. These offers will be made available at https://loadimpact.com. Load Impact premium offers will have focus on providing further simplicity, productivity and ease to use functionality.
    3. We believe the key to Load Impact’s long-term success as a Company is to foster an active community of users around k6 as an open source project. To achieve this long-term goal, it is vital that we do not withhold new features from k6 based on whether or not they compete with our SaaS offering.
    4. Load Impact is a for profit organization, and recognizes that there is a need to balance this requirement with the needs of the k6 open source project. In the longer run, we strongly believe that those two needs will rarely be in conflict.
    5. Load Impact is the initiator of, and an active participant in, the k6 open-source project, trying to serve its needs and lead by example
    1. We Open Source and actively participate in various OSS programs such as Google Summer of Code(GSoC), Rails Girls Summer of Code (RGSoC), Outreachy and Google Code-In (GCI).
    1. With version 6.1.4, the Foxit installer was bundled with potentially unwanted programs like OpenCandy which installed the browser-hijacking malware Conduit.[11][12] Following complaints from users, it was removed after version 6.2.1.[13] In July 2014, the Internet Storm Center reported that the mobile version for iPhone was transmitting unencrypted telemetry and other data to remote servers located in China despite users attempting to opt out of such data collection.[14]
    1. "We are at a time where some people doubt the validity of science," he says. "And if people feel that they are part of this great adventure that is science, I think they're more inclined to trust it. And that's really great."

      These citizen scientists in Finland helped identify a new type of "northern light". Basically, 2 people were able to take a shot of the same display at the same second, 60 miles apart, allowing for depth resolution.

  6. Jan 2020
    1. In many cases, the projects exist, and the developers are eager to do the work, but schedules and the demands of producing sustainable income prohibits focus on the effort. What's needed is a relatively small amount of funding to facilitate that focus.

      True that! I'd love to work on open-source projects like this if only I could feed my family while working on them...

    1. More broadly, we hope that others, especially the hundreds of new startups in synthetic biology, consider sharing pre-competitive ideas, methods, tools, etc. We think the community will be stronger as a result.

      This is a great initiative. Hat's off to this company - Octant-bio for encouraging open sourcing of their hard work and optimization.

  7. Dec 2019
    1. tus is brought to you by the people behind Transloadit but the source code to all of our implementations, this website and even the protocol itself is accessible to everyone under MIT license
    1. If you need a tool to backup your documents and files please take a look at the excellent BackInTime application which is more configurable and provides options for saving user files.
    2. Timeshift for Linux is an application that provides functionality similar to the System Restore feature in Windows and the Time Machine tool in Mac OS.
    1. Choose Your Plan
    2. Transparently Secure. We believe that transparency and openness are the best foundation for trust so we are building Padloc completely out in the open. Our source code is developed under an open source licence so anyone can review it, provide feedback and even offer contributions at any time!
  8. Nov 2019
    1. We hope that this approach will bring us the best of worlds - the ability to have a commercially sustainable product, with high quality - as well as giving back to the open source communities by having our work eventually end up in the open, and ensuring that external contributions are always open source.
    2. Because of the support we've received from open source communities, we've decided to dual-license the code after 18 months

      Interesting licensing solution/choice...

    1. the main reason we built a new multiprocess architecture is that Chromium's multiprocess support was never contributed to the WebKit project. It has always lived in the separate Chromium tree, making it pretty hard to use for non-Chrome purposes.Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could build on it. They said no.
    1. Some time ago I asked on Reddit: “What’s the consensus among the React community for testing React components?” Shawn Wang replied: “testing is an enormously complicated and nuanced topic on which there isn’t a consensus anywhere in JS, much less in React.” I was not trying to find the best library for testing React. Mainly because there isn’t one.
  9. Oct 2019
    1. Probably some context-setting is in order. This meeting is primarily devoted to getting yes-or-no decisions made on suggestions which have fairly clear outcomes. In other words, it's effectively a "shortest job first" throughput-maximizing endeavor where we try to pay down some of the massive triage debt we have while also getting as many suggestions accepted or declined in a short turnaround time.
    1. Issues can be funded by anyone and the money will be transparently distributed to the contributors handling a particular issue.
    2. If you are using Utility-Types please consider donating as this will guarantee the project will be updated and maintained in the long run.
    1. Their hope by announcing so loudly what they have accomplished, is that others in the Android modder/hacker scene will step up and help them turn this root exploit into something useful for users by deploying features that are not currently available through the Google controlled Chromecast experience.
  10. Sep 2019
  11. Aug 2019
    1. I'm working full time on Material-UI since 2019. I was working on it during my free time before that. I hope that I can leverage my full-time involvement in the library to make it really awesome. You are right, the project is well-funded. We hope we can fund the time of more than 1 person full time in the future, with the current growth rate, it should soon be possible. We have 3 people working part-time on the project (Matt, Sebastian and Josh), plus the community behind us (+1,000 code contributors).
    1. Thanks to the lust of innovation brewed by productivism, there’s companies everywhere seeking talented self-motivated creatives to unquestionably follow orders, to ensure their company is the winner out of many losers;

      There are several companies that although they have closed-source products, they have large open-source projects that are core-components to their product. Thing Facebook and it's open-source projects or Microsoft and their open-sourcing of the asp.net and corresponding frameworks. It seems like in general, there is a trend toward companies open-sourcing their DX tools, which is what a majority of open-source projects are....

  12. Jul 2019
    1. Software Sustainability Institute, based at the University of Edinburgh, provides free, short, online evaluations of software sustainability, and fellowships of £3,000 ($US3,800) for researchers based in Britain or their collaborators.

      UK only additional opportunity for open source software funding: Software Sustainability Institute (University of Edinburgh)

    2. One Twitter thread (see go.nature.com/2yekao5) documents grants from the NSF’s Division of Biological Infrastructure, the NIH’s National Human Genome Research Institute and the National Cancer Institute, and a joint programme from the NSF and the UK Biotechnology and Biological Sciences Research Council (now part of UK Research and Innovation). Private US foundations such as the Gordon and Betty Moore Foundation, the Alfred P. Sloan Foundation and the Chan Zuckerberg Initiative (CZI) also fund open-source software support.

      Funding opportunities for open source software

  13. May 2019
    1. By “Infrastructure” we mean

      ​The definition of "open infrastructure" (or the software component of open infrastructure) should include an explicit requirement for open-source code.​ Even an explicit recommendation short of a requirement would be better than the current definition, which is entirely silent the value of opening the code. The Elsevier acquisition of bepress (to use one example among many) would have been much less harmful to the community if the code had been open and user institutions could hold on to the platform, fork it if they wanted, take it in their own direction, and continue using it without becoming Elsevier customers.

    1. Methodology The classic OSINT methodology you will find everywhere is strait-forward: Define requirements: What are you looking for? Retrieve data Analyze the information gathered Pivoting & Reporting: Either define new requirements by pivoting on data just gathered or end the investigation and write the report.

      Etienne's blog! Amazing resource for OSINT; particularly focused on technical attacks.

  14. Apr 2019