Re: [Fofredux-devel] project developer guide

[Andrew T. (nilspace) <nil...@us...>]

Looks great! I made editing changes (line wraps, spelling). Also you
specified that you cannot merge to a stable branch - yet there are
bugfixes. A bugfix may entail a 'merge', right?

Also, we probably want a section on dev practices within the project
itself. Architecture, function and variable naming conventions, etc.
How we suggest modifying/patching.  When/if we have a "plugin" arch,
how to write a plugin.

Thanks Kevin!

Andy
On 12/23/05, Kevin <ke...@dr...> wrote:
>
> I added a developer guide to the repository. (file: DEVELOPER_GUIDE)
>
> Most of this was gleemed from release guidelines / naming conventions
> used by other projects, and also general best practices found on the
> Internet.
>
> I still need to add a few things (like tags used for code reviews), but
> I think it covers the most common things we do day-to-day.
>
> Please review and comment.
>
> --Kevin
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Fofredux-devel mailing list
> Fof...@li...
> https://lists.sourceforge.net/lists/listinfo/fofredux-devel
>


--
Andrew Turner
ajt...@hi...        42.4266N x 83.4931W
http://highearthorbit.com              Northville, Michigan, USA