@Moult Thanks for bringing me and Antonio in to the discussion!
I don't know much of the history here, or what's best for OSARCH, so I can't comment on that. What I can say is what we are looking for with IFC.js: a place to point potential donators to as a means to support AEC FOSS. Right now this potential is wasted, and we have to turn people down, which is incredibly unfortunate. To me, @aothms suggestion:
A narrow focus BIM funding group where we do actual development/projects. And a much broader ARCH group that doesn't do development, but more evangelization and funding others.
makes sense, so that people pointed to the dev. group for donations feel like they're contributing to dev work, not a broader-scoped fund. Eventually we could decide together what to do with the funding, but for now I have no idea how much funding would practically come in, so that's a hard decision we can just postpone, if it were up to me. https://opencollective.com/opensourcebim would work.
Beyond funding, I'd like to place our project under the umbrella of an ARCH group in a way that is visible on the umbrella group and from our project, this can be completely symbolic at the start, see where it goes. Only thing needed here is consistent terminology and imagery, I think?
If this is OK with you, I would be happy putting the logo on our github page/docs (https://community.osarch.org/discussion/310/hunt-for-the-new-osarch-org-logo/p4) with the text "member of OSARCH" or similar, then https://osarch.org/ can include a "members" list linking back to IFC.js. The goal here is just visibility: people on OSARCH can find us, people finding us can find OSARCH, and consistency: what are all these different projects and are they connected somehow? (To my understanding, this does not exist yet, right? At least I don't see references that indicate that BlenderBIM and FreeCad are connected through OSARCH on the respective sites). This membership doesn't have to really mean anything, it can serve just to structure FOSS AEC landscape. We already did this with IFC.js, which exists of the combined projects of me, @agviegas and Harry, but I'd like to take this further. Once again correct me if I'm wrong, and this already exists (for instance the wiki has an overview page).
Let me know what you think, I would rather just do this and worry about the details later, but maybe that's not the way to go.
Hey all - it's a happy 2022 and I think now is ripe to resurrect this thread.
OSArch, even without being a formal organisation, achieved a lot last year. A total of 26 AEC events were either hosted or advertised by OSArch, including the awesome ongoing OSArch Monthly Meetups organised by @Jesusbill with exposure to important industry bodies like FOSDEM and BILT. 14 news articles were published by OSArch.org. The newly launched OSArch subscription now has 100 subscribers. We migrated to Liberachat and registered a community under Libera, with a regular ~40 nicks. The Wiki is up to 4,500 edits, with 500 of those by @duncan alone. Learn.OSArch.org was also launched last year thanks to @SigmaDimensions . 500 new users joined the OSArch Community, a growth of ~50%, contributing ~5200 posts, a growth of 100%, with a thousand unique visitors every day. We helped create connections between FOSS projects, such as continued collaboration between Homemaker, Topologic and the BlenderBIM Add-on. Similarly, IfcOpenShell joined forces with FreeCAD under the OpenCAx umbrella for GSoC. OSArchOrg on Twitter (started Nov 2020) now has 1,780 followers, and OSArch.org on LinkedIn has 1,529 followers. We are also starting to be recognised as a brand, with our logo on the Speckle event, and consistently advertised as such in presentations / talks.
This has all been made possible by all of us together.
I think now is a great time to consider what we want to achieve in 2022. I was reminded by @SigmaDimensions of the post @duncan made here where he talks about having a temporary steering committee. I'd like to pick up where he left off.
The biggest goal I would personally like to see OSArch achieve, is to start making steps to a sustainable FOSS community. A sustainable FOSS community is one where connections are easy to make between FOSS initiatives. We want to encourage synergy, not duplication. This means building up the Wiki, encouraging casual conversation and meetups, and keeping people posted on updates on projects that might be related. A sustainable FOSS community is one which guides newcomers with various skills to find a place for them to fit in and contribute. This means mentorship, breaking down the geeky coding barriers to non-coders, and training. A sustainable FOSS community is one where contributions are reimbursed financially. We want to provide resources for the people, and we can only do that at scale if we ourselves have the financial means to sponsor development, host events, and create commercial partnerships, of which legal representation makes things easier.
Here's what I'd personally like to see in 2022:
Find a project lead to consistently publish news articles, aiming at about 2 articles per month. I am inspired by the work done by Librearts, and think we can do something similar. I think this is a high value, but currently at-risk initiative due to the lack of contributors, and I'd love to see it back on track.
Nominate a temporary steering committee, based on the guidelines of @duncan's post here and my proposal here. A steering committee can help turn hopeful discussion into realities.
Set up a legal organisation. Anywhere is better than nowhere. If we make mistakes, it can be dissolved and recreated elsewhere in the future. As we've seen so far, a legal organisation is not strictly necessary to have an impact, but having a lightweight one can open up opportunities. With it, I'd like to see preliminary transparent budgeting and accounting, so we can start placing some hard numbers against ambitions for future initiatives.
Create a structured professional training program for OpenBIM and open source. Self-learning and self-discovery does not work for everyone. This should be something someone can get some form of academic recognition or certification from. This can also be an income stream to help sponsor development on FOSS projects.
Host an OSArch Hackathon event. I am inspired by @aothms desire to run AEC events from a FOSS lens. I'd like to propose running our own version of GSoC: a mini-GSoC. Participants (not just students) can propose project ideas on any FOSS AEC project that they can hack on between 1-2 weeks. Just a small feature here, a small feature there. However, we can run it as a formal Hackathon event, with a stipend paid to reimburse participants for their contributions. These stipends may be financed through event sponsors who want to promote investment in FOSS AEC. At the end of it, we can host a shared presentation on what was achieved on each project. I see GSoC as a tried and tested model that is easily communicated to potential financiers and academia. I see the scaled down version of 1-2 weeks and financial stipend to be something achievable (we don't have funds for full time programmers) and a stepping stone towards encouraging all FOSS development to be financially sustainable. If it works out, it may be a regular event.
Reinforce a brand or umbrella of projects that agree and support the values of OSArch. @agviegas and @tomvandig talked about how even symbolically OSArch can be seen as a brand of ideals to stand behind. I'd like to get a number of organisations and some branding guidelines, as well as the OSArch symbol recognised in this way. Similarly, I see this as a way to help connect international communities that might wish to be independent, yet still relate back to OSArch. I'd especially love to see OSArch connections to non-English speaking communities. The tools and ideals we build, after all, are for everyone, and although one-size may not fit all, I see affiliations as a good thing.
I'll stop here, since this is getting a bit long, but I hope I've helped resurrect this thread constructively, and would love to hear your thoughts, and let's make 2022 another awesome year! Happy hacking!
Find a project lead to consistently publish news articles, aiming at about 2 articles per month. I am inspired by the work done by Librearts, and think we can do something similar. I think this is a high value, but currently at-risk initiative due to the lack of contributors, and I'd love to see it back on track.
Unfortunately, I don't think I will be able to be back to this, but as I contributed for a while, I have some comments. I really like the way Librearts organize the posts. The weekly recap (should be monthly in our case?) is useful because you can join several subjects and write a longer and diverse post. One of the things I struggled with was to write a full article about a new software release, because I couldn't find much to say other than the release notes (maybe someone else can do this better). I also like the idea of having other categories of posts, like workflows, tutorials and interviews. It helps to gather more potential subjects to write.
Create a structured professional training program for OpenBIM and open source.
Would that include coding? As an aspiring coder, I would like to see this kind of training and be able to contribute to some projects.
I really like the ideas and hope we can achieve that in 2022!
@bruno_perdigao good idea! Monthly recap posts will be a great idea. Hopefully with minimal overlap with Librearts. News articles may include new releases, new tutorials, new downloadable resources / assets, maybe written interviews of developers, software reviews, and call for paid jobs to do with FOSS AEC.
As for the training program, yes. It should include coding. I am currently toying with the idea of partnering with E-Zigurat, an online university who helped deliver an OpenBIM + Python training course. We can supply the content and live sessions and student support, and they can supply the online course platform, student admin, recordings, and certification. I haven't asked them, but I'm currently doing a course with them now which includes coding and IfcOpenShell training (see the OSArch events calendar) and I think it could be promising to run it regularly, perhaps with a profit sharing scheme to then help sponsor more development on FOSS projects.
Comments
@Moult Thanks for bringing me and Antonio in to the discussion!
I don't know much of the history here, or what's best for OSARCH, so I can't comment on that. What I can say is what we are looking for with IFC.js: a place to point potential donators to as a means to support AEC FOSS. Right now this potential is wasted, and we have to turn people down, which is incredibly unfortunate. To me, @aothms suggestion:
makes sense, so that people pointed to the dev. group for donations feel like they're contributing to dev work, not a broader-scoped fund. Eventually we could decide together what to do with the funding, but for now I have no idea how much funding would practically come in, so that's a hard decision we can just postpone, if it were up to me. https://opencollective.com/opensourcebim would work.
Beyond funding, I'd like to place our project under the umbrella of an ARCH group in a way that is visible on the umbrella group and from our project, this can be completely symbolic at the start, see where it goes. Only thing needed here is consistent terminology and imagery, I think?
If this is OK with you, I would be happy putting the logo on our github page/docs (https://community.osarch.org/discussion/310/hunt-for-the-new-osarch-org-logo/p4) with the text "member of OSARCH" or similar, then https://osarch.org/ can include a "members" list linking back to IFC.js. The goal here is just visibility: people on OSARCH can find us, people finding us can find OSARCH, and consistency: what are all these different projects and are they connected somehow? (To my understanding, this does not exist yet, right? At least I don't see references that indicate that BlenderBIM and FreeCad are connected through OSARCH on the respective sites). This membership doesn't have to really mean anything, it can serve just to structure FOSS AEC landscape. We already did this with IFC.js, which exists of the combined projects of me, @agviegas and Harry, but I'd like to take this further. Once again correct me if I'm wrong, and this already exists (for instance the wiki has an overview page).
Let me know what you think, I would rather just do this and worry about the details later, but maybe that's not the way to go.
@tomvandig have a read of the earlier parts of this thread, even a quick read, to get an idea of where this discussion has gone.
Hey all - it's a happy 2022 and I think now is ripe to resurrect this thread.
OSArch, even without being a formal organisation, achieved a lot last year. A total of 26 AEC events were either hosted or advertised by OSArch, including the awesome ongoing OSArch Monthly Meetups organised by @Jesusbill with exposure to important industry bodies like FOSDEM and BILT. 14 news articles were published by OSArch.org. The newly launched OSArch subscription now has 100 subscribers. We migrated to Liberachat and registered a community under Libera, with a regular ~40 nicks. The Wiki is up to 4,500 edits, with 500 of those by @duncan alone. Learn.OSArch.org was also launched last year thanks to @SigmaDimensions . 500 new users joined the OSArch Community, a growth of ~50%, contributing ~5200 posts, a growth of 100%, with a thousand unique visitors every day. We helped create connections between FOSS projects, such as continued collaboration between Homemaker, Topologic and the BlenderBIM Add-on. Similarly, IfcOpenShell joined forces with FreeCAD under the OpenCAx umbrella for GSoC. OSArchOrg on Twitter (started Nov 2020) now has 1,780 followers, and OSArch.org on LinkedIn has 1,529 followers. We are also starting to be recognised as a brand, with our logo on the Speckle event, and consistently advertised as such in presentations / talks.
This has all been made possible by all of us together.
I think now is a great time to consider what we want to achieve in 2022. I was reminded by @SigmaDimensions of the post @duncan made here where he talks about having a temporary steering committee. I'd like to pick up where he left off.
The biggest goal I would personally like to see OSArch achieve, is to start making steps to a sustainable FOSS community. A sustainable FOSS community is one where connections are easy to make between FOSS initiatives. We want to encourage synergy, not duplication. This means building up the Wiki, encouraging casual conversation and meetups, and keeping people posted on updates on projects that might be related. A sustainable FOSS community is one which guides newcomers with various skills to find a place for them to fit in and contribute. This means mentorship, breaking down the geeky coding barriers to non-coders, and training. A sustainable FOSS community is one where contributions are reimbursed financially. We want to provide resources for the people, and we can only do that at scale if we ourselves have the financial means to sponsor development, host events, and create commercial partnerships, of which legal representation makes things easier.
Here's what I'd personally like to see in 2022:
I'll stop here, since this is getting a bit long, but I hope I've helped resurrect this thread constructively, and would love to hear your thoughts, and let's make 2022 another awesome year! Happy hacking!
Unfortunately, I don't think I will be able to be back to this, but as I contributed for a while, I have some comments. I really like the way Librearts organize the posts. The weekly recap (should be monthly in our case?) is useful because you can join several subjects and write a longer and diverse post. One of the things I struggled with was to write a full article about a new software release, because I couldn't find much to say other than the release notes (maybe someone else can do this better). I also like the idea of having other categories of posts, like workflows, tutorials and interviews. It helps to gather more potential subjects to write.
Would that include coding? As an aspiring coder, I would like to see this kind of training and be able to contribute to some projects.
I really like the ideas and hope we can achieve that in 2022!
@bruno_perdigao good idea! Monthly recap posts will be a great idea. Hopefully with minimal overlap with Librearts. News articles may include new releases, new tutorials, new downloadable resources / assets, maybe written interviews of developers, software reviews, and call for paid jobs to do with FOSS AEC.
As for the training program, yes. It should include coding. I am currently toying with the idea of partnering with E-Zigurat, an online university who helped deliver an OpenBIM + Python training course. We can supply the content and live sessions and student support, and they can supply the online course platform, student admin, recordings, and certification. I haven't asked them, but I'm currently doing a course with them now which includes coding and IfcOpenShell training (see the OSArch events calendar) and I think it could be promising to run it regularly, perhaps with a profit sharing scheme to then help sponsor more development on FOSS projects.