Please shamelessly promote your project. Everyone who posted in previous weeks is welcome back this week, as always. 😄
For further actions, you may consider blocking this person and/or reporting abuse
Please shamelessly promote your project. Everyone who posted in previous weeks is welcome back this week, as always. 😄
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (20)
Hey, we're working on xstate: github.com/davidkpiano/xstate - a library for declaratively making state machines and statecharts that not only reduces the complexity of your application behavior, but can also automatically generate tests and visualize app state!
Here's my presentation at React Rally discussing the overall concepts and introducing xstate: youtube.com/watch?v=VU1NKX6Qkxc
Recent slides and use cases for statecharts: slides.com/davidkhourshid/reactive...
Used in React, via React-Automata: github.com/MicheleBertoli/react-au...
And a (beta) visualizer! bit.ly/xstate-viz
It's currently being used in projects such as Gatsby, and workshop.me, and quite a few others! I'd love for people to help contribute documentation, as well as help to add features, fix bugs (there aren't many at all, actually), and create sample projects.
I'm excited about the future of this project because it has foundation in decades worth of software modeling research (statecharts were first introduced in 1987) and has applications in all types of projects, especially user interfaces. There's a huge potential for these ideas to greatly simplify application complexity in a robust, visual way.
So, I have a slightly different angle on this question. While I am looking for folks who want to work on msngr.js (a messaging library for handling publish and subscriptions within JavaScript) I also am not sure where else to take it or if it's simply "done". I have some loyal users but they literally need no additional features or changes.
I would love some thoughts :)
github.com/KrisSiegel/msngr.js
This is really interesting. I'ma check this out as well.
One thing though, don't use the word async as identifier like in your readme because it is a part of the JavaScript language these days.
But really, looks interesting.
Good point!
Cool, I’m gonna check this out.
Hey, I'm the author of Pizzicato.JS (github.com/alemangui/pizzicato), a web audio library.
It's aimed at basic and fun use cases. You can find some things I've created with it on CodePen (codepen.io/alemangui/pen/jBMwqw, codepen.io/alemangui/pen/VpagoY). TonalHub (alemangui.github.io/Tonalhub/) is also powered by Pizzicato, as well as many other projects out there.
If you're curious of how web audio works and want to take a shot at implementing some things drop me a line, I could really use some help :)
hello , i use your pizzicato lib , thanks for big effort,
i looking for method i can export group sound as OneFile MP3 or WAV
If you're looking to make an impact in the Python ecosystem the urllib3 package has a list of outstanding issues marked as Contributor Friendly where maintainers are willing to spend extra time with new contributors and have relatively straightforward changes required in order to ease your way into a new complex codebase. Contributing to urllib3 has a huge impact to the Python ecosystem because it's depended on for some of it's most important modules (pip, requests, and boto3 to name a few!)
Hi all!
I am working on a way to have commit conventions within projects, therefore I introduced
semantic-git-commit-cli, in shortsgc, which helps with that. github.com/JPeer264/node-semantic-...I am also doing now on a research for a GitHub recommender for contributors. Would be neat if any can spare some time and fill in the form (pssst, you can win a 20€ Amazon Voucher Code): goo.gl/forms/ogC5oKJbfM5xhSzr2
With that recommender I want to achieve that you can find projects where you can contribute to next.
I've been working on a pull request plugin for VIM: github.com/AGhost-7/critiq.vim. It does the job for me, but I'm sure there's quite a few features people would like added to it. Could really use some help since I'm not entirely familiar with the vim language.
openstandards.guide to promote open standards easy to comply, badges for validated projects, ramping up on open source projects was never easier with community driven standards. Read what a standard require at the parent standard called “meta” at openstandards.guide/explore/meta. New standard proposals open at github.com/standards/meta/issues.
I just dropped a release candidate for Massive v5:
npm i massive@nextto get it. If anyone's interested in taking a Node+Postgres data access library for a spin and reporting back I'd love to hear from you!Hey! Just wanted to drop in and say thanks again. Sample Programs in Every Language has jumped from essentially nothing to 19 stars and 9 forks thanks to this weekly post. I appreciate the help as it allows me to focus on writing.
Hey everyone! We're working on TorXakis.
More often than not, testing software consumes a large portion of the development budget, however we frequently see cases where unit and integration tests fail to uncover critical errors that appear once the software is deployed. Most testing techniques revolve around specifying a collection of execution sequences that check the expected against the actual behavior. A problem with this is that the number of possible execution sequences is huge, and therefore only a very small portion of these would be covered by test cases that are specified as a sequence of steps. The second problem is that, with the goal of increasing coverage and prevent regression bugs a large number of test cases is written, which eats up the development budget.
Model-based testing is a technique for writing tests, where a model of the system behavior is made a a high-level of abstraction, and then the system-under test is tested against this the expected behavior as specified by the model. Model-based testing relies on different algorithms for generating test cases from models, which allows to achieve a much higher test coverage than standard testing techniques, while requiring only a fraction of the code.
TorXakis is such a model-based testing tool, that has been used to verify large scale systems in well-know high tech companies. This tool is entirely written in Haskell, and its code is available on Github under a BSD3 license.
Since July last year, a lot of effort was put into taking TorXakis from a prototype to an industrial grade tool. Some of the improvements made include:
In addition, there is ongoing work in a new command line interface and a new compiler for the TorXakis language.
A year is almost gone, and there are a lot of interesting challenges ahead to make TorXakis a tool that can be used in production, so we welcome the contributions of anybody interested in the topic.
Further reading: github.com/TorXakis/TorXakis/
Cheers!