On Mon, Jan 10, 2011 at 5:39 PM, Alexia Death <alexiadeath@xxxxxxxxx> wrote: > On Monday, January 10, 2011 19:17:51 Øyvind Kolås wrote: >> Code documentation is also one of the tasks that are not permitted for >> instance in the Google summer of code, perhaps we could come up with a >> set of bounties, or find someone motivated and fund them on a task by >> task basis or even part time for documenting? > > I think this is a frightfully good idea too. One of those tasks could be > writing the GIMP code Codex. Coding standards and best practices and so on. It > could give us much easyer to merge forks for example. Its extremely annoying > having to rewrite most of a great feature to make it fit for merge.... And > yes, I do remember my starting days trying to make sense of the GIMP on the > inside. Note that many of the documents/the start of the documentation described or desired do already exist but might not be appropriately pointed to, and it has already been created and contributed to without monetary reward. Lets hope use of rewards wouldnt scare off people from contributing such work for free. /pippin _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
