Mega maintenance

Published on

I spent an intensive week of countless hours cleaning up the Pepper&Carrot project. It was really necessary as the size of the project and number of contributions went -again- out of my control. Maintaining the overall project started to become a full-time job on its own and I was finding the structure of folders and repositories confusing... so... probably a lot more confusing for the community of contributors. I also desperately needed to find more time to produce future episodes and not only maintain what we have so far. Here are a list of important changes I did to keep scaling up:

Moving from Github to Framagit
I'm moving all the sources of Pepper&Carrot from GitHub to the open and friendly Framagit; Gitlab hosted by Framasoft (you can login to Framagit with your Github account). The repo on GitHub will be removed soon. Thanks again to GitHub for all the fun and hosting. Comment here to let me know your new @name on Framagit and I'll give you permission to clone and push.

Opening the code of the website
The website's php/xml code powered by PluXML and its theme and plugins are now finally open and have their own public repository.

Moving to a group
Pepper&Carrot moved to a group with multiple admin, centralized access permissions, pull request and bug tracker. I no longer own all the repositories under my personal account. This will help maintenance but also reduce the key person risk.

Merging all 25 git translation repos I merged our 25 translation Git repositories into a single one. It's now easier to manage. We still have all our revisions since project creation. The credits are also now centralized to a single at the root.

Simpler file-naming
We had plenty of svg named like that: Pepper-and-Carrot_by-David-Revoy_E##P##.svg ; they are now [E##P##.svg].

Adopting Inkscape 0.92.2
Our renderfarm now uses Inkscape 0.92.2 by default. It breaks small things here and there (punctuation in right-to-left languages) but I'm sure it can be fixed. (If a contributor mastering Arabic is around this is a call to fix our 'ar' folders). I hope those changes will prove to be the right decision! I tried to think "big" and make a structure able to handle Pepper&Carrot if it grows to 100 episodes... because this is where I want to go! To episode 100 and beyond ! :-)

License: "Mega maintenance" by David Revoy − CC-BY 4.0
Tags:  #maintainance  #website  #lab   | Download: Markdown


link ahz  

David, you are truly an artist in many ways. You set up a great website, you help bugfixing the FOSS and you have made nice tutorials. You are also able to draw a comics that cheers me up. Thank you.

link Pepca  

You know you can keep the Github automaticaly updated from the new Gitlab repository? Just setup a simple CI script and it will push your changes automatically. EE versions of Gitlab have some tool to do it even easier.

link CGand Translator,

@cgand on Framagit. Thanks.

link guruguru  

Hi David, I'm @gurugurusp on Framagit. Thanks :)

link Quiralta  

Hey David, @RJQuiralta is here! :D

link Alcean  

@Alcean ready for translating :)

link Alexandre  

Hi David, @almeidaxan here.
Nice to see some changes, especially regarding a more organized workflow. I really support your choice to merge all repos into one. Thanks for the update and keeping up this awesome project.

link David Revoy  

Thank you Ahz! After this long week of cleaning, refactoring and dealing with the technical part of the project, your comment cheers me up! ;-)

link David Revoy  

Thank you Pepca for the information. I didn't know and I studied yesterday evening a bit the situation. Yes, it's possible to sync things; Gitlab has mode to push or pull. But, it is also a problem for privacy: email of our contributors, commit names and our habit (hour we push, productivity, IP from where we push) are still available to a private entity like Github who can use it the way they want.
I decided I'll keep a single repository ; Deevad/peppercarrot , and on it a single with invitation and documentation to adapt to our Framagit page. This way, Github user who wants to use the search engine for a webcomic or Pepper&Carrot will still find the way to our privacy friendly new home.

link David Revoy  


link David Revoy  

Super! :-)

link David Revoy  

Merci !

link David Revoy  

Ha super, added !

link David Revoy  

Added! Nice to see you around!

link David Revoy  

Our group has now 18 members !
I'm sure we can grow to 30 :)

link Pranav  

@gitinator ready for translation.

link Châu  

Salut David, Love coding and work stories. ¡Merci for tell about Framagit too! @Navi wait translate next episode.

link libre fan  

Hello David,

I’m @libre_fan on Framagit.

Congratulations on your move to Framagit (Gitlab)!
Someone else will be delighted about this excellent piece of news:

link Aslan Zamanloo  

Hi there Deevad! Must have been a tremendous workload moving all the repositories from GitHub to Framagit. I made a new account on Framagit. My username is @aslanzm, ready to translate episode 24 into Persian. Any instructions on how to fork and push translations? Is Framagit just like GitHub? Thanks in advance.

link David Revoy  

Hey! Yes, it was a big big work !

Gitlab behaves well; we had no problem so far. I added you to get permission of developer. So, feel free to just clone the repo ( ) , work your langs in a branch, and merge it in master when ready.

Gitlab also give you the possibilty to fork under your profile; work there; and send later "merge request" (instead of "pull request" as on Github). So exept one or two words and a slightly different UI you'll not be lost. So far, I love it. Let me know if you need more info!

link Aslan Zamanloo  

Thanks for the super fast reply and the useful info! I'll let you know if I face any problems. Thanks again.

link Aslan Zamanloo  

Hi there again Deevad. I've translated the episode 24 into Farsi, and all that's left is pushing the files into the repository I've forked from The question is can't you upload multiple files via the web interface? In this case, I should upload the files one by one (which makes a commit for every upload), and the request a merge. Is there a simpler way of pushing files that I'm not aware of?

link David Revoy  

mm... I don't know a lot how to manage things via the web interface. I use git with the command line on Linux.
If you can't upload your work, just open an issue and attach a zip with your folders. I'll merge them manually.

link Aslan Zamanloo  

I'll do so. Sorry for the trouble.

link Moini  

framagit uses the gitlab software, and indeed, gitlab makes a new commit for each newly uploaded file.

If some time you'd like to learn how to use git on your computer (there are graphical programs for doing so, you do not need to be able to use the command line if you don't want to), you'll discover that it's not so hard.

Post a reply

The comments on this article are archived and unfortunately not yet connected to a dedicated post on Mastodon. Feel free to continue the discussion on the social media of your choice. Link to this post:

You can also quote my account so I'll get a notification.
(eg. on my Mastodon profile.)