better documentation
k_and_j - September 15, 2007 - 20:23
| Project: | FooAggregator RSS aggregator. |
| Version: | 5.x-1.x-dev |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | alaa |
| Status: | active |
Jump to:
Description
What are you trying to achieve/have achieved over the other RSS aggregators (particularly the Aggregator and the Aggregation modules)?
#1
we don't have any goals or intention to compete, we simply have an immediate need for a flexible and efficient node aggregator module. used aggregator2 for a while, then feedparser then toyed with all the other modules. tried to provide patches to a couple and they where ignored for a long time.
if in the near future another node aggregator module becomes a defacto standard (in the sense that views and cck are) then we'll most probably switch to it and provide an upgrade/migration path.
I'm not going to try an convince you that fooaggregator is better than any other module. the main difference between it and other modules is probably the level of integration with views.
we're working on an external parser that should make it easier to parse thousands of feeds but that's going slow and there is no telling when it'll be ready.
#2
For me, I needed something that can work and scale unlike the core aggregator. The other problem is that the other modules are either unmaintained (why would I maintain something else and inherit the code and bugs ?) or will force me to use php5 or were not suitable.
I'm using drupal as my personal RSS aggregator.
The only promise I give is this code will be maintained until I find another good alternative. I'll then provide a migration path, give up this project and hopefully contribute to the other one.
#3
I guess I wasn't looking to be convinced, just trying to decide which aggregator is best for me without wasting time trying them all. Your documentation seems sparse, so a "Can do" and "Can't do" list would be nice. Also, a lot of people who are using drupal may not be experts on RSS or aggregators, so spelling this stuff out for them (us) would save a lot of frustration.
You've put a lot of effort into developing the module and maintaining it...you don't have to sell it, but it seems like a good idea to let the world know what you've done.
#4
you are absolutely right, I guess we where just worried about being judged for creating yet another aggregator module and add to the general confusion.
but we should write a proper Readme and good module description. thanx for making us notice.
#5
+1000 Se my other post. Help!