What do you think? Is this a good standard? The infobox on the side is my first stab at getting it to work dynamically as a template (to avoid having to fuss with the layout one very single page).
Question: what do you think should be in the infobox? There are two types of information: required & not required. Anything requires will always be shown even if it is not filled in. Anything not required will only be shown if that information is supplied on the page. Because the way to add an infobox to a page is to copy and paste the template there is an advantage to having all the fields that could reasonable be useful. People can't just add their own field because they want to.
Please remember: the software page is just an introduction and a reference for people to keep learning and to encourage them to browse to other useful pages. Here is an example of a software page on wikipedia https://en.wikipedia.org/wiki/Inkscape
I think the Software Page is good to explain the potential of the software in the AEC field, to show the possible workflows and compatibilities with other AEC software, to link with examples an tutorials of the tool being used in AEC projects, etc. (link to Open Source Educational Resources). Also I would include a link to our Donation Directory if the software is listed there.
I was wrong. I thought I'd worked out how to make some pieces of information not required. It doesn't work. Maybe someone else would like to have a try. Just copy the template to your own user page and use it on a subpage. @bitacovir I've added donation
CoFEA: An initiative that aims to popularise application of open-source simulation software in solving real engineering problems. Even though CoFEA itself sounds like the magic drink which drives engineering minds, it is a combination of the words cooperation and Finite Element Analysis. The aim of the project is to create an environment where engineers could exchange theirs experience and knowledge of open-source simulation codes so that others could use them with joy and confidence.
Interesting project, will be adding it to the wiki shortly and talk to the people behind it. Candidate for a "structural-oriented" meetup presentation
BitByBit: An open source, frictionless web platform that allows creators to program geometry through simple visual programming language or choose monaco typescript editor with full intellisense of bitbybit API. This tool is great for all ages and can fulfil many artistic, educational, and practical needs of its users. Through familiar programming interface used in tools such as Scratch and Blockly.Games we expose powerful 3D algorithms that make it easier to implement various parametric tasks. Our goal is to make it very simple for users to share their ideas and designs by just exporting and importing scripts, uploading designs, and participating in lively discussions on Discord. We want to encourage everyone to engage in the future of this tool.
Very interesting project! Visual programming on the web! I didn't see a license file in github, maybe I missed it. I will reach out to the main developer, we got connected in LinkedIn. Will be adding it to the wiki shortly. Candidate for a meetup presentation (not until we have a clear image of the open source nature).
@bitacovir the term "Open Source" has a definition and a set of licenses that guarantee some rights. It does not just mean anyone can see the source code. A good reference when unsure is the Open Source Definition
@Jesusbill looks to me like they're planning to be Open Core with a mixture of licenses.
Principles
BitByBit will always keep it's Core free and opensource for its users. ... All Core algorithms will always remain opensource
Until they define which parts of the code are actually libre/OSS we can't invite them to this party. Looks a bit like openwashing to me. If the devs need help choosing a license I'm sure we can help. As it stands they don't sound very open at all https://bitbybit.dev/terms-and-conditions
@duncan yes I need to ask the main developer. However, what you link is the terms and conditions of the platform and I would think not necessarily of the code that there is in GitHub.
In any case, I think it is okay to post projects in this directory so that we can inspect them better and then decide whether to include them in the Free Software Directory.
@Jesusbill said
In any case, I think it is okay to post projects in this directory so that we can inspect them better and then decide whether to include them in the Free Software Directory.
If "directory" is this discussion and "Directory" is the list then I agree.
@bitacovir there are a few areas like that which I think would work better as a general page about a subject. More like a page for "Visualisation and Documentation" with a resource list. Each of those things would be good as a point on a list - but not as a whole section cluttering up a software list. I've now started looking for software type taxonomies to see if there is anything out there before we start re-inventing the wheel.
I see some discussion of Blender Add-ons. Remember to add Blender Add-ons to the Software Directory and to the wiki page on Blender and if they can get their own page also add them to the Blender Add-on Category
@bimspot sounds like you might be curious about what Free Software is rather than free software. First thing to learn ... even the name is confusing... I prefer "libre software" to avoid the whole "free-beer or free-dom" issue. Great to have you visiting us! What brings you here? We do have a few listing of important software which support openbim. https://wiki.osarch.org/index.php?title=Free_software_extensions_to_proprietary_software
GAMA is a modeling and simulation development environment for building spatially explicit agent-based simulations. https://gama-platform.github.io/wiki/Home GPL v3.0 license
OpenSimulator is an open source multi-platform, multi-user 3D application server. It can be used to create a virtual environment (or world) which can be accessed through a variety of clients, on multiple protocols http://opensimulator.org/wiki/Main_Page BSD license
Simulation of Urban MObility (SUMO) is an open source, portable, microscopic and continuous multi-modal traffic simulation package designed to handle large networks. https://eclipse.org/sumo Eclipse Public License
UrbanSim is an open source urban simulation system designed by Paul Waddell of the University of California, Berkeley and developed with numerous collaborators to support metropolitan land use, transportation, and environmental planning. https://github.com/UDST/urbansim New BSD License
To add a wiki page to a category you need to add a special piece of wiki markup to the (end of the) page. For a page to go into the Blender Add-on category that text would be
[[Category:Blender Add-on]]
The list of categories currently available is here: https://wiki.osarch.org/index.php?title=Category:Categories @fbpyr
Comments
I've been doing some work on the layout of software pages for the wiki and have this basic page as an example: https://wiki.osarch.org/index.php?title=Inkscape
What do you think? Is this a good standard? The infobox on the side is my first stab at getting it to work dynamically as a template (to avoid having to fuss with the layout one very single page).
Question: what do you think should be in the infobox? There are two types of information: required & not required. Anything requires will always be shown even if it is not filled in. Anything not required will only be shown if that information is supplied on the page. Because the way to add an infobox to a page is to copy and paste the template there is an advantage to having all the fields that could reasonable be useful. People can't just add their own field because they want to.
Please remember: the software page is just an introduction and a reference for people to keep learning and to encourage them to browse to other useful pages. Here is an example of a software page on wikipedia https://en.wikipedia.org/wiki/Inkscape
I think the Software Page is good to explain the potential of the software in the AEC field, to show the possible workflows and compatibilities with other AEC software, to link with examples an tutorials of the tool being used in AEC projects, etc. (link to Open Source Educational Resources). Also I would include a link to our Donation Directory if the software is listed there.
I was wrong. I thought I'd worked out how to make some pieces of information not required. It doesn't work. Maybe someone else would like to have a try. Just copy the template to your own user page and use it on a subpage.
@bitacovir I've added donation
I just updated the license for open drone map because I saw that they changed it to AGPLv2 for all new versions. I assume that was the right thing to do. They also included this link to an explainer about why AGPL in their post https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html
https://www.opendronemap.org/2020/12/ghost-busting-speed-improvements-and-switch-to-agpl-with-2-3-0/
CoFEA: An initiative that aims to popularise application of open-source simulation software in solving real engineering problems. Even though CoFEA itself sounds like the magic drink which drives engineering minds, it is a combination of the words cooperation and Finite Element Analysis. The aim of the project is to create an environment where engineers could exchange theirs experience and knowledge of open-source simulation codes so that others could use them with joy and confidence.
Interesting project, will be adding it to the wiki shortly and talk to the people behind it. Candidate for a "structural-oriented" meetup presentation
BitByBit: An open source, frictionless web platform that allows creators to program geometry through simple visual programming language or choose monaco typescript editor with full intellisense of bitbybit API. This tool is great for all ages and can fulfil many artistic, educational, and practical needs of its users. Through familiar programming interface used in tools such as Scratch and Blockly.Games we expose powerful 3D algorithms that make it easier to implement various parametric tasks. Our goal is to make it very simple for users to share their ideas and designs by just exporting and importing scripts, uploading designs, and participating in lively discussions on Discord. We want to encourage everyone to engage in the future of this tool.
Very interesting project! Visual programming on the web! I didn't see a license file in github, maybe I missed it. I will reach out to the main developer, we got connected in LinkedIn. Will be adding it to the wiki shortly. Candidate for a meetup presentation (not until we have a clear image of the open source nature).
It is open source because we can see the code in guthub, but it is not clear about the licenses.
@bitacovir the term "Open Source" has a definition and a set of licenses that guarantee some rights. It does not just mean anyone can see the source code. A good reference when unsure is the Open Source Definition
@Jesusbill looks to me like they're planning to be Open Core with a mixture of licenses.
Until they define which parts of the code are actually libre/OSS we can't invite them to this party. Looks a bit like openwashing to me. If the devs need help choosing a license I'm sure we can help. As it stands they don't sound very open at all https://bitbybit.dev/terms-and-conditions
@duncan yes I need to ask the main developer. However, what you link is the terms and conditions of the platform and I would think not necessarily of the code that there is in GitHub.
In any case, I think it is okay to post projects in this directory so that we can inspect them better and then decide whether to include them in the Free Software Directory.
Open source game engine, python based.
https://gamefromscratch.com/ursina-engine/
If "directory" is this discussion and "Directory" is the list then I agree.
@duncan yes that is what I meant
I was thinking on a new subcategory under Visualisation and Documentation: Library (texture, models, hdri). To add
https://www.sharetextures.com/
https://3dtextures.me/
https://cc0textures.com/
https://3dmodelhaven.com/
etc...
@bitacovir there are a few areas like that which I think would work better as a general page about a subject. More like a page for "Visualisation and Documentation" with a resource list. Each of those things would be good as a point on a list - but not as a whole section cluttering up a software list. I've now started looking for software type taxonomies to see if there is anything out there before we start re-inventing the wheel.
Can I encourage you to start a wiki page "Visualisation and Documentation" and link to it from https://wiki.osarch.org/index.php?title=AEC_Free_Software_directory#Visualisation_and_Documentation
I see some discussion of Blender Add-ons. Remember to add Blender Add-ons to the Software Directory and to the wiki page on Blender and if they can get their own page also add them to the Blender Add-on Category
looks very cool: https://3d.bk.tudelft.nl/code/ thanks @KasperMiller
added to directory talk page
Set of Blender addons for CAD. Probably too focused on mechanical design?
https://github.com/EleotleCram/blender-cad-tools
interesting list
SPAM!
@bitacovir why do you say I am spam? I just indicated a tool in a topic about free AEC software...
@bimspot I think the suggestion is that the software you have linked to is not free software. See the definition of free software.
I OK, my bad... sorry for that... I was thinking of openBIM, so I will remove the comment.
@bimspot sounds like you might be curious about what Free Software is rather than free software. First thing to learn ... even the name is confusing... I prefer "libre software" to avoid the whole "free-beer or free-dom" issue. Great to have you visiting us! What brings you here? We do have a few listing of important software which support openbim. https://wiki.osarch.org/index.php?title=Free_software_extensions_to_proprietary_software
Done: https://wiki.osarch.org/index.php?title=FLOSS_Visualisation_and_Documentation
GAMA is a modeling and simulation development environment for building spatially explicit agent-based simulations.
https://gama-platform.github.io/wiki/Home GPL v3.0 license
OpenSimulator is an open source multi-platform, multi-user 3D application server. It can be used to create a virtual environment (or world) which can be accessed through a variety of clients, on multiple protocols
http://opensimulator.org/wiki/Main_Page BSD license
Simulation of Urban MObility (SUMO) is an open source, portable, microscopic and continuous multi-modal traffic simulation package designed to handle large networks.
https://eclipse.org/sumo Eclipse Public License
UrbanSim is an open source urban simulation system designed by Paul Waddell of the University of California, Berkeley and developed with numerous collaborators to support metropolitan land use, transportation, and environmental planning.
https://github.com/UDST/urbansim New BSD License
Recently discovered BlenderFDS. Wow. Blender seems to increasingly do everything. https://github.com/firetools/blenderfds
Yes. It is already in our list. :)
I've changed the license for FDS to GNU3.0 https://github.com/firetools/blenderfds/blob/master/LICENSE
To add a wiki page to a category you need to add a special piece of wiki markup to the (end of the) page. For a page to go into the Blender Add-on category that text would be
[[Category:Blender Add-on]]
The list of categories currently available is here: https://wiki.osarch.org/index.php?title=Category:Categories
@fbpyr
@fbpyr I've added the construction lines add-on to the category page which is a quick way to add things to the wiki and still have them be found https://wiki.osarch.org/index.php?title=Category:Blender_Add-on