@hack.near [Posted on Developer DAO Board](https://near.social/#/devgovgigs.near/widget/Post?id=347) ## Idea: bOS Development Cycle Hi bOS! Allow me to introduce a process for coordinating development of **common component libraries**. This can be used to establish a fair, transparent, and impactful rewards program, in order to support builders who are working on specific projects. ### Overview ##### GOALS The main objective is **empowering open collaboration** to share knowledge and maximize opportunities. * Facilitate Onboarding * Coordinate Projects * Support Builders ##### SCOPE We are focused on delivering a community program to engage contributors, learn together, and create solutions. * Recruiting Talent * Organizing Groups * Answering Questions ##### DELIVERABLES The details of each component library depend on its owners, but here is a general summary of desired outcomes. * New and Improved Documentation * Various Common Component Libraries * Streamlined Payment System for Contributors ### Process Essentially, the only requirement of participants is to make a post every two weeks (or so). **Step 1:** create a 2-week sprint #plan here on the Gigs Board **Step 2:** post #updates to learn, build, and solve problems together **Step 3:** submit a #report with details to be reviewed by the Work Group *→ Use #dev / #sprint and other helpful tags, and be sure to tag your components!* ##### TIMELINE Our development sprints begin every other Monday. **Experiment:** March 20-28 **Sprint 1:** April 3-14 **Sprint 2:** April 17-28 ##### RESOURCES The overall budget and compensation would be a responsibility of the bOS Work Group, which should be formally announced at the beginning of next month. Until then, I'm asking leaders of the #bOS dev community to participate in an experiment by following a suggested process, outlined below. This program is open to any builders who are contributing open web components on the blockchain operating system. Much of this work is inspired by the `CommonComponentsLibrary` [template](https://near.social/#/manzanal.near/widget/CommonComponentsLibrary?tab=home), which won first place in the Onboarding Track of a recent [Near Social Hackathon](https://social.near.page/p/hack.near/86920148). #### OG Component Librarians * #DevX ~ @manzanal.near + @bozon.near * #Search ~ @p516entropy.near + @efiz.near * #Design ~ @zahidulislam.near * #Mod ~ @chaotictempest.near * #Gaming ~ @ostolex.near * #DAO ~ @urbanite-social.near * #NFT ~ @microchipgnu.near + * #Wiki ~ @humanman.near + @eugenewolf507.near + @markeljan.near * #Org ~ @contribut3.near * #News ~ @nearweekapp.near * #ETH ~ @dineshkruplani.near * #DeFi ~ @0xprometheus.near * #Stake ~ @azbang.near + @zavodil.near * #Edu ~ @onboarder.near * #Art ~ @duocelot.near * #Gov ~ @devgovgigs.near + @silkking.near * #Docs ~ @dorgon108.near + @dgorton.near * #Auth ~ @adminalpha.near *One type of component library I'm especially interested in seeing developed would be for #data visualization. Here is an emergent collective of related widget builders:* @roshaan.near + @y3k.near + @reallyveryy.near + @sainthiago.near + @mohammadhs.near + @lord1.near + @9c461db4ac11b66ed1167ff969042ac278eaf2d571712585424be00171a63884 + @dataplatform.near ___ > Please reply to mention additional component libraries and / or contributors with respective tags! *For now, there are no expectations of these builders. My only request is for them to consider using the Gigs Board to share project updates via the SocialDB contract. Ideally, this would happen with a regular cadence to effectively drive progress with consistent productivity. Of course, all are welcome to build anything on the bOS.* ##### EXAMPLE On Monday, I'll be sharing my plans to improve this `MultiDAO` [component](https://near.social/#/hack.near/widget/MultiDAO), after considering feedback on this post. *Thanks to @frol.near of the Contract Standards WG and @hackerhouse.near of the DAO Builder Group for their help!* ___ Notice I'm following these [guidelines](https://www.neardevgov.org/blog/near-developer-governance-funding-guidelines), and I'll aim to reply with a Solution post by end of this month. In the meantime, I'd be happy to answer questions and explore ideas further. Really excited to learn more with everyone! Let's connect ♾️ @infinity.near