Hi Everyone!
I have published my first package: Cadence. I was going to wait until I had more nodes in the package before publishing it, but then I found someone needed these nodes.
I know @GavinNicholls is probably going to roast me for publishing a package with only 3 nodes and cluttering up the package repository, but I will try to get more nodes in there soon. The nodes that I’m developing will have at their core a mix of Code Blocks and a few Python Scripts.
The description and keywords of the package need better elaboration, and the annotations and licence declarations of the scripts in the nodes probably need to be better. Actually, I don’t really know much about licences, so I copied an example from @jacob.small and added Apache 2.0 under a properties header with a licence file in the extra folder.
Any opinions, suggestions or pointers for improvement would be welcome.
Crumple began as 2 nodes I think, no worries - just stick at it!
I techically have a 1 node package lurking on there that is waiting for me to feel motivated enough to look into C# for Dynamo if I find my way back to it…
The more C3D packages available the better, and I like the package name as well. I like that the package originated in a problem you needed to solve that you wanted to package to share with others as well, commendable motivations.
This is good to hear about a new package, the only things i would add are as follows:
Do add any compatibility information onto the package. eg that its for Civil 3d 2025 and above. This will stop/mitigate someone installing it onto any other software, then creating posts that it does not work.
Do indicate within the description any info on the python engine that is utilised, though i would suggest you move to pythonnet3 package for the python engine in civil3d 2025 and 2026 because this engine becomes the default in Dynamo V4 which is hosted within Civil 3d 2027.
Great first use case and publish! The more packages we have in the community the better!
I agree with @GavinNicholls - it isn’t the number of nodes which make a package great - I have a few ‘only one node’ packages in my toolbox. Side note for Gavin - I keep half heartedly looking for a venue for a Indian Jones themed workshop/presentation called “Because I hate Snakes: Moving from Python to C# for Dynamo Development”, but it’s tough to find a venue… BILT Europe’s likely the front runner if the timing works out in the coming year, but if you’ve got other thoughts on how to get that type of stuff out there let me know.
I don’t want to distract from your new package @ISECnico, so if you have questions on licenses and packages feel free to start a new forum topic on 'how to select a package license - I promise to weigh in with my usual mix of info and opinion.
Haha honestly I need to get back to ZT packages in Dynamo eventually. Mostly been dabbling with add-ins these days… still use plenty of Python nodes in Dynamo but feeding a lot of AI generated stuff in there vs writing insitu these days - time poor.
Generally stuck using Revit 2025 at the moment where I’ve found Dynamo’s stability… mixed… to be honest - might return to it once I’ve got up to R26 or R27 as my home base. Hard to get users on board if my Dynamo scripts (and often just launching Player, or it is buried o the second screen until users closes it) crash 'em out.
Was going to try loading up Claude with as much context as I could and see how far it gets too an experiment, so Dynamo packages might be the project I give it.
Cadence. 
I was going to wait until I had more nodes in the package before publishing it, but then I found someone needed these nodes. 
