How do you become a MP developer (2 Viewers)

[alc_aardvark]

I have downloaded the source code and run the NUnit tests of which many fail. I have made a number of fixes, but I cannot check in the changes as it requires a usercode / apssword other than the one to log on here.

How do I become a MP developer, as I would like to contibute?

 

[infinite.loop]

you can add your patches directly on the :: SF project page ::

generaly speaking, if someone shows efforts, teamplay and good coding over some time, then he gets invited into the development team.

 

[alc_aardvark]

Thanks

Thanks for the details on submitting patches. I have submitted my first patches (#1883867 nUnit Test fixes). Can you let me know what I can expect to happen next?

Regards.

 

[ziphnor]

Thanks for the details on submitting patches. I have submitted my first patches (#1883867 nUnit Test fixes). Can you let me know what I can expect to happen next?

Its usually a good idea to find a developer who regularly works on the code to which you patch applies, and talk to him/her about the changes. This can be accomplished by for example visiting the mediaportal irc channel.

 

[alc_aardvark]

patch list

Looking at the open patch list, there are 67 open patches with only a handful assigned to developers. Some of them date back to June last year. Shouldn't they be evulated and allocated to a developer or moved to "wont be used" Q (with a reason). There appears to be lots of good work there going to waste, and I am sure a lot of the people trying to add value would do more if they were seeing that their work was being integrated into the base product.

 

[infinite.loop]

Looking at the open patch list, there are 67 open patches with only a handful assigned to developers. Some of them date back to June last year. Shouldn't they be evulated and allocated to a developer or moved to "wont be used" Q (with a reason). There appears to be lots of good work there going to waste, and I am sure a lot of the people trying to add value would do more if they were seeing that their work was being integrated into the base product.

short answer, yes they should.
but patches which actualy make sense and were not created with outdated sources or just incomplete, get added fast.

note: i am not a developer, so i can just try to encourage them to dare to use the "reject" option more often and describe why.

 

[ziphnor]

My guess is that most of those patches have not been integrated because the submitter of the patch haven't talked to the relevant developers. The chances of messing something up by integrating a patch without discussing it with the patch author and/or without having an overview of the code that the patch applies to is very big (I made that mistake not too long ago . As an aside, most patches also lack the necessary description/documentation.

But i do agree that it can be a bit troublesome to find the right developer to talk to, ideally of course, the patch submissions would be given a tag and the developers subscribing to that tag would then be notified.

 

[rtv]

Looking at the open patch list, there are 67 open patches with only a handful assigned to developers.

Don't worry. Every patch gets attention. If it's useful it will be integrated quite fast.

For most "old" patches there at least one of the following reasons apply:
- breaking other parts / plugin compatibility (for minimal benefit)
- not suitable for the majority of users
- not well thought through
- outdated and noone responding anymore
- etc

Nevertheless they are not removed so users might still try them / bring them up to date or similar.
Quite often changes are too big in periods of feature freeze but devs are reconsidering ideas / fixes later.

 

[alc_aardvark]

great replies

Thanks everyone for your fast and frank replies. This gives me confidence to push forward and spend some time learning about the project. I can see that learning about the team is just as important as learning the code .

 

[James]

One big problem with the patch system on SF. Is that it doesn't send emails when new things are added.

I'm very happy to see someone taking an interest in the unit tests

These need a lot of work. We had a push and wrote what was there now, but they have not been worked on in a long time

[EDIT] alc_aardvark, I really recommend you coming into IRC to chat with developers.

Is there an area you are really interested in working on?