hi All, Its been a while since we've seen a pythonocc release. The reason why is that the pythonocc core developers have been working hard launching the OCE <https://github.com/tpaviot/oce> initiative. OCE is a repository where the open source OCC developers share their patches / bugfixes etc. OCE is a significant effort to secure the agile and distributed development of OCC. Good news is that OCC has been really responsive to the project and the OCE dev's are looking fwd to working closer with the OCC team.
A lot of progress has been made so far in OCE; finally most of the OS contributions are found in a single repository, while so far individuals developers had their repositories, leading to a mayhem of fragmented development. So, OCE has made an important step forward to the cohesion of OCC developers. OCE is *easy* to build, is continuously tested and provides moder build and packaging tools. Now, how does this affect pythonocc? Pythonocc built on OCE, such that our users can install from OCE binaries. This speeds up pythonocc development significantly, since changes to OCE [ which evolves at a high pace ] will reflect to pythonocc directly. So far OCC has been putting out very few releases [ although there is the intention now that Salome + OCC dev's will use the same repository, releasing twice a year ], which reflects on pythonocc too. >From pythonocc 0.6 on pythonocc will keep tread with developments in OCE. This is _very_ good news! So, what are the ambitions for the following release? - #1 switch to OCE - #2 the OCC.KBE module offers a high level, well structured pythonic API - #3 Henrik Rudstrøm has done a great job in providing excellent sphinx based documentation, I'd love to see this project completed for the 0.6 release - #4 I'd like pythonocc to be well integrated with PyPi. Can you imagine being able to install pythonocc like: "sudo pip install pythonocc"? - #5 The examples<http://code.google.com/p/pythonocc/source/browse/#svn%2Ftrunk%2Fsrc%2Fexamples%2FLevel1>are very unpythonic and do not reflect the state of the project at all. The examples will reflect the advancements made of the past 2 years. Refactor! Thomas and myself will focus on #1, #2 and #5. Hopefully that answers your question "where do I pitch in?" Glad you asked; PyPi integration is an interesting project in itself, and would be a huge boost for the pythonocc project. Do I have a volunteer? With regard to the Henrik's documentation effort<http://code.google.com/p/pythonocc/source/browse/branches/wrapper_refactor_doc/src/wrapper_refactored/doc_generator.py>; its hard for me to say in what shape or state this code is, so I hope to hear from you soon ;) What struck Thomas and myself is that the OCE project is that there are _far_ more committers on this project than on pythonocc. Why is that? At this moment pythonocc is 98% driven mostly by Thomas and myself. We'd very much like to see this change. Please let us know what we can do from our side to involve the pythonocc community in contributing code. If you have constructive thoughts on how to involve the pythonocc community closer to the project, than please do tell! I consider this the greatest priority! PythonOCC 0.6 is scheduled for release end of september. Thanks, -jelle
_______________________________________________ Pythonocc-users mailing list [email protected] https://mail.gna.org/listinfo/pythonocc-users
