Show quoted text>> [...] Moving that
>> segment up in the file and titling it appropiately should help guide
>> newbies towards the documentation, with a lower chance of them
>> overlooking it and getting lost in the sco/metacpan chaos of file
>> listing; and as such reduce the amount of people asking confused
>> questions on IRC.
>
> IMHO splitting the "Where to get help" section into "Where to get help"
> and "Where is the source", and then arranging stuff like follows would
> be better?
>
> "Where to get help"
> "Where to go next"
> "Where is the source"
>
> This is just a suggestion, if you believe your arrangement is better I
> have no problems applying this.
While i'm very open to provide feedback and suggestions for splitting up
the where to get help section, i think there's a small misunderstanding
here. Yesterday i was being confused by relations in DBIC because i hadn't
found the appropiate thing to read yet, caused by me not seeing an obvious
starting point and thus resorting to grepping with metacpan and hoping for
the best. I'm sure many other newbies run into similar problems.
This change is meant to make it clear for someone who looks at DBIx::Class
on sco or metacpan exactly where they need to start reading to learn DBIC
and to do so in a way that has a minimum chance of people missing the
starting point, by putting it directly under NAME.
Thus, to provide more salient feedback on your exact question up there, i
think it should be ordered like this:
"Where to start?"
"Where to find user resources?"
"Where to find developer resources?"
That would intuitively be the progression someone goes through when using
DBIC: 1. learn, 2. deepen, 3. customize.
Do you agree?
If so i could look at DBIx/Class.pm again and make an additional commit
with the secondary split.
--
With regards,
Christian Walde