contribute?

[Angel]

Hi lostnihilist (and everyone who uses rssdler),

I like rssdler but think it could be easier to use and more stable.

I have a couple patches of my own and can easily fix most of the open
defects listed on the 'issues' page in a day or two. Since you are too
busy to add features, make bugfixes, and put out new releases, do you
think me and/or maybe some other folks can be added as contributors?

I am going to fix up my local version of rssdler anyway, so why not
let everyone benefit?


Thank you,
angel.one<at>gmail dot com

[bde...@gmail.com]

I tried to contact lostnihilist individually a while back about being
added as a contributor but I received no response. I think that a fork
of the project might be a good idea since we won't be able to
contribute to this repository without being able to speak with
lostnihilist. I too have worked on fixing up some problems on my local
version and would like to clean up the code/contribute to make this a
better project. Thoughts on forking?

bd

[Graham Dunn]

Well, technically, by maintaining a seperate repository, you've already forked :) Just make it public... if lostnihilist wants to track your changes, he(she?) can.

You may want to call it something else though, to avoid confusion.

[lostnihilist]

Oh, wow. Sorry guys. I've messed up big time here. I thought I had setup this email account to forward to another one but appear to have screwed something up. I've confirmed that it is working now. Further communication should not be a problem.

I'm open to giving people write access to the repository so that the project can be further developed. The code is, without a doubt, a mess and could use some serious cleaning up. (Hey, it was the first significant program I wrote.) If anyone wants to have a discussion of how that should be undertaken, I have some old notes on what should probably be done to refactor the code and make modification and extensions more simple to add.

I'll see if I can recover the old emails. But new ones coming in will probably receive priority. So, if you can resend patches or update ideas, that is probably the best route. I'm not too sure how to decide who should get write access to the repository. Probably submitting X number of patches or some similar metric would be a good method. I'm open to other decision methods though.

Again, sorry that I've let this languish. I didn't think the project had any activity. Someone just let me know on an IRC channel that this discussion had taken place.
--
lostnihilist

[bde...@gmail.com]

I'm glad to hear from you! I was about to sit down and open up a new project to fork this. I was delaying trying to come up with a good name (which I suck at and rssdler describes the project really well). I look forward to seeing patches and fixes making it into this project soon now.

bd

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rssdler" group.
To post to this group, send email to rss...@googlegroups.com
To unsubscribe from this group, send email to rssdler+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/rssdler?hl=en
-~----------~----~----~----~------~----~------~--~---

[lostnihilist]

If you haven't noticed, a number of bugs listed in the issues as well as the
group emails have been fixed. Besides some comments in the tickets, I haven't
found any patches from people. So, if you have some patches, please send them
in again. Testing the recent svn would also be helpful. If I don't get any bug
reports or patches in the next week or so, I'm going to make another (point)
release. Note that not all issues have been fixed, and I'm not too sure how to
handle all of them. If you have suggestions or patches for a specific issue
listed, definitely send that in please!

Clearly, I'm not actively developing this; so, if you want to carry the
project forward, please drop me an email and we can discuss giving you project
write permissions.

Also, the DVCS Mercurial is now available on Google Code. Does anyone have a
preference for that over svn? I haven't bothered learning it, but wouldn't
mind migrating the code over. If this were to be done, I'd probably do some
heavy code formatting changes to make it more readable (e.g. standardize on 4
space indent).

Thank you for your help.

-- lostnihilist