[Cubicweb] A roadmap to Cubicweb 3.28 (and beyond)

Cesar Lugo Marcos cesar.lugo.marcos at juicemantics.com
Fri May 15 19:53:55 CEST 2020

Hello, I'm new to the mailing lists but have 8 experience with CubicWeb
using your documentation self sufficient, being able to build a large
application with more than a hundred main Entities, integrate it with data
science and interactive charts third party libraries, nice! thank you and

On the other hand, Cubes in the Forge are very valuable and help a lot to
speed things up, and add valuable capabilities. Only most of them have very
limited or no documentation at all, either on how to use them or the
purpose. I use some of them successfully , then tried to use some others
but didn't understand how they work.

When your say... In the medium term, we would like to focus on the
documentation of CubicWeb and
it's ecosystem.

Would you consider adding documentation to those cubes? I think it would be
very valuable.

Again, congratulations. I've used many frameworks for 30 years now and
honestly believe CubicWeb is among the best ones but right now the most
advanced one!

César Lugo.

El jue., 14 de mayo de 2020 3:31 a. m., Simon Chabot <
simon.chabot at logilab.fr> escribió:

> Hi list,
> Last Tuesday at Logilab we had a small meeting to discuss about a roadmap
> to
> Cubicweb 3.28 (and beyond), and we would like to report back to you from
> this
> meeting.
> Cubicweb 3.28 will mainly bring the implementation of content negotiation.
> It
> means that Cubicweb will handle content negotiation and will be able to
> return
> RDF using Cubicweb's ontology when requested by a client.
> The 3.28 will have other features as well (like a new `variables`
> attributes to
> ResultSet that contains the name of the projected variables, etc). Those
> features will be detailed the release changelog.
> Before releasing this version, we would like to finish the migration to
> heptapod, to make sure that everything is ok. The remaining tasks are:
>     - fixing the CI (there is still some random failings, that need further
>       investigation)
>     - migrate the jenkins job that pushes images to hub.docker.com on
> heptapod,
>       to make everthing available from the forge. It will be explicit for
>       everyone when a job is done, and what is its status.
> Beside of releasing Cubicweb 3.28, its ecosystem will also be updated:
>     - logilab-common, a new version will be released very soon, which
> brings a
>       refactoring of the deprecation system, and annotations (coming from
>       pyannotate)
>     - yams, a new version is coming. This version:
>         - brings type annotation (manually done, a carefully checked);
>         - removes a lot of abbreviation to make the code clearer;
>         - removes some magic related to a object which used to behave like
> a
>           string (Laurent Peuch could give more details than myself I
> guess, if
>           need be);
> The goal of these two releases, is to have type annotations in the core
> libraries used by CubicWeb, and then to be able to bring type annotation
> into
> CubicWeb itself, in a future version.
> On those projects, some “modernisation” has been started too ; (fixing
> flake8
> when needed, repaint the code black [0]). This “modernisation” step is
> still on
> going on the different projects related to CubicWeb (and achieved for
> yams, and
> logilab-common).
> In the medium term, we would like to focus on the documentation of
> CubicWeb and
> it's ecosystem. We do know that it's really hard for newcomers (and even
> ourself
> sometime) to understand how to start, what each module is doing etc. An
> automatic documentation has been released for some modules (see [1], [2]
> or [3]
> for instance). It would be nice to automatize the update of the
> documentation on
> readthedocs, update the old examples, and add new ones about the new
> feature we
> are adding (like content negotiation, pyramid predicates, etc). This could
> be
> done in team Friday's sprint or hackathon for instance. CubicWeb would
> also need
> some modernisation (running black ? and above all, make all files flake8
> compilant…).
> Regarding CubicWeb development, all (or, at least a lot of) cubes and
> Cubicweb
> related projects moved from cubicweb.org's forge to our instance of
> heptapod
> ([4] and [5]). Some issues have been imported from cubicweb.org to
> heptapod. New
> issues should be opened on heptapod, and the review should also be done
> there.
> We hope that will ease the reappropriation of the code basis and
> stimulates new
> merge-requests :)
> To end this report, we like to emphasis that we will try to make a « remote
> Cubicweb meeting » each Tuesday at 2 pm. If you would like to participate
> to
> this meeting, it's with great pleasure [6]. We also created a #Cubicweb
> channel
> on matrix.logilab.org ; feel free to ask for an invitation if you'd like
> to
> discuss Cubicweb related things with us.
> All the best, and… see you next Tuesday :)
> Élodie, Fabien, Henri, Laurent et Simon.
> [0]: https://github.com/psf/black
> [1]: https://logilab-database.readthedocs.io/
> [2]: https://logilab-common.readthedocs.io/
> [3]: https://rql.readthedocs.io/
> [4]: https://forge.extranet.logilab.fr/cubicweb
> [5]: https://forge.extranet.logilab.fr/open-source
> [6]: if you need the webconference URL, contact one of us, we will provide
> it
>       to you.
> --
> Simon Chabot
> logilab.fr - services en informatique scientifique et gestion de
> connaissances
> _______________________________________________
> Cubicweb mailing list
> Cubicweb at lists.cubicweb.org
> https://lists.cubicweb.org/mailman/listinfo/cubicweb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubicweb.org/pipermail/cubicweb/attachments/20200515/b5e31a52/attachment-0142.html>

More information about the Cubicweb mailing list