Duplicate functionality

The project description basically explains this, please read it. Thanks! :)

@rcross, thanks for taking the time to write this! :) I guess a proper explanation is in order:

For the past 2 years I've worked at Webdrop (a brazilian Drupal shop that I co-founded) and a couple of our clients asked for job portals. Being good Drupalers, we developed a semi-generic Job Portal system in Drupal 6 and used it for those jobs.

The reason for using Drupal 6 was that the first project was developed 1 year and a half ago and a lot of important Drupal 7 contribs just weren't ready yet so we opted for the more stable version.

About a year ago we decided to re-write the system from scratch using Drupal 7, entities, etc and we've been doing so in a private Beanstalk repository. Not just myself but a couple other guys at the company too. We soon discovered Recrutier and I contacted each maintainer of the Recruiter distribution individually, explained where I was coming from and what I was doing and asked whether they wanted to join forces, etc. Most didn't respond and I got a couple generic "sure if you want to help check out the issue queue" replies.

No hard feelings, but I obviously wasn't taken very seriously. Add to that the fact that our objective is similar in the most part but has some significant differences in the way we are approaching it: We have a job application system, job recommendations, subscriptions, hotsite mode and very nice dashboards and reports. Being open-source, we've been watching the Recruiter project and borrowing good ideas as we go along, so whereas this isn't technically a fork of Recruiter, we have no shame in seeing what they do well and adapting it to out project if relevant.

I've had a lot of questions regarding the Recruiter distribution and basically I've come up with a good answer:

How many e-commerce modules/distros are there for Drupal 7? Commerce and Ubercart that I can think of off the top of my head. What about WYSIWYGs? A handful. (including multiple ckeditor implementations) What about notification modules, etc.

Basically, the great thing about open-source is that we're not confined to a single option for a given task. Thank God we have tons of choices for implementations of a specific feature or functionality and we can choose the one that works best for our particular needs.

Therefore, whereas I don't by any means discard collaborating with the Recruiter team and maybe down the road even merging projects (who knows what could happen!). For the time being, I think developing Drop Jobs independently is an honorable pursuit and I've had some positive feedback and interest from the community that has helped things move along. Some of my Webdrop friends have also chipped in and are contributing and I am confident that we're creating a great product!

Sorry for the long answer but I hope this answers your questions! :)

I agree with Alex,
Recruiter functions are limited and they have closed doors on application feature. even after 2 years development it is useless.
Recruiter cannot be compared with drop jobs. Drop jobs is complete solution for recruitment in many ways.
job application is not even in the scope of the recruiter project,the answer got from recruiter team is "Not in the scope", no hard feelings, they have their own scope strategy,plan and approach.
recruiter is not in usable state.after installing it you need to do lot more
even if all the modules are same or all the function are same ,or may be it is just a copy, but the scope is much larger, and the usability is much wider.I do not take drop jobs as rival or competitor to recruiter, just drop jobs has increased recruiter's usability instead of fork.
Good work alex keep it up.

I'm about to look at Drop Jobs. I had success with eRecruiter. What is important about eRecruiter is that it powers the largest job board in Austria. It serves a particular use case and the developers have made it available. However, what is right for them and what they maintain might be very different from what other people need. It's nice that they made the code available. What code have they made available? Looking at two of the user accounts of the developers Fago and Drunken Monkey, eRecruiter is a driving force behind the Entity API, Rules, Search API, Field Collection, Field Group, and Profile2.

Yes, I agree with Adam the contributions by fago and drunken monkey are great.That's what I am saying,recruiter and Drop jobs cannot be compared.the purpose is different. and goals are different.The audience is different.

Hi Adam,

There's no question they are incredibly talented, core contributors and doing a great job. I don't dispute that at all and, in fact, I openly state that Drop Jobs borrows functionality from Recruiter.

The idea behind Drop Jobs is a lot more ample, it has more features and a nicer Admin UI but basically builds off of my experience developing these portals in Drupal 6 and the solid foundation that is Recruiter!

- Alex

Adam,

Here's another example of 2 newish "competing" distributions: CRM Core and RedHen CRM.

I'm one of the recruiter maintainers and Just learned about this project today. alexweber has contacted me per mail in January and of course I invited him to join the recruiter development effort in the issue queue. He responded that the issue queue is a bit slow for development and I did not react to that anymore and the email got a bit lost.

I'm a bit disappointed that alexweber did not even open an issue in the recruiter issue queue to discuss a fork or how to proceed. However, I can understand that we all have limited time and we are eager to develop things ourselves. So you can follow your vision here and we do our thing in recruiter. I'm looking forward to exchange code between our two projects as they mature and maybe we can even merge them later at some point in time.

@klausi, thanks for your input! I'll open an issue in recruiter now and we can take it from there! :)

the issue mentioned in #11 by alexweber is discussed in the Recruiter issue queue at #1672832: Collaboration with Drop Jobs

Closing this one as well.