On Aug 7, 2010, at 7:50 PM, Mitar wrote: > Hi! > > So, what about this? You have a potential developer wanting to join in > and develop a new feature. Maybe even help with other stuff. But who > is afraid that if he even makes a patch it will stay in the ticket for > next 5 years. So I would like to discuss things in advance, so that if > I spend time working on that I would not do in vain. I would only like > to assume that if the code will be of good quality, will not break > anything, will adhere to coding principles, will do what we discuss it > should do, ...., that it will be added to codebase, preferably for or > even before 0.13. > > Maybe one answer to > http://trac.edgewall.org/wiki/SeaChange/WhatDevelopersWant how an > enthusiastic developer feels. > > My concrete proposals are: > > - make a settings option which would enable html5 doctype on all > current xhtml output > - if this settings option is in effect and (currently) the request is > coming from a known (configurable) browser which support html5 doctype > is changed > - if doctype is html5 attachment field is extended to support > drag&drop and multifile attachments > > I would also implement preprocess interface, where plugins could deny > attachment, preprocess it in some way, maybe even more "replace or not > replace" behavior to it, like I described in previous e-mails. > > Is this a valid proposal? Is it something Trac developers could agree > on that it would be useful to or at least that they would not mind it > be included in the core codebase for those of us who would find it > more then useful. > > So, you have one possible long-term contributor who really likes the > project and would like to join in the active development, but would > like some assurance that time and energy spend on the project would > not go in vain (of course I understand that you do not know me so it > is natural that those assurances would be conditioned by quality of my > results and similar). It just the feeling a person gets from the > tickets, that even if I will do my job properly it will collect dust.
Switching to HTML5 will require a lot more than simply changing the doctype. Genshi would need to support it for one, which I kind of doubt it does. However you are more than welcome to just fork the repos on github or bitbucket and start hacking. Show that the tests all pass and there are no security issues due to differing serialization rules and you will find more support. --Noah -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
