478 Matching Annotations
  1. Feb 2021
    1. This gives them a slight edge but that’s nothing substantial because those fixes eventually reach Ubuntu.
    1. But all of these attempts misunderstand why the Open Source ecosystem is successful as a whole. The ecosystem of fairly standard licenses provides a level playing field that allows collaboration with low friction, and produces massive value for everyone involved – both to those that contribute and to those that don't. It is not without problems (there are many essential but unsexy projects that are struggling with funding), but introducing more friction won't improve the success of this ecosystem – it will just lead to some parts of the ecosystem to break off.
    2. Part of me thinks that open source can be more rewarding to the creators/contributors. But maybe the real contribution is the permanent addition to the tools available to humanity, and if you have the wits, you can make a decent business out of it without tainting open source.
    3. Selling proprietary software is difficult when there is so much gratis Open Source software around.
    4. For a sufficiently successful and industry-relevant open source project, it's possible for the main developers to earn a living e.g. by selling related consulting services.
    5. It turns out that creating and using Free Software is not just good to individuals, but for businesses as well, for example by building upon publicly available components and by collaborating shared software. The term Open Source is a business-friendly rebranding of the Free Software concept. This line of thought was also widely successful, e.g. Firefox/Mozilla was an open sourcing of Netscape software.
  2. Jan 2021
    1. Lemmy is a great open source federated and privacy respecting alternative to Reddit. Nodes can be self-hosted and posts will sync between them.

    1. Unfortunately, this probably means a death knoll for this gem, at least I predict it will contribute to its slow trajectory towards insignificance/unknownness/lack-of-users.

      Why? Because it is already the less popular option in this comparison: https://ruby.libhunt.com/compare-premailer-rails-vs-roadie-rails

      and being actively maintained is an important factor in evaluating competing options.

      So of course people will see that the premailer option is the option that is still actively maintained, is still continuing to be improved, and they'll see that this one has been relegated to dormancy/stagnancy/neglect/staleness, which will only amplify the degree/sense of abandonment it already has from its maintainer (only now it will be its users that start to abandon it, as I now have).

    2. At work, I cannot maintain this project. At home, I'd rather spend time with my children and on projects that I'm currently passionate about.
    1. unlike a traditional computer, a blockchain computer can offer strong trust guarantees, rooted in the mathematical and game-theoretic properties of the system. A user or developer can trust that a piece of code running on a blockchain computer will continue to behave as designed, even if individual participants in the network change their motivations or try to subvert the system. This means that the control of a blockchain computer can be placed in the hands of a community
    1. Augmented Steam is an open source project. You can verify the code for yourself, help us improve it or create your very own version.
    1. Would you work for free? It is a simple but loaded question that requires additional context. Is it working to help a friend do something? Is it work that you would enjoy? Does the act of working for free give you some level of satisfaction? Your gut reaction to the question may have been a hearty, “No,” but many people volunteer for a variety of things all the time, so people will work for free when there is something in it they enjoy.
    2. Open source is fundamentally good with the transparency and flexibility it brings; however, as our reliance on it goes up, the overall investment back into the ecosystem has not. It can be easy to take for granted the time and effort many developers put into open source projects. Yet it is with their time and effort that we often save our own.
    3. These developers are not greedy or selfish for wanting funding for their projects. To the contrary, they want funding to keep the project alive. A person has to eat, after all. Funding the project is a means of changing the maintainer’s timeshare—allowing themselves to put time into the project that otherwise would be used for other employment. There is only so much time in a day that a person can otherwise give.
    4. Funding should not be a struggle for open source projects. We embrace open source into our codebases frequently but have yet to fully embrace the idea that funding it actually helps us too. The bug fixes and feature requests need to be implemented, tested, and reviewed by someone who themselves can only put so much time into the project.
    1. I don’t think he implies that, he didn’t mentioned FOSS or non-FOSS. Third party doesn’t refer to licensing, only to who provides it.
    2. wouldn’t that « lesser » the FOSS effort towards desktop app’s ?
    3. Snap gets rid of dependency mess. Good. Snap offers in one place FOSS and proprietary app’s. Here I am suspicious. It may be an advantage for a commercial app-store and for some users. But this advantage may lead to loss of comfort and flexibility for the many users that rely first on FOSS.
    1. If it is powerful and reliable, that means it serves them better.

      software is often oriented towards performance as primary (if not only) criterium, it is developed through a performance-centric lens.

      other cultural, social, ethical factors are ignored or not taken into account

  3. Dec 2020
    1. You can also purchase a Nextcould hosting service, which on one hand may not seem any different from giving your photos over to Google or Apple, but there's a significant difference: Nextcloud storage is demonstrably encrypted, with source code to prove it.
    1. Following the model of open-source software, we can enter our ideas and expressions into public discourse

      This also isn't a well-aligned argument. Articles published in a for-profit journal are entered into the public discourse (although obviously not into the public domain). Unless public means "without cost", which I don't think it does.

      We might want to broaden this to include open-access, which is specific to publication models.

    1. Our team is building open source community tools and Svelte fits our identity as an independent labor of love with an organic community.
    2. With some frameworks, you may find your needs at odds with the enterprise-level goals of a megacorp owner, and you may both benefit and sometimes suffer from their web-scale engineering. Svelte’s future does not depend on the continued delivery of business value to one company, and its direction is shaped in public by volunteers.
  4. Nov 2020
    1. In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
    2. I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
    3. So I propose having the repo in place, and using it for targeted proposals where we really want feedback from early users, and hold off formalising anything more until early next year, as you said.
    1. Express - 19 $ 🏃‍♀️ Skip the Review Queue 🕒 Published in 3 days 💌 Full Customer Support 💚 Support the team

      Wow, after seeing how this site works, I don't like much like it anymore.

      Esp. this below:

      Choose your preferred publish date - 9 $ Feature your project on top for 14 days and get an additional tweet - 19 $

      I hope there is/will be soon a more open/free alternative (like the "awesome" lists that use GitHub PRs instead of an opaque/proprietary submisison form).

    1. Tunnelgram is fully open source (server and client) and uses the Tunnelwire Encryption Scheme, so you can see all of the code it's built on.
  5. Oct 2020
    1. Free to accessFree to reuseFree to reviseFree to remixFree to redistributeThe question becomes, then, what is the relationship between these additional capabilities and what we know about effective teaching and learning? How can we extend, revise, and remix our pedagogy based on these additional capabilities?

      I look at this and think immediatly about the Git model of allowing people to not only fork and reuse/redistribute pieces, but what about the ability to do pull requests to take improvements and push them back up the the source so that everyone potentially benefits?

  6. Sep 2020
    1. The initials fa in the class refer to Font Awesome, an open- source set of icons created by Dave Gandy,23 which further links this project to the open- source community and its ethos of collaboration. Font Awesome gives the community icons for making professional- grade web apps, rendering artifacts and objects legible in the contemporary web design ecology

      Font Awesome est une police d'écriture et un outil d'icônes qui se base sur CSS, LESS et SASS (Wikipédia, « Font Awesome », consulté le 22 septembre 2020).

  7. Aug 2020
    1. Open Source flutter Apps permits you to make lovely native apps on iOS and Android from one codebase. The most goal of this repository is to seek out free open supply apps and begin contributive. Be at liberty to contribute to the list, any suggestions square measure welcome!
    1. Stallman has also stated that considering the practical advantages of free software is like considering the practical advantages of not being handcuffed, in that it is not necessary for an individual to consider practical reasons in order to realize that being handcuffed is undesirable in itself.
    1. GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.
    2. How does the licensing work in this new setup? Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.
  8. Jul 2020
    1. "Other office suites are focusing on the 'power user' which is a valuable market, for sure, but the real power and range for an open-source office suite alternative is the vast majority which is the 'rest of us. Sometimes we all forget how empowering open source is to the entire world."
    1. This is very irresponsible of them, with respect to the number of downloads. They should finally realize this and just redirect people to LO. Continuing like this hurts the Apache Foundation credibility as well as the open source community as a whole.
    1. This isn’t an accident. OpenOffice’s sidebar code was copied and incorporated into LibreOffice. The Apache OpenOffice project uses the Apache License, while the LibreOffice uses a dual LGPLv3 / MPL license. The practical result is LibreOffice can take OpenOffice’s code and incorporate it into LibreOffice — the licenses are compatible. On the other hand, LibreOffice has some features — like font embedding — that don’t appear in OpenOffice. This is because the two different licenses only allow a one-way transfer of code. LibreOffice can incorporate OpenOffice’s code, but OpenOffice can’t incorporate LibreOffice’s code. This is the result of the different licenses the projects chose.

      What part of LGPLv3 / MPL prevents LibreOffice code from being incorporated back into OpenOffice's Apache Licensed code??

    1. A growing number of platforms, vendors, and partners support the AMP Project by providing custom components or offering integration with AMP pages within their platforms.

      I guess AMP is actually open-source software, but it still feels like it's something non-standard. I guess it's just an alternative open standard to the "main" web open standards.

  9. Jun 2020
    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. Unlike Telegram, WhatsApp is not open source, so there’s no way for security researchers to easily check whether there are backdoors in its code. Not only does WhatsApp not publish its code, they do the exact opposite: WhatsApp deliberately obfuscates their apps’ binaries to make sure no one is able to study them thoroughly. 
  10. 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. 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

  11. 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.

  12. 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.
  13. 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.

  14. 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.

  15. 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!
  16. 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.
  17. 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.
  18. Sep 2019
  19. 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....