Adopting Bazar Model

Talha Mansoor published the first version of Elegant in 2012. It grew in popularity in a short time, due to its clean and functional style.

In November 2018, Matija Šuklje called Elegant’s community into a discussion about the future of the theme. Response was immense. Talha was the first to support the proposal of changing the development model from a single-developer to a community-led project.

He moved Elegant from a personal repository to a separate organization Pelican-Elegant, and added active community members to the team.

This way, the bus factor of the project has greatly improved.

New Governance Model

Since the code base is now tended by more than one, team has put in place some basic rules of governance to avoid people stepping on each-others toes.

We clarified the outbound and inbound licensing situation. We release Elegant (outbound license) under the MIT license and its documentation under the CC-BY-4.0 license. All code contributions are made directly under the “Inbound=Outbound licensing model”. What it means is that, the license everyone contributes their code under (i.e. inbound license) is same as the license that the code is then released under to the general public.

The contribution guidelines are also updated and should be easier to follow now.

We have also started discussing how to vote on new features and other important decisions, which we will put into effect soon.

New Documentation Website

Any good project needs good documentation and deserves a good homepage.

We decided to eat our own dog food and host Elegant documentation on an Elegant-themed Pelican instance. This serves three purposes. One, hosts documentation, two, showcases Elegant features, and third, a testing ground to try out new ideas.

This resulted in elegant.onCrashReboot.com.

Future releases

As we write this blog post, the discussion on how to tackle future releases is still on-going.

Right now, the discussion seems to go in the line of:

  1. 2.0 – All those fixes and features that do not require creating Pelican plugins or changes in Pelican code. This release will have updated documentation too.
  2. 2.1 – Make theme compatible with Pelican 4.
  3. 3.0 – Next generation Elegant – the biggest goal is to remove dependency on Bootstrap, to make it easier to maintain. 3.0.0 should have feature parity with 2.0.0.

Like this post? Share on: TwitterFacebookEmail


Pablo Iranzo Gómez Avatar Pablo Iranzo Gómez opensource enthusiast and Lego fan doing some python simple programs like @redken_bot in telegram, etc

Keep Reading


Published

Last Updated

Category

Contributing

Tags

Stay in Touch

Get Monthly Updates