1

Topic: Development help needed!

Pluck needs your help!
We are looking for PHP-coders to help with the development of pluck.

Some time ago, I myself quit working on pluck, because of my study. Spirit55555 and A_Bach are at the moment the only active members of the development team, but they don't always have a lot of time either. There already are some other people contributing code to pluck, but we would like more people helping us out!

If you're interested, please don't hestitate to leave a message here! Also, if you need help getting started, don't hestitate to ask. Your contributions would be highly appreciated.

Some links that may prove helpful:

2

Re: Development help needed!

I would love to help out on the development.

However, i'm not the most experienced PHP developer, but if I encounter problems I can easily work out how to fix them usually.

If you have any small tasks that need doing then i'm more than happy to help out smile

I'm currently developing modules, so i'm learning the Pluck system!

3

Re: Development help needed!

To reiterate my previous post, are there any small jobs that need doing?

I am more than happy to help out, however I fell uncomfortable working on anything massive. If you can tell me one thing you want doing, I'll work on it smile

4

Re: Development help needed!

RavenWing wrote:

To reiterate my previous post, are there any small jobs that need doing?

You are more than welcome to test our main branch for bugs, fix them in your own branch, and ask for them to be merged.

Work smart, not hard

Kan du læse det her?

5

Re: Development help needed!

I've made the smallest like 2 line edit to the album module, I checked out the latest revision and checked launchpad and certainly not major but, the error ignored me so I stopped it getting thrown.

Are the development team interested in receiving fixes such as this? Or is it wasted because of heavy re-implementation going on anyway?

6

Re: Development help needed!

Jeed wrote:

Are the development team interested in receiving fixes such as this? Or is it wasted because of heavy re-implementation going on anyway?

Even the smallest bug fix is more than welcome smile

Work smart, not hard

Kan du læse det her?

7

Re: Development help needed!

When I searched for a clean and simple CMS for a few, relatively simple, sites I stumbled upon Pluck. Version 4.6.3 impressed me with it's simplicity, especially way I could make my own theme and the backend. Version 4.7 seems to have a few nice new features like the SEO files and submenu so I decided to check the development branch and contribute back where I can. Yesterday I filed some bugs, issues and fixes to launchpad. But there are still some questions about working on Pluck so here we go. smile

One thing that bothers me is the workflow. How does it work for you... Right now I make a clean checkout, try to install a site and find some issues. Attempt to fix them locally and report the bug/fix on launchpad. When I see they are also fixed in the development branch I try to merge the local repo. I get a message from bazaar which tells me to commit but I don't feel like sharing my local version with the world. It contains no real value and contains mostly test code and ipsum lorem pages. So I throw away (or backup) the folder, checkout a clean version and start over. This is of course far from an ideal workflow so please enlighten me smile

Another point is there some information available on the internal changes for 4.7? On launchpad I read that 4.6.3 modules won't work with 4.7 but what is the difference. And what can we expect to break in the (near) future and how is this communicated among developers? Is there for instance a mailinglist?

If I want to make some changes to the gallery, like include an option to add only the selected album(s) instead of the whole gallery on a page, will these changes be accepted to the main branch? In other words what is the big picture? Or does the features grow where the devs need them most (fine by me but good to know).

Will pluck for version 4.7 have some way of dealing with multiple versions of the same site but in different languages. For instance build a site in my native language (Dutch) and translate the pages to English for a broader audience. This requires some serious code design and forces all modules must support this as well.

Well that's all for now. I'll be around both here and on launchpad.

Cheers,
Sander but to avoid confusion just call me San smile

8

Re: Development help needed!

I do all my bug fixes in a local version of the main branch, and update it when there are new commits. If I want to make a larger improvement, I register a new branch on launchpad, and commit my changes to that one. When it gets accepted, I merge it in to the main branch.
So I suggest that you create a branch of the main branch, do your bug fixes in there, and update it when there are new commits.

We haven't documented a lot of the changes we have done, but you can find a little information about the new module system here: http://www.pluck-cms.org/docs/dev:hooks

We are planing on expanding the module system with an universal way of selecting which part of a module you want to include. So if you do that, we will likely accept it.

There is a branch with a module that does that here: https://code.launchpad.net/~habagfx/plu … -core-mods. It is outdated, but we want to be able to support it in pluck in the future. We mainly need to add some more hooks to the main branch.

Sander but to avoid confusion just call me San smile

Damn... Calling all developers with the name Anders. I'm outnumbered... big_smile

Work smart, not hard

Kan du læse det her?