Re: [Banshee-List] Commits list / Code reviews / Community

["Kevin Kubasik" <kevin kubasik net>]

Well, speaking as someone who went through the 'learning banshee for
some small features' the hard way, I can say that some cursory
document comments would go a long way. Even more helpful would be the
mentioned diagrams of descriptions. Overall though, there are worse
projects to try and start with, Mono makes things much easier to read
IMHO, and the irc is usually quite helpful if you ask for it.

I have to ask, I know its super-difficult to do, but will the
refactoring and rewrite currently going down allow for crossfading
support any better? Rhythmbox has a implementation which is pretty
good (all C) if theres any uncertainty to how it has to happen, just
wondering.

Cheers,
Kevin Kubasik
2008/1/18 Ruben Vermeersch <ruben savanne be>:
> Probably the most useful thing for a newcomer (and not only newcomers),
> is a diagram that explains how everything works together. It's nice to
> be able to find everything, but on the other hand, grep can tell me that
> as well. Seeing the big picture, how things interact and what are the
> things that matter the most, that's what grep can't tell you.
>
> That being said, banshee is extremely clean compared to other projects,
> which is one of the main reasons why I ended up here. I can't wait to
> dive back in. Two more weeks left!
>
>
> On Fri, 2008-01-18 at 14:08 -0700, Aaron Bockover wrote:
> > Andrew,
> >
> > Regarding finding stuff in the source tree, one of my goals is to create
> > a more detailed diagram, down the the directory level at least,
> > explaining what goes where, how to find things, etc.
> >
> > As we are still re-organizing a lot of code though, this is something I
> > haven't wanted to really do yet. Unfortunately, large source trees are
> > inherently hard to dive in for newcomers. As we work towards a release
> > from trunk though, expect some better developer documentation to come.
> >
> > If you have any questions about development against trunk, please don't
> > hesitate to ask! As it seems to stand today, myself, Gabriel, and Scott
> > Peterson seem to be the most familiar with the structure of trunk.
> >
> > Best,
> > Aaron
> >
> >
> > On Fri, 2008-01-18 at 15:52 -0500, Andrew Conkling wrote:
> > > On Jan 18, 2008 3:04 PM, Gabriel Burt <gabriel burt gmail com> wrote:
> > >         If you want to read more on good free software community
> > >         practices, I
> > >         suggest Karl Fogel's "Producing OSS" [2].  We are looking to
> > >         implement
> > >         many of these ideas.  Any concrete complaints and suggestions
> > >         for
> > >         improving our community are more than welcome.
> > >
> > >         [2] available free at http://producingoss.com/
> > >
> > > Sounds like a good book.
> > >
> > > With Banshee, I know that my desire to contribute is utterly and
> > > completely hindered by not being able to find my way around the source
> > > tree. The recent diagram added to the Roadmap helps, but it's still
> > > hard to find bite-size ways to help.
> > >
> > > Realistically, I'll probably find my niche in working on plugins, but
> > > the lack of documentation has made it daunting to discover what's
> > > available to be done. Maybe I could help write some--sounds like a fun
> > > idea now that I'm thinking about it--but I'd have to figure it all out
> > > myself. :P
> > >
> > > Man, I must sound like such a whiner!
> > >
> > > Cheers,
> > > Andrew
> > >
> > > _______________________________________________
> > > Banshee-list mailing list
> > > Banshee-list gnome org
> > > http://mail.gnome.org/mailman/listinfo/banshee-list
> >
> > _______________________________________________
> > Banshee-list mailing list
> > Banshee-list gnome org
> > http://mail.gnome.org/mailman/listinfo/banshee-list
>
>
>
> --
> Ruben Vermeersch (rubenv)
> http://www.savanne.be
>
> _______________________________________________
> Banshee-list mailing list
> Banshee-list gnome org
> http://mail.gnome.org/mailman/listinfo/banshee-list
>
>



-- 
Cheers,
Kevin Kubasik
http://kubasik.net/blog