Hi Mike,
Welcome to the OSv community!
As Dor mentioned there are 353 open issues so as you can see there are tons
of things you could help us with :-) Also you may have seen a roadmap email
I have sent recently so feel free to give any feedback you may have.
If you do not mind, here is a list (for starters) of things you may help us
with, if you have time and interest.
1. Improve/refresh documentation - this is very open ended effort but
here are things I am interested in:
- refresh main OSv github page to make it target more users of OSv;
existing one is a little outdated and targets mostly OSv developers I
think
- maybe reference some wiki pages directly or make them somehow
more visible - https://github.com/cloudius-systems/osv/wiki
- add or update existing wiki page
(https://github.com/cloudius-systems/osv/wiki/POSIX-API-support) to list
all supported POSIX/Linux APIs (both from musl and glibc) - see this
discussion
https://groups.google.com/d/msg/osv-dev/GPm5z9c9v54/9_CbAHW4CgAJ
- create some kind of component diagram using draw.io (I started
something for an article I have never finished) so I can share with you
what I have; something that would visualize this
- https://github.com/cloudius-systems/osv/wiki/Components-of-OSv
- ideally update http://osv.io/ (not sure who has access to it); make
it look nicer and update existing content where needed
- reference existing Docker projects to build and run OSv app that I
have created - https://github.com/wkozaczuk/docker_osv_builder
and https://github.com/wkozaczuk/docker_osv_runner.
- create a Wiki page about how memory is allocated in OSv - I wrote
an email about it
- https://groups.google.com/d/msg/osv-dev/Xw3nGuPWzMw/tYVj1d-GAQAJ
2. Do inventory of open issues and properly label them (this may require
knowledge you do not have yet but some things may be self explanatory). My
sense is that some of those are genuine bugs (would be nice to prioritize
them, labels), many are enhancements, many are really questions that should
be closed. Some bugs may have been fixed (especially the old ones) but
needs to be retested and closed. Maybe we should identify some issues as
"Won't fix" because they are so esoteric, I do not know. See this email
about labels
-
https://groups.google.com/forum/#!searchin/osv-dev/issues%7Csort:date/osv-dev/dk2hlmxHKQc/gbb3a75tAgAJ.
3. Implement some kind of remote unit testing mechanism. Currently all
unit tests are executed locally on host on QEMU/KVM but it would be nice to
have a mechanism to execute all unit tests remotely possibly using OSv REST
API so that we can actually verify they work on VMware, XEN or VirtualBox.
4. Fix all remaining warnings in unit tests and httpserver-api module -
just build and run OSv tests to see what they are.
5. If you are into Java maybe play more with graalvm (see this OSv app
that I added recently)
- https://github.com/cloudius-systems/osv-apps/tree/master/graalvm-example.
6. Write an article about OSv - maybe some intro something for brand new
users - maybe use this wiki page
-
https://github.com/cloudius-systems/osv/wiki/Build-and-run-apps-on-OSv-using-Capstan
as a basis.
Here is what I remembered from top of my head. Let me know if you have any
specific questions.
Regards and welcome again,
Waldek
On Monday, November 12, 2018 at 12:56:03 PM UTC-5, דור לאור wrote:
>
> Hi Mike,
>
> You're all welcome! There are lots of open issues on the githubs of the
> various projects,
> you're welcome to take a stab on them.
> Best,
> Dor
>
> On Sun, Nov 11, 2018 at 10:44 AM Mike Kelp <[email protected]
> <javascript:>> wrote:
>
>> Hi there,
>>
>> First off, thanks for trying to accomplish, and sharing, such an
>> important project! I know low-level systems projects like this are long,
>> hard commitments; and not always given the due appreciation. Thank you for
>> doing it.
>>
>> I've been tracking OSv for a while now, hoping to use it with java
>> applications we build and I'm now getting more opportunities to do so. As I
>> get more familiar with it, I'll hopefully be much more useful, but for the
>> time being I wanted to see that best ways I could support the project.
>>
>> I have what I'll call an intermediate understanding of OS architecture (I
>> took Systems Programming / OS architecture courses, etc and have deeply
>> researched how the OSes we use work including virtualization), but haven't
>> done any OS development at all or C development in quite a while so it will
>> take time to build that back up again. With that in mind, I don't expect to
>> be as useful in code for now as I would be in other projects, but
>> meanwhile, I would like to support the project.
>>
>> So, how can I help? Where I can find time, I'm willing to try anything
>> that honestly helps you all.
>>
>> Some random examples to get thoughts going:
>>
>> - Cleaning up issues or any janitorial task there
>> - Automating processes (especially with Java)
>> - Documentation cleanup
>>
>> Let me know what would best improve the productivity as a whole and I
>> will try to jump in.
>>
>> Cheers,
>> Mike
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "OSv Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups "OSv
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
