Open source hunt

    Entry into the hunt


    We believe that the future is for Open-Source, and we try to bring it closer in every way . And we invite you to join.

    If you look at Open-Source in the west, then behind the slender columns of technologies that we all know and love, will be the heads of commercial companies. By creating something, you make life easier not only for colleagues, but also for us. We save time (and therefore money) and create beauty using your labor. We must respect this and help everyone we can. We join our Western colleagues and offer grants for open projects.

    Since March 2012, we open two programs:
    1. OSS Project Sponsorship Program
    2. Project “Hunting for Open-Source”
    The sponsorship program for existing projects will be announced separately, and today we want to invite you to participate in our hunt.

    Very often in work we lack a convenient implementation of one or the other. If we have the opportunity to rectify the situation, we will correct it and share the result with the community. But what if there are currently no resources at hand? Then we suggest you do it!

    How it works?


    1. We openly publish our needs - whether it is end-products or software components.
    2. If you have a desire to do something for people, or you see your need for our list, you contact us.
    3. We sponsor work on this project by publishing its code under an open license (BSD / MIT) of your choice. The authorship, of course, is yours. Our only common requirement is to host a project on Github within our organization.
    4. Our representative takes part in the development as an assistant and a person who can more accurately formulate our needs. Of course, you are not limited to our needs. But their implementation is part of this program :). For real Jedi, this means an extra head, and for those who have just embarked on the path of power - an experienced mentor who will help make everything right.
    5. Together, we bring the project to the first release and beyond, depending on the circumstances:
      • leave the project to support the community
      • We continue to sponsor the further development of the project, transferring it to the OSS support program
      • we take it for independent support if the author is no longer interested in the project

    What can I do right now?


    Right now, we have two needs related to the development of RICH applications on JS. In our opinion, the transition of most of the development to the browser is not far off, it is time to actively prepare.

    Coffeeline inline documentation parser (a-la JavaDoc)


    CoffeeScript quickly grew from a Jeremy toy into a full-fledged language. And no matter how hard he tries to stay as JavaScript as possible, there are significant differences. These differences impose restrictions on the use of tools designed for JS with it. Some time ago, CoffeeLint appeared, followed by CoffeeDoc. Unfortunately, the latter followed the path of docco and Coffee did not have a strict analogue of JSDoc and YARD.

    Since Coffee settled in Rails, he has settled in our hearts. Moreover, our practice has shown that the amount of coffee produced starts to overtake all other languages. With so many, a strict standard of inline documentation is a must.

    Help in documenting our open JS framework


    Of course we tried Backbone, Spine, ExtJS, Sproutcore (+ Ember.JS). Unfortunately, they all give the application power to the developer, defining only five modular entities. And if at first glance, freedom is great, then in practice the Conventions over Configurations approach has proved its effectiveness in the same Rails.

    His name is Joosy and he lives with us for three months. During this time, we managed to build on its basis two large projects that are being prepared for launch and continue to be used for all new ones. Joosy allows you to transparently transfer most of the Rails development (and therefore execution) to the browser.

    The framework is growing at an incredible rate, but problems have come with the transitional age. Tests and human memory are not enough even for us, and even for the release we will need not only dry internal API documentation, but also a full-fledged guide with examples.

    We want to invite to participation in its development a person who is ready, with our constant help, to understand in detail the project and coordinate the development of its documentation.

    Where to write?


    You can contact us using the address hello@roundlake.ru or through the personal mail of the inossidabile and Xternal users .

    Interaction issues are discussed individually and are aimed at ensuring that it is not only effective, but also comfortable for both parties.

    And, of course, we will be happy to discuss the “Hunt” in the comments below.

    Also popular now: