How to participate

If you would like to participate in this effort, here are some ideas on how to do that.

Write software

UnixObjects is not a software project, it is an architecture. You do not contribute code to an architecture. However, by writing software that is compliant with UnixObjects, and publishing it, you contribute to a distributed corpus of software components that are able to interoperate. In this sense, there is a virtual software project around UnixObjects.

Supporting the UnixObjects architecture is an excellent bet as there is nothing to lose. Everything in your work can be backward compatible with the older, less organized approach. The upward potential comes free.

Also, you do not need to support much of the UO specification. It is enough to provide a directory containing commands that operate on $SELF. This alone allows others to parent-link to your shared object and build on it.

Write about UnixObjects

Write an article or blog entry about UO. Then later you get to say you were among the first to discover this revolutionary concept. :-)

Publish a link

Publish a link that points to this website. This will make it easier for people to discover UnixObjects.

Give feedback

I am grateful for any and all feedback, even if it is just to point out a spelling mistake (I am not a native English speaker and I regularly make spelling and grammar mistakes).

Donate to the artist

Consider donating to the author. Much of the research work regarding UO is still waiting to be put online. Your financial support encourages me to continue publishing new material. It also helps me pay for the hosting of these pages.