8 ms·

Ask HN: Anyone have any cool Open Source Projects and looking for contributors?

15 points by 3a2d29 4y ago

Just thought it be nice to have a similar "who's hiring" type thread.

jarsoon 4y ago
what programming language are you most capable of writing at this moment.
- igotsideas 4y ago
  Not op but any suggestions for python projects?
2Gkashmiri 4y ago
are you interested in accounting? there is one gnukhata https://gitlab.com/gnukhata/gkapp https://gitlab.com/gnukhata/gkapp that is looking for contributors to localize it to various countries around the world. it is currently India only but if anyone is willing to help, join up
pistoriusp 4y ago
RedwoodJS is always looking for contributors!
verdverm 4y ago
https://github.com/hofstadter-io/hof https://github.com/hofstadter-io/hof CUE, Go, code gen & data modeling Lots of good first issues ready for your contribution Also opportunity to write in any tech / lang to build examples, demos, or community modules
codingclaws 4y ago
Yeah, I've been working on a Reddit/HN clone called Comment Castles [0] for a couple years. [0] https://github.com/ferg1e/comment-castles https://github.com/ferg1e/comment-castles
kstenerud 4y ago
https://concise-encoding.org/ https://concise-encoding.org/ is looking for help! I'm planning to release v1 later this year, and there are still a number of things to finish: - Finish upgrading the portable testing rig (whereby the tests are defined in CTE format so that they can be run against any implementation). - Bring the Antlr grammar files up to date and make sure they're as easy as possible to build CTE parsers from. - Add schema validation support to https://github.com/kstenerud/enctool https://github.com/kstenerud/enctool for Concise Encoding documents (using https://cuelang.org/ https://cuelang.org/) - Critiques on the format itself (passages that are unclear or don't make sense, features that shouldn't be there or need more work, etc) - Implementations in other languages & platforms (CBE is more important to start because one can always use enctool to convert between CBE and CTE).
- zzo38computer 4y ago
  It is a interesting idea (there are some good things in there) but I think there are some problems with it: - It uses Unicode. - It seems to be rather complicated, more than it should be. - I think that it would be better that comments should not be considered to be a part of the structure. - I think that astronomical year numbering might be better since then there will be zero. - I am not sure about the media encoding (However, I also dislike XML and JSON, too (they also have the flaw of using Unicode, and other problems too; this Concise Encoding fixes some of them, and adds problems of its own). I had some ideas of my own designs too though. I think that the PostScript object format is not too bad, although it also has problems (e.g. the binary format cannot use numbers longer than 32-bits, the binary format does not have dictionaries (except as a non-standard extension which is deprecated anyways), etc).)
  - kstenerud 4y ago
    Hi, thanks for the comments! I've agonized to excess over so many of the design decisions, but here is the reasoning for the concerns you've raised: There is no avoiding Unicode since that is what the world has settled upon. Anything else would limit international support. As soon as comments are allowed in a text format, they become part of the structure, and need rules for where they can and cannot occur. I've tried to make them as forgiving as possible (basically they can be placed between any two tokens). I think the main difference is that most formats only imply rather than specify where they're allowed and not allowed (for example, you can't put a comment in the middle of a number: 1234/blah/5678 does not represent 12345678). Astronomical year numbering is essential in internal runtime representations, but terrible for anything human facing (which is why standard library date APIs present them in era form). I've observed time and time again people making off-by-one mistakes trying to input BC dates in ISO 8601 (which uses astronomical year numbering); it's just not user-frinedly, and doesn't add anything useful to an interchange format since a computer can make the adjustment automatically and without error every time it converts to/from its internal representation. Media is useful for embedding objects that the receiving side will just know how to handle. Media types were added to email and HTTP and various other formats so that one could embed foreign objects into documents in a consistent, compatible way that the operating system could automatically display. For example, an identification card document could include a picture of the person, but if it were just a series of bytes, a Concise Encoding reader wouldn't know what to do with it; only the receiving application would know. However, as a media object "image/jpeg", any CE reader could display the image inline when viewing the document. I think the format looks complicated because I've been explicit to the point of paranoia about codec behavior in order to ensure that no two implementations have subtle behavioral differences (which would open attack vectors). Internally, all of the types follow 4-5 data layout strategies to keep the binary codec size small. The text format will likely see 2% of usage in the real world, so for it my primary concerns are user friendliness and compatibility with the binary format.
als0 4y ago
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
janosdebugs 4y ago
ContainerSSH is always happy to have contributors, but it's a bit of a hard project to get into. :) https//containerssh.io
MilnerRoute 4y ago
There's new forks just starting up for the beloved Cutefish OS and its "Cutefish DE" desktop environment. https://www.reddit.com/r/linux/comments/vwd0m8/i_am_about_to_fork_cutefishos_and_i_need_your_help/ https://www.reddit.com/r/linux/comments/vwd0m8/i_am_about_to... https://www.debugpoint.com/cutefish-os-development-halts/ https://www.debugpoint.com/cutefish-os-development-halts/
zzo38computer 4y ago
My open source project is a puzzle game engine called Free Hero Mesh. I am looking for contributors, of whatever kind of contribution you might like to do; post on the NNTP and/or IRC if you have interested please. The IRC is #freeheromesh on the Libera IRC; there is also a Matrix bridge (although I have not tested it). The newsgroup name on the NNTP is un2.org.zzo38computer.soft.freeheromesh and the NNTP server is zzo38computer.org. There is also a web page http://zzo38computer.org/freeheromesh/ http://zzo38computer.org/freeheromesh/ with some explanations. I do not use GitHub for my own projects; it is fossil, and is mirrored on Chisel. (In future I might also add a mirror on GitHub too, but currently, it isn't)

15 points by 3a2d29 4y ago

Just thought it be nice to have a similar "who's hiring" type thread.

jarsoon 4y ago

what programming language are you most capable of writing at this moment.

igotsideas 4y ago
Not op but any suggestions for python projects?

2Gkashmiri 4y ago

are you interested in accounting? there is one gnukhata https://gitlab.com/gnukhata/gkapp https://gitlab.com/gnukhata/gkapp that is looking for contributors to localize it to various countries around the world. it is currently India only but if anyone is willing to help, join up

pistoriusp 4y ago

RedwoodJS is always looking for contributors!

verdverm 4y ago

https://github.com/hofstadter-io/hof https://github.com/hofstadter-io/hof CUE, Go, code gen & data modeling Lots of good first issues ready for your contribution Also opportunity to write in any tech / lang to build examples, demos, or community modules

codingclaws 4y ago

Yeah, I've been working on a Reddit/HN clone called Comment Castles [0] for a couple years. [0] https://github.com/ferg1e/comment-castles https://github.com/ferg1e/comment-castles

kstenerud 4y ago

https://concise-encoding.org/ https://concise-encoding.org/ is looking for help! I'm planning to release v1 later this year, and there are still a number of things to finish: - Finish upgrading the portable testing rig (whereby the tests are defined in CTE format so that they can be run against any implementation). - Bring the Antlr grammar files up to date and make sure they're as easy as possible to build CTE parsers from. - Add schema validation support to https://github.com/kstenerud/enctool https://github.com/kstenerud/enctool for Concise Encoding documents (using https://cuelang.org/ https://cuelang.org/) - Critiques on the format itself (passages that are unclear or don't make sense, features that shouldn't be there or need more work, etc) - Implementations in other languages & platforms (CBE is more important to start because one can always use enctool to convert between CBE and CTE).

zzo38computer 4y ago
It is a interesting idea (there are some good things in there) but I think there are some problems with it: - It uses Unicode. - It seems to be rather complicated, more than it should be. - I think that it would be better that comments should not be considered to be a part of the structure. - I think that astronomical year numbering might be better since then there will be zero. - I am not sure about the media encoding (However, I also dislike XML and JSON, too (they also have the flaw of using Unicode, and other problems too; this Concise Encoding fixes some of them, and adds problems of its own). I had some ideas of my own designs too though. I think that the PostScript object format is not too bad, although it also has problems (e.g. the binary format cannot use numbers longer than 32-bits, the binary format does not have dictionaries (except as a non-standard extension which is deprecated anyways), etc).)
- kstenerud 4y ago
  Hi, thanks for the comments! I've agonized to excess over so many of the design decisions, but here is the reasoning for the concerns you've raised: There is no avoiding Unicode since that is what the world has settled upon. Anything else would limit international support. As soon as comments are allowed in a text format, they become part of the structure, and need rules for where they can and cannot occur. I've tried to make them as forgiving as possible (basically they can be placed between any two tokens). I think the main difference is that most formats only imply rather than specify where they're allowed and not allowed (for example, you can't put a comment in the middle of a number: 1234/blah/5678 does not represent 12345678). Astronomical year numbering is essential in internal runtime representations, but terrible for anything human facing (which is why standard library date APIs present them in era form). I've observed time and time again people making off-by-one mistakes trying to input BC dates in ISO 8601 (which uses astronomical year numbering); it's just not user-frinedly, and doesn't add anything useful to an interchange format since a computer can make the adjustment automatically and without error every time it converts to/from its internal representation. Media is useful for embedding objects that the receiving side will just know how to handle. Media types were added to email and HTTP and various other formats so that one could embed foreign objects into documents in a consistent, compatible way that the operating system could automatically display. For example, an identification card document could include a picture of the person, but if it were just a series of bytes, a Concise Encoding reader wouldn't know what to do with it; only the receiving application would know. However, as a media object "image/jpeg", any CE reader could display the image inline when viewing the document. I think the format looks complicated because I've been explicit to the point of paranoia about codec behavior in order to ensure that no two implementations have subtle behavioral differences (which would open attack vectors). Internally, all of the types follow 4-5 data layout strategies to keep the binary codec size small. The text format will likely see 2% of usage in the real world, so for it my primary concerns are user friendliness and compatibility with the binary format.

als0 4y ago

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

janosdebugs 4y ago

ContainerSSH is always happy to have contributors, but it's a bit of a hard project to get into. :) https//containerssh.io

MilnerRoute 4y ago

There's new forks just starting up for the beloved Cutefish OS and its "Cutefish DE" desktop environment. https://www.reddit.com/r/linux/comments/vwd0m8/i_am_about_to_fork_cutefishos_and_i_need_your_help/ https://www.reddit.com/r/linux/comments/vwd0m8/i_am_about_to... https://www.debugpoint.com/cutefish-os-development-halts/ https://www.debugpoint.com/cutefish-os-development-halts/

zzo38computer 4y ago

My open source project is a puzzle game engine called Free Hero Mesh. I am looking for contributors, of whatever kind of contribution you might like to do; post on the NNTP and/or IRC if you have interested please. The IRC is #freeheromesh on the Libera IRC; there is also a Matrix bridge (although I have not tested it). The newsgroup name on the NNTP is un2.org.zzo38computer.soft.freeheromesh and the NNTP server is zzo38computer.org. There is also a web page http://zzo38computer.org/freeheromesh/ http://zzo38computer.org/freeheromesh/ with some explanations. I do not use GitHub for my own projects; it is fossil, and is mirrored on Chisel. (In future I might also add a mirror on GitHub too, but currently, it isn't)