Contributing to CFEclipse, and why YOU should do it
Posted At : November 3, 2006 10:46 AM
| Posted By : Mark Drew
Related Categories:
rant,
cfeclipse
<rant>
There are many times that I go through the bugs and enhancement requests for CFEclipse and I feel rather despondent. Why is this you ask? Well, the main reason is that CFEclipse has the wrong market, that is, its a tool written in Java that is used by a community that (on the whole) doesn't have a lot of Java experience (I know, I know, there are many wise people out there that DO have experience, I am just talking overall). This means that there aren't many people that can help with developing the tool.
Every so often I get a cornucopia of requests to fix something or that there is an error that is stopping them doing x or y. Most of the time I am willing to go and fix it as soon as possible, but stop for a minute and thing about something, there is currently only ONE person that is working on CFEclipse code currently, and that is in their spare time (which could be spent with a significant other be it a person or a playstation).
The reason I work on CFEclipse is that I like to add features that *I* need. That is how I got involved in the project. I asked Spike a while back in 2004 if he could add F1 help when you were in a tag or function, and he said "If you want it, do it yourself". So I got tucked in, asked lots of questions, looked through the source, asked more questions, read Articles at Eclipse.org, did searches in the Eclipse Wiki and even bought some books to help me along.
Since then I have got to know more of the code, added more features, fixed bugs for people and talked about it to people and hoped people would get on board. But sometimes I think this has backfired, as people now expect to receive new versions, fixes etc as if I was a commercial supplier. I am not. Its an open source project so you CAN contribute. You can look at the source (I know that wont help to start with) but if you are running Eclipse you can even create a number of Plug-ins yourself (File -> New -> Project -> Plug-in Development -> Plug-in Project, then there are wizards for different types of project) and understand parts of the code structure for different features and extensions.
The reason for this post is when I asked for testimonials a few days back for the new website (which I thank Andy Allan for helping me out doing) I was was a bit disconcerted to get a very harsh comment back, with the words "Shame on all of you for releasing such crap software!". Well, if the software is crap, tell me where its crap, help me make it not crap. If you have no interest in this, then don't use it. I apreciate critisim to a point, especially if it is constructive but it felt exactly like when a client says to you "The website doesn't work.", err... which part?, "I dunno, it just doesn't".
Previous contributors to CFEclipse have left for reasons of their own (usually that they aren't coding ColdFusion anymore) but I need this tool for my work and hence I work with it and contribute to it. If you don't think that is a valid option, then go and buy another editor, or failing that, use notepad.
I am not saying that you shouldn't let me know if anything is wrong, but at least have some common courtesy in the way you do it.
</rant>
I wish right now that I knew Java, unfortunately I don't. I would be happy to help in any way I can, but frankly I don't know whether there is anything in my skill set that would be useful. I've offered to help with Fusebox aspects (specifically since while plugging in the Fusebox and Circuit DTD's) work well, there is no way to do that with the fusedocs dtd that I have found. If I can do anything, I am more than willing.
Grr.
Don't worry about just one rude comment. I enjoy using your cfeclipse. It's a great open-source software!
I still find it odd that Adobe continues to 'ignore' CFEclipse. I don't know if it's just me but it seems like with a small drop of the $100 million they are flashing around for Flex development or whatever - they could support CFEclipse, bundle it with FlexBuilder and everyone could be happy.
@Brad: Great to hear it! Thanks!
@Jim: Adobe arent ignoring, quite the opposite, they have been involved in getting 1.3 working on Eclipse 3.1. They released the Coldfusion tools for Eclipse which are designed to work with CFEclipse and in the labs site (dont know where) had instructions to use CFEclipse. So they are pretty much behind the project and give it acknowledgement. I dont know how much you want Adobe themeselves to do... Bundling with FlexBuilder would be a definate possibility... will have a chat with them and see if we can do it by the next version.
@Kevin: well... I dont want paying per-se, but maybe "oportunities" to go to conferences and talk about it would help, hey... the USA is pretty far away (commercially speaking) even with the exchange rate!
@Matt: I am going to do a post about how the dictionaries work and the process that everyone can do to fix stuff, that is the easiest thing really and will contribute a lot... will let you know when we have got some of the website going (doing design and html at the mo)
Adobe, hire this guy! :)
I like the idea of a "Job Posting" section - it'd be nice to break that down into skill level and time. That would enable people like me to look and find things that would fit in my schedule and skill level (both are usually 0) :)
Jim
oh, and cfeclipse is great too...
Can't help with the java stuff, but let me know if you need a hand with documnentation, etc
I'm with the ton of others who don't know java, but love your work. I'm also short on time. However, I have saved time using CFEclipse. My skill set is perceived by employers to be higher because I know how to use CFEclilpse. That is worth some cash. A CD off your wishlist does not do just to what you deserve. Set up a Paypal account and I'll donate there. Or post your address and I'll mail you a check (assuming you can cash a check from a US Bank). I may not be able to afford what I really think CFE is worth, but maybe I'll get a payment plan going.
<evangelical preacher tone>
CFEclipse users unite. Let's do more than pat Mark on the back and say, "Atta-boy". Dig into those pockets. Five or ten bucks times even half of the users of CFEclipse would surely help Mark feel, not just hear, our appreciation.
</evangelical preacher tone>
Does the community feel that CFEclipse *should* become an 'official' Adobe project? I see suggestions here of Adobe paying Mark to work on it or bundling it with Flex Builder etc.
And Mark - Since you are the lead developer (or perhaps more aptly the sole developer), what would you think of Adobe taking a more active fiscal role and adopting CFEclipse as a project that it supports?
Not that anything would come of this ... but it would be interesting to find out what the community thinks, what those intimate with the project thinks, and what Adobe personnel thinks about an Adobe promoted project.
It would be nice to know what the original developers thoughts were - I could possible see during the initial development they would want to keep Macromedia/Adobe out of the picture so they could develop exactly what they wanted - but now it seems the project has reached the 'growing pains' point where there are a lot of people with great ideas, along with users demanding features - but limited resources to implement them.
In regards to 'bundling' it with Flexbuilder - I'd rather see it remain standalone - either as a free or paid product - I do like the flexibility of the Eclipse plugins!
Right now I think I'd give priority to the 'Job Posting' list so people can start helping out where possible. :)
With regard to sponsorship, well, that is a tricky question. How would a project like ours remain impartial? We want to provide an IDE for all ColdFusion versions (Railo, Adobe, New Atlanta etc) to help any CFML (the language) developer.
Hence the impartiality... but the problem has been lack of new blood, maybe my fault or whatever I dont know... so at the moment I am kind of happy (ITS MINE! YOU HEAR? ALL MINE! MWAHAHAH) but also kind of frustrated (New features vs Bug Fixes).
With regards to cold hard cash. What would it be used for? Well, currently, if I am honest, I would like to be able to go and represent CFEclipse at the conferences, I like showing people the product, converting people and getting feedback on new features etc.
In case anyone hasnt spotted it yet, the conferences are in the US of A. I am in the UK so its expensive. So, currently I am saving up to see if I can make an appearance at cf.objective and CFunited next year.
Just to set the record straight (and I am sure I have mentioned and blogged about it before), Adobe does contribute to the project, and I do talk about stuff to people on the CF Dev team, nothing to do with new features but ways of making sure we are compatible with each other.
Hopefully the new site will show CFEclipse in a better light, and provide "jobs" for things we want to accomplish.
There are some tasks that people can take on, and if anyone tried to make a plugin (as described in my blog post) they could turn their hand to figuring stuff like update sites (which at the moment is a PITA for me), Ant tasks, ways of doing unit tests etc. You are all clever people, suggestions are always welcome.
(I am much more relaxed now after some Single Barreled Jack Daniels, so annoyed comments about CF now wash over me)
I'm a motorcyclist and every year on one of our mailing lists we sponsor an "over the pond" trip where everyone chips in and we send two people 'over the pond' one from the US (to Europe) and one from Europe (to the US). They come over for a week and ride bikes :) Everyone on the mailing list chips in a buck or two and that more than covers airfare and hotel, etc... Seems like we could do something similar here. Maybe we can get you to Kentucky to the JD factory :)
But I shall put up a "Donate" button, I didnt know if the community would classify this under "Cheeky Bastard" or "Fair Enough"
CFEclipse *should* become an 'official' Adobe project? I see suggestions here of Adobe paying Mark to work on it or bundling it with Flex Builder
I wouldn't want CFE to become an offical Adobe product in the way CF or Photoshop is. Paying Mark to work on it, or donating some dev. time to it is not the same as endorsing it (AOL don't endorse Firefox, last time I looked).
I would love to see it optionaly bundeled as a freebie with FlexBuilder, but it should also be availdible by itself, free is possible.
IDE. Now that Flex is out and special routines have been developed for CF
programers it seems 'reasonable' for Adobe to make CFEclipse the programers
IDE. I would welcome Adobe's involement in the developement of CFEclipse.
I sent a message via "Ask Mark" a few weeks back asking for thoughts and suggestions about where to start contributing. Never heard back. Sure, I know, you're busy. We're all busy. :-)
Anyway, as I mentioned in my "Ask Mark" post, I'll have to dust off my (mad) Java skillz, but I've been using the product exclusively for over a year now, I recently bought a new Mac and I had decided it was time to start contributing to a product I used daily.
If you can dig out that post and find some time to point me in the right direction, I'd like to get involved to whatever degree I'm capable.
Just wanted to remind you that some of us really are willing (and occasionally able) to help out, but it does seem a bit overwhelming and, speaking for myself, I'm a little hesitant to take even more of your time to get me ramped up and provide the guidance I'm sure to need when taking it all in.
In the meantime, CFEclipse is a fantastic product with no more or less deficiencies than most other products out there. Ignore the asshats who chose to focus on the deficiencies. There are an awful lot of us who manage to use the product quite effectively on a daily basis.
Rob
@Tom: I dont see why Adobe couldnt bundle CFEclipse with Flex Builder, the only reason I could think it would be a negative thing is that people would be asking Adobe for support for CFEclipse and I am sure they dont want that!
So anyway, I'm looking for some guidance on small bugs that should be pretty simple which you just haven't had time to get to. By starting small, I'm hoping to learn my way around the code and refresh my Java at the same time.
Are there any bugs that are bugging you? head over to http://trac.cfelcipse.org and have a look and see if any of the bugs affect you and you would be interested in fixing them (look for the RC1 bugs specifically! as I want to get that out of the door ASAP)
Hope you are still up for being involved!
I'll consider this my invitation Mark. =)
The http://trac.cfeclipse.org repository is a good place to check out what bugs are current and what needs fixing.
MD